What working with us actually looks like.
Not a highlight reel. The shape of a real engagement, week by week, including the parts that go wrong.
Start to finish
Week 1 — Discovery.
We learn the business before the requirement. What decision is this meant to change? Who has to use it? What happens if it ships late? You get a written brief, user flows, a scope with explicit exclusions, and a firm cost. You own that document whether or not you continue with us. Occasionally discovery concludes you shouldn't build the thing, and we say so — it's the cheapest possible outcome for you and the most expensive for us, which is why it's worth trusting.
Weeks 2–3 — Foundations.
Environments, repositories in your name, CI, error monitoring and analytics. Instrumentation goes in before features, so the "is this working?" conversation has data behind it from the first release rather than the fourth month.
Fortnightly — Releases.
Every two weeks something you can open and use, on a staging environment, with a short note on what changed and what to look at. No six-month silences. Changing direction in week three is cheap and in week twenty is not, which is exactly why we release early and often.
Ongoing — Change.
Scope changes are quoted and approved in writing before the work happens. Not as bureaucracy — so that nobody discovers a disagreement at invoice time.
Launch.
A checklist, not an event: performance budget, error monitoring, rollback plan, support rota, a go/no-go call someone is willing to make.
Handover.
Documentation, a walkthrough, and credentials transferred. You should be able to take the work to another team. Most clients don't. The point is that they could.
What we do when it goes wrong
Every engagement has a bad week. What matters is what happens in it.
If we're going to miss a date, you hear it before the date passes, with a revised date and the actual reason. Not on the day.
If we estimated badly on fixed-price work, we absorb it. That's what fixed means.
If we shipped a defect, we fix it inside the 90-day warranty at no charge, and we tell you what let it through.
If the engagement isn't working, you can end it on 30 days' notice, pay for what's done, and take the work with you. That's in the contract, not just on this page.
What we ask of you
- Honest constraints — the real deadline and the real budget, not the negotiating ones
- One decision-maker who can say yes
- Feedback within the agreed window, because a fortnightly cycle only works if the fortnight is used
- Your own backups of anything you send us
- Early warning on compliance or data-residency requirements, because they change the architecture rather than a setting
Sectors we've worked in
The constraints change by sector. See the sixteen industries we work in →
Tell us what you're trying to build.
Send the requirement. You'll get a written response within one business day — scope, approach and an honest view on whether we're the right fit.