Last verified: November 22, 2026
What You Can Now Do
Context Memo now ships an interactive sales funnel canvas on the Performance page: you can build and configure the canvas, map your pipeline stages to funnel stages, view conversion problems, and set goals for each stage. The change is in what you see first. Instead of reading stage counts as a list and inferring health, you look at a diagram that shows volume moving between stages and flags the transitions where it drops. The task this replaces is the weekly guess about where the pipeline is actually breaking. You stop asking "does this look normal?" and start answering "stage three is converting below the goal we set, and it has been for three cycles."
Where It Is in Context Memo
Open the Performance page. The Funnel Canvas sits there as its own view. On that screen you'll find the canvas itself, your mapped pipeline stages rendered as connected funnel stages, automatic problem detection on the transitions between them, and the goal field for each stage. Configuration happens in the same place as viewing, so you aren't moving between a settings page and a reporting page to adjust a mapping.
How to Use It
- Go to the Performance page and open the Funnel Canvas. You'll see an empty canvas ready for configuration if this is your first visit.
- Map your existing pipeline stages to funnel stages. Each mapped stage appears on the canvas as a node, connected in sequence, so the diagram matches the pipeline you already run rather than a template.
- Review the problems the canvas surfaces automatically. Conversion bottlenecks are flagged on the transitions where volume drops off, so you can see which handoff is costing you deals before you open a single deal record.
- Set a goal on each stage. The canvas then shows stage performance against that target instead of in isolation, which is what turns a number into a signal.
- Return to the canvas on your reporting cadence, weekly or monthly, and compare flagged transitions to the goals you set. Stages that stay flagged across cycles are structural problems, not noise.
Why We Built It
Customers kept telling us the same thing: they could see their stage counts but couldn't see their funnel. Knowing that 40 opportunities sit in one stage tells you nothing about whether that stage is working, because there was no stage-level target to measure it against and no view of what happened at the transition before it. The cost was measured in reaction time. Deals got stuck in a stage for weeks, and the problem only became visible when the quarter came in short, which is too late to fix the stage that caused it. The canvas puts the whole funnel on one screen, marks the transitions where volume is leaking, and holds each stage against a goal you set deliberately.
What It Does Not Do Yet
Stage mapping is a manual step. You map your pipeline stages to funnel stages yourself the first time you configure the canvas, and you'll need to revisit that mapping if you change your pipeline structure. We chose manual mapping on purpose, because pipeline stage names vary enough between teams that an automatic guess would be wrong often enough to erode trust in the diagram. Problem detection runs on the transitions the canvas can see, which means its output is only as good as the mapping you give it. Check the mapping first when a flag looks wrong.
Goals are set per stage, individually. There is no bulk goal import or goal templating in this release, so configuring a funnel with many stages takes a few minutes of deliberate input. That's the right trade for now: goals you set one at a time are goals you've thought about.
This is pipeline visualization, not pipeline management. The canvas reads your stages and shows you where conversion is breaking. It does not move deals, change stage definitions, or write back to your CRM. Keep your CRM as the system of record. Context Memo integrates with HubSpot, and the canvas is built to sit alongside that system rather than duplicate it.
One practical note on fit: the canvas is useful in proportion to the pipeline data behind it. If you've only recently connected your pipeline, give the stages time to accumulate volume before you read bottleneck flags as fact. A transition flagged on four deals is a hypothesis. The same flag on four hundred is a finding.
