Define, then build.
Customer flows, staff flows, the data model, brand kit, UI standards, architecture, the stack. All settled before a line of code.
Every shop says they plan first.
So the claim is worth nothing. Here is the list instead.
What that usually meansa scope doca deadlinea feature list
- Customer flowsevery path in, including the ones that go wrong
- Staff flowswhat each role does, in what order, on which screen
- Roles & permissionswho can see and change what
- The data modelwhat things exist, and how they relate
- Information architectureevery screen, and what lives on it
- Scopeand what is deliberately left out of it
- Brand kitcolor, type, logo, voice
- UI standardscomponents and states the whole product obeys
- Architecture & stackchosen for this business, not our favorite
Nine documents. Before anyone writes code.
Staff flows is the one almost nobody writes — and the one that decides whether a system gets used or quietly worked around. We write it because we've worked it: two restaurants owned, two platforms we run today.
Most projects lock the wrong layer.
They fix the scope and the deadline — the things in the contract — and let the data model emerge underneath while it's being built. We do it the other way round.
You can only move fast if the foundation doesn't.
Iterating on screens is quick. Iterating on the data model is a rebuild. Settling the bottom two takes us days rather than a six-week discovery, because we've run these businesses — we're not being taught yours from scratch.
Which is why a new feature isn't a change order here.
Build a better toothbrush and you'll get another toothbrush.
Ask how to clean a mouth instead, and you might end up with something better than a brush — worth more, and nobody else has one.
We're not trying to sell you a solution we already wanted to build. Most vendors are — they arrive with the thing they know how to make, and you end up shaped like their software.
What that looked like on a real project
“Put our booking form online.”You get a web form on a nicer site. The owner still writes every quote by hand, still sends a payment link to hold the date, still tracks who has paid what. The same job, with a login screen.
What actually is a catering booking?Not a form — an event with a before and an after. The date is held and priced against his real minimums, the deposit is taken, a prep sheet is generated for the kitchen, a reminder goes out three days ahead, and the guest gets their own portal to manage the booking and settle the balance. The thank-you and feedback request follow on their own. He stopped being the step in the middle of any of it.
Fitting into someone else's product used to be the sensible trade — custom was too expensive to be worth it. That stopped being true.
Almost anything is buildable now. The only question left is what should be.
What that looks like.
Same five phases, every project, every industry.
We sit down and map how the business actually runs — not how software wishes it ran. This is the phase that decides whether the rest of them work.
- Every workflow, written down: who does what, in what order, and where it breaks today
- The data model — what things exist, and how they relate
- Information architecture: every screen, and what lives on it
- A written spec you sign off on before anything gets built
Brand kit and design system first, so every screen after this is assembly rather than invention.
- Colors, type, logo, components — the whole kit
- Every screen wireframed against the spec
- You see the entire product before a line of code exists
Stack, schema, then code — against a spec that's already settled. This is the part AI makes fast, and it's only fast because the thinking is done.
- Database and migrations, versioned from day one
- Auth, payments, email, integrations
- A staging URL you can click, updated daily
Live, on your domain, with your team trained on it.
- Domain, SSL, deploys, monitoring
- Payments switched on and tested with real money
- SEO foundations — schema, sitemap, metadata, Google Business Profile
- Training, and documentation your staff will actually read
This is the half most shops skip. The monthly isn't rent on software you already paid for — it's ongoing support and a product roadmap we keep building with you. Businesses change; the system should change with them.
- A roadmap we set together and revisit as the business moves
- New features shipped as you need them, not when a vendor decides
- Ongoing SEO — content, listings, technical fixes
- Hosting, backups, monitoring, and someone to text when something breaks
- You own the code the whole time — the roadmap is a partnership, not a lock-in
You won't spend the first two weeks teaching us your business.
We've been the operator — the one paying for the software, chasing the deposit, and doing by hand the job the system was supposed to do. Define is recognition, not education, and that's the whole reason it takes days.
Week one starts with a conversation.
Thirty minutes. No pitch deck required.
“I've been building since the yellow pages mattered more than the internet.”Tony · Founder, LFG Ventures