Process
How a project actually moves, start to finish.
No black box where your project disappears for three weeks and reappears looking nothing like what you asked for. Here’s the actual sequence.
Scope, honestly.
1–3 days
We ask what you're trying to solve, not just what you think you want built. Sometimes those are different things, and it's cheaper to find that out in week one than month three.
- 30-minute call to understand the problem at a high level
- We ask about your current workflow — what works, what breaks, what's manual when it shouldn't be
- We identify risks and ambiguities before they become problems
- If we think you need something different from what you've described, we'll say so
A real estimate.
2–5 days
Timeline and cost, in writing, before anything starts. If the honest estimate is higher than you expected, we'll tell you why — not quietly pad it later.
- Detailed written proposal with fixed price and fixed timeline
- Scope clearly described — what's in, what's out
- Payment schedule outlined (typically 40% to start, 40% mid-project, 20% on delivery)
- No hourly billing surprises — you know the total before you commit
Build in visible stages.
Project timeline
You see progress regularly, not a single reveal at the end. Feedback happens while it's still cheap to change something.
- Work is broken into 1–2 week sprints
- You get a working preview link after each sprint, not just screenshots
- Weekly async update — what was done, what's next, anything that needs your input
- Feedback incorporated before moving to the next stage
Test before it matters.
1–2 weeks before launch
We test against the actual use cases, not just the happy path. The edge cases your business runs into every week — those get tested too.
- Staging environment that mirrors production
- User acceptance testing — you and your team use it before it goes live
- Performance testing under realistic load
- Cross-device and cross-browser testing for anything user-facing
Launch, then stay reachable.
Ongoing
We hand off documentation, not just a login. And we don't disappear the day after go-live.
- Deployment to your server or cloud — you own it entirely
- Admin and user documentation handed off at launch
- 30-day post-launch support included in every project
- Maintenance retainer available if you want ongoing support beyond that
Why trust a small team
Because the people scoping your project are the same people building it. There’s no relationship manager translating your concerns to a developer you’ll never meet, no junior team quietly inheriting the project once the senior person who pitched you moves on to the next deal.
We’re small enough that your project has a name to us, not a ticket number. That’s the actual structural reason response times stay fast and nothing falls through the cracks.
Response time to messages
Same day or next morning
Status updates
Weekly, without you having to ask
Access to your work-in-progress
Staging link after every sprint
Post-launch support (included)
30 days minimum
Who you talk to
The person building it
Process FAQ
Questions we get before projects start.
How long does a typical project take?
A 5–8 page marketing website typically takes 3–5 weeks. A client portal or booking system is 6–10 weeks. A full custom software build (CRM, inventory system, etc.) is usually 10–18 weeks. These ranges assume a responsive client — significant delays in feedback extend timelines.
What do I need to provide to start a project?
A clear description of the problem you're solving, access to any existing systems or data we need to integrate with, and a point of contact who can answer domain questions and give feedback during the build. We handle the rest.
How do you handle changes mid-project?
Small clarifications within the agreed scope are handled as part of the project. Material scope changes — new features, significant rework, new integrations — are scoped separately with a written change order showing the additional cost and time. Nothing changes without your approval.
What if I'm not happy with the work?
We build in review stages specifically to catch issues early. If something isn't right, we fix it — that's included. If the final delivery doesn't match the agreed scope, we make it right. We've never had a project end in dispute, and our preference is to resolve concerns the moment they arise, not after handoff.
Do you sign NDAs?
Yes. We're happy to sign a mutual NDA before any detailed discussion of your project. Our standard NDA is simple and balanced — we don't need our lawyers to review yours, and we don't expect you to need to review ours.
Who owns the code at the end?
You do, fully, upon final payment. You get the full codebase, access to all repositories, and complete ownership. We retain the right to list the project in our portfolio (anonymised if you prefer), but we have no claim to the work product itself.
Ready to start? We respond within one business day.
The first conversation is free, no-commitment, and you’ll leave knowing whether we’re the right team for what you need.