05 / How we work
Make the next decision easier at every stage.
Scope, progress and responsibility stay visible at every stage. The specific terms belong in your proposal and agreement, and are settled before development begins.
- I
Discuss the milestone
Tell us where the product is now, what needs to change and who will use it. A short description is enough. Nate reviews fit, the key unknowns and the decision you need to make.
- II
Scope and propose
Where uncertainty is substantial, start with a paid scoping engagement. Define the deliverables, exclusions, dependencies, estimate and acceptance criteria for implementation.
- III
Agree the terms
Confirm the contracting identity, scope, payment milestones, source ownership and third-party licenses, review process and support responsibilities. Work begins under the agreed contract and initial-payment arrangements.
- IV
Review working software
Build toward a defined milestone, with demonstrations and written decisions. Changes are reviewed for their effect on scope, cost and timeline before they are included.
- V
Accept and hand over
Review the agreed acceptance evidence and complete the documentation, deployment and access handover specified in the scope. Existing clients use the separate private client workspace.
- VI
Plan what follows
Discuss support needs and the next release after the current milestone. Maintenance and new functionality have their own scope, capacity and commercial terms.
What needs to happen next?
A short brief is enough to begin. You do not need a finished specification.A short brief is enough to begin. You do not need a finished specification.
Discuss your project