Max Tymoshyn, founder of Norml Studio
Max TymoshynFounder, Norml Studio

Draft proposals using approved CRM and discovery inputs

A proposal needs to reflect the agreed work as well as the prospect’s situation. Norml builds a workflow that gathers selected CRM and discovery records, drafts the narrative and inserts approved commercial details into your proposal format. The account owner reviews the source evidence and unresolved items before the document can be shared with a prospect.

Keep the proposal tied to approved inputs

The first scope can connect HubSpot opportunity context with a Google Docs proposal template. AI assists the narrative; commercial fields are copied from approved records and checked independently.

Solution
Automations
Tools
Claude, HubSpot, Google Docs
Trigger
An account owner requests a proposal draft for a verified opportunity and selects the approved scope, pricing and template versions.
Outcome
Create an internal proposal draft with source references, preserved approved commercial values and a review list; return its link to the opportunity record.

Select the opportunity evidence

Match the prospect and opportunity by stable identifiers. Gather only the discovery notes and CRM fields authorized for that proposal. Separate customer statements, agreed requirements and the team’s recommendations so the draft does not present a suggestion as a commitment.

Preserve approved commercial terms

Insert the exact approved scope, currency, price and payment terms. Missing approval blocks a client-ready draft. The workflow does not calculate an estimate, select a discount or invent a delivery date; those decisions belong to your existing commercial process.

Produce a version for review

Create a draft using the selected template and record the input versions. Link it to the opportunity with a review status. Repeated requests reuse the recorded draft or create an explicit new version; changed pricing invalidates the earlier approval.

Prepare the proposal rules before connecting records

Approved template and source fields

Provide the current proposal structure and the fields allowed to populate it. Identify which narrative sections may be drafted and which legal or commercial clauses must be copied exactly.

Verified records and document access

Confirm the CRM opportunity, source-note permissions and the destination document location. The Google Docs API can populate template placeholders, but account access and sharing policy must be checked for your chosen setup.

Commercial and final reviewers

Name who approves scope and pricing, who resolves missing information and who can share the completed proposal. Limit model inputs to the necessary prospect context and agree retention of draft evidence.

Test the draft against approved examples

  1. Map a completed proposal

    Compare one approved proposal with its CRM and discovery inputs. Document source precedence, protected wording and the fields that need commercial approval.

  2. Build the assembly and review step

    Generate narrative only within the allowed sections and populate protected values through explicit field mapping. Show a checklist for missing inputs and mismatched versions.

  3. Verify revisions and interrupted runs

    Test absent pricing approval, a changed scope and a document creation timeout. Resolve whether a draft already exists before retrying. Hand over version tracking and the final sharing boundary.

Proposal workflow questions

Will AI decide what the project should cost?
No. Prices, hours, discounts and delivery commitments must come from your approved estimation and commercial process. The workflow copies those values and checks that the draft matches them. An absent approved figure remains a blocker.
Can we reuse text from previous proposals?
Yes, where your team approves reuse and the material is appropriate for the new prospect. Client-specific names, confidential details and unsupported claims must be excluded. The current template and approved scope take precedence over an old example.
Does creating a proposal also send it?
No. The output is an internal draft and a review handoff. Sending, recipient selection, document sharing and signing are separate actions owned by an authorized person.
What happens if the deal changes after drafting?
The draft records the input versions used. A changed scope or commercial value triggers a new comparison and review. The workflow must not overwrite a reviewed document silently or preserve approval for outdated terms.
Show us your approved format, an example opportunity and the commercial approval rules. We will define which text can be drafted and which values must remain exact.

Bring a proposal and the records behind it

Discuss your automation