One piece of software, built small and shipped. The length depends on what you need; the scope says which, in writing, before anything starts.
Week by week
- Week 1 — the job, written down. What the software has to do, who uses it, and what “done” looks like. You agree the plan before we write code. If a spreadsheet or a setting would solve it, we’ll say so here.
- The middle weeks — build, show, adjust. Working software in your own accounts from early on, not a big reveal at the end. A short demo every week, so you can change course while it’s still cheap to.
- Throughout — tests and a repeatable deploy. Every change is checked automatically and goes out the same way every time, so shipping it again next year isn’t a guess.
- Final week — the handover. The code, a README the next developer can follow, and a walkthrough with your team.
If there is an AI feature in it, it is tested against real examples with known right answers before your team relies on it — see App development.
Things we have built
A booking engine for a rental business that never promises the same board twice (Wave and Wander), and a learning platform for paramedic training (RustyMedic).
What happens after
Keep going with another sprint, or retain us month to month. If the software needs somewhere solid to run, that’s a Cloud Foundation; if it handles anything sensitive, Incident Readiness makes sure there’s a plan for the bad day. Or walk away — it’s your code either way.
