Market, Industry and Technology Analysis

Introduction

Product development does not begin with an idea alone. It begins with a disciplined understanding of the environment in which a product must create value. A product may be technically impressive but commercially unsuccessful if the target market is too small, customer needs are misunderstood, competitors are stronger, substitutes are overlooked, regulations are restrictive, or the required technology is immature.

Market, industry and technology analysis provides the evidence required to make informed product decisions. Market analysis examines customers, needs, demand, segments and growth. Industry analysis examines competitors, suppliers, distributors, substitutes, regulation and industry profitability. Technology analysis examines whether a proposed solution can be built, integrated, operated, scaled and maintained at acceptable cost and risk.

These analyses are interdependent. A market opportunity may depend on a technological breakthrough; technology adoption may depend on regulation and ecosystem partners; and competitive advantage may depend more on distribution or data than on the product itself. Product managers therefore combine quantitative estimates with qualitative judgement and continuously update their assumptions as evidence changes.

Learning Objectives

By the end of this chapter, learners should be able to:

1. Estimate market opportunity using TAM, SAM and SOM.
2. Segment markets using meaningful customer and usage variables.
3. Analyse macro-environmental forces using PESTLE.
4. Evaluate industry structure using Porter’s Five Forces.
5. Compare competitors and substitutes through structured benchmarking.
6. Analyse trends, ecosystems and sources of market power.
7. Assess technological feasibility, maturity, risk and scalability.
8. Translate analytical findings into product-development decisions.

1. The Scope of Environmental Analysis

A useful analysis operates at three levels.

The levels should not be treated as separate reports. They form a decision chain:

Customer problem → addressable market → competitive position → feasible solution → viable product strategy.

Analysis should also distinguish facts, estimates and assumptions. A reported number from a government statistical agency is not equivalent to an internal estimate based on interviews. Both may be useful, but they should be labelled differently. Product teams should record the source, date, method, confidence level and implications of each important assumption.

2. Market Definition and Segmentation

A market is not simply a group of people who could theoretically use a product. It is a group of customers with a shared problem, a relevant use context, the ability and willingness to buy, and access to a transaction or adoption mechanism. Market definition should therefore specify:

• the customer or buyer;
• the user, if different from the buyer;
• the job, problem or outcome sought;
• the product category or substitute solutions;
• the geographic and regulatory boundary;
• the time period; and
• the unit of demand, such as users, subscriptions, transactions or devices.

Market segmentation

Segmentation divides a broad market into groups that are sufficiently similar in needs or behaviour and sufficiently different from one another to justify different product or marketing decisions. Common bases include:

• Firmographic: industry, organisation size, revenue and location.
• Demographic: age, income, occupation and household structure.
• Psychographic: values, attitudes, lifestyle and risk orientation.
• Behavioural: frequency of use, purchase occasion, loyalty and adoption behaviour.
• Needs-based: desired outcomes, pain intensity and unmet needs.
• Technographic: current systems, connectivity, device ownership and technical capability.

Needs-based and behavioural segmentation are often more actionable than demographic segmentation because they connect directly to product design and usage. A segment should be evaluated for its size, growth, accessibility, problem intensity, willingness to pay, competitive pressure and strategic fit.

A segment is attractive only if the organisation can reach it and serve it profitably. A large segment with expensive acquisition, complex regulation or weak willingness to pay may be less attractive than a smaller specialist segment.

3. Estimating Market Size: TAM, SAM and SOM

The TAM–SAM–SOM framework separates theoretical demand from the portion that can realistically be served and captured.

• Total Addressable Market (TAM): total potential revenue or volume if the product category were fully adopted within the defined market.
• Serviceable Available Market (SAM): the portion of TAM that fits the product’s geography, customer type, capabilities and business model.
• Serviceable Obtainable Market (SOM): the portion of SAM the organisation can reasonably capture within a specified period, considering competition, resources and execution.

TAM is useful for understanding long-term potential, but it is frequently overstated. SAM and SOM are more relevant to near-term planning.

A top-down estimate starts with external market data and applies filters. A bottom-up estimate starts with the number of potential customers, expected usage and price. The bottom-up revenue estimate is:

where N is the number of potential customers, f is the average purchase or usage frequency per period, p is the price per purchase or unit, and t is the number of periods considered. The units must be consistent. For example, if N is customers, f is purchases per customer per month, p is currency per purchase and t is months per year, the result is currency per year.

For a subscription product, a simplified annual revenue estimate is:

where r is the proportion of potential customers expected to subscribe in the period and P is monthly subscription price. This estimate assumes a constant average subscription rate and price and does not account for churn, discounts, taxes or refunds. If customer counts change materially over time, a cohort or monthly model is more appropriate.

Worked example: bottom-up market sizing

An educational software company defines its SAM as 40,000 eligible institutions. Research suggests that each institution could purchase an average of 25 licences at £18 per licence per month. The theoretical annual SAM revenue is:

40,000 × 25 × £18 × 12 = £216,000,000

The company expects to reach 3% of institutions within five years. If its SOM assumption is based on institutions rather than licences, the estimated annual SOM revenue at that penetration is:

£216,000,000 × 0.03 = £6,480,000

This is an estimate, not a forecast. It assumes the 3% penetration applies uniformly, that all 25 licences are purchased, and that price remains £18 per month. Sensitivity analysis should test lower adoption, lower utilisation and price discounts.

A penetration estimate can be expressed as:

The numerator and denominator must refer to the same period, geography, customer definition and unit. Mixing users with organisations, or annual customers with monthly customers, produces a misleading result.

Triangulation and sensitivity

Credible market sizing compares at least two methods. If a top-down estimate is much larger than a bottom-up estimate, the difference should be investigated rather than averaged automatically. Important sensitivity variables include price, adoption rate, customer count, usage frequency, churn, regulatory eligibility and sales capacity.

4. PESTLE Analysis

PESTLE examines external forces that may create opportunities or threats:

PESTLE is not a list of news headlines. Each factor should be linked to a time horizon, probability, impact and product implication. For example, a new data-protection rule may affect architecture, consent design, storage location, supplier contracts and launch timing.

A practical prioritisation score can be calculated as:

This is a decision aid rather than a scientific law. If both factors are scored from 1 to 5, the resulting score ranges from 1 to 25. Teams must define the scales consistently. A high score indicates that an issue deserves investigation or mitigation; it does not prove that the event will occur.

PESTLE should be revisited because external conditions change. Scenario planning is useful when uncertainty is high. A team may define optimistic, base and adverse scenarios and examine how each would affect market size, cost, technology choice and launch timing.

5. Industry Structure: Porter’s Five Forces

Porter’s Five Forces analyses the pressures that influence industry profitability and the ability of firms to capture value.

Rivalry among existing competitors

Rivalry tends to increase when many competitors offer similar products, market growth is slow, switching costs are low, fixed costs are high, or competitors frequently reduce prices. Differentiation, brand, network effects, service quality and specialised capabilities can reduce direct rivalry.

Threat of new entrants

Entry is easier when capital requirements are low, technology is widely available, regulation is limited and distribution channels are open. Barriers may include scale economies, trust, intellectual property, data advantages, certifications, switching costs and access to suppliers.

Bargaining power of buyers

Buyers have greater power when they are concentrated, can compare alternatives easily, purchase large volumes, face low switching costs or can produce the solution themselves. Buyer power may force lower prices, additional service or customised features.

Bargaining power of suppliers

Suppliers are powerful when they are concentrated, provide specialised inputs, have strong intellectual property, or would be costly to replace. Cloud infrastructure, semiconductor components, data providers and specialised technical labour may all be strategically important suppliers.

Threat of substitutes

A substitute solves the same underlying customer problem through a different approach. A spreadsheet, manual process, consultant or physical product may substitute for software. Substitutes constrain price even when direct competitors are absent.

The Five Forces model describes structural pressure, not a complete competitor analysis. It should be combined with customer research, capability analysis and ecosystem analysis. Digital markets may also require explicit consideration of platform dependence, data network effects and complementors.

6. Competitors, Substitutes and Benchmarking

Competitor analysis should include more than organisations with an identical feature set. Four useful categories are:

1. Direct competitors: offer a similar product to the same target segment.
2. Indirect competitors: solve a related problem through a different product category.
3. Substitutes: provide another way to achieve the desired outcome.
4. Potential entrants: have capabilities or adjacent products that could enter the market.

A competitor profile may include target segment, value proposition, pricing, channels, strengths, weaknesses, technology, partnerships, customer reviews and likely strategic response. Public information is useful but incomplete; interviews, trials and win–loss analysis can reveal the customer’s actual decision criteria.

Benchmarking compares performance or capability against a reference point. A feature benchmark should not merely count features. It should assess customer value, quality, usability, reliability, integration, total cost of ownership and evidence of adoption.

A weighted scorecard can support comparison:

Here, wᵢ is the weight assigned to criterion i, sᵢ is the score of the alternative on criterion i, and n is the number of criteria. If weights sum to 1 and scores use the same scale, the overall score remains on that scale. The method assumes criteria are sufficiently independent and that the scores are meaningful; it should not conceal important disqualifying risks. A product that fails a mandatory safety or legal requirement should not be rescued by a high total score.

7. Trends, Drivers and Weak Signals

A trend is a sustained direction of change; a fad is usually shorter-lived and less structurally significant. Product teams should distinguish:

• Drivers: forces causing change, such as demographic shifts or regulation.
• Indicators: observable evidence, such as adoption rates or investment.
• Implications: consequences for customers, business models and technology.
• Uncertainties: factors whose direction or timing is unclear.

Trend analysis should examine historical evidence, current indicators and plausible future effects. Useful sources include official statistics, academic research, industry reports, patent databases, procurement data, company filings, product reviews, search behaviour and expert interviews. No single source should be treated as neutral or complete; commercial reports may use opaque definitions, while search data may show interest rather than purchasing behaviour.

A trend becomes strategically relevant when it affects a customer problem, changes the economics of delivery, alters regulation, or shifts the basis of competition. For example, the growth of generative AI may create new product capabilities while also increasing concerns about accuracy, copyright, privacy, data leakage and accountability.

8. Ecosystem Analysis

An ecosystem is the network of actors whose resources, decisions and interactions influence a product’s value. Actors may include customers, users, suppliers, distributors, regulators, platforms, complementors, standards bodies, service providers and communities.

The product manager should identify:

• who provides essential inputs;
• who controls customer access or discovery;
• who owns important data or interfaces;
• which complements increase product value;
• where standards or interoperability matter;
• which actors can block, imitate or commoditise the offering; and
• how value and revenue are distributed.

Ecosystem mapping often reveals that the product is not an isolated object. A healthcare application may depend on clinicians, hospitals, insurers, identity providers, device manufacturers and regulators. A connected-home product may depend on operating systems, communication standards, installers and cloud infrastructure.

Network effects occur when the value to one participant changes as participation changes. Direct network effects arise among similar users; indirect effects arise when one group attracts complements or another group, as in a platform. Network effects can create defensibility, but they can also create concentration, lock-in and governance responsibilities.

9. Technology Scouting and Feasibility

Technology scouting is the systematic search for technologies, suppliers, research findings, patents, standards and emerging capabilities that may enable or threaten a product. It should be connected to a product need rather than driven by fascination with novelty.

A feasibility assessment considers at least five dimensions:

1. Technical feasibility: Can the required performance be achieved with available components, algorithms, skills and infrastructure?
2. Operational feasibility: Can the organisation deploy, monitor, support and maintain the solution?
3. Economic feasibility: Can it be delivered at a cost compatible with the business model?
4. Regulatory and ethical feasibility: Can it comply with applicable requirements and responsible-use expectations?
5. Scalability: Can capacity, reliability, security and support grow with demand?

Technology Readiness Levels

Technology Readiness Levels, commonly expressed from TRL 1 to TRL 9, describe progression from basic principles to a proven system in an operational environment. The precise definitions vary by institution, so teams should state the framework used. A laboratory prototype is not equivalent to a production-ready service. Product decisions must also consider manufacturing readiness, integration readiness, cybersecurity and organisational capability.

Technical proof of concept

A proof of concept should test the riskiest assumptions, not merely demonstrate an attractive interface. A useful experiment specifies the hypothesis, test method, success threshold, data required, duration, cost and decision rule. For example:

A document-classification model will achieve at least 90% precision on a representative validation set while keeping average processing time below two seconds per document.

The measures must be defined. Precision is the proportion of predicted positive cases that are actually positive:

This formula applies to a binary classification context and does not by itself measure coverage. If missing positive cases is also important, recall should be assessed:

The validation data should represent real operating conditions. Performance on a convenient laboratory dataset may not generalise to different languages, devices, users or environments.

Technology risk and total cost

Technology risk includes uncertain performance, integration failure, supplier dependence, cybersecurity vulnerabilities, data quality, obsolescence, maintainability and skills shortages. A risk register should record the risk, cause, consequence, likelihood, impact, owner, mitigation and contingency.

Technology cost is broader than purchase price. Total cost of ownership may include acquisition, integration, licences, hosting, energy, training, support, upgrades, compliance, downtime and disposal. A low initial cost may produce a high lifecycle cost.

10. Integrating Analysis into Product Decisions

Analysis becomes valuable when it changes action. A product team may use findings to decide:

• which segment to serve first;
• which problem to prioritise;
• whether to build, buy, partner or license;
• which features belong in the minimum viable product;
• which claims can be responsibly made;
• what evidence is needed before a funding gate;
• how to position against alternatives; and
• whether to proceed, pivot, pause or stop.

A useful decision record links each conclusion to evidence and uncertainty. For example:

The analysis should be updated at stage gates. Early estimates may guide exploration; later decisions require stronger evidence from prototypes, pilots, contracts, compliance reviews and actual customer behaviour.

Illustrative Case: GreenRoute Fleet Software

Background

GreenRoute is a fictional start-up considering software that helps small delivery fleets reduce fuel consumption and emissions. The proposed product combines route planning, driver guidance and performance reporting.

Problem

The founders initially described the market as “all commercial vehicles.” This definition was too broad. It included large logistics firms with sophisticated systems, owner-drivers with limited budgets, public-sector fleets and companies operating under different regulations.

Analysis

The team conducted interviews with fleet owners, drivers and operations managers. It identified a promising initial segment: regional firms operating 10–50 delivery vehicles, using basic spreadsheets and experiencing high fuel costs. The segment had a clear economic problem, but adoption depended on integration with existing telematics devices and driver acceptance.

A competitor review found several established route-planning systems. Direct competition was strong, but many small firms considered those systems expensive or difficult to configure. Substitutes included manual scheduling, generic mapping applications and outsourced planning.

PESTLE analysis identified fuel-price volatility as an economic driver, emissions reporting as a regulatory driver and privacy concerns relating to driver data as a legal and ethical issue. Ecosystem analysis showed dependence on mapping data, vehicle telematics providers, fuel-card data and fleet-management resellers.

The technical team tested whether route recommendations could be generated within the required time and whether data from two common telematics systems could be integrated reliably. It discovered that route optimisation was technically feasible, but inconsistent vehicle data would reduce recommendation quality. The team therefore treated data integration as a core feasibility risk rather than an implementation detail.

Approach and solution

GreenRoute narrowed its beachhead market to regional delivery firms in one country. It designed a pilot with ten fleets and defined success measures: reduction in fuel consumption, route-planning time, driver acceptance and weekly system reliability. It pursued a partnership with a telematics provider rather than building device integrations independently.

The minimum viable product focused on reliable data import, route planning, exception alerts and transparent reporting. Advanced predictive features were postponed until data quality had been demonstrated.

Outcome

The fictional pilot produced mixed results: route-planning time improved, but fuel savings varied by fleet because driver behaviour and vehicle condition differed. The company learned that a credible product claim should specify the conditions under which savings occur. It also learned that reseller partnerships could reduce acquisition cost but might weaken direct customer relationships.

Learning points

1. A broad market statement is not a usable segmentation strategy.
2. Substitutes include manual and informal processes.
3. Technical feasibility includes data quality and integration, not only algorithm design.
4. Regulatory and privacy issues should be considered before launch.
5. Pilots should measure customer outcomes, not merely feature completion.
6. Partnerships can accelerate entry while creating dependency and governance issues.

Challenges, Limitations and Responsible Practice

Market estimates are uncertain because definitions, sources and assumptions differ. Teams may suffer from confirmation bias, selecting evidence that supports an attractive idea. Competitor analysis can also become superficial if it relies only on websites and feature lists.

Ethical analysis is essential. Customer research should use informed consent, minimise personal data collection and protect confidential information. Products using AI or automated decisions require attention to bias, explainability, human oversight, security and accountability. Environmental claims should be supported by credible evidence and should not imply benefits that have not been measured across the product lifecycle.

Regulatory obligations vary by jurisdiction and product category. Product teams should obtain appropriate legal, security, safety and compliance advice rather than treating a general framework as a substitute for professional review. Intellectual-property searches should not be interpreted as definitive legal clearance without qualified advice.

Best practice is to maintain an assumptions log, triangulate evidence, involve technical and commercial specialists, test the highest-risk assumptions early, document uncertainty and revisit analysis after material changes. The goal is not to predict the future perfectly. It is to make better decisions, expose risks early and allocate learning effort where it has the greatest value.

Chapter Summary

Market, industry and technology analysis provides the evidence base for product-development decisions. Market analysis defines customers and problems, segments demand and estimates opportunity through TAM, SAM and SOM. Bottom-up sizing is often valuable because it makes customer counts, usage, price and adoption assumptions visible.

PESTLE identifies political, economic, social, technological, legal and environmental influences. Porter’s Five Forces examines rivalry, entry, buyer power, supplier power and substitutes. Competitor analysis should include direct and indirect competitors, substitutes and potential entrants. Benchmarking is most useful when it assesses customer value, performance, experience, economics and trust rather than merely counting features.

Trend and ecosystem analysis reveal changes and dependencies beyond the immediate product. Technology scouting and feasibility assessment test whether a solution can be built, integrated, operated, scaled and governed. Technical proofs of concept should target the riskiest assumptions and use clearly defined measures.

Effective product managers integrate these perspectives into choices about segments, positioning, partnerships, architecture, MVP scope, evidence requirements and launch timing. Because evidence is incomplete and conditions change, analysis must be transparent, iterative and ethically responsible.

Key Terms

TAM: Total potential market demand within a defined category and boundary.

SAM: Portion of TAM that fits the product’s capabilities, geography and business model.

SOM: Portion of SAM that the organisation can realistically obtain.

Market segmentation: Division of a market into groups with meaningful similarities and differences.

Needs-based segment: Customer group defined by a shared problem or desired outcome.

PESTLE: Framework analysing political, economic, social, technological, legal and environmental forces.

Industry: Network of organisations and activities involved in supplying related products or solutions.

Competitive rivalry: Intensity of competition among existing firms.

Substitute: A different solution that satisfies the same underlying customer need.

Benchmarking: Structured comparison against competitors, standards or reference performance.

Ecosystem: Interdependent network of actors influencing a product’s value creation and delivery.

Complementor: Actor whose product or service increases the value of another product.

Technology scouting: Systematic search for relevant technologies, suppliers, research and standards.

Technical feasibility: Degree to which a proposed solution can achieve required performance.

Technology Readiness Level: Scale describing progression from basic research to proven operational technology.

Proof of concept: Focused experiment testing whether a critical technical or commercial assumption is credible.

Total cost of ownership: Full lifecycle cost of acquiring, operating, maintaining and retiring a solution.

Network effect: Change in value associated with changes in participation or connected users.

Review Questions

Short Answer Questions

1. What is the difference between TAM, SAM and SOM?
2. Why are substitutes included in competitor analysis?
3. List the six dimensions of PESTLE.
4. What is the purpose of a technical proof of concept?
5. Name three factors that can increase buyer power.

Long Answer Questions

1. Explain how a product team can create and evaluate a needs-based market segment.
2. Compare top-down and bottom-up market-sizing methods, including their strengths and limitations.
3. Explain Porter’s Five Forces and discuss how each force may affect product strategy.
4. Describe how ecosystem analysis can reveal dependencies that are missed by competitor analysis.
5. Explain why technical feasibility includes operational, economic, regulatory and scalability considerations.

Analytical / Application Questions

1. A firm identifies 12,000 potential customers. Each could purchase 4 units per year at £75 per unit. Estimate the annual market value and state two assumptions that should be tested before using the estimate for planning.
2. Select a product category and construct a compact PESTLE analysis. For each factor, identify one likely product implication and one uncertainty.
3. A proposed AI product performs well in a laboratory but poorly on data from real customers. Analyse possible causes and recommend a feasibility-testing plan before launch.

Multiple Choice Questions with Answers

Question 1

Which statement best describes SOM?

A. The total theoretical demand for every related product

B. The portion of the market that fits the product’s capabilities

C. The portion of SAM the organisation can realistically capture

D. The number of competitors currently operating

Correct Answer: C. The portion of SAM the organisation can realistically capture

Question 2

A company has 2,000 customers, each purchasing 3 units per year at £40 per unit. What is the estimated annual revenue?

A. £8,000

B. £24,000

C. £80,000

D. £240,000

Correct Answer: B. £24,000

Question 3

Which PESTLE factor primarily concerns data-protection law?

A. Political

B. Social

C. Legal

D. Environmental

Correct Answer: C. Legal

Question 4

Which force is represented by a customer switching from specialist software to a spreadsheet?

A. Supplier power

B. Threat of substitutes

C. Threat of new entrants

D. Competitive rivalry only

Correct Answer: B. Threat of substitutes

Question 5

Which is the strongest example of needs-based segmentation?

A. Customers aged 18–25

B. Customers living in cities

C. Customers who need rapid compliance reporting

D. Customers using a particular smartphone brand

Correct Answer: C. Customers who need rapid compliance reporting

Question 6

In a weighted scorecard, what does the weight normally represent?

A. The importance assigned to a criterion

B. The number of competitors

C. The product’s unit price

D. The age of the technology

Correct Answer: A. The importance assigned to a criterion

Question 7

What should a high-risk technical proof of concept primarily test?

A. The attractiveness of the presentation design

B. The riskiest feasibility assumption

C. The maximum number of marketing channels

D. The organisation’s historical revenue

Correct Answer: B. The riskiest feasibility assumption

Question 8

Which statement about precision is correct?

A. It is true positives divided by true positives plus false positives

B. It is true positives divided by true positives plus false negatives

C. It is false positives divided by all negative cases

D. It is total correct predictions divided by total predictions

Correct Answer: A. It is true positives divided by true positives plus false positives

Question 9

Why can a feature-count comparison be misleading?

A. Features never influence customer value

B. It ignores the value, quality and usability of capabilities

C. Competitors cannot be compared quantitatively

D. It always produces identical scores

Correct Answer: B. It ignores the value, quality and usability of capabilities

Question 10

Which issue is an example of ecosystem dependence?

A. A product has a colourful user interface

B. A service relies on a mapping platform controlled by another firm

C. A team holds a weekly planning meeting

D. A customer changes a password

Correct Answer: B. A service relies on a mapping platform controlled by another firm