Cadence
B2B SaaS that turns weekly client updates into a five-minute ritual with read receipts.
Overview
Cadence is built on an uncomfortable truth of agency life: clients rarely leave over bad work — they leave over silence. It turns the weekly client update from a dreaded blank page into a five-minute structured ritual, delivers it as a designed Friday Digest, and closes the loop with read receipts.
The client never logs into anything. The digest lands in their inbox, reads in two minutes, and tells the agency it was opened.
The Challenge
Agencies lose clients to invisibility. Work happens all week, but if none of it is narrated, the client's experience is silence punctuated by invoices — hence the 'any update?' email, which always arrives precisely when trust has already begun to erode. Every existing fix (dashboards, portals, PM-tool guest access) fails the same way: it asks the client to do work. The product had to repair visibility while demanding effort from no one — five minutes from the agency, zero from the client.
Goals
- 01
Make composing a weekly update take five structured minutes, not a blank-page hour.
- 02
Deliver updates as an artifact clients actually read — designed, skimmable, no login.
- 03
Give agencies proof of the ritual: read receipts with open timestamps per client.
- 04
Build the cadence itself into the product — scheduling, streaks, and status make Friday automatic.
Research
The research sat in the agency-client relationship itself: post-mortems of churned retainers, the way account leads describe update-writing ('I put it off because it takes an hour to figure out what to say'), and the client side — what they actually want to know is narrow: what happened, what's next, is anything blocked.
That three-question shape meant the blank page was the real enemy. Structure the questions and the update writes itself; the composer is essentially a form that produces prose.
Strategy Thesis
“Anchor everything to one artifact — the Friday Digest — and make consuming it effortless.”
Instead of a portal clients won't visit, Cadence produces a single weekly artifact with a name, a schedule, and a design. The digest is the product; the app is just the pen. Its three-column composer mirrors the three questions clients actually have, so drafting is assembly rather than authorship.
Zero client effort is a hard rule: no accounts, no logins, no 'view in browser' hostage-taking. And because a ritual needs proof, read receipts close the loop — the agency doesn't wonder whether the silence-repair is working; it sees the open timestamps.
Design Process
- Step 01
Shape the composer around the client's three questions
Did-this-week / next-week / blockers became the composer's three columns. Account leads fill slots instead of drafting memos, and the output prose inherits a consistent editorial voice.
- Step 02
Design the digest like an email worth opening
The Friday Digest was designed as an artifact — typographic hierarchy, project status at a glance, two-minute read length — because the artifact's quality is what makes the ritual stick on both sides.
- Step 03
Close the loop with receipts
Per-client read receipts with open timestamps turn 'did they see it?' from anxiety into telemetry, and the SCHEDULED status makes the weekly rhythm visible inside the team.
Final Solution & Gallery
The live product runs the full loop: onboard, draft in the three-column composer, preview the digest as the client will read it, set it to SCHEDULED, and watch the read-receipt cards fill in as clients open.
Results & Metrics
The build's commitments to both sides of the relationship:
- the structured composer turns updates into a weekly ritual
- 5 min
- clients read everything with no account, ever
- 0 logins
- read receipts per client, per digest
- Timestamped
- the Friday Digest — the whole product converges on it
- 1 artifact
Key Takeaways
- 1
B2B retention problems are often communication-shaped; the fix is a ritual, not a feature list.
- 2
Products anchored to one named artifact are easier to adopt than products anchored to a workflow.
- 3
Asking zero effort of the second party is a viable — and rare — design constraint worth designing around.
Concept client, real build — every interaction shown is live in the linked product.