How we build, ship and keep things running.
Five steps, a fixed price agreed before anything starts, and no account layer between you and the engineer doing the work. Here is what happens between your brief and launch day.
Process
From brief to live, one loop at a time.
Brief
1 to 2 days. You send a few honest paragraphs covering what you’re building, who it’s for, and when you need it live. We reply with either a straight answer or a short list of questions, because the fastest way to an accurate quote is usually one more round of detail.
Discovery
3 to 5 days. We review your current site or systems, establish what a first version genuinely needs, and put a fixed price and a written plan in front of you before any development begins.
Build in loops
Most of the timeline. We ship in short weekly loops, which means you see working software early enough to redirect us before we are committed to the wrong direction.
Launch
A day, planned well ahead of time. We move in a controlled window, test as we go, and stay available for the first 48 hours afterwards, which is when unexpected problems normally surface.
Run and improve
Ongoing. Once you’re live we monitor how the site performs, repair what breaks, and keep delivering small improvements rather than waiting for the next expensive redesign.
Tooling
How we use modern tooling.
Research and first drafts
Competitor scans, technical options and a first pass at structure, so an engineer starts from something rather than a blank file.
Tests and code review
A first pass of tests written and obvious issues flagged, before a person reviews every change properly.
Log analysis
Logs and error reports scanned for patterns that would otherwise take hours of reading to notice.
AI tools do a share of that work. The engineer on your project decides what ships, reviews every change and takes responsibility for the outcome, so the tooling never gets the final say on what reaches your customers.
Not for us
A few things we turn down on purpose.
Guaranteed results. We won’t promise a Google ranking, a PageSpeed score or a conversion rate, because those depend on auctions, algorithms and competitors that nobody here controls.
Offshore handoffs. The person who scopes your project is the person who builds it, so your brief is never thrown over a wall to a different organisation halfway through delivery.
Big-bang launches. We would rather deliver something small and genuinely working than disappear for six months building in the dark before anybody outside the project has seen a single screen.
Communication
How you’ll hear from us.
You get direct access to the engineer doing the work, rather than an account manager relaying messages between you and a development team you never meet. We update you at the end of each build loop with working software you can open and click through, instead of a status report written in project jargon.
Most projects run over email and a shared chat channel, with a call whenever a decision genuinely needs a conversation rather than a paragraph. If you want more structure than that, we will establish whatever reporting rhythm suits your organisation.