Does this work with our templates and our records?

The pattern needs a template set you already use and an authorized way to read the opportunity record. Any system that exposes that can carry it; the audit confirms whether yours does.

What happens when a price or term is outside the template?

It is flagged with the rule it sits outside of and routed to the person who holds pricing authority. Deal desk approval routing takes it from there.

The proposal that goes out is usually the last one with the names changed

Today

Numbers typed while the record sat in another window

The proposal that goes out is usually the last one with the names changed.
The quote carries numbers nobody can trace back to the record, because somebody typed them while the record sat in another window.
Your template has moved on and the copies have not, so a superseded term survives in a document that reads current.
The review happens after the document has already been promised to somebody.

With agents

Your record's values into your template, with the working shown

The reviewer checks rather than rebuilds.
A non-standard term is visible before the document is promised.
A past proposal can be explained.

How an agent runs it

Assembly is where the errors enter and review is where they are supposed to leave. The workflow puts your own record's values into your own template, shows its working, and stops before anything goes anywhere.

Reads

Takes the opportunity record and your current template set as the only inputs, so the document starts from your material.

Assembles

Builds the proposal and the quote from the template, with the record's values filled into the places your template names.

Shows

Names the source of each value it filled, so a reviewer can check a number against the record instead of trusting it.

Checks

Compares the assembled document against the current template and reports missing sections, superseded terms, and values the record cannot support.

Flags

Marks every price, term or discount that sits outside the template, and says which rule it sits outside of.

Human gate

Nothing goes out. The review and the send are a person's, every price or term outside the template is a person's decision, and the whole assembly can be run by hand at any point because the templates and the records are yours.

Records

Keeps which template version and which record fields produced the document, so a question about a past proposal has an answer.

Results

What changes when assembly stops being retyping

Check rather than rebuild

The document arrives assembled from the current template with each value's source shown.

A non-standard term shows early

The check runs against the template and marks what sits outside it.

A past proposal can be explained

The template version and the record fields that produced it are kept with the document.

Where this fits

Workflow / Automate a Workflow

Tier 1 through the Automate a Workflow door: one process end to end, from the record to a document a person reviews. The boundary is the document leaving. The price, the terms and the send stay a person's, and the workflow signs nothing. It extends toward The sales ops coordinator as an AI Employee as a possible next step rather than a promised state, where drafting is one duty among several. How It Works shows how the gates and the authorizations are built.

Tier 1 / Prove

How It Works

Questions, answered

No. It drafts and a person sends. The gate is closed by default and the workflow signs nothing. The templates and the records stay in your systems, so the assembly can be run by hand at any point without the agent.

AI Opportunity Audit

See how much your template and record could have assembled

Bring the last proposal you sent and see how much of it your template and your record could have assembled.

Book an audit