Write the statement of work
We turn your brief into a short document listing what will be built, what is explicitly out, the systems it touches, and the tests that prove it is done. You sign that off before any engineer is assigned.
Hire developers · Engagement model
A contract engagement buys a defined outcome rather than open-ended capacity: an integration, a migration, a feature or an audit, written down with its acceptance tests before anyone starts. When the deliverable passes those tests and the handover notes are in your repository, the contract closes.
Scope and acceptance criteria written before work starts
Billing tied to milestones or a capped estimate
Ends with code, notes and a walkthrough in your hands
How it works
We turn your brief into a short document listing what will be built, what is explicitly out, the systems it touches, and the tests that prove it is done. You sign that off before any engineer is assigned.
One engineer, or a pair for larger pieces, is chosen for the specific stack and problem in the statement of work, and is given access only to the repositories and environments the task needs.
Work is cut into two to four checkpoints, each ending in something you can run or review: a branch with tests, a staging deployment, a migration dry run with its report.
If you want something the statement of work did not cover, it is written up with its effect on effort and dates, and you decide whether to add it, swap it for something else or leave it for later.
Your team runs the acceptance tests, we walk your engineers through the code and its operating notes, a short warranty window covers defects against the agreed scope, and the engagement ends.
Fit
Connecting a payment provider, moving a database to a managed service, building one reporting module or upgrading a framework version are tasks with a recognisable finish line.
A product group that rarely touches native mobile code, search tuning or infrastructure as code can bring in that expertise for the length of one task without adding a permanent seat.
Security reviews, performance investigations and architecture audits suit a contract because the output is a report and a set of prioritised fixes, not ongoing presence.
Finance teams that sign off projects rather than headcount often find a milestone plan with a capped estimate easier to approve than a monthly rate.
Responsibilities
You decide what goes into the statement of work and approve every change request; we are responsible for flagging gaps and risks in it before work begins.
How the contractor sequences the work, which tests they write and how they structure the code inside your conventions is our responsibility, not something you need to manage hour by hour.
Your nominated reviewer runs the acceptance tests and either signs off a milestone or lists what fails; nothing is treated as delivered until that sign-off.
Everything written under the contract is committed to your repositories and the rights pass to you as agreed in the contract, usually on payment of each milestone.
Releases to live environments follow your change process and are approved by your team, so a contractor never pushes to production on their own authority.
Terms
Agree whether you pay per accepted milestone, against a capped time-and-materials estimate, or a fixed fee, and what happens to the remaining budget if the work finishes early.
Agree who can raise a change, how quickly it is estimated, and whether approved changes extend the timeline, the budget or both.
Agree how long after acceptance defects against the original scope are fixed without charge, and how a defect is distinguished from a new request.
Agree when ownership of the code transfers, how any pre-existing libraries or tools brought by the contractor are licensed to you, and the confidentiality obligations on both sides.
In contract development the document written before coding matters as much as the code. A good one names the inputs, the outputs, the environments, the data and the tests. A weak one says build the checkout integration and leaves both sides to discover their disagreement at the acceptance meeting.
We spend real effort on that document because it protects you as much as us. It is the reference for every change request, every milestone review and every argument about whether something counts as a defect.
A demo shows the happy path on the day. Acceptance tests, written in advance and run by your reviewer, show that the edge cases agreed in the scope are handled: the refund that fails halfway, the migration that hits a duplicate key, the webhook that arrives twice. They also become regression tests your team keeps.
A contract that ends well leaves no dependency on the contractor. That means code in your repositories from the first day, secrets in your vault rather than a personal laptop, operating notes written for someone who was not in the room, and a recorded walkthrough your engineers can return to.
If any of those are missing at the end, the contract has created a support obligation you did not budget for. We treat the handover pack as a milestone with its own sign-off for that reason.
FAQ
The contractor raises it as soon as it is visible, with a written note of what was assumed, what is actually true and the options. You choose whether to rescope, pause or continue as planned; nothing changes silently.
Yes. If the first task goes well and more work appears, you can sign a further statement of work or move the same engineer onto an augmentation arrangement. Each is agreed separately.
It helps a great deal. Someone on your side who can read the code and run the acceptance tests makes sign-off meaningful and keeps the knowledge in your company after the contract ends.
Small enough to have a clear output. A focused code audit or a single third-party integration can be a contract; a vague request to improve performance usually needs a short discovery step first to define what done means.
Alternatives
If the need is ongoing capacity inside your sprints rather than one deliverable, embedding an engineer under your own lead is the better shape.
Open registerA full product with design, several platforms and a launch plan is a commissioned build, priced and run as a project.
Open registerWhen nobody can yet write the acceptance tests because the architecture is undecided, senior technical leadership should come first.
Open registerA guide to who owns planning, QA, continuity and handover under each model.
Open registerPrimary sources
Dated official documentation, standards, and research that support the factual claims on this page.
How employment status rules can apply to contractors engaged through companies in the UK.
Background on when commissioned work belongs to the commissioning party under US law.
How to read this page
Scope, cost and timeline figures are planning guidance until confirmed in a written proposal. Diagrams and screens are illustrations, not client deliverables, and source-code rights and handover follow the signed agreement. See the delivery process and the full disclaimer.
Next decision
Define outcomes, constraints, evidence, rights and handover before delivery begins.
Commercial rights, repositories, environments, documentation, acceptance and handover remain contract-defined.