# Write client proposals with AI and Google Docs instead of PandaDoc

> Turn discovery-call notes into a scoped, priced proposal with a four-step AI prompt sequence, lay it out in a reusable Google Docs template, and collect signatures with Google Docs eSignature (if your Workspace plan includes it) or a DocuSign account you already have. Replaces PandaDoc's writing and template work; not its analytics, CRM sync or payments.

- Outcome: I want to send professional, accurate proposals quickly and get them signed without paying for PandaDoc.
- Replaces: PandaDoc (partial)
- Uses: Claude — Turn discovery notes into scope, pricing table and risks; review the draft like a sceptical client.; ChatGPT (optional) — Alternative assistant for the same prompt sequence.; Google Workspace — Google Docs proposal template, Drive folder per client, and (on eligible plans, when the admin enables it) Docs eSignature.; DocuSign eSignature (optional) — Signature option if your Google Workspace plan lacks eSignature and you already pay for DocuSign.
- Extra monthly cost: $0 — Assumes you already pay for an AI assistant and a Google Workspace plan. Google Docs eSignature is listed for Workspace Individual, Business Standard and Plus, and several Enterprise/Education editions when the admin turns it on; it is not listed for Business Starter. If you don't have it and don't already pay for DocuSign or similar, you'll need a separate e-signature tool, which is an extra cost.
- Difficulty: easy; skill: basic; setup: 2–3 hours to build the template, pricing rate card and saved prompts
- Evidence: editorial; illustrative example: false; last reviewed 2026-10-13
- Canonical: https://onelesstool.com/workflows/client-proposals-with-ai-docs

## Good fit for
- Freelancers, consultancies and agencies sending a handful of custom proposals a month
- Teams already on Google Workspace Business Standard or higher (eSignature included when enabled)
- Service businesses whose proposals are mostly custom scope rather than catalogue quotes

## Not a fit for
- Sales teams that rely on PandaDoc's CRM sync to create documents from deals and update deal stages automatically
- Businesses that collect payment inside the proposal at signing
- Teams that need view tracking (who opened what, for how long) to time follow-ups
- Organisations with formal approval chains and a shared, governed content library
- Regulated agreements where your legal team requires a specific e-signature provider

## Before
Create a PandaDoc document from a template or CRM deal, drag in content-library blocks, build the pricing table, route it for internal approval, send it, watch view analytics, and collect signature and payment in PandaDoc.

## After
Paste discovery notes into Claude and run four prompts (brief → scope → pricing → risks), paste the result into a copy of your Google Docs proposal template, check every number against your rate card, export or share, and request signatures with Docs eSignature (or DocuSign). Follow-ups are scheduled in your calendar instead of triggered by view alerts.

## Steps

### 1. Check what you'll lose and what you'll use instead

List the PandaDoc features you use weekly. PandaDoc's own plan comparison puts **CRM integrations, content library, document analytics and approval workflows on Business** (not Starter), and **payment collection** on both Starter and Business. If any of those drive your sales process, this workflow is only a partial replacement.

Then confirm your signature route:
- **Google Docs eSignature**: listed for Workspace Individual, Business Standard/Plus and some Enterprise/Education editions, **only when your admin enables it**. Up to 10 signers and 200 fields per request; an audit-trail page is added to the signed PDF. Not listed for Business Starter.
- **DocuSign** or another e-signature tool you already pay for.
- If you have neither, budget for one before cancelling PandaDoc.

### 2. Build your Google Docs template and rate card

Paste the **proposal template** (artifact below) into a new Google Doc: turn on Markdown (Tools > Preferences), then right-click > **Paste from Markdown**. Add your logo, set heading styles and brand colours, and save it in a Drive folder named `Templates`.

Keep a **rate card** in a Google Sheet: service, unit, price, minimum, notes. The AI will only use prices from this sheet. This is the most important control in the workflow.

Move your reusable blocks (case studies, team bios, terms) into one `Proposal library` Doc. It's a manual content library: copy, don't link.

### 3. Run the prompt sequence on your discovery notes

In one conversation (or a Claude Project / ChatGPT Project holding your rate card, library and template):

1. **Discovery → brief**: structure the messy notes and list unknowns.
2. **Brief → scope**: phases, deliverables, acceptance criteria, out of scope.
3. **Scope → pricing table**: line items priced *only* from your rate card, with the arithmetic shown.
4. **Risks and assumptions**, then the **executive summary** last.

Answer the unknowns the AI lists before moving on. Don't paste confidential client data your agreement or your AI plan's data settings don't allow.

### 4. Assemble the document and check every number

Make a copy of the template in the client's Drive folder (`Proposals/<Client>/<YYYY-MM-DD> <Project>`). Paste each section in using Paste from Markdown.

Then verify by hand:
- Each line item's price matches the rate card; recalculate totals in the Sheet, not in your head.
- Dates are achievable and dependencies are stated.
- Names, company details and the validity date are correct.

Finally, run the **Sceptical client review prompt** and fix what's fair.

### 5. Send and collect signatures

**Google Docs eSignature** (if enabled): in the Doc, go to **Tools > eSignature**, choose each signer under "Insert fields for", drag in Signature and Date signed fields, then click **Request signature**, add signer emails and optionally turn on automatic reminders. When everyone has signed, the final PDF (with its audit trail page) is saved in the same Drive folder as the original Doc, and linked in the completion email.

**DocuSign**: download the Doc as PDF (**File > Download > PDF**), upload it to DocuSign, place fields and send.

Either way, also email the client a short cover note with the summary and a deadline for questions.

### 6. Replace the missing tracking and payment steps

- **Follow-ups**: without view analytics, add a calendar reminder 2 and 5 business days after sending. Use the **Follow-up email prompt** with the proposal summary.
- **CRM**: paste the proposal link and value into the deal record by hand (or with an automation tool you already use).
- **Deposits**: send the deposit invoice from your accounting/invoicing tool when the signed PDF arrives.

## Prompts

### 1. Discovery notes → structured brief
Turn raw call notes into a clean brief and surface what you still need to ask.

```text
You are helping me write a proposal for {{client_company}}. My company: {{your_company}}, which does {{your_services}}.
Here are my raw discovery notes:
{{discovery_notes}}
Produce: 1) the client's situation in 3 sentences; 2) their goals, each with a measurable success indicator; 3) constraints (budget hints, deadlines, decision-makers, approvals); 4) a numbered list of open questions I must answer before scoping. Don't fill gaps with assumptions; list them as questions.
```

### 2. Brief → scope of work
Define phases, deliverables, acceptance criteria and exclusions.

```text
Using the brief above and my answers to the open questions ({{answers_to_open_questions}}), write the scope of work:
- {{phase_count}} phases, each with duration estimate, deliverables (with format), and an acceptance criterion per deliverable.
- An "Out of scope" list of at least 5 items the client might reasonably assume are included.
- Dependencies on the client (inputs, approvals, access) with deadlines.
Use plain language. Match how we usually deliver: {{delivery_approach}}.
```

### 3. Scope → pricing table (rate card only)
Price the scope strictly from your own rate card, with arithmetic shown.

```text
Price the scope above using ONLY this rate card. Never invent a price or discount:
{{rate_card}}
Output a Markdown table: item | qty | unit | unit price | line total. Then subtotal, tax at {{tax_rate}}, and total in {{currency}}.
Show your quantity reasoning for each line in one short sentence underneath. If something in scope has no rate-card entry, put "PRICE NEEDED" instead of a number.
Add a separate "Optional add-ons" table for: {{optional_items}}.
Payment terms to state: {{payment_terms}}.
```

### 4. Risks, assumptions and executive summary
Protect the project with explicit assumptions, then write the summary last.

```text
For this proposal:
1) List 5–8 assumptions that, if wrong, would change cost or timeline (inputs, feedback rounds, access, third-party tools).
2) A risk table: risk | likelihood | impact | mitigation. Include at least one risk on the client side and one on ours.
3) Then write a 4–5 sentence executive summary for {{decision_maker_role}}: their situation, outcome, our approach, total investment of {{total_price}}, and the next step ({{next_step}}). No superlatives, no claims we can't prove.
```

### Sceptical client review prompt
Stress-test the draft before sending.

```text
Act as {{decision_maker_role}} at {{client_company}} reading this proposal for the first time, with a budget of about {{client_budget_hint}}. Be sceptical.
List: anything unclear; anything that looks padded; questions you'd ask before signing; places where scope and price don't match; and the single biggest reason you might say no. Then suggest the smallest edits that fix each point.
Proposal:
{{proposal_text}}
```

### Follow-up email prompt
Replace view-triggered follow-ups with a scheduled, helpful nudge.

```text
Write a short follow-up email (under 90 words) to {{client_name}} about the {{project_name}} proposal I sent on {{sent_date}}. Mention one specific benefit from the summary: {{key_benefit}}. Offer a 15-minute call to answer questions and note the proposal is valid until {{valid_until}}. Friendly, no pressure, no "just checking in".
```

## Templates and scripts

### Proposal template (Markdown — paste into Google Docs with Paste from Markdown) (template)

```markdown
# Proposal: {{project_name}}
**Prepared for:** {{client_name}}, {{client_company}}
**Prepared by:** {{your_name}}, {{your_company}}
**Date:** {{date}}  ·  **Valid until:** {{valid_until}}  ·  **Reference:** {{proposal_id}}

---

## 1. Summary
_Three to five sentences: their situation, the outcome they want, what you'll do, the investment, and the next step._

## 2. Your goals (as we understood them)
- Goal 1 — how we'll know it's achieved: ____
- Goal 2 — ____
- Constraints we heard: budget, deadline, internal capacity, approvals

## 3. Scope of work
### Phase 1 – {{phase_1_name}} ({{phase_1_duration}})
- Deliverable: ____ — format: ____ — acceptance: ____
### Phase 2 – {{phase_2_name}} ({{phase_2_duration}})
- Deliverable: ____

### Out of scope
- ____ (anything the client might reasonably assume is included)

## 4. Timeline
| Milestone | Target date | Depends on |
|---|---|---|
| Kick-off | ____ | Signed proposal + deposit |
| Phase 1 complete | ____ | Client feedback within 3 business days |
| Final delivery | ____ | ____ |

## 5. Investment
| Item | Qty | Unit price | Total |
|---|---|---|---|
| ____ | 1 | ____ | ____ |
| **Subtotal** | | | ____ |
| Tax ({{tax_rate}}) | | | ____ |
| **Total** | | | **____** |

**Optional add-ons** (not included in total)
| Option | Price | Notes |
|---|---|---|
| ____ | ____ | ____ |

**Payment terms:** {{payment_terms}} (e.g. 50% on signature, 50% on delivery; net 14). Invoices sent from {{invoicing_tool}}.

## 6. Assumptions
- Client provides ____ by ____.
- One round of consolidated feedback per deliverable; extra rounds billed at {{hourly_rate}}.

## 7. Risks and how we'll handle them
| Risk | Likelihood | Mitigation |
|---|---|---|
| ____ | Low/Med/High | ____ |

## 8. Why us
- Relevant result 1 (real, approved for reference)
- Relevant result 2

## 9. Terms
{{terms_reference}} (link to or attach your standard terms; have a lawyer review them once.)

## 10. Acceptance
By signing, {{client_company}} accepts this proposal and the terms referenced above.

| | {{client_company}} | {{your_company}} |
|---|---|---|
| Name | | |
| Title | | |
| Signature | | |
| Date | | |
```

## Limitations
- No document view analytics (opens, time per page); follow-ups are scheduled by hand.
- No automatic CRM sync of documents, values or deal stages.
- No payment collection at signing; deposits are invoiced separately.
- No governed content library or approval workflow; reusable blocks live in a Doc and approvals are manual.
- Pricing tables in Docs are static; there are no client-selectable optional items or automatic totals.
- Google Docs eSignature is only available on certain Workspace editions and only when your admin enables it; it allows up to 10 signers and 200 fields per request.

## Risks
- **reliability** (high): AI can miscalculate totals or invent prices. Price only from your rate card, mark gaps 'PRICE NEEDED', and recalculate totals in a spreadsheet.
- **sensitive_data** (medium): Discovery notes may include confidential client information. Check your client agreements and your AI plan's data settings before pasting them in.
- **compliance** (medium): Some contracts or industries require a particular e-signature provider or audit standard. Confirm Google Docs eSignature meets your legal requirements before relying on it.
- **functionality_loss** (medium): Losing CRM sync and view tracking can slow follow-ups for sales-led teams.
- **data_portability** (low): Export signed PandaDoc documents and your templates' text before cancelling; they won't be accessible afterwards.

## Verification checklist (run before cancelling)
- [ ] You rebuilt your last real proposal with this workflow and every price, total and date matches the original (or is knowingly updated).
- [ ] You confirmed in Google Docs that the eSignature option appears on your account (or you have an existing DocuSign/e-signature account), and completed a test signature with a colleague.
- [ ] The signed test PDF includes the audit trail and is saved in the right Drive folder.
- [ ] A full proposal took you under 60 minutes from notes to send.
- [ ] Your team agrees which lost features (view tracking, CRM sync, payments, approvals) you can live without, and has a manual replacement for each.
- [ ] All active and signed PandaDoc documents and template content are exported before cancelling.

## Savings methodology
Savings = PandaDoc seats × price per seat (monthly, or annual ÷ 12) − incremental cost. Incremental cost is $0 when you already pay for an AI assistant and a Google Workspace plan with eSignature, or for an existing DocuSign account. If you must buy a separate e-signature tool, subtract its monthly cost. Setup and per-proposal time are not monetised.

Example: A two-person consultancy on PandaDoc Business (billed annually) that sends 6–8 proposals a month, uses Google Workspace Business Standard and already pays for Claude. $98/mo → $0/mo. Assumptions: PandaDoc Business is $49 per seat per month billed annually ($65 billed monthly) per PandaDoc's plan comparison page, checked 2026-10-13: 2 seats × $49 = $98. Google Workspace Business Standard lists eSignature in Docs and the admin enables it; Workspace is already paid for and not counted. Claude is already paid for other work and not counted. The consultancy doesn't rely on PandaDoc's CRM sync, analytics or in-document payments.

## Sources
- PandaDoc Help: Compare subscription plan features: https://support.pandadoc.com/en/articles/9715033-compare-subscription-plan-features (accessed 2026-10-13)
- Google Docs Help: Request eSignatures: https://support.google.com/docs/answer/12315692 (accessed 2026-10-13)
- Google Workspace pricing: https://workspace.google.com/pricing (accessed 2026-10-13)
- Google Docs Help: Use Markdown in Docs: https://support.google.com/docs/answer/12014036 (accessed 2026-10-13)
