Every industry market share data project stands or falls on two questions: what do you want to know, and do you have the data? The first unpacks into at least six dimensions - time horizon, competitor visibility, product segmentation, geographic granularity, competitive set and transaction type. The second surfaces the real constraints - historical availability, authorisation, extraction, geography, collective capability and timing - and the group's weakest link sets the baseline for everyone. Working through both before contracts are signed is why projects that survive this stage rarely fail afterwards.
Every sales conversation at PowerStats begins with two deceptively simple questions: "What do you want to know?" and "Do you have the data?" On the surface, they sound like a routine qualification exercise. In practice, they are the most important diagnostic tools in the entire industry market share data space. Each question unpacks into layers of complexity that determine whether a project succeeds, stalls or never gets off the ground.
This article walks through the hidden dimensions beneath both questions - the trade-offs, the constraints and the collective dynamics that shape every data-sharing programme. Whether you are an OEM exploring competitive intelligence for the first time or a distributor evaluating participation, understanding these two questions will save you time and sharpen your expectations before committing resources.
What do you want to know?
The most common answer is predictable: "We want to know competitor sales." It makes sense. Any manufacturer would like to understand what their rivals are doing. However, this response often reveals a fundamental misunderstanding about how industry market share data actually works.
Many leads assume they can simply purchase competitor data off the shelf - a product they can buy without any reciprocal obligation. In reality, every PowerStats project operates as a participation model. You contribute your own sales data in order to receive data from everyone else. This is not passive consumption. It is a give-to-get exchange, and it is the only way the model works. Companies that refuse to share their own information drop off quickly. That drop-off rate is relatively low, but it acts as an efficient filter that saves both parties time. If a company will not contribute, the conversation ends respectfully and early.
For leads who say yes, the conversation opens up considerably. Because "what do you want to know?" remains wide open - and the complexity is only just beginning.
Time horizon
How far back does the lead want the data to go? Only the latest month? Or twenty years, to understand how events like the global financial crisis or COVID-19 reshaped their market? Historical depth adds strategic context, but it also introduces feasibility challenges. Not every participant can supply two decades of archived records, and the group's collective capability sets the boundary for everyone.
Competitor visibility
Does the lead want open reporting - results broken out by brand name - or aggregated data where they see their own performance against an "all other" total? Open reporting delivers richer competitive intelligence, but it requires greater disclosure from every participant. In some jurisdictions, open reporting models may not be permitted at all. The choice between open and closed reporting shapes the entire project design.
Product segmentation
How finely does the lead want to slice the data? By power band, fuel type, cutting deck size, capacity range, number of motors - the list of possible product segmentation attributes is essentially unlimited. A boat engine distributor might want to filter by fuel type and horsepower range. A lawnmower manufacturer might care about cutting deck width and drive type. The number of categorisation filters is as many or as few as the customer needs.
This matters far beyond the dashboard. Product metadata drives capital allocation and research and development decisions at the highest level. When an OEM detects a shift in consumer preference - from corded electric to battery electric, or from sit-on to stand-on mowers - that signal informs factory investment, tooling decisions and production planning. The metadata is where the strategic value lives.
Geographic granularity
Does the lead want data by country, by state or region, or down to postcode level? Geographic granularity determines both the value and the feasibility of the project. A national view reveals broad trends. A postcode-level view enables zone-by-zone analysis that connects market share to specific dealer territories. However, not every participant can supply data at that resolution, so the group's collective capability once again defines the limit.
Competitive set
Not every competitor matters equally to every lead. Some OEMs have a shortlist of top-tier rivals without which the entire project would be meaningless. Defining the competitive set is a strategic choice. It shapes who is invited to participate, which brands appear in the dataset and how the project is scoped from the outset.
Transaction type
What stage of the supply chain does the lead want to track? Retail sales to the end user represent real-time consumer preference - the most valuable and granular data point. Wholesale shipments from factory to dealer provide strong regional demand signals. Factory export data, the earliest stage, confirms what left the production line but loses visibility on what happens downstream.
These categories represent a tiered value chain, and the right choice depends on what is actually achievable in a given geography and product segment.
Beyond the six: distribution channel and technology transitions
Two additional dimensions frequently surface during project design. Distribution channel - the route through which the end customer acquired the product - is distinct from transaction type. A boat sold through a boat builder follows a different commercial path from one sold through a marina dealership. An outdoor power product purchased through an internet store behaves differently from one bought at a chain retailer. Capturing this dimension adds another layer of market intelligence, but it requires every participant to track and report that data consistently.
Technology transitions introduce a more fundamental question. When an industry that has historically produced internal combustion equipment begins shipping electric alternatives, the group must decide: does it add fuel type as a new metadata attribute within the existing project, or does the disruption warrant an entirely separate project? A separate project could include electric-native startups that were never part of the original competitive set. Established OEMs often want to understand how these newcomers perform, because companies that have been electric from day one can sometimes outperform incumbents adapting decades of combustion expertise. This is not a hypothetical scenario - it is a real decision that participant groups work through as part of project design.
Do you have the data?
The second question sounds even simpler than the first. It is not. "Do you have the data?" unpacks into six distinct constraints, each of which can block, reshape or redefine a project.
Historical availability
If a lead wants ten years of historical data, they may not actually have it. This happens more often than you would expect. Companies that are excellent at manufacturing their product are not always disciplined about archiving sales records. ERP migrations are a common culprit. When a company upgrades its sales tracking system, the migration consultant may charge significant fees to ingest historical records. Companies often import only the minimum the law requires and leave older data behind - sometimes in paper form that is simply too expensive to digitise. The data existed once, but it no longer exists in a usable format.
Authorisation and governance
A sales manager may want industry market share data urgently, but they may lack internal corporate sponsorship or legal sign-off to participate. The business side might decide that disclosing sales volumes to competitors is not worth the intelligence received in return. Legal counsel might not be comfortable with the perceived risk, even though PowerStats operates under strict data and security protocols with uniform contracts and simultaneous release to all participants. In our experience, roughly two to five percent of eligible participants are lost at this stage. Overcoming governance blockers is possible when an internal champion pushes participation through the organisation, and PowerStats can provide documentation to support legal review. However, if the business itself has decided the risk outweighs the reward, that position is very difficult to shift from the outside.
Operational extraction
Sometimes a company has the data and the authorisation, but extracting it in the required format on a monthly cadence is operationally difficult. This often affects larger organisations that are relatively new to a particular market or have not yet established all their data flow functions and warranty registration systems. In these situations, PowerStats can work around the constraint by collecting data directly from the company's distributed dealer network - setting up an account for each independent distributor at no additional cost and deferring monthly uploads to this network while the factory handles only direct deliveries. Roughly two to five percent of participants require this approach.
Geography and infrastructure
Retail sales data is only valuable if it can actually be captured. In some geographies, it simply cannot be. Consider an outboard engine sold to a fisherman in a remote Southeast Asian island community for cash, with no phone number or email on file. There is no warranty registration. Nobody records the retail sale. The customer disappears into an archipelago, and the data point vanishes with them.
In general, the more developed the nation, the higher the chance of retail data being tracked. Similarly, the more expensive the item, the more likely it is that a full retail framework exists - warranty agreements, finance arrangements and after-sale support all create data trails. A cheap item in a less developed market may never see registration at all.
When retail data is not collectable, the approach shifts down the value chain. If retail is not possible, wholesale provides meaningful insight into regional demand. If wholesale is not possible, factory export data at least confirms what left the production line. It is better to work with the data the market actually provides than to force a collection framework that does not exist.
Collective participant capability
This is the constraint that leads most often overlook. "Do you have the data?" does not apply to one company in isolation - it applies to all participants as a group. If one participant out of twenty cannot supply data by state, the entire project cannot track that dimension for anyone. If one participant can only provide seven years of history while everyone else can provide ten, the project gets capped at seven years for the whole group.
This is a fairness principle. Every participant receives access to the same dataset, and PowerStats does not favour or disfavour any company. One participant's limitation becomes the common denominator for everyone.
Moreover, the collective constraint is not always about capability. It can be about willingness. A company that dominates a particular power band or product segment might strategically prefer coarse aggregation rather than revealing exactly how dominant they are across detailed sub-segments. A weaker competitor, by contrast, might push for maximum granularity to understand precisely where the gaps lie. This creates a negotiation process. PowerStats facilitates consensus, and the leverage is straightforward: imperfect data beats no data. Without agreement from everyone, the project does not run. In our experience, that threat is far more persuasive than any argument for ideal specifications. The group always reaches consensus. Nobody has ever walked away.
Timing and distributed networks
Global OEMs with vast distribution networks do not control every node in their supply chain. Independent distributors and dealers operate on their own systems, their own timelines and their own priorities. Even if a project sets a submission deadline of the tenth of the month, one regional distributor that needs until the twentieth pushes the entire project's deadline to the twentieth - because complete data requires every participant to report.
PowerStats does not impose a deadline and ask participants to meet it. Instead, we ask each participant when the earliest possible submission date is for their entire network. The latest answer becomes the project baseline. The slowest link in the distribution chain drives the timeline for everyone.
The chain is only as strong as its weakest link
A recurring theme connects both questions: the collective constraint. Industry market share data projects operate as a chain. Every dimension - historical depth, geographic granularity, product segmentation, submission timing - is defined not by the most capable participant but by the least capable or least willing one. This is not a design flaw. It is a fairness mechanism that ensures every participant receives the same data under the same conditions.
Understanding this dynamic early changes the conversation. Instead of designing an ideal specification and hoping everyone can meet it, project design starts from what is collectively achievable and builds upward. The result is a realistic, sustainable programme that every participant can support - rather than an ambitious one that collapses when a single contributor cannot deliver.
These two questions and the dimensions beneath them form the diagnostic framework for every PowerStats project. They surface real constraints before contracts are signed, through a formal project specification that every participant confirms in writing. It is a process that prioritises substance over speed - and it is why projects that survive this stage rarely fail afterwards.
Key takeaways
- Industry market share data requires participation, not passive consumption - you contribute your own data in order to receive data from the market.
- "What do you want to know?" unpacks into at least six dimensions: time horizon, competitor visibility, product segmentation, geographic granularity, competitive set and transaction type.
- Product metadata drives capital allocation and research and development decisions - detecting demand shifts early informs factory investment upstream.
- "Do you have the data?" is constrained by historical availability, authorisation, operational extraction, geography, collective capability and timing.
- The weakest link in any participant group sets the baseline for everyone - data granularity, historical depth and submission deadlines are all collectively defined.
- Imperfect data shared across a full competitive set is more valuable than perfect data that never materialises because one participant cannot meet the specification.
Frequently asked questions
Can you buy competitor sales data without contributing your own?
No. Every PowerStats project operates as a give-to-get exchange - you contribute your own sales data in order to receive the aggregated data from everyone else. Companies that will not contribute drop out of the conversation early, which acts as an efficient filter that saves both parties time.
What if my company does not have years of historical sales data?
This is more common than expected - ERP migrations often leave older records behind, sometimes in paper form too expensive to digitise. The project simply works with what the group collectively holds: if one participant can supply seven years of history while others hold ten, the project is capped at seven years for everyone.
Why does one participant's limitation affect the whole project?
Because every participant receives access to the same dataset under the same conditions, the least capable or least willing participant defines each dimension - historical depth, geographic granularity, segmentation and submission timing. It is a fairness mechanism rather than a design flaw, and project design starts from what is collectively achievable.
What if retail sales data cannot be captured in my market?
The approach shifts down the value chain. Where retail data cannot be tracked, wholesale shipments still provide meaningful insight into regional demand; where wholesale is not possible, factory export data at least confirms what left the production line. It is better to work with the data a market actually provides than to force a collection framework that does not exist.
Ready to explore what industry data can do for your business?
These two questions are where every PowerStats project begins. They uncover what you actually need, what is feasible and where the real value lies - before anyone signs a contract. If you are considering shared industry market share data for the first time, or if you are an existing participant exploring a new market or product category, get in touch to start the conversation. You can also explore how PowerStats works across different industries to see where this model is already in operation.
