The short version
A typical engagement runs in six steps: discovery, estimate, build in sprints, QA, release and support. For dedicated developers, discovery is a skills conversation and the build begins as soon as the developer starts. For a fixed-price project, it is a scoping exercise and a written estimate first. Either way, you work in your own tools, you see working software regularly, and you can scale down on notice.
The six steps
1. Discovery
We start by understanding the problem rather than the feature list. What are you trying to achieve, who uses the product, what exists already, and what constraints apply: budget, deadlines, compliance, integrations? For a project we will ask for existing designs, code or documents. For a developer engagement we ask what skills, seniority and working hours you need.
You get a straight answer on whether we are the right fit. If an off-the-shelf tool or a smaller first release would serve you better, we will say so.
2. Estimate
For a defined project, we break the work into screens, pages and APIs and price it using the published per-unit rates on /pricing. You see how the total is built. For a team engagement, the estimate is a monthly plan. Our rates are published, so what you read before the call is what we quote after it.
For dedicated developers, matched profiles within 2 business days, and developer starts within 5 to 7 business days of selection.
3. Build in sprints
Work is organised in short sprints, each ending with working software you can use, not a status report. Scope is agreed at the start of a sprint and reviewed at the end, so priorities can change without a renegotiation. We use your task tracker where you have one and set one up otherwise.
4. QA
Testing is part of each sprint, not a phase at the end. Features are checked against the agreed behaviour before they are shown to you, and larger releases get a regression pass. Where a project has automated tests, they run before code is merged.
5. Release
Releases are planned with you: what goes out, when and how to roll back. We prefer small, frequent releases to large ones, because they are easier to test and to undo. We deploy to your infrastructure or accounts where you want that.
6. Support
After release we can stay on for fixes and new work. You can keep a developer on a monthly plan, scale down with notice, or end the engagement. All code is delivered to you throughout, not only at the end.
Standard engagement terms
These are the terms for dedicated developers and staff augmentation. They are the same for every client.
| Term | What it means |
|---|---|
| Minimum commitment | 1 month |
| Scaling down | 2 weeks' notice to scale down or end |
| Trial | a 1-week paid trial to check skills and working style; if the fit isn't right, we replace the developer at no extra cost |
| Replacement | free replacement at any time, with a handover overlap so work doesn't stop, within 5 business days |
| Project management | a project manager at no extra cost when you have 2 or more developers |
| Working hours | at least 4 hours of overlap with your working day, with full overlap available on request |
| IP and NDA | all code and IP are assigned to you; we sign an NDA before kickoff |
| Billing | billed monthly in advance; invoices in USD, GBP, AUD, AED or INR |
| Tools | your tools and process: Slack, Teams, Jira, GitHub, daily stand-ups |
Details of how each model works are on the pages for staff augmentation and a dedicated development team. Ownership and confidentiality are covered in Security and NDA.
How we communicate
| Cadence | What happens |
|---|---|
| Daily | A stand-up with you or your lead, and ongoing chat in Slack or Teams |
| Per sprint | Planning at the start, a demo of working software at the end |
| Weekly | A short written update on progress, blockers and what is next, where you want one |
| On request | Calls with the engineers working on your product |
You have a named contact, and for teams of two or more developers, that is a project manager. If something is going wrong, you should hear it from us first. We would rather report a delay early than explain it late.
Code review and quality practices
These are practices we follow, not guarantees of outcomes.
- Pull requests. Changes are made on branches and merged through pull requests.
- Peer review. A second engineer reads the code before it is merged.
- Your repository. Work happens in your Git repository wherever possible, so you hold the history from day one.
- Version control discipline. Small commits with clear messages, so changes can be understood and reverted.
- Written decisions. Significant technical choices and their reasons are recorded, so the next developer does not have to guess.
- Handover. If a developer changes, the overlap period is used for a real handover, not a quick hello.
Tools
We work in whatever you already use. Typically that is Slack or Teams for chat, Jira or a similar tracker for tasks, GitHub for code, and the usual video call tools. We can set up a simple board and repository if you do not have them. Our own technical stack is on the technology page.
What we ask of you
Good engagements are two-sided. We ask for a person who can answer questions and make decisions within a day or so, access to the tools and documents the work depends on, and honest feedback at each demo. Delays in decisions are the most common reason a sprint slips, so we flag them early and keep a visible list of open questions.
When this model is not the right one
A dedicated developer is a poor fit when you need a one-off, tightly specified deliverable and have no one to direct the work: a fixed-price project suits that better. A fixed price is a poor fit when the scope is uncertain and will change weekly. A monthly team is better there. If you are unsure, describe the project and we will recommend one.
