The whitespace matrix is finished. Twelve accounts down the side, six products across the top, forty-one empty cells shaded amber. It went to the QBR, the regional director called it the clearest picture of the base anyone had built, and six weeks later the same forty-one cells are still amber. Nobody called anyone.
That is the normal outcome, and it is not a failure of the analysis. The matrix did exactly what it was built to do. It answered the question "what has this account not bought from us." What it did not answer, because it cannot, is the question a rep has to answer before picking up the phone: why this account, why this product, why this quarter. The empty cell is a fact about your order history. A reason to call is a fact about the customer's year.
What the matrix actually knows
Look at where the inputs come from. DemandFarm, which sells the category, describes the analysis as running on previous purchases plus current account data (opportunity type, industry, account type, products used) and a read of which products are succeeding in the market. Prolifiq is more specific about the plumbing: pull the data from your CRM, your billing system, and account team knowledge, then map it against every product, module, service and SKU you sell.
Both descriptions are accurate, and both describe the same closed loop. Purchase history is yours. Billing is yours. The product catalogue is yours. Account team knowledge is your own people's recollection. A whitespace matrix is a very good picture of your own filing cabinet, and every cell in it was populated by something that happened inside your four walls.
The prioritization inherits the same property. Prolifiq's scoring model is a sensible one: score each gap on deal size, win probability, strategic value and time to close. Read those four criteria again and notice that all four are estimates made by the seller, about the seller's own portfolio. Rank a hundred gaps that way and you have ranked your own opinions in a defensible order. Not one of the four inputs knows whether the account has the problem right now.
None of this is a knock on the tools. Mapping the base is genuinely hard and worth doing, and if you have not done it, do that first. Account mapping is the prerequisite here, not the competitor. The point is narrower than a takedown: the matrix is a complete answer to a question of coverage, and a blank answer to a question of timing.
An empty cell has four causes, and only one is a deal
- They bought it elsewhere. The cell is empty because a competitor filled it two years ago. That is a displacement conversation with a renewal date attached, and it is worked completely differently.
- They do not have the problem. A forty-person firm with no field team is not a gap in your field service module. It is a company that will never need one, and the amber shading is telling you nothing at all.
- They have the problem and already solved it internally. A spreadsheet, a contractor, two hours of somebody's week. Real demand, currently satisfied. The opening is a cost comparison, not a capability pitch.
- They have the problem, unsolved, and something this year made it urgent. This is the only version that is a deal this quarter.
The matrix renders all four identically. Same amber, same cell, same weighted score. Telling them apart is not a harder version of whitespace analysis. It is a different input, and it does not live in the CRM.
What has to be true before a rep works a gap
Four conditions. A gap that fails any one of them goes back in the pile.
1. The gap is real, not a data artifact
Much of the amber in a first-pass matrix is bad plumbing: a subsidiary billing under a different account ID, a product bought under a legacy SKU, a pilot that never got recorded as a sale. This is not a hypothetical risk. Salesforce's 2026 State of Sales, drawn from 4,050 sales professionals across 22 countries, found that high performers prioritize data hygiene at 79%, against 54% for underperformers. Cleaning the base is what the good teams do first. Before a gap becomes a target, somebody confirms it against billing rather than against the CRM.
2. The account shows the problem, with a date on it
This is the condition the matrix cannot evaluate, and it is the one that decides the quarter. Something has to have happened at that account, recently, that your product addresses. Not a persona fit. Not an industry average. A specific, dated, checkable fact. That is what a buying signal is, and the date carries as much weight as the signal itself: evidence from eleven months ago describes a problem somebody has already solved without you.
3. A named person owns that problem
"Acme has a compliance gap" is not workable. "Acme hired a Director of Compliance in March, and the posting lists the exact reporting obligation your module produces" is workable, because it arrives with a person, a mandate, and a reason that person is receptive now. Whitespace is drawn at the account level, and accounts do not take meetings.
4. You can open without flattery
The practical test costs thirty seconds: write the first sentence. If it reads "I noticed you are not using our analytics module," you have described your own order book to a stranger, and it will not land. If it reads "your Q2 call flagged inventory write-downs twice and your operations lead is hiring for demand planning," you have described their year. When you cannot write the second kind of sentence, the evidence is not there yet and the gap is not ready. It is the same discipline as lead scoring: a score nobody can explain in a sentence is a score nobody acts on.
Where the missing evidence actually lives
Nearly all of it is public. That is the part teams find surprising. The reason a gap is worth working this quarter is usually disclosed somewhere by the account itself, in the ordinary course of running a business, months before it reaches a sales conversation.
| Source | What it proves | Useful shelf life |
|---|---|---|
| Job postings and careers pages | Where budget and headcount are going, in the account's own words | 2 to 3 months |
| Earnings calls and investor decks | What leadership committed to publicly, which is what middle management gets measured on | One quarter |
| Annual filings and risk sections | Obligations and exposures the company is required to disclose, often naming your exact problem | One year |
| Press releases, launches, expansions | New operations that create new needs: a new plant, a new region, a new segment | 3 to 6 months |
| Public docs, changelogs, status pages | What they actually run, which corrects the technographic guess in the matrix | Weeks |
| Leadership changes | A new owner for the problem, with a mandate and a short window to show a win | 1 to 6 months |
Prolifiq's own guidance gets close to this. It advises refreshing whitespace immediately after major triggers like an acquisition, a leadership change, a contract renewal or a competitive entry. The trigger list is correct. What goes unstated is who watches for the triggers. In most teams the honest answer is nobody, and the refresh happens quarterly because the calendar says so, not because anything changed at the account. External evidence is also a different kind of input from the intent data many teams have already bought: intent tells you somebody at a company read something, while a filing or a posting tells you what the company committed to do.
Running this without adding a research quarter
The obvious objection is time. Six sources times two hundred accounts times six products is not something a territory owner does between forecast calls. The same Salesforce research puts average selling time at 40% of the week. Handing that rep a second research job makes the number worse, which is why the honest version of this argument usually dies at the QBR.
So do not hand it to the rep. The work is mechanical, and it decomposes cleanly:
- State what each product is for as a problem, not a feature. Your inventory module is not "inventory management," it is "write-downs caused by demand forecasts built in spreadsheets." Problems are searchable. Features are not.
- Turn each problem into queries that can be run against public sources without a human choosing the wording every time.
- Run every account against every problem, not only the ones a rep already likes. The entire value of covering the base is that the coverage is not selective.
- Return the evidence with its source and its date, per account and per product, and drop anything with no evidence rather than guessing at it.
- Overlay the result on the matrix. Amber now has two states: gap with evidence, and gap without. The first is this quarter's call list. The second is a coverage report, and it waits.
That is what PitchSmart is built to do. It takes what you sell, derives the problems each product solves, researches every account on your list against those problems, and returns the matched signals with their sources attached, so a gap arrives carrying a reason and a citation instead of a colour. The same 2026 Salesforce data has sellers expecting automation to cut prospect research time by 34%, which is roughly the shape of the saving on offer here: the reading gets delegated, the judgement does not. If you would rather build the habit by hand first, the account research process is the manual version of the same loop.
Sequencing still matters afterwards. Evidence tells you which gap is live this quarter. A land and expand plan tells you what order to take them in once you know.
What to measure, so it does not become a slide
Whitespace work fails quietly. It produces a deliverable that looks like progress, gets praised in the room, and never converts. Because the deliverable is a slide, there is nothing to check six weeks later. Three numbers prevent that:
- Share of gaps carrying dated evidence. On a first pass it is always a minority of the amber. That minority is your actual pipeline. The remainder is a coverage report, and calling it pipeline is how forecasts go wrong.
- Time from evidence to first touch. Hiring signals and leadership changes decay. If the matrix refreshes quarterly and the signal was already three months old when you found it, you are calling after the decision was made.
- Meeting rate on evidence-backed gaps against the rest. This is the only number that settles the argument internally, and it is cheap to run. Take one territory, split the amber cells into the two states, and compare.
Expansion earns the discipline. SaaS Capital's 2026 survey of more than 1,000 private B2B SaaS companies puts median net revenue retention at 103% for bootstrapped companies between $3M and $20M in ARR, with the 90th percentile at 117.9%. That spread is the difference between a base that roughly holds its ground and a base that grows without new logos, and it is won one specific, well-timed expansion conversation at a time.
Keep the matrix. It is the right map of the base, and the account plan it feeds is the right container to hang the work on. Just stop treating the empty cell as the finding. The empty cell is the question. The reason to call this quarter is the answer, and it was never going to be in your CRM, because it never happened there.
