White Space Analysis for Manufacturers and Distributors
Find the Revenue Already Inside Your Accounts
Christian Wettre
EVP, GM North America
Pull up last year's customer report. Revenue is flat. The account list is stable. Nobody churned. The retention number looks fine. The average order value is holding. On paper, the business held its ground, and if you stopped reading there you would walk into the new year with a reasonable degree of confidence. But the question that report cannot answer is whether those customers are buying everything they could be. A handful of accounts probably account for most of the revenue. Many of the rest are buying one product line from you and two or three more from a competitor, and nothing in your system flags that as a problem because nothing in your system knows it is happening. The gap is real, it is measurable, and it belongs to you if you go looking for it.
This article explains how to see that gap. What white space analysis is, why your ERP will never surface it on its own, how to calculate your share of wallet in any account, and how to build a grid that turns a revenue theory into a rep's actual week.
What White Space Actually Means in a Distribution Business
This article is about commercial white space in your customer base, not physical floor or plant space utilization. The two uses of the term collide often enough in manufacturing that it is worth saying once, plainly, before moving on.
Commercial white space is the intersection of an account you already serve and a product line they have never bought from you. That is the working definition. Not a prospect you have never spoken to. Not a customer you lost. An active account, already in your system, already ordering, that has never touched a category you carry.
The term appears in two spellings across the industry. White space analysis and whitespace analysis refer to the same discipline. Both appear throughout this article.
What white space is not
Distinguishing white space from adjacent concepts keeps the analysis clean.
- Prospecting is finding new accounts. White space is finding new revenue inside accounts you already have. The two require different motions, different data, and different conversations.
- Churn risk is an account pulling back from what they already buy. White space is the mirror image: categories they have never started.
- Upselling is selling more of what a customer already buys, typically a higher volume or a premium version. White space is selling something from a different category entirely.
A customer who buys your fasteners but has never ordered your cutting tools is a white space opportunity on cutting tools. That gap exists whether or not the rep has ever noticed it, and it will not appear on any report your ERP generates.
Why Your ERP Cannot Show It To You
The ERP records transactions. Every order, every line item, every shipment. It is exceptionally good at that. The problem is structural: a product a customer never ordered generates no transaction, so it generates no row. There is nothing to query. You cannot filter for the absence of a record.
Order history answers what they bought. It has no mechanism for answering what they did not buy, because what they did not buy left no trace.
This is a boundary, not a defect. The ERP was built to track what happened, not to model what could happen. Asking it to surface white space is like asking a bank statement to tell you what you could have bought but did not. The data was never there to begin with.
The same limitation applies to your transaction history in any form. Export it to a spreadsheet, run it through a BI tool, visualize it in a dashboard. You will get increasingly sophisticated pictures of what customers did buy. The gap stays invisible.
What closes the gap is a second layer of analysis built on top of the transaction record: a structured view of what each account could be buying, compared against what they are. That comparison requires knowing your full sellable portfolio, mapping it against each account, and treating every empty cell as a question rather than a non-event. The account knowledge problem is well documented in distribution, and it sits directly upstream of every white space gap a rep fails to close.
That is the logic behind the grid, which the later sections build out. But before you can act on a gap, you need a way to size it.
Share of Wallet, and How to Calculate It
Share of wallet is the percentage of a customer's total spend in your category that flows to you rather than to competitors or other suppliers. It is the most direct measure of how much of an account you actually own.
The formula is straightforward:
Share of wallet = (your revenue from the account) ÷ (account's total spend in your category) × 100
The numerator is easy. Your ERP has it. The denominator is where the work is.
Estimating total category spend
You will rarely know a customer's total spend with certainty. Customers do not volunteer that number, and they may not track it cleanly themselves. The honest approaches to estimating it:
- Account size and industry benchmarks. A manufacturer of a given size in a given sector typically spends within a predictable band on the categories you serve. Comparable accounts in your own book of business are the most grounded reference you have.
- Known equipment base. If you supply maintenance, repair, and operations products, the customer's installed equipment tells you roughly what they consume. A facility running a certain number of production lines has a calculable floor for consumables and parts.
- What comparable accounts buy from you. If similar customers in similar industries buy across five product lines, and this account only buys from two, the gap between the two and five is a reasonable proxy for underpenetration.
- Direct conversation. Reps who ask the question get an answer more often than those who assume they already know. "What does your annual spend look like on this category?" is a legitimate account development question.
The denominator will always be an estimate. That is acceptable. An imprecise share-of-wallet figure still tells you whether an account is 20% penetrated or 80% penetrated, and those two situations require completely different conversations. Precision matters less than direction.
When you are working across a territory of dozens or hundreds of accounts, the share-of-wallet calculation becomes the filter that separates the accounts worth a development conversation from the ones that are already well covered.
Building the Grid: Accounts Against What They Could Buy
The grid is the practical core of whitespace analysis. One axis lists your accounts. The other lists your product lines or categories. Each cell in the matrix represents a relationship between one account and one category. The question each cell answers is simple: are they buying this from you, or not?
What goes in the cells
The simplest version uses three states:
- Active: the account has ordered from this category in the past twelve months.
- Lapsed: the account ordered historically but has not in the past twelve months.
- Never: no order history in this category at all.
The "never" cells are your white space. The "lapsed" cells are a different but related conversation, closer to win-back than to new development. Keeping them separate matters because the sales motion is different.
Where the data comes from
Your ERP order history populates the "active" and "lapsed" cells directly. That data exists and is reliable. The "never" cells are defined by what is absent, which means you need a complete list of your own product categories before you can identify them. Many distributors find that step harder than expected. Product hierarchies in ERP systems are built for purchasing and fulfillment logic, not for sales planning. A category that makes sense to a buyer may span several product codes that a rep would never think to connect.
Cleaning and structuring your product taxonomy into sales-meaningful categories is often the first real work of a white space programme. It does not need to be perfect to be useful. A working draft of ten to fifteen top-level categories is enough to start.
What a meaningful gap looks like
Not every empty cell is worth pursuing. A meaningful gap has at least two characteristics: the account has a plausible operational reason to buy the category, and the category represents material revenue if converted. An industrial distributor whose customer runs a fabrication shop has a plausible reason to buy abrasives. That same customer probably does not need janitorial supplies in volume. The grid surfaces both gaps equally; the rep's judgment closes the filter.
This is also where cross sell opportunities become visible at scale. When you can see, across a territory of fifty accounts, that thirty of them buy category A but only eight buy category B, the cross sell motion is obvious in a way it never is when you are looking at one account at a time.
If you want to see what this looks like on your own accounts, Account Explorer builds this grid from your existing data. Start a trial on your own accounts.
Turning the Grid Into Territory and Account Plans
A grid nobody acts on is a spreadsheet exercise. The point of building it is to change what reps do on Monday morning.
From grid to rep priorities
Territory planning starts with segmentation. Once the grid exists, accounts fall into tiers by the size of their white space and the value of closing it. Large gaps with high estimated spend go to the top of the call plan. Well-penetrated accounts move to a maintenance cadence.
This is where account planning software and territory planning software earn their place. Fifty accounts against fifteen product lines is manageable by hand. Two hundred is not.
What a rep actually does with it
The grid gives a rep a specific reason to call. Not "checking in" but "you have never ordered from our cutting tools line and you have three machining centres on site. I want to understand why."
Key account management software structures those conversations and keeps the account plan current as orders change. Without it the grid ages out quickly. Choosing a manufacturing CRM in 2026 covers what to look for when the account planning layer is a requirement.
Multi-site and buying group complexity
A customer with five locations may buy different categories at different sites, through a central purchasing function that consolidates some decisions but not others. A category that looks like a gap at the account level may already be covered at one site and absent at two others. Map the buying centres, not just the legal entity.
Where to Start With the Data You Already Have
Nothing in the preceding sections requires new software to begin. The first version of a white space grid can be built from an ERP export and a spreadsheet. It will be imperfect and it will take longer than a dedicated tool, but it will show you things that are not visible anywhere in your current reporting.
Start here:
- Export twelve months of order history at the line-item level, with account, product code, and revenue.
- Map your product codes to sales-meaningful categories. Aim for ten to fifteen. Do not let the ERP's purchasing hierarchy dictate this step.
- Build the matrix. Accounts on rows, categories on columns. Mark each cell active, lapsed, or never.
- Score the gaps. For each "never" cell, note whether the account has an operational reason to buy the category. Discard the implausible ones.
- Rank the remainder by estimated revenue. The top ten gaps across your territory are your first development list.
That list is the output. A set of specific accounts, specific categories, and specific reasons to have a conversation. That is what white space analysis produces when it is done well: not a strategy document, but a pipeline.
The SugarAI and Epicor integration that TCP builds reads ERP transaction data directly into the CRM account record, so the grid stays current without manual exports. If you want to see what the analysis looks like on your own accounts before committing to a platform, start a trial on your own accounts or download the Account Explorer brochure to understand the full capability first.
Frequently Asked Questions
Three things: a complete list of your product categories structured for sales planning rather than purchasing logic, at least twelve months of order history at the line-item level with account and product code, and a working definition of your active account base. With those three inputs, you can build a first version of the grid. Additional data that improves the analysis includes account size, industry classification, known equipment or facility profile, and any existing notes on competitive relationships. None of that is required to start. It improves the quality of the gap scoring, but the grid itself can be built and acted on without it.
The right platform depends on where your data lives and how your sales team operates. For manufacturers already running Epicor, the most important requirement is that the key account management layer reads from the ERP rather than duplicating it. A platform that requires manual data entry to stay current will not stay current. SugarAI, which TCP implements for manufacturers and distributors, integrates directly with Epicor so that account records reflect actual transaction history without a separate export process. The account planning and white space grid functions are built on top of live ERP data, which means the grid reflects what customers are actually buying today rather than what they were buying when someone last ran a report. Requirements to evaluate include ERP integration depth, territory assignment logic, multi-site account structure support, and whether the platform surfaces gaps automatically or requires manual analysis.
The formula gives you a starting point: your revenue from the account divided by the account's total spend in your category, multiplied by 100. The numerator comes from your ERP. The denominator requires estimation. Beyond the estimation methods covered in the body of this article, there are two additional approaches that work well in distribution specifically. First, triangulate across your own book: if you have thirty accounts in the same sub-vertical and twenty of them buy across six categories while this account buys across two, the gap is a reasonable proxy for underpenetration even without an exact spend figure. Second, use purchasing conversations strategically. Buyers in distribution often know their total category spend better than sales teams assume, and a rep who frames the question as a service inquiry rather than a competitive one gets an answer more often than not. The goal is not a precise percentage. It is a directional signal strong enough to rank accounts by development priority.
Prospecting is the work of finding and qualifying accounts that have never bought from you. White space analysis is the work of finding revenue that is missing inside accounts that already buy from you. The two processes use different data, require different conversations, and have different cost structures. Prospecting requires building awareness and trust from zero. White space development starts with an existing relationship and a transaction history. The sales cycle is typically shorter, the conversation starts from a position of established credibility, and the cost of acquisition is lower. The two are complementary rather than competing, but conflating them leads to underinvestment in the existing base.
Cross sell opportunities become visible when you compare what each account buys against what accounts of similar size, industry, and operational profile buy. The gap between the two is the starting list. From there, filter by plausibility: does this account have the operational context to need this category? A customer running a paint line is a plausible buyer of surface preparation products. A customer in light assembly probably is not. The accounts that pass the plausibility filter and represent material revenue are the cross sell list. Reviewing that list quarterly against actual order history shows which gaps are closing and which are not, which in turn tells you whether the conversation is happening or whether the gap is structural.
Account development in distribution is fundamentally a coverage problem. Most accounts are underpenetrated not because the rep has tried and failed but because the rep has never had a structured view of the gap. The grid changes that. With a clear picture of which categories an account has never bought, the rep has a specific reason for every call rather than a general relationship maintenance motive. The most effective development cadence combines a quarterly grid review with a monthly account conversation focused on one gap at a time. Trying to introduce three new categories in a single conversation rarely works. Introducing one, demonstrating fit, and earning the trial order before moving to the next is the motion that actually converts white space into revenue.
Build a matrix with your accounts on one axis and your product categories on the other. Pull twelve months of order history from your ERP and mark each cell as active, lapsed, or never purchased. Every "never" cell where the account has a plausible operational need is a white space gap. Prioritize by estimated revenue: the accounts with the largest gaps relative to their size are where you start. The process does not require specialized software at small scale, but it does require a clean product taxonomy and a commitment to reviewing the grid on a regular cadence rather than treating it as a one-time exercise.
Account planning software is a tool that structures the relationship between a sales team and its existing customer base. It typically maps accounts against products or services, tracks conversation history, surfaces gaps, and integrates with CRM and ERP data to keep the picture current. It is most useful for distributors and manufacturers with more than fifty active accounts per rep, where manual tracking becomes unreliable. Below that threshold, a well-maintained spreadsheet is often sufficient. Above it, the grid degrades without a system to refresh it, and white space that was identified six months ago may no longer be accurate.
Yes, at small scale, and here is where it breaks. A spreadsheet works well for a single rep managing thirty to fifty accounts across ten to fifteen categories. The grid is buildable, the gaps are visible, and the maintenance burden is manageable if the rep is disciplined about updating it after each order cycle. It breaks in three situations: when the account count exceeds what one person can maintain manually, when the product taxonomy is complex enough that mapping codes to categories requires ongoing judgment, and when the organization needs to share the view across multiple reps or managers. At that point, the spreadsheet becomes a bottleneck rather than a tool. Cells go stale, versions diverge, and the grid stops reflecting reality. The transition to dedicated software is not about analytical sophistication. It is about whether the grid can stay current at the scale the business actually operates at.
Quarterly is the practical standard for most distributors. The grid is built on order history, which changes continuously, but a monthly refresh creates more administrative overhead than signal. Quarterly gives enough time for a genuine gap to either start closing or remain stubbornly open, which is itself useful information. Accounts that have been identified as white space for three consecutive quarters without movement are telling you something: either the rep is not having the conversation, the product is not a fit, or there is a competitive relationship that needs to be surfaced and addressed directly. Trigger a refresh outside the quarterly cadence when a significant account change occurs: a new buyer, a site expansion, a merger, or a major order in a new category.
