Demo your API in Claude on a sales call
Prospects ask if you work with Claude. You should run your product live in the assistant on the call, not promise a roadmap item.
Pick two tools that match your best buyer story, rehearse the prompt, and run them in Claude Desktop before you pitch enterprise features.
The result
A repeatable five-minute demo script: connect MCP once, run two tools live, and send connect docs after the call.
What breaks today
The prospect asks about Claude. You share a Loom recorded last quarter, mention a beta waitlist, and lose the deal to a competitor who ran their API live in chat.
Today
You describe integrations in slides. The prospect nods, checks the competitor, and picks whoever proved it in Claude already.
After scope
You paste a link or run a saved prompt, show export plus status in Claude, and follow up with install docs the same day.
When to use this guide
Pick this workflow if one of these matches your week.
- Every discovery call where AI assistants come up.
- You have MCP in staging but never show it externally.
- Champions need ammo to sell you internally.
- You want to test which tool story closes before you scope v2.
How to do it
Fixed scope, async delivery, and a handoff call. Same process on every Tookay Build.
- 01
Pick two tools that match your best buyer
Usually one create action and one read action: start job, check status. Or search, then fetch detail. Match what your ICP actually buys.
- 02
Rehearse in Claude Desktop or Cursor
Use the same MCP config file you will ship. No localhost-only shortcuts. If it fails in rehearsal, it fails on the call.
- 03
Script the prompts in plain language
Write what you will type verbatim. Prospects forgive rough UI. They do not forgive you hunting for the right tool name mid-call.
- 04
Follow up with connect docs
Send install steps, auth notes, and the two example prompts within an hour. Link to your docs page, not a zip file.
Copy-paste scripts
Use on fit calls, in sales demos, or when writing scope docs.
Open the demo
I use [PRODUCT]. Show me how I'd run it from here. Start with [PRIMARY ACTION] on a sample input.
Show status or retrieval
Second prompt proves the loop closes without opening your app in another tab.
Now check the status of that job / pull the result. Use my account context.
Objection: can my team script this?
Only if CLI is in scope. Bridges MCP for users and CLI for their dev team.
Same actions exist on CLI for our scripts. Run [CLI COMMAND] with the same parameters.
What good output looks like
Structured enough to forward or build on.
Sample result
On call: prospect sees PDF export start and complete inside Claude in under two minutes.
Follow-up email: MCP JSON snippet, link to docs, two copy-paste prompts, 30-day bug-fix note.
Result: objection moves from "do you integrate?" to "when can we turn it on for customers?"
Tips that save time
- Hide tools you have not tested in the last week.
- Use a staging API key with realistic sample data.
- Record the rehearsal Loom for async champions.
- If MCP is not shipped yet, do not demo mock tools. Book Audit instead.
Common questions
Key takeaways
- Demo two tools max on a call. More reads as a product tour nobody asked for.
- Rehearse with the same MCP config you ship to customers.
- Send connect docs within an hour while the call is fresh.
Continue reading
Related sales 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.
- Audit or Build: which offer fits your week4m
A clear path: Audit when scope is fuzzy, Build when the tool list is on paper. Same €2,900 total if you do both.
Ready to scope your v1?
Fifteen-minute fit call. Fixed price. MCP and CLI in your repo in ten to fourteen days.