Does your project have a higher market share than Tesla

One of the most common weaknesses in EU funding proposals is not the market size itself. It is the way market share is justified. Many proposals present impressive revenue forecasts, attractive serviceable markets, and ambitious adoption curves. On the surface, the business case may look convincing. The numbers are clean, the tables are well formatted, and the growth trajectory looks exciting. But when the evaluator looks closer, a simple question appears.

That question is often where credibility starts to break. Not because the applicant lacks ambition. Because the proposal treats market share as something to choose rather than something to derive. In competitive EU funding calls, especially those involving innovation, commercialisation, scale-up, and exploitation, this distinction matters. A small market share that is well justified can be far more credible than an impressive number with no visible logic behind it.

The classic shortcut

The shortcut is familiar. A team defines the total addressable market, narrows it to a serviceable available market, and then decides to take a percentage of that market.

From that moment, the rest of the financial model is built on top of the assumption. Revenue projections, customer numbers, production needs, investment requirements, profitability, and impact claims all depend on that percentage. The problem is not that 5% is impossible. The problem is that the proposal often does not explain why 5% is credible for this specific company, segment, product, business model, capacity, pricing, route to market, and competitive environment. Why not 0.5%? Why not 1.2%? Why not 8%? Without derivation, the number is not an argument. It is a wish written as a percentage. If the assumption is weak, everything built on top of it becomes weaker too.

The Tesla reality check

Tesla is a useful reminder of how misleading market share can become when the market is not defined carefully. Depending on the period, geography, and category, Tesla may look like a small participant in the total European passenger car market and a much stronger participant in the battery electric vehicle segment. If the denominator is all passenger cars, the share tells one story. If the denominator is battery electric vehicles, the share tells another. If the denominator is premium electric sedans, fleet purchases, specific countries, or early adopters in a price band, the story changes again. The question is not simply whether the share looks large or small. The real question is whether the denominator is the right one. Market share does not mean much until the market is defined with precision.

The first problem: markets are defined too broadly

Many EU proposals start with a large market because large markets look attractive. The proposal may refer to healthcare, construction, energy, mobility, agriculture, manufacturing, cultural heritage, cybersecurity, or industrial automation as if the entire category were commercially reachable. This creates a false sense of opportunity. A broad market can be relevant for long-term vision, but it is rarely useful for validating near-term adoption. Evaluators need to understand the first reachable segment. A medical device company may describe the European healthcare market, while the first realistic segment is private diagnostic centres in three countries using a specific workflow. A climate-tech company may describe industrial decarbonisation, while the first reachable segment is mid-sized ceramic manufacturers operating a specific kiln and facing carbon cost exposure. A SaaS company may describe digital transformation, while the first segment is regulatory teams in medtech SMEs preparing documentation under a specific framework. The narrower segment is where market share must be made credible. When the denominator is wrong, the market share becomes distorted.

The second problem: market share is treated as a wish

The second recurring problem is that market share is presented as an aspiration rather than a calculation. A proposal may state that the company will capture 3%, 5%, or 10% of a serviceable market within five years. The figure appears precise, but the logic behind it is not visible. Evaluators then ask practical questions. How many customers does that percentage represent? How many units must be sold? How many deployments must be completed? How many salespeople are needed? How long is the sales cycle? How many pilots convert into paid customers? What is the expected churn? What pricing model is used? What capacity constraints exist? If the proposal cannot answer these questions, the market share is only declared. The issue is arbitrary ambition, especially when the number has no visible relationship with the business model.

Market share should be derived bottom up

Market share should not be selected first and justified later. It should be derived from the commercial reality of the company and target market. A bottom-up approach starts with the adoption mechanism. It asks who buys, who uses, who pays, who decides, how long adoption takes, what resources are needed, and what limits growth speed. For a physical product, the calculation may start with production capacity, manufacturing lead times, certification, distribution, installation, maintenance, and after-sales service. For SaaS, it may start with acquisition channels, conversion rates, onboarding capacity, annual contract value, churn, expansion revenue, and customer success resources. For a platform technology, it may start with use cases, licensing model, partner channels, integration complexity, validation requirements, and regulatory or procurement constraints. For a clinical or regulated product, it may start with approvals, reimbursement, procurement cycles, hospital integration, and evidence generation. Only after this logic is clear should the proposal express the result as market share. The market share should be the output of the model, not the input that makes the model attractive.

Revenue share, unit share, and customer share are not the same

Another common weakness is that proposals do not define what market share measures. Market share can refer to revenue, units sold, number of customers, installed base, users, licences, transactions, volume processed, or capacity deployed. These are not interchangeable. If a company sells a physical device at a stable price, units sold may be the cleanest basis. If the company sells enterprise software with variable pricing, customer numbers may be more meaningful than revenue share. If the business model is usage-based, transactions or processed volume may matter more. The same percentage can mean very different things depending on what is measured. A 1% revenue share in a market with high-value enterprise contracts may require only a small number of customers. A 1% customer share in a fragmented market may require thousands of accounts. A 1% unit share in a hardware market may require manufacturing and logistics capacity the company does not yet have. Evaluators need to know what the percentage represents.

The capacity test

One simple way to test a market share assumption is to translate it into capacity requirements. If the proposal claims a certain share of the market, how many units, customers, contracts, deployments, or sites does that imply? Can the company deliver that volume within the timeframe? A manufacturing company may forecast revenue that implies 20,000 units per year by year five. If current production capacity is 500 units per year and the proposal does not explain scale-up, suppliers, quality control, working capital, or manufacturing partners, the forecast becomes fragile. A SaaS company may forecast hundreds of enterprise clients. But if each deployment requires a three-month integration process and a specialist team, the adoption curve needs a clear scaling plan. A medtech company may forecast rapid hospital adoption. But each sale may depend on procurement committees, clinical validation, IT integration, and budget approvals. The capacity test converts market ambition into operational reality.

The sales ramp-up test

A second useful test is the sales ramp-up test. Market share is not captured instantly. It is built through awareness, validation, pilots, procurement, negotiation, implementation, support, retention, and expansion. Many proposals show a smooth revenue curve that rises quickly after the project ends, but the adoption sequence is not explained. A credible ramp-up should be linked to channels, conversion assumptions, partner agreements, pilot outcomes, regulatory milestones, and commercial resources. If the company plans to sell through distributors, the proposal should explain how distributors will be selected, what incentives they have, how many opportunities they can generate, and what support they need. If the company plans direct enterprise sales, it should explain the sales cycle, qualified leads, conversion rates, account value, and sales team capacity. If adoption depends on pilots, it should explain how many pilots are expected, how many can convert, and what evidence is required. A market share projection without sales ramp-up logic is not a commercial strategy. It is a curve.

The pricing test

Market share also depends on pricing, and pricing is often underdeveloped. A revenue forecast can look credible until the evaluator checks the implied price per customer, unit, or deployment. If the pricing model is unclear, the forecast is difficult to assess. For physical products, the proposal should explain unit price, margin, production cost evolution, and whether prices decrease with scale. For SaaS, it should explain whether pricing is per user, site, transaction, module, data volume, or enterprise licence. It should also explain whether the forecast assumes average contract value, expansion revenue, churn, or tiered pricing. For regulated or clinical markets, pricing should consider reimbursement, procurement limits, willingness to pay, health-economic evidence, and alternatives. Revenue is not only a function of market size. It is also a function of what customers will actually pay and how often they will pay it.

The adoption barrier test

A proposal may define a relevant market and derive a reasonable adoption curve, but still underestimate adoption barriers. These barriers vary by sector. In healthcare, they may include clinical evidence, reimbursement, data protection, workflow integration, procurement, liability, and clinician trust. In industry, they may include downtime, certification, legacy equipment, safety, maintenance, and return on investment. In public-sector or cultural heritage markets, adoption may depend on procurement rules, conservation standards, budget cycles, institutional capacity, and trust. In energy, barriers may include permitting, grid connection, regulation, capex intensity, and long asset lifetimes. Evaluators do not expect all barriers to be solved immediately. They do expect the proposal to recognise them and explain how they affect market entry. If the forecast assumes rapid adoption but barriers are not addressed, the market share looks optimistic. If barriers are linked to validation, partnerships, evidence, and milestones, the same ambition becomes more credible.

The competitor test

Market share is also a competitive claim. To capture part of a market, the company must displace, complement, or create an alternative to existing solutions. This requires understanding direct competitors, current behaviours, workarounds, incumbent suppliers, internal processes, and the cost of doing nothing. Many proposals compare technical features but do not explain why customers would change behaviour. A technology may be better, but customers may accept inferior solutions because they are familiar, integrated, cheaper, already approved, or low risk. A credible market share calculation should reflect the competitive path. Which segment is most likely to switch first? Which alternative is being replaced? What evidence suggests customers care enough to adopt? What switching costs remain? What advantages can the company defend? A patent may support differentiation, but it does not automatically create freedom to operate, market access, or customer adoption. We discuss this distinction in Patent granted does not mean freedom to operate. Evaluators look for logic that connects differentiation to adoption.

The evidence test

The strongest market share assumptions are supported by evidence close to the target segment. This evidence can include customer interviews, letters of intent, paid pilots, distributor discussions, procurement feedback, early sales, waitlists, willingness-to-pay tests, usability studies, benchmark data, or adoption evidence from comparable technologies. The key is not to list evidence randomly. The key is to connect each piece of evidence to the assumption it supports. If the proposal assumes a high pilot-to-customer conversion rate, show evidence from previous pilots or explain why the assumption is conservative. If it assumes a certain price, show willingness to pay, comparable pricing, cost savings, or procurement feedback. If it assumes adoption in a specific segment, show that the segment has been contacted, interviewed, tested, or validated. If it assumes international expansion, explain why evidence from the first market can transfer. Many proposals have evidence, but it is not connected to the market share model. The evaluator sees activity, but not derivation.

A weak version

A weak market share justification often sounds like this:

This paragraph may sound confident, but it leaves too many questions unanswered.

• Why is EUR 12 billion the relevant market?
• Which part of that market is actually reachable first?
• Why is 5% conservative?
• How many customers does EUR 60 million represent?
• What price is assumed?
• How long is the sales cycle?
• What production or deployment capacity is needed?
• What evidence shows customers will adopt?
• Which competitors or alternatives are being displaced?
• Which barriers could slow adoption?

The number may be possible. But the proposal has not justified it. The evaluator is left with a conclusion without the reasoning chain.

A stronger version

A stronger version does not need to be much longer. It needs to be more traceable.

This version is stronger because the evaluator can follow the logic. The market is defined. The customer count is visible. The revenue logic is connected to pricing. The adoption assumption is tied to evidence and capacity. The claim is still ambitious. But it is no longer arbitrary.

Why arbitrary market share damages impact credibility

In EU proposals, market share is rarely just a commercial figure. It often supports broader impact claims. Revenue forecasts may feed into job creation, emissions reduction, cost savings, productivity improvements, patient benefits, industrial competitiveness, European strategic autonomy, or environmental outcomes. If the market share is weak, these downstream impact claims become weak too. If the proposal claims emissions reduction based on expected adoption, the adoption assumption must be credible. If the number of deployed units is unrealistic, the emissions impact becomes unrealistic. If the proposal claims job creation based on revenue growth, but revenue depends on an arbitrary percentage, the employment impact becomes fragile. This is why evaluators may challenge impact even when the technical solution is strong. The weakness may sit in the commercial assumptions that translate technology into impact.

Why arbitrary numbers create ESR comments

When market assumptions are weak, Evaluation Summary Report comments rarely say, “the 5% market share is arbitrary.” They often appear in broader language. The ESR may say that the commercialisation strategy is not sufficiently convincing, revenue projections are not adequately justified, market entry lacks detail, or expected impact is not fully substantiated. These comments can be frustrating because the proposal may include market numbers. But including numbers is not the same as justifying numbers. This is the same logic we discussed in Not sufficiently justified in EU proposals: why evaluators need evidence, not more words. When a number lacks derivation, the solution is not more optimistic text. The solution is to show the reasoning behind the number. Evaluators need to understand how the conclusion was reached. If they cannot follow the chain from market definition to adoption, pricing, capacity, and evidence, the forecast becomes vulnerable.

The role of AI in checking market assumptions

AI can help applicants review market assumptions, but only if used critically. A generic AI tool may make a business section sound more polished. It may improve fluency, restructure paragraphs, or add confident language. But a smoother paragraph does not automatically make market share more credible. The real test is whether AI can challenge the assumption. Why this market? Why this share? Why this adoption speed? What evidence supports the conversion rate? What operational constraints limit scale-up? What denominator is being used? What would an evaluator question first? This is why proposal evaluation needs more than rewriting. A proposal can be perfectly phrased and still contain weak assumptions. We explore this issue in Would your EU proposal survive AI evaluation?. The useful role of AI is not to make arbitrary numbers sound better. It is to expose the assumptions that make them arbitrary.

A practical market share checklist

Before submitting an EU funding proposal, every market share assumption should be tested against a practical checklist.

• Is the market definition specific enough?
• Is the denominator the total market, the serviceable market, or the first beachhead segment?
• Is the market share measured by revenue, units, customers, licences, transactions, or deployed capacity?
• Does the forecast translate the percentage into an actual number of customers or units?
• Is the pricing model visible?
• Is the sales ramp-up explained?
• Are conversion rates justified?
• Are production, deployment, or service capacity constraints addressed?
• Are procurement, regulation, validation, or integration barriers reflected?
• Is customer evidence linked to the forecast?
• Are competitors and current alternatives considered?
• Are assumptions conservative enough for the maturity level of the company?
• Does the impact model depend on the same adoption assumptions?
• Could an evaluator reproduce the logic from the proposal text?

If several answers are unclear, the forecast may still be attractive, but it is not yet evaluator-proof.

What evaluators actually look for

Evaluators are not asking applicants to be timid. They understand that EU funding often supports ambitious technologies with significant market potential. But they do look for credibility in numbers. A credible forecast shows that the team understands the market, customer, adoption process, commercial constraints, and evidence needed to justify growth. A strong proposal does not simply say that the company will capture a share of the market. It shows how that share emerges from a realistic route to market. A small, well-derived market share can be more convincing than an arbitrary 5%. A larger share can also be credible if the market is narrow, the segment is well defined, and the company has evidence to support the adoption logic. The issue is not the number alone. The issue is whether the proposal gives evaluators a reason to trust the number.

Where Ruthless Evaluator fits

This is exactly the type of weakness Ruthless Evaluator is designed to detect before submission. Not because market share assumptions need to be pessimistic. Not because ambition should be removed. Not because financial projections must be perfect. Market assumptions should be visible, traceable, and connected to evidence. Ruthless Evaluator helps applicants, consultants, startups, SMEs, universities, research centres, and innovation teams identify when commercial claims are unsupported, market definitions are too broad, revenue projections depend on arbitrary percentages, and impact claims depend on unjustified adoption assumptions. It helps flag issues such as:

• market definitions that are too broad
• unexplained SAM or SOM assumptions
• market share percentages with no bottom-up derivation
• revenue projections disconnected from pricing
• customer numbers that do not match sales capacity
• adoption curves that ignore procurement or validation barriers
• impact claims that depend on unrealistic deployment assumptions
• commercial strategies that sound attractive but are not yet defensible

The goal is not to make the business case sound more impressive. The goal is to make it harder to reject for avoidable reasons.

Better to challenge the number before evaluators do

Market share is not a decoration in an EU proposal. It is often one of the pillars supporting the commercial and impact case. If that pillar is weak, the proposal becomes vulnerable. If the number is arbitrary, evaluators may question not only the forecast but also the maturity of the team commercial thinking. Before submission, teams should challenge every market share assumption with uncomfortable but necessary questions.

• Why this percentage?
• Why this market definition?
• Why this first segment?
• How many customers or units does the forecast imply?
• Can the company deliver that volume?
• What evidence supports the adoption rate?
• What sales process is assumed?
• What pricing model is used?
• Which barriers could slow adoption?
• Which competitors or alternatives must be displaced?
• Which impact claims depend on this forecast?

If the proposal cannot answer these questions clearly, the evaluator may answer them negatively during assessment. Ambition is not the problem. A well-justified market share tells the evaluator that the team understands not only the size of the opportunity, but also the path required to capture it. Better to meet Ruthless Evaluator before submission than inside the Evaluation Summary Report.

app.ruthlessevaluator.ai