How We Work

How we work

Most software projects go wrong the same way: the scope was never written down, so nobody can agree on what "done" means. We solve that by pricing discovery separately and refusing to quote a build before the specification exists.

1. Discovery & Scoping

1–2 weeks

Before we write a line of code, we get specific about what we're building and why. You get a written specification, user flows, wireframes, a technical architecture recommendation, and a fixed-price quote for the build.

This phase is paid, and it's credited in full against the project if you proceed within 60 days. If you decide not to proceed, the specification is yours to take to any developer — no strings.

2. Design

2–3 weeks

We design the interface before building it, so changes happen in a design file rather than in production code. You approve high-fidelity designs for every core screen and a clickable prototype before development starts.

3. Development

6–12 weeks, depending on scope

We build in two-week sprints. At the end of each one you get a working build to test and a short written update covering progress, decisions made, and anything that needs your input. You have access to the staging environment throughout — no black box.

4. Testing & Launch

2–3 weeks

Functional, cross-device, and cross-browser testing. Performance, accessibility, and security review. User acceptance testing with your team. Then production deployment, App Store and Google Play submission where relevant, and a handover session with full documentation and source code.

5. Support & Growth

Ongoing

Every build includes a post-launch warranty on defects. Beyond that, most clients move to a monthly retainer so there's always capacity reserved for fixes and improvements.

What you can count on

Fixed scope, fixed price. Discovery produces a written specification and a fixed quote. You're not exposed to an open-ended hourly meter.
You own everything. Source code, designs, accounts, and infrastructure transfer to you. No proprietary platform you can't leave.
Visible progress. A working build every two weeks and a written update every week.
No surprise invoices. Out-of-scope requests are estimated in writing and only start once you approve them.
Built to be maintained. Documented, tested, standard technologies — so another team could pick it up if they ever needed to.

What we ask from you

Projects run late for predictable reasons. These are the ones in your control:

One named decision-maker who can approve work
Feedback and approvals returned within 3–5 business days
Timely access to accounts, credentials, and brand assets
Content and data supplied in the agreed format by the agreed date

Book a free 30-minute call to talk through your project, or browse our services.