Internal numbers and public surfaces are different audiences. This essay covers the /dashboard pattern — real numbers private to the founder and investors, sticker prices and architecture facts public to the rest of the world. The wall between the two is enforced structurally by the public-content scrubber, not by founder vigilance.
The pattern matters because it resolves a tension most founders face: public credibility wants real numbers; competitor hygiene wants concealed numbers. The compromise many founders make — vague metrics like "thousands of users" — is worst of both worlds. Read this for the cleaner answer.
The Daily AI Agents dashboard pattern separates internal numbers from the public surfaces.
Internal /dashboard. Lives at http://127.0.0.1:3100. The design goal is a single private view of live MRR, customer count, gross margin, churn, individual customer LTV, and performance by product line. A declared payment ledger feeds it; Paperclip renders it. The founder reads it daily; the agents query it programmatically when sizing decisions (an example threshold: when internal MRR drops below the configured floor, the ad-spend skill halts).
Public surfaces. The website pages, the founder letters, the ship log, the method paper. None of them quote internal numbers. They quote sticker prices — the publicly listed price of an offer, which is a stated commitment, not realized intake. And they quote architecture facts — how the system is structured, what gates exist — which are observable in the public documentation.
The wall between the two is enforced by the public-content scrubber from Chapter 4. The scrubber is the structural mechanism; the /dashboard pattern is the organizational discipline.
The tension deserves a second look because the usual escape hatch fails. Public credibility wants real numbers; competitor hygiene wants concealed numbers. Vague metrics like "thousands of users" or "top 10 in our category" concede both goals at once. The /dashboard pattern is a clean answer: show real numbers privately to the people who need them (yourself, investors under NDA, employees), publish architecture and method publicly.
A subtle Daily AI Agents benefit: the discipline also forces you to publish interesting things. If you can't talk about internal financials, you have to talk about how the system is built, what failed and why, what the method is. Those 3 topics produce better content than vanity metrics anyway.
Chapter 5 summary: Internal /dashboard shows real numbers (MRR, customer count, P&L); public surfaces show only sticker prices and architecture facts. The wall is enforced structurally by the scrubber. Forces public content to be about method, not metrics.
← Voice-gating and public-content scrubbing · full paper · Founder UX: sessions, delegation, deep-work →
AI is already answering for your business. We check whether it's right.
Discuss an engagement Examine a finding