Find the Buyer, the Trigger, and the Urgency

Task

Interview best-fit clients and lost prospects to isolate the buyer, urgency, and trigger event.

Summary

Use interviews and deal history to understand who acts, what changes, and why the problem becomes urgent.

Find the Buying Trigger Before You Build Around the Customer

Task ID: S1-06

A good customer interview does not ask whether people like an idea. It reconstructs a real buying decision: who felt the problem, what changed, why waiting became costly, who joined the decision, and why the buyer chose, delayed, or rejected an option. That evidence helps a company decide which customer, problem, and result are strong enough to build around.

The sale looked clear until you asked why

A founder can often name the company’s favorite customers. The reasons are usually less precise: “They understood the value,” “They were a good fit,” or “They came through a referral.” Lost prospects produce equally vague explanations such as price, timing, or changing priorities.

Those phrases describe the end of the sale, not the cause of it. They do not identify the person who first felt the problem, the event that made the status quo unacceptable, the consequences of waiting, or the internal path from concern to approved spending. In business-to-business purchases, several people may follow partly overlapping paths through need recognition, search, comparison, selection, use, and reassessment. Those paths are rarely linear, and the people who use a solution may not be the people who approve or block it.

This matters before a company turns custom work into a repeatable offer or standalone product. Without a clear buying trigger, the company may package work that customers praise but rarely prioritize, choose a target customer that is easy to reach but expensive to serve, or build software around a recurring annoyance that does not create a funded decision.

The operating principle is simple: reconstruct actual decisions before interpreting the market. Interview best-fit clients to understand why strong customers acted and what result they expected. Interview lost prospects to learn where the same story breaks: weak urgency, the wrong buyer, an unacceptable risk, a better alternative, or no decision at all.

The work can begin without a completed pricing model, product roadmap, or formal market-segmentation project. It has no hard prerequisite. It does, however, become more credible when the team can compare interview accounts with recent sales records, proposals, delivery experience, support history, retention, and financial results. “No dependency” should not be interpreted as “no preparation.”

Reconstruct the event, not the opinion

The most useful interview is about one specific buying episode. It starts with a prompt such as:

“Take me back to the point when this problem first became important enough to address. What was happening?”

This approach is close to the critical incident technique, which asks people for factual accounts of events that materially affected an outcome rather than broad opinions about what usually happens. The technique focuses attention on the situation, the actions taken, and the result.

Three ideas must remain separate throughout the research:

A trigger is not the underlying problem. The problem may have existed for years. The trigger is what changed: a missed deadline, leadership change, new customer, audit finding, failed implementation, budget window, hiring surge, contract renewal, regulation, or visible cost increase. Urgency is the consequence of not responding after that trigger.

Consider a company that has handled new-client onboarding through spreadsheets and senior employees for several years. The manual process is the underlying problem. A major customer escalation, a large hiring class, or an approaching renewal may be the trigger. The risk of losing revenue or failing the next onboarding cycle creates urgency. The buyer is not necessarily “the company.” It may be an operations leader who starts the work, a delivery executive who becomes the internal champion, and a finance leader who approves spending.

Specific-event interviews also reduce a common weakness in market research: people are poor witnesses to their own hypothetical future behavior. A chronological reconstruction asks what they did, who they contacted, what documents they created, what alternatives they considered, and what finally changed. Event-history methods used by the U.S. Census Bureau similarly use timelines and anchor events to help respondents place past events more accurately and consistently.

The distinction between stated preference and observed action is central. A prospect may say that speed, automation, or analytics is important. The buying history may show that the organization acted only after a customer complaint, a leadership deadline, or a costly operational failure. The latter is stronger evidence for qualification, positioning, and offer design.

Choose interviewees for contrast, not convenience

“Best-fit” should not mean the largest, friendliest, or most available customer. It should mean customers whose evidence supports the business the company wants to repeat. Useful selection criteria include:

• a clear and important problem;
• a relatively direct sales process;
• good delivery economics;
• limited exceptional or one-off work;
• fast time to a meaningful result;
• strong retention or repeat purchase;
• willingness to act as a reference.

Not every criterion must be present. The team should state which ones define fit before recruiting. Otherwise, “best fit” will quietly become “people who like us.”

Lost prospects should also be chosen deliberately. Include recent, qualified opportunities that seriously considered the offer. Separate at least three outcomes: a competitor won, the prospect chose an internal or status-quo alternative, and the prospect made no decision. An unqualified lead that never engaged cannot explain why a credible buyer rejected the offer.

For a narrow first pass, a balanced set might include six to eight best-fit clients and four to seven lost or stalled prospects. Within that set, seek different decision roles where the purchase is complex: the person who first raised the issue, the internal champion, the budget owner, a user, and a technical, legal, procurement, or risk reviewer. Buying-center research shows that organizational purchasing involves multiple participants and that their composition and influence vary with the buying situation.

The working target of 10–15 interviews is a planning starting point, not a universal benchmark. A systematic review found that studies with relatively homogeneous populations and narrow objectives often reached code saturation—the point at which few new topics appeared—within 9–17 interviews. A separate study found that identifying the main topics took about nine interviews, while understanding their nuance and variation required 16–24.

That distinction matters. Ten strong interviews may be enough to identify a recurring trigger in one tightly defined segment. They are unlikely to explain several industries, price levels, buying motions, geographies, and decision roles at once. The appropriate number rises when:

• customers differ materially in size, regulation, or use case;
• several people influence the purchase;
• lost prospects tell a different story from clients;
• sales cycles are long or poorly documented;
• the company is testing more than one proposed customer or problem;
• early interviews continue to produce new triggers or decision criteria.

A practical stopping rule is to review the sample after every three interviews. Stop only when the team can name the repeated patterns, identify the important exceptions, and explain why additional interviews are unlikely to change the immediate decision. Interview count is the activity measure; evidence coverage is the quality measure.

Candidate selection should be recorded before outreach. A simple sampling table can prevent the founder or sales team from filling the calendar only with supporters.

The goal is not statistical representation of the whole market. It is useful contrast among cases that can test the company’s current belief.

Run a disciplined interview process

Use a semi-structured guide: the same core questions in every interview, with freedom to probe unexpected details. Official qualitative-research guidance describes this format as a way to keep interviews relevant while allowing follow-up questions and unanticipated topics. The same guidance warns that leading wording, interviewer reactions, and unexamined assumptions can shape responses.

The founder or salesperson should help identify candidates and provide account context, but should not automatically conduct every interview. A lost prospect may be more candid with a neutral researcher who did not own the sale. Social-desirability research shows that interviewees may omit unwelcome views, try to please the interviewer, or react to subtle signals such as approval, surprise, or disagreement.

A useful interview sequence follows the buying episode chronologically.

1. Set the scene. Confirm that the discussion concerns one real purchase or attempted purchase. Ask permission to record, explain how notes will be used, and offer anonymity in the summary.

2. Go back before the search. Ask how the work was handled before the buyer considered change. This reveals the status quo and the true alternatives.

3. Find the first visible change. Ask what happened immediately before the issue received attention. Probe for dates, meetings, failures, deadlines, new leadership, customer pressure, or financial events.

4. Test urgency. Ask what would have happened if the buyer had waited three, six, or twelve months. Look for consequences already felt, not merely possible benefits.

5. Map the people. Ask who raised the issue, who investigated, who shaped requirements, who approved money, who could veto, and who would live with the result.

6. Reconstruct the search. Ask which alternatives were considered, including internal work, delay, another provider, a tool, a new hire, or doing nothing.

7. Reconstruct the decision. Ask what narrowed the field, what proof was required, what created doubt, and what finally tipped the decision.

8. Separate expected from realized value. With clients, ask what result they expected at purchase and what actually happened. With lost prospects, ask what outcome they still wanted and how they pursued it.

9. Close without selling. Ask what the interviewer misunderstood, what question should have been asked, and who else saw the decision differently.

Avoid questions such as “Would automation have helped?” or “Was price the main issue?” They insert the company’s theory into the answer. Prefer “What happened next?”, “How did you handle that?”, “Who became involved?”, and “What made that matter then?”

A useful probe is to ask twice about vague explanations:

“You said timing was not right. What else was happening in the business at that point?”

Then:

“What would have needed to change for the timing to become right?”

This does not assume that “timing” is false. It tests whether timing means no budget, weak urgency, internal risk, another priority, an absent decision-maker, or a polite rejection.

Use an event timeline when memory is uncertain. Put the trigger, first internal discussion, first vendor contact, business case, approval, decision, and implementation or abandonment on one line. Anchor the timeline to records such as the proposal date, a board meeting, a renewal, or a known incident. Timeline-based recall tools are designed to improve the placement and consistency of past events.

flowchart LR
    A[State the buyer and trigger hypothesis] --> B[Select clients and lost prospects]
    B --> C[Reconstruct one real buying episode]
    C --> D[Map timeline, people, alternatives, and consequences]
    D --> E[Code every interview in one evidence matrix]
    E --> F[Compare repeated patterns and exceptions]
    F --> G{Evidence supports one customer, problem, and result?}
    G -->|Yes| H[Use it to shape the offer and next tests]
    G -->|Not yet| I[Narrow the segment or collect more evidence]

In plain language: start with a hypothesis, collect contrasting cases, reconstruct actual events, compare them systematically, and make an explicit proceed-or-learn-more decision.

The following is a working resource estimate for a 10–15 interview cycle, not an industry standard.

A lean team needs a research lead, a note-taker or analyst, and access to the founder, sales, delivery, and customer records. Basic tools are enough: a calendar, consented recording or transcription, a spreadsheet or qualitative-analysis tool, and the customer relationship management system. Software can accelerate transcription and grouping; it should not decide which evidence is credible or whether the business should narrow its focus.

Turn interviews into evidence

Interview notes are not the final result. The work becomes useful when every conversation is reduced into the same comparison structure.

The Framework Method is well suited to this task because it places cases in rows and analytical categories in columns, making similarities and differences visible across interviews while preserving links to the original material. It was developed for systematic, team-based analysis of qualitative data.

Use a matrix with columns such as:

• account and segment;
• interviewee role in the decision;
• situation before the search;
• trigger event;
• evidence of urgency;
• consequence of delay;
• people involved and their concerns;
• alternatives considered;
• decision criteria and proof required;
• reason won, lost, delayed, or abandoned;
• expected result;
• realized result for clients;
• exact buyer language;
• supporting record;
• analyst confidence;
• unresolved question.

Keep three layers separate.

Observation is what the interviewee said or a record shows.

Interpretation is what the team thinks it means.

Hypothesis is what the team will test next.

For example:

Observation: Three operations leaders began searching within two weeks of a customer escalation.
Interpretation: External accountability may create more urgency than internal inefficiency.
Hypothesis: Offers framed around protecting renewals will outperform offers framed around saving staff time for this segment.

Counts can show recurrence, but they are not market-share estimates. A purposive interview set is designed to find and explain patterns, not to estimate population percentages. The team should report “mentioned in six of eleven interviews in this sample,” not “55% of the market.”

Interview evidence should also be checked against behavior and records. Compare the story with customer relationship management timestamps, proposal versions, sales-call notes, contract dates, invoices, support tickets, onboarding effort, delivery margin, retention, and the result the customer actually achieved. Qualitative research gains credibility when interviews are considered alongside documents, observations, or service records rather than treated as the only source of truth.

Interview-note template

Account:
Interviewee and decision role:
Date of decision:
Outcome: Won / Competitor / Internal alternative / No decision / Delayed

Before the search:
Trigger event:
Evidence of urgency:
Consequence of waiting:
Who first raised the issue:
Who approved:
Who influenced or blocked:
Alternatives considered:
Decision criteria:
Proof required:
Reason for final decision:
Expected result:
Realized result, if applicable:
Exact phrases worth preserving:
Records that support or contradict the account:
Researcher interpretation:
Open questions:

Buying-trigger summary template

Target customer:
Primary buyer or champion:
Economic buyer:
Recurring problem:
Most common trigger event:
Why the issue becomes urgent:
Cost or risk of delay:
Status-quo alternative:
Other alternatives:
Proof required to buy:
Common reason for loss or no decision:
Expected result:
Evidence supporting the pattern:
Contradictory cases:
Confidence: High / Medium / Low
Next decision:

Illustrative example output

The following example is fictional and shows the level of specificity required.

Target customer: Operations leaders in 50–250 employee professional-services firms with several client-delivery teams.
Recurring problem: Handoffs between sales and delivery create rework and inconsistent client onboarding.
Trigger: A client escalation or renewal risk exposes the cost of the handoff failure.
Urgency: Leadership needs a corrected process before the next major onboarding cycle, usually within 30–90 days.
Buying group: Operations leads the work; finance approves; delivery managers and system owners influence feasibility.
Status quo: Senior employees manually coordinate exceptions.
Why clients buy: The offer provides a defined process, measurable first result, and implementation support without requiring a full system replacement.
Why prospects do not buy: No executive owner, no near-term client risk, or the problem is painful but still cheaper to absorb than to change.
Confidence: Medium. The pattern appears across several independent accounts, but the no-decision group needs more representation.

A useful summary must include contradictory cases. Suppose two customers bought without the apparent trigger. The team should investigate whether they experienced a different trigger, belonged to a different segment, or acted because of a pre-existing relationship. Removing exceptions makes the summary look cleaner but less useful.

Decide whether the evidence is strong enough

The primary activity measure is completed interviews. It is useful because unfinished interviews produce no evidence. It is not a success criterion by itself.

The work is complete when the company has:

• notes for every interview, tied to one specific decision;
• a balanced record of best-fit clients and credible losses or no-decisions;
• a cross-interview evidence matrix;
• a buying-trigger summary that names the customer, people, problem, trigger, urgency, alternatives, and desired result;
• direct buyer language;
• contradictory cases and unresolved questions;
• links to sales, delivery, product, and financial records where available;
• a documented decision to proceed, narrow the segment, revise the hypothesis, or collect more evidence.

The evidence is strong enough to depend on when the team can answer five questions without using broad labels:

1. Who acts? Name the organization type and the roles that start, approve, use, and block the purchase.
2. Why now? Name the trigger and the consequence of waiting.
3. What are they replacing? Include manual work, an employee, a provider, another product, delay, and doing nothing.
4. What result justifies spending? Describe the result in customer and financial terms where the evidence allows it.
5. Why this company? Identify proof and delivery strengths that appear in actual wins, not only in internal positioning.

A decision scorecard can make the review more rigorous.

The pattern does not need to be universal. It needs to be coherent enough to guide the next decision. One strong segment with a repeated trigger is more useful than a broad persona assembled from incompatible cases.

The National Science Foundation’s I-Corps program illustrates the principle at a much larger scale. Its customer-discovery process is designed to test commercial assumptions, and its mentor role explicitly includes helping teams recognize and reduce confirmation bias. In one official case, Sensatek reported that more than 165 interviews helped it identify the economic value of avoiding turbine outages and refine the relevant market opportunity. That is a case example, not a required interview count for every company. It shows why the purpose of interviews is to change or sharpen a commercial decision, not to confirm enthusiasm.

Validation should occur at three levels:

• Account validation: Did the notes accurately capture what the person said? Where appropriate, send a short factual summary back to the interviewee.
• Pattern validation: Does the same interpretation hold across clients, losses, roles, and segments?
• Behavior validation: Do sales, delivery, product, and financial records support the interview account?

A second team member should review a sample of transcripts and coding. Differences in interpretation are not automatically errors; they reveal where categories are vague, evidence is thin, or the team is importing assumptions. Official qualitative-research guidance recommends reflexivity—actively examining how the researcher’s background and expectations may have shaped the work—and notes that more than one researcher can help challenge individual bias.

Common ways the work looks finished when it is not

Only happy customers were interviewed. This reveals why advocates rationalize a purchase, but not why credible buyers reject, delay, or avoid it.

The interview became a product review. Feature feedback may be useful later. It does not explain the original buying trigger.

“Price” was accepted as the reason for loss. Price may mean weak urgency, unclear value, high implementation risk, a budget mismatch, or a polite exit. Ask what the prospect chose instead and what made that option acceptable.

One person was treated as the whole account. In a complex sale, the champion’s story may omit the financial, technical, procurement, or user decision.

Several markets were mixed into one average. A trigger repeated in founder-led agencies may not apply to regulated enterprises. Analyze materially different segments separately.

The team stopped at the target count. Ten or fifteen completed calls are not enough when the final interviews still add new decision roles, loss reasons, or triggers. Conversely, continuing indefinitely adds cost without improving the immediate decision.

Buyer language was converted too quickly into internal jargon. Preserve exact phrases before summarizing. They may later improve qualification, positioning, sales discovery, and onboarding.

Interview claims were not checked against delivery and financial evidence. A customer can value a result that the company cannot deliver repeatedly or profitably. This task supports a choice about what to build around; it cannot make that choice without margin, retention, effort, and outcome evidence from adjacent work.

The founder used the interviews to defend an existing idea. When the interviewer explains the product, corrects the participant, or searches only for supporting remarks, the exercise becomes a sales conversation. The National Science Foundation’s emphasis on reducing confirmation bias is relevant because commercial teams naturally have incentives to preserve a favored interpretation.

The summary removed uncertainty. A credible buying-trigger summary distinguishes strong patterns from tentative ones. It states what is known, what is inferred, and what still needs testing.

The result should be a defensible statement such as:

“This type of customer buys when this event creates this consequence, these people become involved, and this result justifies action.”

When the team can say that, show the evidence, name the exceptions, and explain its confidence, it is ready to use the finding in offer design and further product decisions. When it cannot, the correct result is not a broader persona. It is a narrower hypothesis and another round of evidence.

Sources

Primary and official sources

• U.S. National Science Foundation, “FAQ: I-Corps Team Solicitation.”
• U.S. National Science Foundation, “Sensatek Propulsion Technology.”
• U.S. Census Bureau, “SIPP Introduction & History” and “Organizing Principles and Interview Procedures.”
• UK Statistics Authority, “Ethical Considerations Associated With Qualitative Research Methods.”

Open research

• Hennink and Kaiser, “Sample Sizes for Saturation in Qualitative Research: A Systematic Review of Empirical Tests.”
• Hennink, Kaiser, and Marconi, “Code Saturation Versus Meaning Saturation: How Many Interviews Are Enough?”
• Gale and colleagues, “Using the Framework Method for the Analysis of Qualitative Data in Multi-Disciplinary Health Research.”
• Woolsey, “The Critical Incident Technique: An Innovative Qualitative Method of Research.”
• “B2B Customer Journeys: Conceptualization and an Integrative Framework.”
• “The Buying Center Concept as a Milestone in Industrial Marketing: Review and Research Agenda.”
• Bergen and Labonté, “Social Desirability Bias in Qualitative Health Research.”
• “Use of Qualitative Methods in Published Health Services and Management Research: A 10-Year Review” and “A Practical Guide to Using the Positive Deviance Method in Health Services Research.”