CAIN-42 CLAWXFALSEWORK: selling tools
Evidence for FALSEWORK: 1. Evidence pack · 2. Answers to buyer questions · 3. Figures & benchmarks · 4. Selling tools · IHVRK kit · Learn it
The evidence is your best sales tool: a buyer can check it without trusting you. Press Copy on any box, fill in the [brackets] and send it, one person at a time.
What to send, and when
| When | Send this |
|---|---|
| First message | A short personal note with the kit page |
| They reply, "show me" | The live demo on a call, using the script below |
| "Send it to our engineer" | The kit and the evidence pack |
| Security review or questionnaire | The answers page. Never upgrade a NO to a YES. |
| Finance or procurement wants records | The figures page and figures.tsv |
| Ready to go ahead | The hand-off below. The founder does the contract, price and setup. |
Who to approach
- Investor / technical due-diligence advisor: Is the product real?
- CTO inheriting a codebase: What did the last team or contractor really build?
- Founder before a raise: Will diligence find embarrassing fakes?
Questions to ask them
- Who wrote most of this code, and how?
- What is the next event where someone will scrutinise it?
- Have you ever found a function that looked right but faked its result?
- How big is the codebase, and is it Python?
- What would it cost you if an investor found a fake first?
30-second pitch
FALSEWORK finds code that looks finished but is fake: hardcoded results, random numbers posing as scores, checks that can never fail. We recorded 7 live checks, including 6 attack cases it had to refuse or flag, and every one matched. You can re-run them yourself without an account. Don't trust us. Check it: https://cainstudio.online/ihvrk-falsework.html
First email
Subject: is your AI-written code real or just tidy? Hi [first name], AI tools write code that looks finished. Some of it is not: typed-in results, random "scores", security checks that can never fail. We grade every Python module real or fake, show the exact lines, and sign the report so you can re-check it. Fixed price from $1,500, 48 hours. Try it on one file: https://cainstudio.online/top25-falsework-demo.html The evidence: We recorded 7 live checks, including 6 attack cases it had to refuse or flag, and every one matched. You can re-run them yourself without an account. Check it yourself: https://cainstudio.online/ihvrk-falsework.html [your name], working with FIRME AI CORPORATION [your postal address] If you'd rather not hear from me again, just say so and I won't write again.
LinkedIn connection note (under 300 characters)
Hi [name], we audit AI-written Python for code that looks finished but fakes its results. Useful before a raise or a handover. Happy to show a 2-minute example.
One follow-up, three days later (then stop)
Hi [first name], if you paste any one Python file into the demo, you'll see in seconds what an audit looks for. Want me to run your most important module for free as a sample?
Live demo call script
1. Show the normal case Do: Open https://cainstudio.online/top25-falsework-lab.html and run: Your code: honest constant-time compare Say: Real code must grade REAL or nobody trusts the alarms. 2. Now the attack Do: Run: Sample: A signature check that never checks the signature Say: A deterministic detector, not the model, finds the defect the AI is then asked to fix. 3. Now the attack Do: Run: Sample: A metric that reports a random number as accuracy Say: A deterministic detector, not the model, finds the defect the AI is then asked to fix. 4. Let them check you Do: Send the kit link and ask them to run python3 verify.py --live on their own computer. Say: They don't have to take your word for any of this. That's the point. 5. Say the limit yourself Do: Tell them what the kit does not show. Say: Say it before they ask. It costs nothing and it earns trust.
When they push back
Can it catch everything?
No, and we say so: on a fresh blind set it caught 3 of 12. It is precise, not complete; a person reviews the report.
Our linter already does this.
Linters find errors. FALSEWORK finds code that runs fine but fakes its result.
Is our code sent to an AI?
No. The decision is rule-based; nothing is sent to a model.
We use TypeScript.
Then this is not the right tool today; it is Python-focused.
Why should I believe your numbers?
You shouldn't have to. Run the kit on your own computer: https://cainstudio.online/ihvrk-falsework.html. It re-sends every request and compares the answers, using no code of ours.
What doesn't it do?
Written down here: https://cainstudio.online/top25-falsework-limits.html
Are you SOC 2 or ISO certified?
No, we hold no certification. What we offer instead is evidence you can check yourself.
Has anyone independent tested it?
No third-party audit has been completed. The attack cases in the kit are our own. I'd rather tell you that now.
Who else uses it?
We are an early company. I can show you the product working and the evidence, not a customer list.
It found nothing. So we're safe?
No. It means none of its checks fired. It doesn't prove something is safe.
How much is it?
Sell FALSEWORK as the Fabrication Audit: a graded, signed report on a codebase, reviewed by a person.
One-page summary (paste into a document or email)
FALSEWORK by FIRME AI CORPORATION, a California corporation What it does FALSEWORK finds code that looks finished but is fake: hardcoded results, random numbers posing as scores, checks that can never fail. The evidence We recorded 7 live checks, including 6 attack cases it had to refuse or flag, and every one matched. You can re-run them yourself without an account. Recorded 2026-11-03. 7 live checks. Median round trip 79 ms including network; this is not a load test or an SLA. Check it yourself https://cainstudio.online/ihvrk-falsework.html Zip SHA-256: 73b429aefe029a29aad62c4482f64bb88df76d2cc7bfd85236ef01b3a87a1385 Signing key fingerprint: 1cacdfc1fc2024b6bb4f8fb02c7c80f4a57f44c5adb11c507190781b5d613de3 Run: python3 verify.py --live (Python 3, no account, no code of ours) What it does not do Written down here: https://cainstudio.online/top25-falsework-limits.html What this is not Not a third-party audit, a certification or a guarantee. No SOC 2 or ISO certification is held. Contact [your name], working with FIRME AI CORPORATION, [your email]
After the call: the proposal email
Hi [first name], Thanks for your time. As discussed, here is what I suggest for FALSEWORK. What you told me: [their problem, in their words] What we'd do: Sell FALSEWORK as the Fabrication Audit: a graded, signed report on a codebase, reviewed by a person. Evidence you can check before deciding: https://cainstudio.online/ihvrk-falsework.html Answers for your security review: https://cainstudio.online/evidence-falsework-answers.html Figures for your files: https://cainstudio.online/evidence-falsework-figures.html Limits: Written down here: https://cainstudio.online/top25-falsework-limits.html Next step: [date], [who]. The founder, Vincent Noriega, handles contract and setup. [your name], working with FIRME AI CORPORATION [your postal address] If you'd rather not hear from me again, just say so and I won't write again.
Hand-off to the founder
To: vincent@firmeai.com Subject: Lead: FALSEWORK - [company] Company: [company] Person: [name], [job title], [email] What they said: [paste their reply] Evidence already sent: https://cainstudio.online/ihvrk-falsework.html Price mentioned: [what you quoted, or none] Next date: [date]
The rules
- Send each message yourself, one person at a time. No bulk lists and no automated sending.
- Commercial email needs your real name, a real postal address and a way to opt out, and you stop when someone asks (US CAN-SPAM; many countries are stricter, so check yours).
- Never change a number, invent a customer, or say certified, audited or guaranteed.
- Only test a system the client owns or operates, after they confirm it in writing.
- Your share is agreed in writing with FIRME AI CORPORATION before your first message (email vincent@firmeai.com). Nothing here promises income. Most messages get no reply; that is normal.