CAIN-42 CAIN StudioPlaybook · objections
Objections — the ten you will hear
The honest answer to each one, including the soak, the price, and “we have a vendor”.
Ten objections, with the honest answer. Copy the answer; do not improvise a bigger claim.
“We already have a security vendor.”
Keep them. They gave you a report you have to trust; this gives your buyer a record they can re-run offline. It complements the vendor.
“Isn’t this just a scanner / pen test?”
A scanner gives alerts. A pen test gives a report. This gives a ranked finding, the patch, and a verifier the buyer runs themselves.
“We can do this internally.”
Then you are both the claimant and the verifier. We remove that conflict and give your buyer an independent artifact.
“Too expensive.”
Compare it to the deal it unblocks and the hours your team spends answering the questionnaire. It is reusable for every future buyer.
“Is this a certification?”
No. It is evidence, not a certificate. We state that limit in the report.
“Why not use an LLM to grade it?”
Because a model grading itself repeats its own blind spots. Our detector and our prover are independent of the model.
“What if you find nothing?”
You get a signed clean record with the limits of what was checked. It is still evidence; it is not a promise of safety.
“Have you passed a 72-hour soak?”
No. The hosted consensus cluster has not completed a 72-hour soak; the current public run is 24 hours and its checkpoints are published. The audit does not depend on that claim: every finding and fix is re-runnable with the verifier in the bundle.
“Who else uses you?”
We are a three-person team with a small number of paying customers. We are not going to pretend to be a big firm. What we offer is a fixed-price proof you can check yourself.
“What if the bundle doesn’t verify?”
You do not pay. That is the guarantee, and it is the reason the proof is the product.