2 Market Changes and Project Value

From market conditions to revenue

A project's market outlook affects its value because market conditions shape the cash it is expected to generate. Assessing market changes means translating shifts in demand, competition, prices, and customer behavior into realistic revenue and cash-flow forecasts, rather than simply extending past sales trends.

A useful starting relationship is:

Revenue changes when either units sold or realized price changes. Product mix can also shift the average net price.

Demand and customer behavior

Distinguish a Movement along the demand curve from a Shift in demand. A price change generally changes the quantity customers demand when other factors are held constant. A shift in demand means customers would buy more or less at a range of prices; changing preferences, incomes, population, or the availability of substitutes can cause such a shift.

Forecasts should identify who is likely to buy, how often, and in what quantities. Relevant factors include:

• Market size and adoption: A larger addressable market or faster adoption can increase expected sales. A smaller market or slower adoption can delay or reduce them.

• Purchase frequency and retention: More repeat purchases or lower customer churn can raise recurring revenue. Lower usage, delayed repurchases, or higher churn can reduce it.

• Customer mix: A shift toward higher-value or lower-value customers changes average sales and may also affect service or selling costs.

• Substitutes and preferences: Customers may switch to alternatives, change what they value, or stop buying altogether.

Useful evidence includes customer interviews, observed purchase and renewal behavior, sales pipelines, market data, and carefully designed tests. Distinguish evidence of current interest from evidence of actual willingness to pay and repeat purchase.

Competition and pricing

Competition affects both the number of units a project can sell and the price it can sustain. New competitors, expanded capacity, or improved substitutes may force discounts, reduce market share, or increase marketing and service costs. A competitor's exit, a differentiated product, or strong customer loyalty may support higher prices or sales. Competition can also affect innovation and product quality, which in turn influence future demand.

Price elasticity of demand describes how strongly customers respond to price changes. When demand is elastic, a price increase can reduce quantity by a larger percentage and lower total revenue. When demand is inelastic, quantity falls by a smaller percentage and revenue may rise. Elasticity can differ by customer group, product, and time period.

For example, a project expecting to sell $10{,}000$ units at a net price of $\$50$ has projected revenue of $\$500{,}000$. If a competitor's move leads to a $5\%$ net-price cut while expected unit sales also fall by $8\%$, projected revenue becomes $9{,}200 \times \$47.50 = \$437{,}000$, a $12.6\%$ decrease. The revenue impact is larger than either percentage change alone because both price and volume changed.

From revenue to project value

Revenue is not the same as cash flow. A market change can also affect variable costs, customer-acquisition expenses, staffing, capacity needs, working capital, and the investment required to sustain growth. A lower price may increase sales volume but still reduce profit if the additional units do not cover their costs. Growth can require new investment before it generates additional cash.

Reflect market changes in forecasts of Operating cash flows, then assess how those expected cash flows affect value. Do not assume that a $10\%$ change in revenue produces a $10\%$ change in value: the result depends on margins, costs, investment, timing, and risk. Discounted-cash-flow analysis values expected future cash flows while accounting for their timing and risk.

Assessing market changes

Use a structured assessment to connect market evidence to project value:

1. Establish a baseline. Record expected units, net price, customer mix, costs, and timing, and state the assumptions clearly.

2. Identify market changes. Consider demand, customer behavior, competitor actions, substitutes, and likely pricing responses.

3. Translate changes into assumptions. Estimate effects on volume, realized price, mix, costs, and investment. Avoid counting the same effect twice.

4. Build scenarios. Compare a base case with plausible downside and upside cases. Examples include slower adoption, stronger price competition, or higher customer retention.

5. Test sensitivity. Vary key inputs, such as price, sales volume, and adoption timing, to see which assumptions most affect cash flow and value.

6. Update as evidence changes. Compare actual customer and competitor behavior with the forecast and revise assumptions when warranted.

Scenarios are not predictions. They make uncertainty visible and show which market assumptions drive the project's value.