Roderic Andrews — Case Study Roderic Andrews rodericandrews.com ↗
Case Study · Partner operations

PartnerLedger.

partner ledger · where the work lives

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.

Read the brief
01 · The BriefPL·CS

What it is, and the call that made it.

What it is partner ledger · where the work lives

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 unobvious call PartnerLedger in one move.

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.

02 · The Work3 views

Four screens. One ledger.

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.

Home dashboard showing a social score of 87, a good/bad event bar chart over the last 30 days, a contribution index with DU filed and DU delivered bars per partner, a pending-actions list and a recent-activity feed.
Home · social score + contribution indexPL·CS·01
PL·CS·01

The Standing Score

Trust is a running total, not an opinion.

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.

Use case "+ 14" good against "– 2" bad, on a score of 87.

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.

Project jobs view listing seven jobs with columns for job ID, title, state, requester, executor, deadline, DU and signed, above tiles for open jobs, DU spend, decisions and pending sign-offs.
Jobs · state, executor, DU, signedPL·CS·02
PL·CS·02

The Job Table

Every row carries its own receipt.

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.

Use case "PENDING SIGN-OFFS 1" — one row in seven still without a tick.

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.

Work Map screen with a data-quality banner, five counters for visible, blocked, missing specs, missing state and stale issues, repo and state filters, and an isometric map of project districts with five labelled workstreams.
Work Map · public snapshot + data qualityPL·CS·03
PL·CS·03

The Operating Map

The map tells you how much of itself to trust.

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.

Use case "MISSING SPECS 102" and "MISSING STATE 320" out of 624 visible.

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.

03 · The Delivery85 days

Built and shipped.

85 days DURATION
456 commits EFFORT

Sector: Partner operations · Role: Architecture · Design · Scope: Jobs · decisions · sign-offs

Designed, engineered & shipped by Roderic Andrews — Product Designer & Design Engineer

04 · The Pitchhire the operator

Hire the operator.

PartnerLedger is the evidence. Your product is the point.

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

Book the walkthrough.

Thirty minutes. The build, end to end.

I'll walk you through how it was built — live, with your questions.