I still meet teams that build every proposal by hand. They copy the deal into a doc, fix formatting, hunt for the right pricing table, then wonder why velocity stalls at the end of the month. The fix is not "work faster." It is removing the assembly step entirely. Here is the workflow I walk customers through when they want a first proposal out the door in about a minute after setup is done.

This guide assumes you use HubSpot for deals and are fine with Google Slides or Docs for your template. Portant also supports Microsoft formats, but Slides is a fast path for polished proposals. You will install from the HubSpot marketplace, connect your workspace once, then reuse the same pattern on every deal.

Before you start: checklist

  • A HubSpot deal with contact, company, and line items populated the way you want them on paper
  • A proposal template in Google Slides or Google Docs with clear placeholders for names, scope, and pricing
  • Admin access to install Portant and approve OAuth scopes

If line items are messy, fix them first. Automation copies what you store. Clean data beats a pretty template with wrong totals.

Step 1: Install Portant from the HubSpot marketplace

Open the HubSpot marketplace listing for Portant and install the app to your portal. Complete the OAuth prompts and connect the Google account that owns your template files. If your IT team requires a review, send them the HubSpot integration overview and the doc on how we connect Google and HubSpot safely.

After install, confirm you can open Portant from a deal record. If you cannot, fix permissions before you touch templates. Nothing downstream works if the app cannot read the deal.

While you are in the marketplace, note that Portant is a HubSpot Certified App and a HubSpot Essential App for 2025. That matters when your security team asks whether the integration is a side project or a primary product bet. We are also rated 4.9 out of 5 on the HubSpot Marketplace and G2, which usually helps internal champions move reviews along.

Step 2: Pick or create your proposal template

Start from a template your team already trusts. If you want a ready made HubSpot pattern, browse the simple HubSpot proposal in Slides or the personalised proposal automation example. Duplicate it into your workspace so you are not editing the public sample directly.

Label sections the way reps think: executive summary, scope, pricing, terms, next steps. You can add conditional logic later so optional modules appear only when a deal property says so. For your first pass, keep the structure boring and reliable.

If you sell multiple products, consider one base template with modules toggled by deal type rather than ten nearly identical decks. Reps should recognize the layout instantly. Brand and legal should bless one master structure. Ops should own the branch rules. When those three agree, adoption sticks.

Step 3: Insert HubSpot merge tags

Replace static text with merge fields for contact first name, company name, deal amount, close date, and any custom properties your proposal requires. For pricing tables, use line items so quantities, discounts, and totals stay aligned with the deal.

Preview with a real deal before you go live. I always ask teams to pick their messiest recent opportunity, not the happy path demo deal. If the template survives the messy deal, it will survive the quarter.

For pricing, decide whether you show list price, net price after discounts, or both. Finance and sales should agree on what the buyer is allowed to see. Merge the same fields your quotes would use so there is never a mismatch between what the AE promises and what operations invoices later.

Step 4: Create the workflow trigger

In Portant, define when to generate the proposal. Common patterns include deal stage moves to "Proposal sent," a button on the deal, or a workflow action your RevOps team already uses. The goal is one obvious action for reps, not five optional paths.

Wire document workflows so generation, optional manager notification, and email handoff happen in sequence. If legal needs to see exceptions, add an approval step only for deals over a threshold. Keep the default path fast.

Step 5: Generate, send, and track

Open the deal, run the workflow, and let Portant render the Slides or PDF. Send through your connected email so the thread stays human. After send, rely on HubSpot timeline events and document records to see opens and signatures without asking the rep for a forward.

For the bigger picture on proposals in HubSpot, read proposal automation for HubSpot. It lines up with the same object model you just used.

Common blockers and quick fixes

Blank merge fields. The generator did its job. The property is empty. Fix the deal, add a validation rule, or mark the field required before the stage that triggers send.

Wrong Google account connected. The template lives in a shared drive, but OAuth went to a personal account. Reconnect with the workspace identity that owns the canonical template folder.

Line items look right in HubSpot but wrong on paper. Check product descriptions, hidden discounts, and currency properties. Line item tables need the same discipline as your CRM hygiene.

Reps skip the workflow. Usually the manual path is still faster for edge cases. Add a light exception process, then close the gap with better templates so the automated path wins on speed every time.

Scaling the same pattern across teams

When you roll out beyond one region, clone the template per segment only if language or compliance truly differs. Otherwise use properties for localized terms and keep one structure. Fewer masters mean fewer midnight emergencies when legal updates a clause.

Pair enablement with short Looms recorded on real deals. People imitate video faster than they read a twenty page playbook. Celebrate the first rep who clears a full week without a manual proposal. Momentum is social.

What to measure in your first 30 days

Track median time from "ready to propose" to "sent," count of proposals sent per rep, and reprint rate after errors. If reprints drop and time to send falls, you have a story for leadership that does not rely on vibes. Teams that adopt Portant often cite about 125 hours reclaimed per month and about $24,000 average annual savings once busywork leaves the critical path. Your pilot should aim to show directionally similar relief on the one workflow you picked.

Layer in buyer side signals when you can. If your stack supports it, note when prospects open the proposal and how long they spend on pricing pages. Reps sell smarter when they know whether silence means "not interested" or "still routing internally." Combine CRM tasks with those signals so follow up feels helpful, not random.

Finally, write down the top five support questions you get in week one. If the same question repeats, fix the template or the training, not the rep. Good automation is boring on the outside and disciplined on the inside.

If you want a single reference for the full platform story after proposals are live, bookmark the complete guide to document automation in HubSpot. It connects quotes, contracts, and follow through in one narrative your enablement team can reuse. Treat that guide as the syllabus, and this article as the first lab.

What "60 seconds" actually means

After setup, the clock starts when the deal is clean and the rep clicks generate. The first time you do this, budget an hour for template and workflow work. That is the investment. The payoff is hundreds of one minute sends later. If you want deeper automation across quotes and contracts, continue with the complete guide to document automation in HubSpot.

Frequently asked questions

Can we use Word instead of Google?

Yes. Connect Microsoft 365 and map the same merge fields into a Word template. The steps parallel what you did in Slides.

What if proposals need a custom introduction?

Add a short free text property on the deal for narrative intro, merge it near the top, or use AI assisted drafting with human review for the first paragraph. Never let AI invent legal terms.

How do we prevent wrong templates?

Restrict template libraries by team, use deal type properties to branch, and train managers to spot check the first week of go live.

Do we need a developer for custom objects?

Not for most proposals. Standard deals, contacts, companies, and line items cover the majority of use cases. Custom objects help when your commercial model maps to something beyond those four.

Can proposals include attachments or appendices?

Yes, when your template references merged sections or linked assets your process already trusts. Keep heavy files out of email when possible. Prefer links to a secure resource with a clear name.

How does this relate to quotes and contracts?

Same engine, different templates. Many teams automate the proposal first, then add contract automation once pricing language stabilizes. The goal is one habits stack inside HubSpot.