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 everyone else. The wall between the two is enforced structurally by the public-content scrubber, not by founder vigilance.
The pattern matters because it solves a tension every founder faces: public credibility wants real numbers; competitor hygiene wants concealed numbers. The compromise most 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 6 public surfaces.
Internal /dashboard. Lives at http://127.0.0.1:3100. Shows live MRR, customer count, gross margin, churn, individual customer LTV, performance by product line. Stripe MCP 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 methodology ebook. None of them quote internal numbers. They quote sticker prices ($99/mo for Starter, $47 ebook, $497 course) which are publicly stated commitments, not realized intake. They quote architecture facts (340 skills, 4 pillars, 11 P-gates) which are observable in the public skill catalog and the public docs.
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 pattern matters because it solves a tension every founder faces. Public credibility wants real numbers; competitor hygiene wants concealed numbers. The compromise most founders make — vague metrics like "thousands of users" or "top 10 in our category" — is worst of both worlds. 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 methodology 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 →