Assembles a priced, compliant, on-brand proposal from the deal record, so the rep edits rather than writes.
what it is built to move
to the Scan's evidence — before any scope
to a system in production, not a pilot
modeled targets · not client results · timings are CRFT's standard engagement
Every proposal is rebuilt from the last similar one somebody can find. Pricing rules get applied from memory, the legal language drifts, and a deal sits for three days waiting on a document that is 80% identical to one already sent.
Where the Scan startsWith your last 20 proposals, your pricing rules and where deals stall in review.
Four lines, the same four on every system we build. Where they fall is what makes this one different from the last one.
The signals it works from. Typically connects to CRM, CPQ or pricing rules, Document storage and E-signature.
The calls it makes on its own, unattended, every time it runs.
Into the tools the work already lives in.
The rep reviews and sends, and an approver still approves. Pricing authority is a control, not a bottleneck to automate away — the system enforces it faster, it does not remove it.
The same four legs as every CRFT engagement — written for this system rather than in general.
We read your last twenty proposals to find what actually varies. Usually it is far less than the team believes, and the constant part is the build.
Scope follows the pricing rules. Simple rate cards are quick; usage-based and multi-year terms are the real work.
Ships against your real templates, not a rebuilt version of them. If the output does not look like your document, nobody uses it.
Edits are the signal. What reps change after generation tells it what the template gets wrong, and the draft needs less editing each month.
Hours from request to sent proposal, and how much of the generated draft survives to the sent version.
Five inputs, a published price, a report in 48 hours. Decide with numbers — then own what gets built.