Deal in.
Signed
proposal out.
A block canvas for the documents that carry money: proposals, quotes, invoices, statements of work. Behind them sit CPQ — configure, price, quote, off a real product catalog with discount caps and approvals — and CLM, which carries the signed contract on through clauses, redlines, e-signature and renewal.
The document is
the deal surface.
A proposal is the last thing a client reads before they say yes, and too often it is a copy of last month's file with the name changed. PaperIQ makes it a live document: composed from blocks, priced from the same engine that quotes the job, branded automatically, and signable in place.
Blocks, not templates
Drag in event headers, scope sections, pricing tables, invoice blocks and data tables. Every block renders for the recipient on a phone; static blocks print, and the live ones — video, embeds, panoramas — fall back to a still or a link.
Resolved at render time
CRM fields drop in as variables and resolve when the document is rendered — viewer, PDF and Word read one map — so a token the CRM never answered stays visible instead of vanishing.
Brand pull from a URL
Point PaperIQ at a site and it lifts the palette, type and logo, shows you what it found, and applies it on your say-so. The workspace defaults behind it are admin-only.
Analytics down to the section
You see how many times it was opened, by how many people, and the seconds each section held them — the difference between a silent client and a stuck price.
Configure, price, quote
A real product catalog — SKU, cost, unit type, billing cycle — with rules that require, exclude or auto-add products against each other as the quote is built. Discount caps and approval thresholds are authored once; a guided quote that trips one routes into a shared inbox as a fixed chain, so a later policy edit can never rewrite an approval already in flight.
The contract after the signature
Contracts sit in one repository you filter by status and type, counterparty paper included. Paste their revised text and get a tracked-changes diff you accept or reject change by change; signing is native and free on every tier. Renewal, notice and payment dates surface on the document as obligations.
Native in Salesforce
Generate a document from an Opportunity and a template without leaving Salesforce, save it back with file versioning, and the signed result writes onto the record. Salesforce is the deepest integration; the product stays CRM-agnostic.
Get paid in the document
A Stripe payment link sits on the invoice block, and deposit and milestone schedules reconcile to the cent against the same frozen totals.
A room the buyer can ask questions in
Each stakeholder gets their own link. A question agent answers only from the document itself, a mutual action plan tracks who owes what, and per-person engagement lands in the seller's inbox.
Start from the deck you already have
Drop a PDF deck and PaperIQ proposes a document — sections, tables, images, floorplan hotspots — for review before anything is created, with no AI tokens spent on the conversion. A 24-page deck became 18 sections, 4 tables, 43 images and 9 hotspots in 4.9 seconds (measured 2026-09-01).
One version per send
Every send mints a version and the live link always resolves to the latest. Presentation mode and search run over the resolved text.
Sample data Drawn procedurally in your browser — no screenshots, no stock imagery, and no real client on the page.
Compose it.
Toggle blocks on and off. The document rebuilds, the pricing table re-totals, and the read-time estimate moves — the same loop a rep runs before hitting send.
Document preview · Larchmont Wedding 2026 Sample data
Blocks
Line items here are illustrative. In the product one shared pricing engine prices the block, so what the document prints and what the buyer is charged are the same number.
Try the rule.
Drag the discount a rep might ask for. This model re-prices its own line items and stops at the margin floor rather than warning you and letting you click past. In PaperIQ the same idea ships as an approval gate: a discount over the threshold your org configures routes for approval, and the send is refused — fail-closed — until it clears.
Sample data The list price, cost and floor below are an illustrative quote, not a customer’s.
One source for
every number.
The failure mode PaperIQ is built against is drift: the proposal says one price, the work order another, the invoice a third. PaperIQ removes the retyping step entirely.