The sales conversation for Crypto Audit
A word-for-word starting point. Make it sound like you after the first few calls.
The shape of every call (same for all 25)
- Open with their world, not ours (1 minute). One sentence about a problem they likely have. Never start with "CAIN-42 is a Byzantine trust fabric"; say that later, when they ask how it works.
- Discover (5-10 minutes). Ask the questions below and listen. Write down their exact words; you will use them in the follow-up email.
- Show (5 minutes). Run the live demo with them watching. Nothing is pre-recorded: every button calls the real product. Let them pick an attack.
- Offer (2 minutes). One offer, one price, one date. Do not list all 25 products.
- Next step (1 minute). Before you hang up, agree a date: payment, a scoping call with the founder, or a "no".
Openers (pick one)
- "Does any of your code still hash passwords with MD5?"
- "We find quiet encryption mistakes in code."
Discovery questions
Ask, then stop talking. Each question tells you whether they have the problem and how much it matters.
- What sensitive data do you handle?
- Who wrote the auth code?
The five-minute live demo
Share your screen. Everything below calls the real product, so it can occasionally be slow or rate limited (a "429" means too many tries from one address; wait a minute). Practise it three times before your first call.
- Live demo tools: run modern code first (clean), then the three-mistake snippet.
Objections and honest answers
| They say | You answer |
|---|---|
| "Our code passes tests." | Weak crypto passes tests; that is why it's dangerous. |
If you do not know an answer: "Good question. I will get you a precise answer from our engineers by tomorrow." Then email the founder. Never guess.
Next: the offer, the price and how to close →
FIRME AI CORPORATION · CAIN-42 is a Byzantine trust fabric. Numbers marked "our own check" were run by us, not by an independent party. Nothing on these pages is a certification.