Most sales teams know how many proposals they send each month. Far fewer know how many actually get opened. And almost no one can tell me, stage by stage, where deals go quiet between "sent" and "signed."
That gap matters. If you're creating 50 proposals a month but only 20 get viewed, you don't have a pricing problem. You have a delivery problem. The fix might be as simple as changing when you send or checking that emails aren't landing in spam. But if 40 get viewed and only five get signed, the issue is different. Maybe the pricing structure doesn't match what was discussed. Maybe the proposal doesn't answer the buyer's real question.
A proposal engagement funnel gives you that clarity. Instead of treating proposals as a black box between "sent" and "closed," you can see each step of the journey and find the exact point where deals stall.
Why proposal engagement visibility matters
When I work with sales managers who are frustrated by low close rates, the conversation almost always starts at the pipeline level. "We need more deals." Or "Our reps aren't closing fast enough." These are real concerns, but they're symptoms.
The question that usually gets skipped is: what happens to the proposal after it leaves HubSpot?
Without visibility into document engagement, managers are coaching blindly. They can see deals in a pipeline, but they can't see whether a buyer actually opened the proposal, reviewed the pricing, or shared it with their procurement team. That missing data means the coaching conversation defaults to "What's the status?" instead of "Here's where this deal stalled, and here's what to try next."
Funnel-level visibility changes that conversation. When you can see that 80% of proposals are getting viewed but only 15% are getting signed, you know the problem isn't reach. It's content, pricing, or timing. When you can break that data down by rep, template, or deal stage, the next action becomes obvious.
What a healthy proposal funnel looks like
I think of the proposal funnel in seven stages, each representing a different level of buyer commitment:
- Created: the document exists in your system
- Sent: it reached the buyer's inbox
- Viewed (1+): the buyer opened it at least once
- Viewed (3+): the buyer returned to review it multiple times
- Signature requested: an eSignature was added to the document
- Signed: the buyer signed
- Completed: all parties signed and the process is done
Each transition tells you something different. The drop between Sent and Viewed is about delivery and attention. The drop between Viewed and Signed is about content and conviction. The drop between Signed and Completed is often about internal process on the buyer's side, or friction in your signing flow.
In a healthy B2B proposal funnel, I'd expect 70 to 85% of sent proposals to be viewed at least once. Below 60% usually signals a delivery problem. Repeat views (3+) are a strong buying signal. They often mean the document is being shared internally or reviewed against a budget. When repeat view rates are very low, your proposals may not be giving buyers enough substance to bring into their internal conversations.
Where teams typically leak
The most common leak is between Sent and Viewed. Managers tend to overlook it because they assume delivery equals attention. Some reasons proposals go unviewed:
- The email lands in spam or a promotions tab
- The subject line doesn't give the buyer a reason to open
- Timing is off (sent late on a Friday or during a holiday week)
- The sender isn't someone the buyer recognizes
The second most common leak is between Viewed and Signed. This one is harder to diagnose because it could involve content, pricing, legal friction, or a deal that was never as warm as the rep believed. But patterns across many proposals narrow it down. If every proposal to a specific industry stalls at the same point, you likely have a template or positioning problem. If the stall rate is consistent across templates but varies by rep, it's a selling or timing issue.
A less obvious leak happens between Signature Requested and Signed. The buyer is engaged, the proposal has been reviewed, and an eSignature has been requested. But nothing happens. This is often about friction in the signing experience itself. If signing requires a desktop browser, multiple form fields, or a confusing redirect, some buyers simply don't complete it.
The Portant properties that power the funnel
When you use Portant's HubSpot integration, every document created through Portant becomes its own Custom Object record inside HubSpot. This is what makes the funnel report possible. Each document record carries properties that track its journey:
- Document Status: tracks the lifecycle stage. Values include Pending, Draft, Approved, Sent, Signature Requested, Partially Signed, Signed, and Completed.
- Number of Times Viewed: counts how many times the recipient opened the document.
- Document Created: the timestamp of when the document was generated.
Because these are native HubSpot properties on a Custom Object, you can filter, group, and report on them the same way you report on deals, contacts, or companies. No CSV exports. No switching to another tool's analytics dashboard.
You can see your created documents directly in HubSpot by visiting the Portant Document Object view in the docs. From there, you can build lists, filters, and the funnel report I'll walk through next.
Building the funnel report step by step
Here's how I set one up in HubSpot.
1. Open the report builder
Go to Reports in the main navigation and click Create Report. Choose Custom Report Builder so you have full control over data sources and filters.
2. Select your data source
Choose the Portant Document custom object as your primary data source. If you want to cross-reference deal data like deal amount or pipeline, add Deals as an associated object.
3. Set up your funnel stages
Use the Document Status property as your stage dimension. Order the values to match the natural progression:
- Pending
- Draft
- Approved
- Sent
- Signature Requested
- Partially Signed
- Signed
- Completed
Not every document passes through every stage. Some skip from Sent directly to Signed if no formal signature request step is needed. That's fine. The report shows you where documents actually land.
4. Add date filters
Filter by Document Created to scope the report to a specific period. I recommend starting with the last 90 days so you have enough data for patterns without noise from older records. Rolling date filters like "this month" or "this quarter" make the report useful for recurring reviews.
5. Add breakdowns
Once the basic funnel works, add dimensions to slice the data:
- Deal owner to compare performance by rep
- Deal pipeline if you run separate pipelines for different products or regions
- Template name to see whether certain proposal templates convert better than others
6. Save and share
Save the report to a dashboard your sales managers review weekly. I place it alongside deal velocity and pipeline value reports so the document funnel sits in context. If deals are moving but proposals aren't being signed, the document process needs attention. If proposals are moving but deals are stalling, the bottleneck is somewhere else.
How to interpret funnel data
Once the report is running, here's what I look for at each transition.
Low sent-to-viewed ratio (below 60%). This is a delivery problem, not a content problem. Check email deliverability, sending times, and whether the recipient is the right contact. Review whether the email that accompanies the document gives the buyer a clear reason to open it.
High views, low signature rate. The document is reaching buyers, but it's not closing them. Look at the proposal content. Is the pricing clear? Does the scope match what was discussed? Are there objections the proposal doesn't address? I also check length. A 20-page proposal for a straightforward deal can lose buyers just as quickly as a thin one-pager for a complex sale.
High single views, low repeat views. Buyers are glancing but not studying. This often means the proposal lacks the detail a CFO or procurement lead needs to review. Adding a clear pricing summary, a timeline, and specific deliverables often increases repeat views.
Stalled at Signature Requested. The buyer is engaged but not signing. Check whether the signing experience works well on mobile. Check whether the legal language is creating hesitation. Simplifying the signing flow can improve conversion more than rewriting the proposal itself.
Upstream fixes vs downstream fixes
A funnel tells you where to focus. Without one, you're guessing. With one, you can split improvement work into two categories.
Upstream fixes address problems before the buyer sees the document:
- Adjust send times based on when proposals get the most opens
- Write subject lines and preview text that give buyers a reason to click
- Confirm you're sending to the decision-maker, not just the first contact on the deal
- Check spam and deliverability settings for your sending domain
Downstream fixes address problems after the document is viewed:
- Review your proposal template for clarity on pricing, scope, and next steps
- Test shorter vs. longer formats to find the right depth for your typical deal size
- Simplify the signing experience with fewer fields and mobile-friendly layouts
- Add follow-up automation that triggers when a proposal is viewed but not signed within a set window
The goal is to fix the weakest link in the funnel first. If only 40% of proposals are being viewed, improving the proposal template won't move the needle until you fix the delivery problem.
Using funnel data for rep coaching and template optimization
One of the most useful things I've done with proposal funnels is bring them into one-on-one coaching sessions. Instead of reviewing deals in the abstract ("What's happening with the Acme deal?"), managers can pull up the funnel filtered by deal owner and talk about real numbers.
If a rep's proposals get viewed at a high rate but don't get signed, the coaching conversation shifts to proposal content and objection handling. If another rep's proposals aren't being viewed at all, the conversation shifts to email delivery and sending habits. This is more productive than "Why haven't you closed more deals this month?" because it points to a specific stage that needs work.
Template optimization follows the same logic. If you run multiple proposal templates, the funnel shows which ones convert at higher rates. A template that looks polished but consistently stalls at the viewing stage might need a simpler layout or a different delivery email. A template with a strong sign rate is worth studying and replicating across the team.
Frequently asked questions
Do I need Portant to build this funnel?
You need document engagement data inside HubSpot as reportable properties. Portant creates a Custom Object for each document with status, view count, and timestamp properties that make this type of reporting possible. Without that data in HubSpot, you would need to track each step manually or export from a separate tool.
How often should I review the funnel?
Weekly works well for managers running active sales teams. Monthly is enough for smaller teams or longer sales cycles. The key is consistency. A funnel is most useful when you compare trends across time, not just a single snapshot.
What if I don't have enough data yet?
Start building the report with whatever data you have, even if it's only a few weeks of documents. The structure matters more than the volume at first. As data grows, patterns become clearer. I usually see meaningful signals after about 50 to 100 proposals flow through the system.
Can I use this for documents other than proposals?
Yes. The same funnel concept works for contracts, quotes, or any document that follows a creation-to-completion lifecycle. The Document Status property tracks the same stages regardless of document type. You can filter the report by template or document type to build separate funnels for each category.
