Customer, Problem, and Fit

Northstar begins with the customer situation, not a package name. The first decision is whether the observed problem is important, serviceable, and sufficiently evidenced to justify designing a bounded offer. The retained Customer-Problem Brief supplies the accepted facts that open the Offer Spec.

An offer should begin with a customer situation, not with a feature list. Northstar did not begin by inventing a gold maintenance tier. It began with a retailer that had emergency interruptions, uneven service records, and eight sites managed by one regional operator.

The intended customer is the kind of buyer and operating situation for which the offer is built. It is narrower than everyone who could possibly buy. For Northstar, the intended customer is a regional retailer with five to ten locations inside the current service area, ordinary commercial heating and cooling equipment, and one person accountable for facilities across the sites.

The customer problem is the undesirable condition the customer is trying to change, expressed in the customer's work rather than the seller's capabilities. Northstar's customer problem is not lack of a preventive-maintenance subscription. It is avoidable operating interruption and incomplete maintenance evidence across multiple stores.

The current alternative is the method the customer uses now, including delay or no action, and the cost, inconvenience, risk, or limitation that accompanies it.

These statements establish fit before price. If the intended customer and problem are vague, every later choice becomes unstable: packages accumulate features, salespeople negotiate around uncertainty, and delivery absorbs cases the offer was never built to serve.

Build a Customer-Problem Brief

A Customer-Problem Brief is a one-page record of the evidence behind the customer and problem choice. It contains five items:

1. 01the customer's operating context;
2. 02the problem in observable terms;
3. 03the consequence if the problem continues;
4. 04the evidence collected and its limits;
5. 05the conditions that make a customer eligible or ineligible.

The brief is deliberately separate from the Offer Spec while the idea is being tested. Once the offer is released, its accepted conclusions can be summarized in the Offer Spec and the underlying evidence retained for review.

Table 2.1 - Match evidence to the decision it can support

The table prevents a common evidence error: asking one source to answer a question it cannot answer. Interviews can reveal how a facilities manager evaluates risk, but stated willingness to pay is not the same as a signed order. Service records can show emergency calls, but they do not prove why every incident occurred. A pilot can reveal delivery work, but a small early sample does not establish long-term market behavior.

Research on new-product pricing supports integrating customer-value information with market and organizational inputs rather than treating price as an isolated calculation (Ingenbleek et al. 2013). Executive attention and cross-functional pricing capability are also associated with stronger pricing practice, although observational relationships should not be read as universal causal laws (Liozu and Hinterhuber 2013).

Write the problem in observable language

Use a sentence that a customer and an operator could both test:

When [situation occurs], [customer] experiences [observable condition], which creates [material consequence]. The current alternative is [current response], limited by [constraint].

Northstar writes:

When equipment condition differs across stores and maintenance records are incomplete, the regional facilities manager cannot plan interventions consistently. Emergency interruptions disrupt store operations, while reactive service provides little comparable history for the next decision.

This formulation avoids three weak substitutes for a problem:

• —a broad aspiration such as improve efficiency;
• —a seller-centered statement such as customers need our platform;
• —an unsupported diagnosis such as downtime is caused by poor maintenance.

The last statement might be true in a particular incident, but the evidence must establish it. Northstar can say that emergency interruptions occurred and records were inconsistent. It cannot yet promise that its program will prevent every closure.

State the consequence without inflating it.

A useful problem has a consequence the customer recognizes. The consequence may be lost time, avoidable cost, delayed revenue, risk exposure, rework, poor visibility, or a blocked decision. Quantify it only when the calculation is supportable.

For example, a customer may estimate the cost of one closed store hour. Northstar should record who made the estimate, what it includes, and the range of uncertainty. It should not turn one customer's estimate into a market-wide fact. If the consequence is strategically important but hard to monetize, state the operational effect directly and use a range or conditional estimate instead of invented precision.

The practical test is whether the consequence changes a decision. If the retailer would take no action even after seeing the evidence, the problem may not support a paid offer now. If the consequence matters but Northstar cannot affect it safely or economically, the opportunity is still a poor fit.

State who is eligible and what is outside the offer

Eligibility criteria are observable conditions a customer must meet for the ordinary path. They protect the customer from an unsuitable promise and the seller from unplanned work. Good criteria can be checked before signature.

Northstar's first release requires:

• —five to ten locations;
• —every location inside the published service area;
• —ordinary commercial heating and cooling equipment;
• —safe and scheduled access to each unit;
• —one customer contact authorized to coordinate all locations;
• —agreement to the standard twelve-month term and documentation method.

An exclusion is a condition the offer does not cover. It should identify the boundary and, when useful, the next available action. Northstar excludes regulated clean-room equipment, locations outside the service area, unsafe or inaccessible units, repairs and parts, after-hours visits, and equipment that cannot be assessed within the planned visit duration. An excluded customer may receive a separate inspection, a change proposal, or a referral. The exclusion is not permission to improvise.

Eligibility differs from qualification rhetoric. It is not a description of an attractive account. It is a delivery and commercial test tied to the actual promise.

Separate the buyer from the user and beneficiary

In many offers, one person approves the purchase, another coordinates it, and others experience the result. Name each role before writing the package.

At Northstar:

• —the regional facilities director approves the commitment;
• —store managers provide local access;
• —technicians perform and document the visits;
• —finance staff process quarterly invoices;
• —store employees and customers benefit from fewer interruptions.

This role map exposes prerequisites. The program cannot succeed if store managers do not grant access or if no regional contact resolves scheduling conflicts. Those are customer responsibilities, not hidden delivery assumptions.

For a software offer, the equivalent roles might include the person who approves the business case and budget, an administrator, end users, information-security reviewers, and finance approvers. For professional services, the client may need to supply data, make decisions within a set time, and assign a project lead. Use role names from the customer's actual work.

Study the current alternative

The customer is already doing something, even if that action is delay, manual work, or acceptance of the condition.

Northstar's retailer calls contractors when equipment fails, stores visit notes in inconsistent local files, and relies on the regional manager to assemble history when a decision is due. Northstar should confirm each statement with the retailer and available records. It should not assume that reactive work is always irrational. The customer may prefer it when equipment is near replacement, the interruption cost is low, or preventive access is difficult.

Record four comparisons:

• —what the customer does now;
• —what the customer pays or commits now, when supportable;
• —what the current approach does well;
• —which limitation the proposed offer changes.

Also identify the buyer's other credible choices: another provider, internal staff, equipment replacement, a narrower inspection, insurance, software, or no action. Use current, attributed market evidence for claims about competitor price or capability. A salesperson's recollection may be a lead for research, not a verified fact.

This comparison helps Northstar avoid selling preventive care as an abstract good. The offer must be more useful than the retailer's available alternatives for this equipment, geography, and management structure. It also improves price research because the buyer compares the proposed commitment with a real choice, not with zero.

Ask questions that change the offer

An interview guide should not be a general discovery script. Ask questions whose answers alter eligibility, package contents, price input, contract terms, or delivery.

For Northstar:

1. 01How many locations does one facilities team coordinate?
2. 02Which equipment types and ages create materially different service work?
3. 03What record proves that a visit was useful?
4. 04Who grants site access, and how often does access fail?
5. 05Which events require after-hours response?
6. 06How are emergency calls and scheduled maintenance purchased today?
7. 07What would make a twelve-month commitment unacceptable?
8. 08Which location changes occur during a year?

Record the answer and the decision it affects. A question with no possible consequence is conversation, not design evidence.

Rate confidence honestly.

For each material claim, use one of three confidence levels:

• —Observed: supported by a direct record, behavior, or completed transaction.
• —Corroborated: supported by more than one independent source but not yet tested in the full offer.
• —Assumed: plausible and important, but still dependent on a pilot or later evidence.

Northstar marks the existence of emergency calls as observed, the need for consistent records as corroborated across interviews and observations, and the claim that two visits per year will reduce interruptions as assumed. This does not weaken the case. It tells the team what to measure.

Do not turn confidence labels into scoring theater. Their purpose is to direct the next action. An assumed claim that could make the offer unsafe or unprofitable blocks release. An assumed claim with limited downside may be tested in a controlled pilot.

Make the fit decision

At the end of the evidence review, choose one of four actions:

1. 01Proceed: the problem is material, the customer is identifiable, and the company can test a bounded response.
2. 02Narrow: the problem is real, but the eligible customer or promise must be smaller.
3. 03Collect evidence: one or more material assumptions need a record, observation, or paid test.
4. 04Stop: the problem is weak, the company cannot affect it responsibly, or the work cannot support a viable offer.

Northstar chooses narrow. It proceeds only with five to ten in-area locations and excludes older equipment until an inspection shows that the planned service time is realistic. This decision is more useful than a broad claim that multi-site retailers are the target market. It tells sales whom to approach, tells delivery what to inspect, and tells finance which cost range to test.

Conclusion

• —Build a Customer-Problem Brief that ties each claim to evidence suited to the decision.
• —State eligibility criteria and exclusions that sales and delivery can verify before signature.
• —Classify evidence as observed, corroborated, or assumed, then proceed, narrow, collect evidence, or stop.

Chapter glossary

• —Intended customer: The buyer and operating situation for which the offer is deliberately built.
• —Current alternative: What the customer does now, including delay or no action, and the limitations of that choice.
• —Customer-Problem Brief: A one-page record of the customer context, observable problem, consequence, evidence, and eligibility boundaries.
• —Eligibility criteria: Observable conditions a customer must meet to use the ordinary path.
• —Exclusion: A condition or work category the offer does not cover, with the next permitted action stated when useful.
• —Observed: A confidence label for a claim supported by a direct record, behavior, or completed transaction.
• —Corroborated: A confidence label for a claim supported by more than one independent source but not yet tested in the full offer.
• —Assumed: A confidence label for a plausible material claim that still requires a pilot or later evidence.