The ledger we needed. Partner relationships, deliverables and trust accrue in one place — the work and the receipts on the same surface. In active build; a working ledger runs today.
The ledger we needed. Partner relationships, deliverables and trust accrue in one place — the work and the receipts on the same surface. In active build; a working ledger runs today.
Partner relationships fall apart when the delivery and the trust live in different systems. Jobs, decisions, sign-offs and spend accrue in one ledger, so the record becomes a by-product of doing the work rather than an admin tax on top of it.
PartnerLedger puts the work and the receipts on the same surface. Jobs, decisions, sign-offs and spend accrue in one place, so the record is a by-product of doing the work rather than an admin tax bolted on afterwards.
The four captures below walk the same tenant from top to bottom: the daily home view with its social score and contribution index, the per-project job table with its state and signed columns, the repository-wide work map with its data-quality banner, and the knowledge base that will feed the assistant.
Everything shown is the demo tenant. The counts, states and labels quoted here are read straight off the screens.
A social score of 87, +3 this week, split into +14 good and −2 bad. Underneath it: 8 deliveries, 4 on-time, 2 beyond-call against 1 missed SLA and 1 reverted job. Thirty days of bars, accent for positive, red for a bad event.
The score is not a rating anybody typed in. It is assembled from the same events the work already generates — deliveries, on-time hits, missed SLAs, reverted jobs. The contribution index then breaks it down per partner as DU filed and DU delivered.
Seven jobs in Concierge. Five open, 153 DU spend this month, 3 decisions, 1 pending sign-off. The table columns are JOB ID, TITLE, STATE, REQUESTER, EXECUTOR, DEADLINE, DU, SIGNED — states running In progress, Delivered, Accepted, Clarifying, Open loops, Killed.
The SIGNED column is the whole argument in one strip: six ticks and one dash. Delivery and agreement sit on the same row, so nobody has to reconcile a delivery tracker against an approvals thread to find the one job nobody signed.
624 visible issues, 5 blocked, 102 missing specs, 320 missing state, 307 stale. Above them a Degraded banner: snapshot age 40 min, stale after 30, degraded after 120, 1 degraded repo, with the instruction to treat counts as incomplete.
Most dashboards report a number and stop. This one reports the number and the confidence in the number in the same frame. The five workstream districts are the shape of the work; the counters above are how much of it is actually described.
Sector: Partner operations · Role: Architecture · Design · Scope: Jobs · decisions · sign-offs
Designed, engineered & shipped by Roderic Andrews — Product Designer & Design Engineer
Everything on this page — the engineering, the design, the positioning — was built by one operator. That's the offer: a product designer who writes the code and wires the growth. No hand-offs, no telephone game, no agency margin.
Design · Engineering · Marketing · Intelligence · Video · Growth
I'll walk you through how it was built — live, with your questions.
Thirty minutes. The build, end to end. Replies same day.