The offer, the price and the close
Sell Crypto Audit inside the Fabrication Audit, with Fix + Prove for each finding.
What you sell
Fabrication Audit
Finds code that looks finished but is not, with a signed report the client re-checks.
$1,500 standard · $3,500 deep · $6,000 diligence (for an investor or acquirer)
Turnaround: 48 hours for the standard tier; larger scopes agreed in writing · Payment: 50% up front
What the client receives
- report.md: every module graded REAL / PARTIAL / STUB / UNKNOWN, with the exact lines that caused each grade.
- findings.json: the same result for the client's engineers, machine readable.
- evidence.zip: a signed record plus a small checker that imports none of our code.
- A list of the files that were clean, and a section of notes from the person who reviewed it.
What the offer itself says about its limits
- The detector is precise but narrow: it misses many kinds of fake code. A clean grade is not a guarantee.
- A person reviews every finding before the report goes out.
Price source: Operator playbook stream 1 (docs/strategy/CAIN-AS-A-BUSINESS-OPERATOR-PLAYBOOK.md); delivered by cain_audit. Prices are the founder's proposed list prices, not validated market rates; any discount needs the founder's OK.
Also offer
Fix + Prove
We ship the patch and prove it: the test fails on the old code and passes on the new.
$500 small fix · $1,500 standard · $2,500 complex fix
Turnaround: 1–2 weeks · Payment: 50% up front
What the client receives
- The patch, applied on a branch.
- An independent test that fails on the old code and passes on the new.
- A signed, hash-chained record and a standalone verifier.
- A short note the buyer can forward to their own customer.
What the offer itself says about its limits
- A proof covers the contract and the tests we ran; it is not a proof that the whole system is safe.
- If the independent test cannot run, the verdict is NOT_VERIFIED and nothing is issued.
- We do not claim a fix we did not prove.
Price source: cain_audit/products.py → fix-prove. Prices are the founder's proposed list prices, not validated market rates; any discount needs the founder's OK.
What you need from the client
- What they use AI for, in their own words.
- An engineer for a one-hour setup call.
How to close
- Run their worst-suspected file.
- Quote the Fabrication Audit.
- Hand to the founder.
Copy you can send
First email
Subject: quiet encryption mistakes in your code
Hi [first name], Code with weak encryption runs fine and passes tests. Crypto Audit finds it: MD5 passwords, switched-off checks, keys in the code, with the fix for each. Live demo: https://cainstudio.online/guide-crypto-audit-lab.html [your name], working with FIRME AI CORPORATION
LinkedIn connection note (under 300 characters)
Hi [name], we find weak encryption in Python code (MD5 passwords, switched-off TLS checks, short keys). Happy to show it.
Follow-up, three days later
Hi [first name], demo: https://cainstudio.online/guide-crypto-audit-lab.html
Fill in the brackets by hand for each person. Never paste the same message to a list.
Hand-off to the founder
Email vincent@firmeai.com with: company, person and role, what they said in their own words, which offer, the price you quoted, and the agreed next date. The founder handles scoping, written authorisation to test, invoices and delivery.
Next: the rules, the glossary and the quiz →
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.