How to Automate Proposal & Contract Signing as a Solopreneur

The Job to Be Done (High-Stakes Agreements Only)

Proposal automation is not “pretty PDF faster.” On retainers, placement fees, and B2B terms, the job is: correct legal entity, correct fee table, signed audit trail, and payment trigger if applicable — without you rebuilding Word docs at 11pm.

Low-stakes $500 fixed-fee PDFs can stay manual. This playbook is for deals where a typo costs real money or enforceability.

• Success metric: scope agreed on call → DocuSign envelope sent in under 30 minutes (repeat templates).
• Failure metric: wrong fee, wrong entity name, or duplicate Payment Link on a live counterparty.
• Out of scope for v1: AI-generated contract clauses, multi-party redlines, enterprise CLM — merge into counsel-approved templates only.

Recommended Lean Stack (2026)

Canonical lean path: Stripe Payment Link → webhook → Make/n8n → programmatic PDF → DocuSign → auto-email. Swap PDFMonkey for Google Docs export if volume is low.

The Agreement Pipeline — What Must Happen in Order

Seven ordered steps. Make and n8n builds below execute this sequence — do not skip dedupe on deal_id before DocuSign sends.

1. 1

   Trigger: scope locked on call / CRM stage

   hybrid

   Deal row exists with client legal name, fee structure, term length, and template_id.

   Typical duration: 5–15 min (human confirms scope)

2. 2

   Generate programmatic PDF from template

   automation

   Scope, fees, payment schedule, and governing law merged into one PDF — no manual Word edits.

   Typical duration: 10–45 sec

3. 3

   Create e-sign envelope (DocuSign / PandaDoc)

   automation

   Client receives sign link; you are signer #2 or CC for countersign.

   Typical duration: 15–60 sec

4. 4

   Optional: Stripe Payment Link for deposit / first retainer

   automation

   Payment Link metadata carries deal_id; checkout.session.completed fires webhook.

   Typical duration: Instant (client pays async)

5. 5

   On signature: archive + notify

   automation

   Signed PDF to Drive `/Agreements/{client_slug}/`, CRM stage → Won, Slack + email to you.

   Typical duration: 30–90 sec

6. 6

   Auto-email countersigned package

   automation

   Client gets PDF + payment receipt (if applicable) + next-step calendar link.

   Typical duration: 10–30 sec

7. 7

   Human QA gate (high-stakes only)

   human

   You verify fee table, entity name, and indemnity clause before envelope sends in prod.

   Typical duration: 3–8 min per deal until template stable

The Data Contract: Fields Your Automation Cannot Guess

High-stakes automation fails when it guesses entity names or fee math. Normalize to this shape before PDF merge or DocuSign runs.

Normalized payload (target shape)

{
  "event": "agreement.generate_and_send",
  "deal_id": "deal_8842_retainer_acme",
  "client_legal_name": "Acme Holdings LLC",
  "client_slug": "acme-holdings",
  "signer_email": "cfo@acme.co",
  "signer_name": "Jordan Lee",
  "template_id": "retainer-msa-2026-v3",
  "fee_total": "8000.00",
  "fee_currency": "USD",
  "payment_terms": "50-deposit",
  "governing_law": "Delaware",
  "stripe_payment_link_needed": true,
  "is_test": false
}

Stripe Payment Link → Webhook Payload (Real JSON)

When deposit collection runs through Stripe Payment Links, your Make Webhooks module or n8n Webhook node receives `checkout.session.completed`. Map metadata.deal_id — never search by email alone on B2B deals.

Stripe event (trimmed — real shape)

{
  "id": "evt_3Pexample",
  "type": "checkout.session.completed",
  "data": {
    "object": {
      "id": "cs_live_a1B2c3D4",
      "livemode": true,
      "customer_details": {
        "email": "cfo@acme.co",
        "name": "Jordan Lee"
      },
      "amount_total": 400000,
      "currency": "usd",
      "metadata": {
        "deal_id": "deal_8842_retainer_acme",
        "template_id": "retainer-msa-2026-v3",
        "payment_terms": "50-deposit"
      },
      "payment_link": "plink_1Pexample"
    }
  }
}

DocuSign Connect (envelope completed)

{
  "event": "envelope-completed",
  "data": {
    "envelopeId": "a1b2c3d4-e5f6-7890-abcd-ef1234567890",
    "envelopeSummary": {
      "status": "completed",
      "customFields": {
        "textCustomFields": [
          { "name": "deal_id", "value": "deal_8842_retainer_acme" }
        ]
      },
      "recipients": {
        "signers": [
          { "email": "cfo@acme.co", "status": "completed" }
        ]
      }
    }
  }
}

Filter Stripe: livemode equals true in production. Dedupe DocuSign Connect on envelopeId before Drive upload.

Make Build: Stripe Webhook → PDF → DocuSign → Email

Ten-module scenario — names as they appear in the Make editor. Run DocuSign Connect listener as a separate scenario to avoid mixing send and archive paths.

1. Step 1

   HubSpot — Watch deals (or Webhooks — Custom webhook)

   Trigger when deal stage = "Proposal ready" OR receive POST from internal "Send agreement" button via webhook.

   Mapping:

   Map deal properties → normalized payload. HubSpot module outputs `dealId`, `amount`, custom props.

   Failure mode:

   Stage drift — lock stage names; add Filter: `template_id` is not empty.

2. Step 2

   Tools — Set variable (Normalize payload)

   Build object matching NORMALIZED_PROPOSAL_PAYLOAD_EXAMPLE.

   Mapping:

   `{{1.properties.legal_entity_name}}` → `client_legal_name`; slugify for `client_slug`.

   Failure mode:

   Missing governing_law — default from template map, not empty string.

3. Step 3

   Flow Control — Router

   Route 1: `is_test=true`. Route 2: production. Route 3: missing signer_email → Slack error.

   Mapping:

   Conditions on `payload.is_test` and email regex.

   Failure mode:

   Unmatched route — enable Fallback → #ops-errors Slack message.

4. Step 4

   HTTP — Make a request (PDFMonkey Generate Document)

   POST `https://api.pdfmonkey.io/api/v1/documents` with template_id + merge data JSON.

   Mapping:

   Body: `{ "document": { "document_template_id": "{{payload.template_id}}", "payload": { "client_legal_name": "...", "fee_total": "...", "governing_law": "..." } } }`

   Failure mode:

   Missing merge field → PDF renders blank table — validate required keys in Router before HTTP.

5. Step 5

   HTTP — Get a file (PDFMonkey download URL)

   Poll document status until `success`; download PDF binary.

   Mapping:

   Output `pdf_binary` + `pdf_filename` = `{{client_slug}}-agreement.pdf`.

   Failure mode:

   Timeout on large templates — add Sleep 2s + Repeater max 5.

6. Step 6

   DocuSign — Create envelope from documents

   Upload PDF; recipient 1 = client signer; recipient 2 = you (optional countersign).

   Mapping:

   Set `customFields`: deal_id, template_id. Email subject: `Agreement — {{client_legal_name}}`.

   Failure mode:

   Wrong DocuSign account (demo vs prod) — Router switches account by `is_test`.

7. Step 7

   Stripe — Create a payment link (conditional)

   If `payment_terms` = 50-deposit: amount = fee_total × 0.5 in cents; metadata.deal_id.

   Mapping:

   Line item name: `Retainer deposit — {{client_legal_name}}`; redirect URL = thank-you page.

   Failure mode:

   Currency mismatch — pass `fee_currency` explicitly; never assume USD in multi-currency deals.

8. Step 8

   Gmail — Send email (proposal sent)

   To signer: DocuSign sign link + Stripe Payment Link URL in body (if deposit).

   Mapping:

   Body template per template_id branch; BCC yourself on first 10 live deals.

   Failure mode:

   Link rot — generate fresh Payment Link per deal; never reuse static link.

9. Step 9

   HubSpot — Update a deal

   Stage → "Agreement sent"; properties: envelope_id, payment_link_url, sent_at.

   Mapping:

   Store DocuSign envelopeId from step 6 response.

   Failure mode:

   CRM update fails but client got email — idempotent retry on deal_id.

10. Step 10

    Webhooks — Custom webhook (DocuSign Connect listener scenario)

    Separate scenario: on `envelope-completed`, download combined PDF, file to Drive, send countersigned email.

    Mapping:

    Parse DOCUSIGN_CONNECT_WEBHOOK_EXAMPLE shape; lookup deal by custom field deal_id.

    Failure mode:

    Connect retry storm — dedupe on envelopeId in Data store before Drive upload.

n8n Build: Same Pipeline with Node Names

Same pipeline in n8n — node names from the editor. Self-hosters: store deal_id dedupe in static data or Redis; cloud users can use n8n Data table.

1. Step 1

   Webhook (POST /agreement-send)

   Receive normalized payload from HubSpot workflow HTTP action or internal form.

   Mapping:

   Respond immediately 200; pass body to next node.

   Failure mode:

   No auth — add Header Auth `X-Agreement-Token` and IF node to reject.

2. Step 2

   Set (Edit Fields)

   Map incoming JSON to canonical keys; compute `client_slug` with Code node if needed.

   Mapping:

   Same shape as NORMALIZED_PROPOSAL_PAYLOAD_EXAMPLE.

   Failure mode:

   Undefined merge fields — Code node throws on missing required keys.

3. Step 3

   IF

   Branch: production vs test vs error (missing signer_email).

   Mapping:

   `{{ $json.is_test }}` equals false AND email contains `@`.

   Failure mode:

   False negatives on email — trim whitespace in Set node.

4. Step 4

   HTTP Request (PDFMonkey)

   POST document generation; Authentication: Bearer API key.

   Mapping:

   JSON body with template_id + fee_total + governing_law + client_legal_name.

   Failure mode:

   429 rate limit — Wait node 3s + retry once.

5. Step 5

   HTTP Request (Download PDF)

   GET download_url from previous response when status = success.

   Mapping:

   Binary property `data` for DocuSign upload.

   Failure mode:

   Binary not passed — set Response Format to File in HTTP node.

6. Step 6

   DocuSign (Create Envelope)

   Use n8n DocuSign node or HTTP to REST `/envelopes` with base64 PDF.

   Mapping:

   customFields: deal_id; recipients.signers[0].email = signer_email.

   Failure mode:

   OAuth token expired — refresh credential before go-live week.

7. Step 7

   Stripe (Create Payment Link)

   Only when payment_terms matches deposit pattern; metadata.deal_id required.

   Mapping:

   amount: Math.round(fee_total * 0.5 * 100) in Code node for cents.

   Failure mode:

   Float cents error — always integer cents in Code node.

8. Step 8

   Gmail (Send)

   HTML email with sign URL + payment link; attach nothing (links only).

   Mapping:

   Subject line includes client_legal_name for searchability.

   Failure mode:

   Gmail daily cap — Workspace account required above ~10 deals/day.

9. Step 9

   HubSpot (Update Deal)

   Patch deal stage and custom envelope_id property.

   Mapping:

   Use deal_id from payload as object ID lookup first if webhook lacks HubSpot id.

   Failure mode:

   Wrong deal updated — never search by company name alone; always deal_id.

10. Step 10

    Webhook (DocuSign Connect) → Google Drive → Gmail

    Second workflow: envelope-completed → upload to `/Agreements/` → send countersigned copy.

    Mapping:

    Drive folder path uses client_slug from Data store keyed by deal_id.

    Failure mode:

    Duplicate uploads on Connect retry — IF node checks envelopeId in static data.

Human QA Gates (Legal & Money Stops Here)

Money and enforceability stop here. Automation merges approved templates — it does not replace counsel on new deal shapes.

• Legal entity name matches counterparty

  PDF title block and DocuSign recipient company field match signed LOI or email confirmation.

  When: Every placement fee and B2B SOW until template proven

• Fee table arithmetic

  Retainer math, placement fee %, and deposit amount match verbal agreement on call.

  When: Before DocuSign envelope sends — automation cannot fix wrong numbers

• Governing law and liability caps

  Template clause matches your jurisdiction; no AI-drafted indemnity without counsel on new deal types.

  When: First use of each template_id in production

• Stripe livemode + Payment Link amount

  Test card in test mode; live deal uses live link with correct cents integer.

  When: Before first live deposit link goes out

• DocuSign Connect dedupe fire drill

  Replay envelope-completed webhook twice — one Drive file, one countersigned email.

  When: Before marking Connect workflow live