Building FoxyInvoice — Chapter 9: The daily cadence — twenty minutes that run the business
This series is written in the open, from a real production system. This chapter is the daily operating loop — the habit, not the feature, that actually runs the business. [All chapters and diagrams live in the public repo.] Products don't fail from missing features; they fail from absent operators. The antidote isn't more hours — it's a cadence : a small, fixed routine you can keep on your worst…
In this chapter, the focus is on the daily operating loop that drives the business, specifically the 20-minute routine that keeps the go-to-market running. This routine consists of four steps, each with a specific timeframe:
1. Triage (5 min): The feedback console, lead queue, and error console are checked for actionable items. Anything that can be addressed is assigned, while the rest is left unattended.
2. Hunt (10 min): Hacker News and Reddit are searched for mentions of the product. Relevant comments are prioritized, with strict phrase matching used to avoid noise.
3. Judgment (5 min): The radars score determines whether a genuine demand exists. If so, a reply is drafted and posted in the appropriate channel. All other cases are ignored.
4. Feed the machine (5 min): Recurring questions are turned into product improvements, such as FAQs, templates, UX fixes, or new chapters.
The entire process is designed to minimize human judgment and maximize machine automation. By focusing on the judgment step, the routine ensures that operators are only responding to genuine demand. This approach emphasizes the importance of operator habits over engagement mechanics for users. The final step involves tracking metrics like signups, invoices created, feedback count, and crawler hits to gauge the week's progress.
Written by urgent.news from Dev.to's reporting — not their text. Machine-written — may contain errors; check the original before relying on it.
This story
This is one outlet's version. Read the fullest account.
