Audit or Build: which offer fits your week
Two fixed offers, one outcome. Audit ranks your tools and quotes Build. Build ships MCP and CLI when scope is already written.
Fuzzy scope means Audit. Stable API plus a written tool list means Build. Audit fee credits toward Build within 60 days.
The result
A clear path: Audit when scope is fuzzy, Build when the tool list is on paper. Same €2,900 total if you do both.
What breaks today
Founders either jump to Build with vague scope and hit mid-project surprises, or stall in research because they fear committing to the wrong tools.
Today
You guess scope, start Build, and spend week two renegotiating tools. Or you research for a month and lose the customer who asked about Claude last quarter.
After scope
Audit in five days gives you ranked tools plus a Build quote. Or you skip straight to Build with scope already written. Same total when you do both.
When to use this guide
Pick this workflow if one of these matches your week.
- You debate which five actions to ship first.
- You have a clear tool list and a stable API ready to go.
- You want a fixed quote before €2,900 checkout.
- You need written excludes before a contractor touches your repo.
How to do it
Fixed scope, async delivery, and a handoff call. Same process on every Tookay Build.
- 01
Check if your API is stable
Breaking changes mid-sprint kill MCP timelines. If the API is still moving, fix that first or limit Audit to read-only tools.
- 02
Choose Audit if the tool list is not ranked
Pay €790. Get competitor check, five to ten ranked actions, v1 specs, and a fixed Build quote. No code.
- 03
Choose Build if scope is on paper
Pay €2,900 with fifty-fifty split. Ten to fourteen days. MCP plus CLI in your repo, docs, thirty-day bug fixes.
- 04
Credit Audit toward Build
If you Audit first, Build is €2,110 within 60 days. Total €2,900. Same as skipping Audit with clear scope.
What good output looks like
Structured enough to forward or build on.
Sample result
Audit deliverable: ranked tools, specs, excludes, Build quote €2,900
Build deliverable: repo PR, MCP config snippet, CLI binaries, connect docs, handoff call
Timeline: Audit 5 days · Build 10–14 days after kickoff
Tips that save time
- Book a fifteen-minute fit call if you are unsure. We disqualify bad fits before payment.
- Full refund if we are not a fit before work starts.
- Kickoff within five business days of checkout.
Common questions
Key takeaways
- Audit is paid discovery, not a PDF nobody reads.
- Build needs a locked list of five to ten tools with excludes.
- Audit plus Build totals €2,900 at founding rates.
Continue reading
Related process guides.
- Which MCP tools to ship first when users ask about Claude6m
A ranked v1 tool list with specs, auth notes, and a fixed Build quote you can checkout without guessing.
- Demo your API in Claude on a sales call5m
A repeatable five-minute demo script: connect MCP once, run two tools live, and send connect docs after the call.
Ready to scope your v1?
Fifteen-minute fit call. Fixed price. MCP and CLI in your repo in ten to fourteen days.