🦊 FoxyInvoice

Chapter 12 — Engagement & automation: UI first, then automate

"Engagement" conjures dark-pattern streaks and notification spam. It shouldn't. Engagement is the product working so well that leaving it half-finished feels like loss — progress the user doesn't want to abandon, moments of completion worth screenshotting, and gentle machines that act on the user's behalf. This chapter is the engagement surface we shipped, in the order it was built, under one governing rule: build the manual UI first; automate only flows that already proved themselves by hand.

The onboarding staircase (first five minutes)

A new signup lands on a three-step wizard: name your business + pick currency → add your first client → "you're ready" (with the founding- code hint for testers). Each step is one decision, skippable, and writes real data — so finishing onboarding is having a workspace. Then the dashboard's get-started checklist walks the rest: first invoice, first send, first payment link. The metric this staircase serves is the only one that matters early: time to first sent invoice. Everything that shortens it is engagement; everything that lengthens it is churn you built yourself.

Progress you can see (and don't want to lose)

Gentle machines: automation that acts for the user

Each of these automated after a manual version proved the flow — reminders were conceptually "send that email yourself," recurring was "clone that invoice monthly," quote-accept was "click Convert when they say yes." Automation amplified verified behavior instead of guessing at it.

What we deliberately did not build

The refuse-list from Chapter 02, enforced in practice: no time tracking, no expense ledger, no inventory, no notification inbox vying for attention. Also — no streak mechanics, no badges, no emails manufacturing re-engagement. The product's hook is the user's own unpaid invoice; we just make sure it's easy to finish and easy to chase.


Recap. Onboard to a finished-feeling workspace in three steps, never lose work, show honest usage, and let gentle machines — reminders, recurrence, quote acceptance — act on the user's behalf. Automate only what proved itself manually, and measure everything against time-to-first-sent-invoice.

Next: Chapter 13 — War stories: five postmortems and the lessons they paid for.