Missing features

When a prospect doesn’t buy because you’re missing a feature they need, that’s valuable information. Tracking these feature requests helps you prioritize your product roadmap and — when features are implemented— automatically identifies warm prospects to contact.

This article covers how missing feature tracking works in Rizer, how to set it up, and how to turn feature gaps into won-back revenue.

Why track missing features

Every lost deal teaches you something. When the lesson is “we need to build X,” capturing that systematically creates two opportunities.

Product roadmap prioritization

Product teams constantly decide what to build next. They have ideas from customers, prospects, internal stakeholders, and their own vision. Missing feature tracking adds hard data to these decisions.

Instead of “some prospects have asked for Salesforce integration,” you can say “we’ve lost $750,000 in deals because we don’t have Salesforce integration, with an average importance rating of 4.5 out of 5.”

That’s a different conversation. Revenue impact and importance ratings help product teams prioritize based on business value, not just gut feeling or who speaks loudest.

Automatic re-engagement

Here’s where missing feature tracking really shines: when a feature is implemented, Rizer automatically moves affected deals to Ready for callback.

Think about what this means. You implement a feature, and instantly you have a list of prospects who specifically asked for that thing. They’re warm leads — they already evaluated you, liked what they saw except for this gap, and now the gap is filled.

Without tracking, you’d have to manually remember which deals wanted which features and reach out one by one. With tracking, it happens automatically. Implement the feature, get the list, start the conversations.

The main view of your feature gap data lives at Features inside the main menu.

What you’ll see

The report displays a table with your missing features:

Status — Current development status of the feature (Unplanned, Planned, Implemented, Rejected).
Missing feature — The feature name and which of your products it relates to.
Avg importance — Average importance rating across all deals that requested this feature. Scale of 1-5, where 5 means deal-breaker.
Value — Total value of deals lost because of this missing feature. This is the revenue impact.
Build cost — Your estimated cost to build the feature, if you’ve entered one.
Net value — Value minus build cost. The potential ROI if you built it.
Value/Cost — Ratio showing return on investment. Higher numbers mean better ROI.
Last requested — When this feature was most recently mentioned in a lost deal.

The report is sortable. Click column headers to sort by value (highest impact features), importance (most critical to prospects), or status.

Filtering the report

Narrow down the data:

Product filter — See missing features for specific products. Useful when focusing on one product line.
Status filter — See only features in a particular status. For example, filter to “Planned” to see what’s coming.
Importance — See missing features by how important they are to your future customers.

Reading the data

The report answers questions like:

Which missing features are costing us the most revenue?
Which features are deal-breakers vs. nice-to-haves?
What’s the potential ROI of building specific features?
What are prospects asking for most recently?

Look for features with high value and high importance. These are causing real pain — prospects want your product but can’t buy without this capability. They’re your highest-priority opportunities.

Drilling into details

Click the arrow next to any feature to see the individual deals affected:

Company name
Deal value
Importance rating for that specific deal
Lost date
Contact information
Current recycling status

This drill-down shows exactly who wanted this feature. When it’s implemented, these are the prospects to contact.

Setting up missing features

Before you can track feature gaps, you need to configure your missing features in Rizer.

During onboarding

When you first set up Rizer, the onboarding wizard includes a missing features step. The AI scans your HubSpot deal history looking for feature requests mentioned in deal notes.

For each suggested feature, you can:

Accept it (it’s a real feature request)
Edit the name (clarify or standardize)
Remove it (it’s not actually a feature gap)
Assign it to a product
Set the current status

This gives you a starting point based on your actual deal data.

Adding features later

To add a missing feature after onboarding:

Go to Features
Click + Feature
Select which product this feature relates to
Enter the feature name
Set the current status
Optionally enter build cost and expected dates
Click Save

The feature now appears in dropdown lists when recycling deals.

Feature fields explained

Product — Which of your products this feature relates to. If it’s a platform-wide feature, you might assign it to multiple products or a general category.
Feature name — A clear, consistent name. Avoid variations like “Salesforce integration,” “SFDC sync,” and “integrate with Salesforce” as separate features — pick one name and use it.
Status — Where the feature is in your development process (covered in detail below).
Build cost — Your estimated cost to build this feature. This enables ROI calculations. Enter in your default currency.
Expected completion date — For planned or in-progress features, when you expect to be implemented. This helps with callback timing.
Release date — For implemented features, when it actually was implemented.

Feature statuses

Each missing feature has a status reflecting where it is in your development process.

Unplanned

The feature isn’t on your roadmap. You’re tracking the request but haven’t committed to building it.

Most features start here. You’re collecting data on demand before deciding whether to build.

Callback behavior: Deals linked to unplanned features use their standard callback date based on the recycle reason. They don’t auto-trigger based on the feature.

Planned

The feature is on your roadmap but work hasn’t started. You’ve decided to build it — the question is when.

Set an expected completion date when you move a feature to Planned. This helps with reporting and sets expectations.

Callback behavior: Deals can have their callback date set to align with the expected completion. “When feature is implemented” becomes a meaningful callback option.

Implemented

The feature has been implemented and is available. This is the trigger that matters.

When you mark a feature as Implemented:

Set the actual release date
All deals linked to this feature automatically move to Ready for callback
Your team gets notified that these prospects are ready for re-engagement

This is the magic moment. Implement a feature, instantly get a list of warm prospects who wanted exactly that thing.

Callback behavior: Deals auto-trigger to Ready for callback regardless of their scheduled callback date.

Rejected

You’ve decided not to build this feature. Maybe it doesn’t fit your product vision, the market has moved on, or the cost isn’t justified by the demand.

Setting this status is honest. It keeps your feature list clean and sets proper expectations.

Callback behavior: Deals linked to Rejected features don’t auto-trigger. They use their standard callback date. You might still win these deals back for other reasons, but not because you built this feature.

Recording missing features when recycling

Feature gap data gets captured when you recycle a deal. Here’s how to record it properly.

When to link a missing feature

Link a deal to a missing feature when:

The prospect explicitly said they need a capability you don’t have
A feature gap was a significant factor in their decision
They would have bought if you had this feature

Don’t link a feature when:

It was mentioned in passing but wasn’t a real factor
You’re guessing about what they might have wanted
The primary reason for loss was something else entirely

Quality matters more than quantity. Accurate links lead to accurate data and effective re-engagement.

The missing feature section

When recycling a deal — whether from HubSpot or Rizer — you’ll see a missing feature section in the form.

Selecting a feature

Choose from features you’ve already configured:

Click the feature dropdown
Select the relevant feature
If it’s not in the list, click + Add new to create it

You can link multiple features if more than one gap contributed to the loss. But be thoughtful — if you link every possible feature, the data becomes less useful.

Importance rating

Rate how important this feature was to the deal, from 1 to 5:

5 — Deal-breaker They absolutely could not proceed without this feature. It was the primary reason for the loss. If you had it, they would have bought.
4 — Very important A major factor in their decision. Not the only reason, but significant. Having the feature would have substantially improved your chances.
3 — Important Would have meaningfully improved their experience with your product. A real consideration, but not decisive on its own.
2 — Nice to have They mentioned it and it would have been helpful, but it wasn’t a significant factor in the decision.
1 — Minor Came up in conversation but didn’t really matter to their decision. Barely worth tracking.

Why importance matters

Importance ratings help prioritize:

A feature with 10 deals at importance 5 is more urgent than one with 10 deals at importance 2
Value times importance gives a truer picture than value alone
Features that are deal-breakers deserve more attention than nice-to-haves

When reviewing the Missing Features report, look at both total value and average importance. A feature with moderate value but very high importance might be more strategic than one with high value but low importance.

The feature-to-callback connection

The real power of missing feature tracking is the automatic connection to callbacks.

How it works

You recycle a deal with recycle reason “Missing feature”
You link it to a specific feature, say “Salesforce integration”
The deal goes to Recycling, waiting
Months later, your product team finishes building Salesforce integration
Someone marks the feature as Implemented in Rizer
All deals linked to that feature automatically move to Ready for callback
Your team sees these deals in their ready queue with “Feature implemented” as the trigger

No manual tracking required. No remembering which deals wanted which features. Implement the feature, get the prospects.

Setting up for auto-callback

To make sure deals auto-trigger when features are implemented:

When recycling:

Select “Missing feature” as the recycle reason (or include it if multiple reasons apply)
Link to the specific feature
Set the callback date to “When feature is implemented” if that option is available, or set a fallback date

When managing features:

Keep feature statuses updated as development progresses
Mark features as Implemented promptly when they ship
Include the actual release date

What happens when a feature is implemented

When you mark a feature as Implemented:

Go to Features
Find the feature and click the menu icon
Click Edit
Change status to Implemented
Enter the release date
Click Save

Immediately:

All deals linked to this feature move to Ready for callback
The “Triggered by” field shows “Feature Implemented”
Your team can see exactly why these deals are ready

Managing your feature list

Over time, your missing features list will need maintenance.

Adding new features

Add features when:

A prospect mentions a capability you don’t have
You notice a pattern in loss reasons that relates to a feature gap
Your product team identifies a gap worth tracking

Don’t wait for onboarding AI to find everything. If you’re recycling a deal and the relevant feature isn’t in your list, add it on the spot.

Editing features

Update feature information when:

Development status changes (Unplanned → Planned → Implemented)
Expected completion dates shift
You want to refine the name or product association
Build cost estimates change

To edit:

Go to Features
Click the menu icon next to the feature
Click Edit
Update the fields
Click Save

Merging duplicates

Sometimes the same feature ends up in your list multiple times with different names. “Salesforce integration,” “SFDC sync,” and “Salesforce connector” might all refer to the same thing.

To merge:

Identify duplicates
Decide which name to keep
Edit deals that reference the wrong name to use the correct one

Handling implemented features

Once a feature is implemented and you’ve re-engaged the affected deals, the feature stays in your list with Implemented status. This is fine — it’s historical data.

Over time, implemented features accumulate. You can filter the report to hide them if the list gets long, but there’s no need to delete them.

Common questions

What if a feature is partially built?

If you’ve built something that partially addresses the request, you have options:

Keep the status as Planned until it fully ships
Mark it Implemented and note the scope in your re-engagement
Create a new feature for the remaining gap

The right approach depends on whether the partial solution would satisfy the prospects who requested it.

Should I track every feature request?

Track features that:

Come up multiple times
Have real revenue impact
Are potential roadmap candidates

Skip features that:

Were mentioned once in passing
Have minimal impact
Are clearly out of scope for your product

The goal is useful data for prioritization, not an exhaustive list of everything any prospect ever mentioned.

How do I handle features that take years to build?

For long-term features:

Keep them in Planned status
Update expected dates as timelines evolve
Consider whether deals should wait that long or use other callback triggers

A deal recycled with a 2-year feature dependency might need a fallback callback date. Circumstances often change in 2 years regardless of the feature.

Can prospects be linked to multiple features?

Yes. A single deal can be linked to multiple missing features if several gaps contributed to the loss. Each link gets its own importance rating.

When any of those features are implemented, the deal becomes ready for callback. You might reach out about one feature while others remain missing — that’s fine. Partial improvement is still worth communicating.

What if a feature ships but the prospect already bought elsewhere?

This happens. When you re-engage, you’ll learn the prospect’s current situation. Maybe they:

Went with a competitor but are unhappy
Built something themselves that’s not working well
Found another solution they’re satisfied with
Are now evaluating again for expansion or other reasons

The feature getting implemented creates a reason to reach out. What you learn in that conversation determines next steps. Not every outreach results in a deal, but you won’t know until you try.

Categories

Why track missing features

Product roadmap prioritization

Automatic re-engagement