Money and scope
Scope and timeline are agreed in writing before we start. Anything outside that scope is quoted before any work happens.
How we run a project
Scope agreed in writing, working software reviewed every week, and a handover into accounts you own.
Every week
- Working software, reviewedA demo on a real environment.
- A short written updateWhat shipped, what is next, what changed.
- Answers the same dayFrom the engineer doing the work.
Four phases, start to handover
The same four on every engagement, from a two-week sprint to a full build.
- Frame
The business outcome, the systems you already run, the constraints and what “done” means, agreed in writing.
- Design
Architecture, integrations, data model and scope, decided while changing them is still cheap.
- Ship
A demo on a real environment every week, with a short written update.
- Own
Repositories, infrastructure, documentation and a recorded walkthrough, all in your accounts.
Money, people and security
The people
A senior engineer leads the engagement, writes the code and stays on it after the sale.
Security and data
NDAs before any access. Named accounts, staging data wherever possible, and your data is never used to train anyone’s model.
Everything lands in your accounts
Our access is removed when you say so, and your team can run and extend the system without calling us.
- Repositories
- Infrastructure-as-code
- Documentation
- Runbooks
- Recorded walkthrough
Delivered intoYour repositories, cloud and accounts
Tell us what you’re building
We reply with questions or a time for a call, then send a written scope and quote.