The canon

How every micro-SaaS gets run.

Six Posts. The functional fundamentals every solo SaaS founder converges on at $5K to $500K ARR. Read in order, or jump to what's bleeding.

  • customers

    Know who's paying, know what they're doing.

    Coming · May 11

  • support

    Hear what your customers are telling you.

    Coming · May 18

  • product

    Know what's shipping in your own software.

    Coming · May 25

  • communication

    Tell your customers what's happening.

    Coming · Jun 1

  • rhythm

    Actually run the thing every day.

    Coming · Jun 8
How to read this

Read in order, or jump to what's bleeding.

The Posts are sequenced by what most founders feel first. Revenue is the wedge — failed payments leak 5–10% of MRR every month, and the email layer that fixes it is the highest-leverage operational hour you can spend. Customers comes next: you can't fix what you can't see, and the customer graph is what surfaces silent churn before it cancels.

Support and Product run in parallel — Frankie sorts the inbox, Bug files the Issues, Inky writes the changelog. Communication is the customer-facing visibility layer: status pages, release-note emails, the visible artifacts that prove the company is alive. Rhythm is the operating cadence: Monday brief, daily digest, quarterly retrospective.

If something specific is bleeding right now, jump to the Post. If you're just trying to understand the operational layer for a $5K–$500K ARR SaaS, read Revenue first. Powered by Beer.