The Problem
Agencies spend 2–4 hours writing a client report. Every month. Per client.
Not pulling the data — tools like AgencyAnalytics and DashThis already do that. The part that takes the time is the bit that comes after: turning numbers into sentences. Writing the narrative. Explaining what happened, why it matters, what they’re going to do about it. That part is still completely manual.
That’s 2–4 hours per client that isn’t spent on strategy, optimisation, or anything that actually moves the needle for that client. It’s skilled people doing manual work — copying numbers, formatting slides, writing summaries — instead of the value-adding work they were hired to do.
More clients means more of that. It doesn’t scale.
The Gap
Every reporting tool on the market automates data collection. None of them write the report for you.
That’s the gap. And it’s a real one — not a feature request, not a nice-to-have. For agencies doing this every month for 20, 30, 50 clients, it’s a meaningful chunk of their operations.
What We’re Building
Lenny.so connects to an agency’s marketing platforms per client — Google Analytics, Google Ads, Meta, Search Console. Data syncs nightly in the background. When it’s time to report, the AI writes a full narrative: what happened, why, what to do next. The agency reviews it, makes any edits, and sends it.
2–4 hours becomes 5 minutes.
On top of that: flat pricing. Unlimited clients on every plan. No per-client add-ons, no pricing that punishes you for growing.
What We’re Betting On
A few things have to be true for this to work:
-
The narrative quality has to be good enough to trust. Not perfect — agencies will still review and edit. But good enough that the edit is light, not a rewrite.
-
Agencies have to care enough about the time savings to pay for it. We think they do. Time spent on manual reporting is time not spent on the work that actually keeps clients.
-
Flat pricing is actually a differentiator, not just a feature. Per-client pricing is the norm. We think it’s a genuine pain point, not just a minor annoyance.
We’ll find out.
Where We Are
No code yet. The stack is decided, the architecture is planned, tickets are in Linear, repos are set up. This entry is being written before the first real commit lands in the product repo.
This build log exists to document what happens next — accurately, in the order it happens. If it goes well, maybe it becomes something. If it doesn’t, it’s still an honest record.
Either way, this is where it started.