Proposal First Drafts

Workflow Overview

The trigger

A proposal is needed — either from an AI Opportunity Audit deliverable, a direct client request, or a sales opportunity that requires formal documentation.

The steps

Step 1: Gather Input Data

• System receives structured input:
  • Client name, contact details, company information
  • Problem statement (from assessment, audit, or discovery call notes)
  • Proposed scope (workflow description, systems involved, steps)
  • Pricing tier and engagement type
  • Timeline (start date, duration, key milestones)
  • Any special terms or conditions

Tools: CRM (stores client data and opportunity details), form or structured input (Typeform, Airtable, or custom), document generation system

Failure mode: Input is incomplete, inconsistent, or copied from a previous proposal without updating
Fix: Required fields validation; template that forces fresh input for each proposal; review step before generation

Step 2: Select Template

• System selects the appropriate proposal template based on:
  • Engagement type (AI Opportunity Audit vs. First Workflow Build)
  • Industry or vertical (if applicable)
  • Special requirements (regulatory, technical complexity)
• Template includes:
  • Standard sections (problem, approach, scope, timeline, pricing, terms)
  • Placeholders for variable content
  • Consistent formatting and branding

Tools: Document template system (Google Docs templates, Word templates, or dedicated proposal tool like PandaDoc)

Failure mode: Wrong template selected; outdated pricing or terms in template
Fix: Template versioning with clear dates; central template repository; regular review cycle

Step 3: Generate First Draft

• System populates the template with input data:
  • Client information inserted into appropriate fields
  • Problem statement reformatted into proposal language
  • Scope detailed with standard language + custom elements
  • Pricing calculated and formatted
  • Timeline presented with milestones
• Document is saved with a consistent naming convention
• Draft is sent to proposal owner for review

Tools: Document automation (Documint, Pandadoc, or custom script using python-docx / Google Docs API)

Failure mode: Variables don't populate correctly; formatting breaks; document is unreadable
Fix: Template testing with sample data; validation step before sending to owner; fallback to manual edit

Step 4: Review and Edit

• Proposal owner reviews the draft:
  • Check that problem statement accurately reflects client needs
  • Verify scope is complete and accurate
  • Confirm pricing is correct
  • Add any custom language or special terms
  • Ensure tone and style are appropriate
• Edits are made directly in the document
• Version is saved as "ready for client"

Tools: Document editor (Google Docs, Word), version control

Failure mode: Proposal contains errors, outdated information, or inappropriate language
Fix: Standard review checklist; second pair of eyes for high-value proposals; final validation before sending

Step 5: Send to Client

• Proposal is exported to PDF (or sent directly from proposal platform)
• Email is drafted with:
  • Personalized greeting
  • Brief summary of what's included
  • Clear call to action (sign, schedule call, ask questions)
  • Deadline or validity period (if applicable)
• Proposal is sent and tracked

Tools: Email client, proposal tracking (if using PandaDoc or similar)

Failure mode: Wrong version sent; proposal sent to wrong person; tracking fails
Fix: Pre-send checklist; confirmation of recipient; tracking verification

Step 6: Track Response

• System tracks:
  • When proposal was sent
  • When it was opened (if tracking enabled)
  • Response deadline
  • Client questions or feedback
• Automated reminders are sent before deadline
• Outcome is recorded (signed, rejected, negotiated)

Tools: CRM, proposal tracking, calendar

Failure mode: Proposal is forgotten; no follow-up; outcome not recorded
Fix: Automated reminder at 3 days before deadline; CRM update required to close opportunity

The failure modes

Rough build cost

These are typical market costs to build this reference design. If your version fits our scope bound (at most 3 systems, 10 steps, 1 trigger), our fixed price is $4,500 for a First Workflow Build.

Timeline: 3-4 weeks from scope sign-off to live system (our fixed-price build commits to 5 weeks from a signed spec, including testing and handover)

Rough ongoing cost (by hand)

If done manually:

Hidden cost: Inconsistency between proposals, errors, missed follow-ups, lost opportunities

What this excludes

• Legal review — Contract terms and legal language are separate from proposal generation
• Pricing strategy — How prices are determined is a business decision, not part of the automation
• Client discovery — Gathering the initial requirements is a separate workflow (assessment or audit)
• Negotiation — Handling counteroffers and revisions is a different process

Why this matters

Proposals are a critical touchpoint in the sales process. A sloppy proposal:

• Erodes confidence — Errors or inconsistencies suggest sloppy work ahead
• Delays decisions — Unclear proposals require clarification, extending the sales cycle
• Creates inconsistency — Different proposals look different, making your offer seem variable
• Wastes time — Manual drafting takes hours that could be spent on actual work

How we'd approach building this

1. Audit current proposal process — How are proposals created now? What takes the most time? Where do errors occur?
2. Standardize the templates — Create consistent templates for each engagement type with all standard language
3. Identify variable data — What changes from proposal to proposal? Where does it come from?
4. Design the automation — Map the flow from input → template → generation → review → send → track
5. Build and test — Create the automation; test with sample data; validate output
6. Train and handover — Document the process; train whoever owns proposals
7. Iterate — Track proposal conversion rates; refine templates and process based on results

The runbook

Owner: [Named person on internal team]

Daily checks:

• Proposals sent in the last 48 hours (confirm receipt)
• Proposals due for follow-up
• New proposal requests

Weekly checks:

• Proposal conversion rate
• Average time from send to decision
• Common questions or objections

When things break:

1. Check if the issue is with input data, template, or generation
2. Manually create the proposal if automation fails
3. Investigate and fix the root cause
4. Escalate to [support contact] if not resolved within 24 hours

Questions this raises (for the client)

1. What information do you absolutely need before you can write a proposal? What can you infer or assume?
2. How long does it currently take to write a proposal? What parts take the most time?
3. What's your proposal conversion rate? Do you track why proposals are rejected?
4. Who reviews proposals before they're sent? Is that person consistently available?
5. What happens to proposals after they're sent? How do you track responses and outcomes?

Related teardowns

• Inbound Lead Qualification — What happens before a proposal is needed
• New Client Intake — What happens after a proposal is accepted
• Assessment Funnel — How the free assessment identifies proposal-worthy opportunities
• Workflow Build — What the proposal promises to deliver