Storydoc + HubSpot Proposal Automation Workflow

Most sales teams are still copy-pasting deal details into a Google Slides deck, exporting a PDF, and attaching it to an email they wrote from scratch. That process takes 45 minutes per deal on a good day. It also produces a static artifact you can never track. I’ve watched reps at Series A companies lose deals because they had no idea the champion forwarded the proposal to a skeptical CFO who bounced after the pricing slide. No alert. No signal. Nothing.

Storydoc changes the output format. HubSpot anchors the record. Make is the glue that makes both tools talk without anyone touching a keyboard. This tutorial walks the full workflow, end to end.

Why This Stack and What You’re Building

The goal: a rep moves a deal to “Proposal” stage in HubSpot and, within 90 seconds, a fully personalized Storydoc story exists. The prospect’s name, company, use case, and pricing are pulled directly from deal properties. A share link lands on the deal record. A follow-up enrollment fires only when the prospect actually opens the deck, not on a three-day timer.

Storydoc is worth calling out specifically because it tracks engagement at the section level. You can see that a viewer spent 4 minutes on the ROI slide and skipped the team slide entirely. That signal is ten times more actionable than a generic “proposal opened” ping from PandaDoc, and I’d push back on anyone who says otherwise. Storydoc’s own benchmark data shows interactive presentations close at higher rates than static PDFs. I’ve seen that hold directionally true across the B2B SaaS clients I work with at Homegrown Growth Co. The HubSpot Research Sales Trends report consistently flags follow-up timing as a top close-rate driver, which is exactly what this automation addresses.

The Full Workflow, Step by Step

Before you build: you need a Storydoc account with API access (Business plan or above), a HubSpot account with custom deal properties enabled, and a Make account. You also need a Storydoc template already built with merge variable placeholders for company_name, contact_first_name, use_case, and pricing_tier. Set those up in Storydoc’s template editor before touching the automation. Skipping this step and building the Make scenario first is the single most common mistake I see on first deploys.

// Make Router filter condition
// Branch 1: proceed to Storydoc
{
  "condition": "{{deals.associations.company.name}}",
  "operator": "not_empty"
}

// Branch 2: Slack alert
{
  "condition": "{{deals.associations.company.name}}",
  "operator": "is_empty",
  "action": "POST /slack #rev-ops-alerts",
  "message": "Deal {{deals.id}} hit Proposal stage with no company association. Proposal not sent."
}

// Storydoc API call body (Branch 1)
{
  "template_id": "YOUR_TEMPLATE_ID",
  "variables": {
    "company_name": "{{deals.associations.company.name}}",
    "contact_first_name": "{{deals.associations.contact.firstname}}",
    "use_case": "{{deals.properties.primary_use_case}}",
    "pricing_tier": "{{deals.properties.pricing_tier}}"
  }
}

What This Gets You and Where to Extend It

Once this is running, you have a closed loop. Deal stage change creates a trackable proposal. Engagement data lands on the deal record automatically. Follow-up sequences fire on real buyer intent signals rather than arbitrary time delays.

The first extension I build for clients after this is a Gong alert that fires when a deal has been in Proposal stage for more than five days without a single Storydoc view. That is a dead proposal. The rep needs a phone call, not another drip email.

If your team needs e-signature on top of engagement analytics, don’t try to squeeze PandaDoc into the Storydoc slot. Use them sequentially. Storydoc handles the “sell the vision” moment. PandaDoc closes the paperwork. They are not competitors in a well-designed proposal stack. They serve different jobs at different points in the same conversation. That hand-off can also be automated: when Proposal View Count exceeds 3 in HubSpot, trigger a PandaDoc document send via Make using the same contact and deal data you’ve already mapped.

The whole workflow takes about four hours to build the first time. After that, every rep on your team sends a consistent, trackable, personalized proposal in under two minutes of their own effort. That is the version of sales operations that actually moves close rates.