Everything in writing
Scope, architecture decisions, change orders, and handover notes are written documents you keep. If it was only ever said on a call, it does not exist.
How we work
A process designed around the ways projects usually fail.
Software rarely goes wrong because someone wrote bad code. It goes wrong because nobody agreed what was being built, the client could not see progress, or the handover never happened. Each step below exists to close one of those gaps.
01
Discovery & scope 3 – 7 days
A working session to pull apart the problem, the users, and the constraints. You leave with a written scope document: what we are building, what we are explicitly not building, the architecture, the timeline, and a fixed price. This document is the contract — nothing gets built from a verbal brief.
02
Design & architecture 1 – 2 weeks
Interface design and technical architecture happen together. You review clickable prototypes before a line of production code is written, because changing a screen in Figma costs minutes and changing it in production costs days.
03
Build in two-week sprints Ongoing
Every two weeks you get a working, deployed build you can click through — not a status report. You have a shared channel with the engineers doing the work, and a live board showing exactly what is in progress.
04
Testing & launch 1 – 2 weeks
Automated tests, a staging environment that mirrors production, load testing where it matters, and a security pass. We handle the deployment, the DNS, the certificates, and the store submissions.
05
Handover & support 30 – 90 days
Source code in your repository, infrastructure in your cloud account, and written documentation your next developer can actually follow. Post-launch support is included, and a retainer is available — never required.
Principles
Six rules we do not bend.
Two-week cadence
A deployed, clickable build every fortnight. You judge progress by using the product, not by reading a percentage in a spreadsheet.
Direct to the engineers
You share a channel with the people writing your code. No account manager relaying questions and losing the detail on the way.
Least privilege by default
We work inside your cloud accounts with scoped, auditable roles. Access is granted for what a task needs and revoked at handover.
Tested before it ships
Automated tests, a staging environment mirroring production, and a security pass are part of the build, not an upsell.
Honest trade-offs
Every meaningful decision comes with what it costs you. Faster, cheaper, and more flexible rarely coexist, and we will not pretend otherwise.
Where the work lives
In your accounts, from the first commit.
We do not run projects out of a private environment and hand you a zip file at the end. Your organisation owns the repositories, the cloud accounts, and the design files throughout — which means at any point you could carry on without us.
| Communication | Shared Slack or Teams channel, plus a weekly written summary |
| Planning | Linear or Jira board you can see at any time |
| Design | Figma files shared with you from day one |
| Code | Your GitHub or GitLab organisation, with pull-request review |
| Infrastructure | Your AWS, Google Cloud, or Azure account, provisioned as code |
| Monitoring | Error tracking and uptime alerts wired up before launch |
Handover
What you own when we're done.
Delivered to you
- All source code in your repositories, with full commit history
- Infrastructure defined as code, running in your cloud account
- Written architecture and deployment documentation
- Environment variables and secrets transferred through a secure vault
- Design files, exported assets, and a component library
- A recorded walkthrough for whoever maintains it next
What happens to our access
- Our cloud and repository access is revoked at handover unless you retain us
- Client data in our systems is deleted on request per our Privacy Policy
- Confidentiality obligations continue after the engagement ends
- You keep a perpetual licence to any of our pre-existing tooling used in your build
Start with a discovery call.
Thirty minutes, no pitch deck. We will ask what you are trying to build, tell you honestly whether we are the right team, and follow up in writing either way.