Mapping Value Creation and Capture in Technology Companies

Hello. This first module establishes an enterprise-wide view of leadership: before deciding what to build or fund, you need to see how a company works for the people who depend on it. Later lessons will examine executive accountabilities and how to assess initiatives. Today, you’ll build the starting map: who contributes to a technology or product company, what value each group receives, and how the company earns enough to sustain the exchange.

The goal is not to master accounting or complete a nine-part business plan. It is to be able to look beyond an appealing product idea and explain the business around it. Allow about 35–40 minutes, including the short videos and reading.

Begin with the people around the product

A product may be designed for one person, purchased by another, delivered with help from partners, and funded by investors. Treating all of them as “the customer” hides important differences. For example, a workplace software tool can be pleasant for employees to use but still fail if their employer cannot justify paying for it. Conversely, a paying buyer may see financial benefits while employees find the tool burdensome.

R. Edward Freeman’s account of stakeholder theory offers a useful starting point: a business can create—or impair—value for customers, suppliers, employees, communities, and financiers. Their interests sometimes conflict, but the business cannot be understood by looking at just one group.

For this lesson, distinguish three things:

• A contribution: what a stakeholder supplies, such as payment, work, technology, capital, or permission to operate.
• Value received: what makes participating worthwhile to them. It may be money, saved time, useful experience, learning, or reduced risk.
• Value captured by the firm: the revenue the company retains after paying the costs required to serve customers. Revenue alone is not profit.

This is an executive lens, not just an ethical checklist. If a critical partner cannot earn enough to participate, or employees cannot do the work sustainably, an attractive customer proposition may not survive.

Turn the stakeholder picture into a business model

A business model connects three questions: What valuable outcome does the company create? How does it deliver that outcome reliably? How does it receive payment and cover the cost of doing so?

The Business Model Canvas makes those connections visible on one page. Watch the overview and its technology-company example; there is no need to memorize every box yet.

You can compress the canvas into a few executive questions. Customer segments and value proposition identify who benefits and why they would choose this offering over an alternative. Channels and relationships explain how people find, receive, and continue using it. Resources, activities, and partners explain what must happen behind the scenes. Revenue streams and cost structure reveal whether the exchange can support a business.

The Google example illustrates a feature common in technology: different groups can play different economic roles. Search users receive a useful service without paying for each search; advertisers pay to reach an audience. The users still matter enormously to the business model. Equally, a “key partner” need not be peripheral or easily replaced—an essential external relationship can determine whether the offering works at all.

For innovation leadership, this distinction changes the questions you ask about a concept. “Will people use it?” is necessary, but not sufficient. You also need to know who will pay, what outcome warrants payment, which capabilities make delivery possible, and which participants must find the arrangement worthwhile.

See how value is shared

The value stick adds an economic view to the stakeholder map. Read the short explanation, then use the image as a reference.

Willingness to pay is the most a customer would pay for an offering, given their alternatives. The customer’s benefit from a purchase is the gap between that amount and the actual price. The firm receives the price but incurs costs to deliver the offering; the gap between price and cost is its margin for the costs included. A supplier’s willingness to sell is the lowest compensation at which supplying an input would be worthwhile. The gap between its payment and that minimum is value for the supplier.

Consider a deliberately simple transaction: a customer would pay at most 150 units, the firm charges 100, and it pays one supplier 65 to provide the entire offering. That supplier would have accepted 45. On these assumptions, the customer receives 50 units of value above the price, the firm retains 35 before any other expenses, and the supplier receives 20 above its minimum. These are different shares of value, not three versions of company profit.

Real technology companies have many employees, suppliers, and costs, so a single stick is a simplification. Willingness to pay and willingness to sell are also estimates, not figures you can usually read from an invoice. The model’s practical lesson is the set of levers it reveals: a better experience may raise customer willingness to pay; a more effective delivery system may reduce cost; a better arrangement for a partner may make participation worthwhile without simply demanding a lower price. Raising price alone can increase the firm’s share while reducing the customer’s share—it does not necessarily create more value overall.

Map a product company as a whole

Imagine a company offering software that helps commercial fleet operators detect maintenance problems earlier. A maintenance planner uses the tool; an operations executive approves the purchase. The company combines product design, software development, vehicle data, cloud infrastructure, and customer support to deliver a credible warning that helps the operator avoid disruption.

A compact stakeholder map might look like this:

The company creates value if earlier, usable warnings genuinely improve decisions for operators and planners. It delivers value through the software, integrations, support, and partner arrangements—not through the prediction algorithm alone. It captures value through subscriptions paid by fleet operators. It must use that revenue to compensate employees and partners, run the service, and fund the business.

Suppose, purely to make the economics visible, that the operator would pay up to 150 per vehicle each month, the subscription costs 100, and providing the service costs the firm 65 per vehicle-month in attributable delivery costs. The operator has an estimated 50 of benefit above the price; the firm has 35 remaining before costs omitted from that estimate, such as some central overhead. Neither number proves success. The operator’s willingness to pay must be tested against its alternatives and actual results; the firm must establish that the service remains reliable as it grows.

Notice two common traps. First, the buyer’s benefit does not guarantee the user’s benefit: a planner overwhelmed by false alarms may stop using the system, undermining the promised savings. Second, the firm’s revenue is not all the value it creates—or all the value it keeps. Employees and partners need a worthwhile share, while effects on the wider community may be positive or negative. Investors’ funding supplies capital; it is not customer revenue.

An executive-ready first map therefore shows more than a list of stakeholders. It identifies the buyer and user separately, names the outcome each needs, states how the firm gets paid, identifies the capabilities and partners required for delivery, and marks uncertain claims—such as the amount of downtime actually avoided—as assumptions rather than facts.

Conclusion

A technology company creates value through an outcome people prefer to their alternatives, delivers it through a coordinated set of activities and relationships, and captures part of that value through its revenue model after meeting its costs. The strongest map keeps buyers, users, employees, partners, investors, and wider impacts in view without assuming they all benefit in the same way.

This map is the baseline for the next lesson. You’ll use it to distinguish what a functional executive, product or innovation executive, business-unit head, and CEO are each accountable for—and where their decisions must connect.