Replace a bakery's paper notebook with an invoicing app
A developer had Claude Code interview him, plan and build a count, delivery and invoice app for his wife's four-cafe bakery in about 20 hours.
Done with Claude Code
What they did
The author's wife ran her bakery from one paper notebook of shelf counts and invoices. He used Claude Code with a skill pack that interviewed him one question at a time. It wrote the scope, plan and spec, which he approved. It then built the app in 8 small checked slices: count, deliver, branded invoice, and a ledger of who owes what.
How it went
He says the interview caught a server clock that would misdate evening invoices and a pricing link that would rewrite old invoices. Each slice ended with 'calls I made that you should check.' A hand-timed run still found a wrong assumption in the plan.
Worth knowing
Keeping decisions in plan files let him start fresh chats without losing context. Only real use caught the one wrong guess the plan carried to the end.
Try it yourself with Claude Code
I want an app for my [type of small business] to replace [current paper process]. Interview me one question at a time, then write a scope document, a screen-by-screen plan and a technical spec. Wait for my approval on each. Build it in small slices, and end each slice with a list of decisions you made that I should check. Store money in whole cents and dates in [your time zone]. Ask before deploying or sending any emails.
Swap the highlighted [parts] for your own details.
Source: DEV Community · Earl Grey · Oct 20, 2026
Written with AI assistance from the original post and checked against our editorial guidelines. Results are as reported by the source, not independently verified. Spotted a mistake? Tell us.
