- 01
Brief
You tell us what you want to build, who it is for and what is driving the timing. We reply in writing with questions.
From you
Answers to the questions we ask
You receive
A clear view of whether we are the right fit
- 02
Scoping
We turn the brief into a written specification: features, architecture, main risks, what is out of scope and an estimate.
From you
Decisions on priorities
You receive
Specification, architecture note and written estimate
- 03
Contract
Confidentiality, ownership of the work, payment stages and how changes are handled all go into the agreement before the build starts.
From you
Review by your own adviser
You receive
A signed agreement with ownership assigned to you
- 04
Build
Work runs in short cycles. Each one ends with working software on staging for you to try, and a written note of what changed.
From you
Feedback on each cycle
You receive
Repository access, staging and regular written updates
- 05
Testing and security
Automated tests, security review and load checks suited to the product. Smart contracts holding real value go to an independent outside auditor.
From you
Sign-off on the release criteria
You receive
Test results and any audit findings, with their fixes
- 06
Launch and handover
We release to production, then hand over the repository, accounts, credentials and the documentation another team would need.
From you
Acceptance of the release
You receive
A running product and everything needed to run it
- 07
Support, if you want it
Maintenance and further development are a separate, optional agreement. Nothing in the handover depends on it.
From you
A decision on what you need
You receive
Agreed support terms, or a clean finish
Tell us what you want to build.
A few lines are enough. We reply in writing with questions.