Why we built SendBriefs around the brief, not the dashboard

The default answer#

If you survey the agency-reporting tooling category for 30 minutes, you notice every product has converged on the same structural answer: the dashboard is the deliverable.

AgencyAnalytics, Whatagraph, DashThis, Reportz, Databox — all of them frame the workflow as "configure a dashboard, share it with your client." Even tools that ship PDF export treat the PDF as a static photograph of the dashboard, not as a different artifact with different requirements.

This is a strange place to converge, because clients don't actually consume reports as dashboards. They consume them as briefs.

What the client actually does#

When a brief lands in a client's inbox, here is what they do:

1. Open it on their phone or laptop, depending on context
2. Scroll through the top half in about 90 seconds
3. Read the metric strip, see the deltas
4. Read whatever's in the headline narrative section
5. Maybe scroll into a section that surprised them
6. Forward it to one or two people on their team with a short note
7. Close the tab

The full read time for a well-written brief is 3–5 minutes. The client is not logging into a dashboard, navigating to a saved view, and exploring filters. They are reading a document, in the same way they read every other document that lands in their inbox.

The deliverable shape that maps to this behavior is a brief: narrative-led, mobile-friendly, forwardable as a single artifact, readable in one pass.

Why dashboards are the default anyway#

Three reasons the industry converged on dashboards despite the consumption mismatch:

1. They're easier to build. A dashboard is essentially a saved query + a chart library. The hard problem of "what does this number mean?" is dodged by showing the number and letting the reader decide.
2. They're easier to sell. "Beautiful real-time dashboards your clients can access anytime" is a pitch that resonates with the agency buyer — even though their clients rarely visit.
3. They feel modern. Dashboards = data-driven = sophisticated. Briefs = documents = 2008. The category has aesthetic biases.

These are real reasons, but they're not reasons grounded in what the client actually does with the artifact.

What changes when the brief is the product#

When you treat the brief as the deliverable, three product decisions follow:

• The editor is block-based, not chart-based. You compose narrative blocks and data blocks side by side, like a document, not a chart grid like a dashboard.
• Approvals are inline. Reviewers comment on specific paragraphs and metric tiles, not on entire dashboard tabs. The brief becomes a working document.
• Delivery is push, not pull. Briefs are sent to recipients via email + a hosted URL. Clients don't log into a tool; they open an email and read the artifact.

These three choices flow naturally from "the brief is the product." None of them follow naturally from "the dashboard is the product."

What this does not mean#

We're not anti-dashboard. Dashboards have legitimate uses:

• For your team: real-time operational visibility into what's happening in client work
• For specific client roles: the head of marketing analytics may genuinely want a saved view they can poke at
• For ad-hoc questions: "I want to slice this by region and time-of-day" is a dashboard question, not a brief question

What we are claiming is that the dashboard is not the artifact most agencies should be optimizing for in their reporting motion. The brief is.

The simpler test#

If you can answer "yes" to all three of these for your current reporting tool, your tool matches your workflow:

1. Does your client ever forward what you ship them, as-is, to someone else on their team?
2. Could a senior executive at the client read the artifact in 3 minutes and walk away with the right takeaway?
3. Could the same artifact serve as the canonical record in a retainer-renewal conversation six months later?

If you answered "no" to any of them, you're shipping the wrong shape.

---

More essays in the Friday Brief. Or reserve a Founders Circle seat — 25 agencies, lifetime founder pricing.