Nothing starts until you approve the scope.
Six steps, in order, with a clear decision point at every one. You can stop after step three and walk away with a document you own and did not pay for.
- 01
Tell us what you need
A short form or a twenty-minute call, on your schedule. Where the project stands today, what it has to do, what it has to work around.
You do
Describe the problem in your own words. No technical answers needed.
We do
Read it before we call, and prepare the questions that apply to your case.
- 02
We scope it in writing
Features, integrations, technical requirements, assumptions, risks and exclusions — in plain English, and in enough detail that a partner can price it without guessing.
You do
Answer follow-ups and decide on the trade-offs we lay out.
We do
Recommend a direction on every technical choice, and write down what you pick.
- 03 Decision point
You approve the scope
The decision point. Nothing is quoted, contracted or built before your sign-off — and changes at this stage cost nothing, because nobody has estimated anything yet.
You do
Read it, change what needs changing, and approve — or stop here and keep the document.
We do
Freeze the version everyone will be held to, yours to keep either way.
- 04
We match the partner
Shortlisted from the network by domain experience, stack and real current capacity — then one recommendation, with named engineers and our reasoning.
You do
Meet the team if you want to. Say no if it does not feel right.
We do
Brief them technically, confirm capacity, and sign the back-to-back contract.
- 05
The partner quotes it
A fixed price against the exact document you approved. Straightforward projects are usually quoted within five business days; complex ones can take up to ten.
You do
Review one price and one milestone plan. Accept, adjust scope, or stop.
We do
Challenge the estimate line by line and set up escrow before work begins.
- 06
We run delivery
Your delivery manager holds the partner to the scope, runs one weekly review with you, and closes the project with handover, documentation and IP transfer.
You do
Accept each milestone. One meeting a week, one person to talk to.
We do
Everything else: standups, QA gates, escalation, escrow releases, release management.
What an agency-ready scope contains.
Seven sections. The last three are the ones that usually get left out — and the ones that later turn into change orders.
- 01 Project summary — what this is and who it is for
- 02 Feature-level scope, written per user role
- 03 Technical requirements, integrations and data model notes
- 04 Non-functional requirements: performance, security, accessibility
- 05 Assumptions — what we are taking as given
- 06 Risks — what could move the timeline, named in advance
- 07 Exclusions — what is explicitly not in this price
Field service scheduling platform
- Dispatcher console — 14 requirements IN
- Technician mobile app — 9 requirements IN
- ERP sync — invoices, stock, customers IN
- Customer self-service portal OUT
- Historical data migration before 2021 OUT
How escrow works, in four moves.
- Step 1
Milestones are defined
Each one has a deliverable, a date and written acceptance criteria — agreed before any money moves.
- Step 2
You fund the milestone
The amount sits in escrow. The partner can see it is there; nobody can draw on it yet.
- Step 3
You accept the work
We review it against the criteria first and raise what is missing. You sign off only when it matches.
- Step 4
Escrow releases
Payment goes to the partner. If the engagement has to change, the unreleased balance stays yours.
And our fee?
Included in the project quote, plus a placement commission from the partner. There is no separate consulting invoice and no charge for scoping. The commission is one rate, fixed in the partner agreement before any brief is sent, and we challenge the partner's estimate line by line before it reaches you — a padded quote is the quickest way to lose the approval we both need.