Key Concepts and Vocabulary in Opportunity Selection and Problem Framing

The language gap that kills discovery

Customer discovery fails quietly when founders and customers use the same words to mean different things. A dispatcher says "scheduling is fine" while overtime reports show 14 percent above plan. An operations director says "we need better software" but will not sign a check until you name the workflow break. Vocabulary is not academic decoration in ENT 401. It is the interface between your hypothesis and the customer's lived reality.

This lesson builds the core vocabulary for opportunity selection and problem framing. You will learn terms investors, operators, and researchers use when they evaluate whether a problem is venture-scale, reachable, and ownable. Every definition connects back to RelayOps, our anchor B2B SaaS venture serving mid-market field-service companies (roughly 50 to 500 technicians) with dispatch and scheduling software.

When Maya Chen and Jordan Okonkwo interviewed their first ten prospects, they lost two meetings because they said "optimization" while buyers heard "another IT project." When they switched to "missed first-visit slots" and "overtime on heat-wave weeks," conversations lengthened and buyers brought colleagues. Precision in language is a competitive advantage in discovery.

Customer jobs, pains, and gains

The Jobs to Be Done (JTBD, a lens that focuses on what customers hire a product to accomplish in a situation) framework begins with a simple claim: customers do not buy products; they hire solutions to make progress in a specific circumstance. A plumbing company does not want "dispatch software." It wants to keep promised arrival windows, avoid technician idle time, and finish the day without angry callbacks.

In opportunity selection, you separate three elements:

Functional job: the practical task (assign the right technician to today's emergency leak call).

Emotional job: how the buyer wants to feel (in control when three techs call in sick by 9 a.m.).

Social job: how the buyer wants to be seen (credible to the CEO when utilization metrics slide).

Pains are obstacles, risks, and bad outcomes before and during the job. For RelayOps prospects, pains include double data entry between phone system and spreadsheet, inability to see senior tech skills during reroutes, and customer complaints that hit online reviews.

Gains are outcomes buyers want, including required gains (must-haves to consider a solution), expected gains (standard in the category), desired gains (nice surprises), and unexpected gains (delighters). A required gain for dispatch tools is mobile visibility of today's board. A desired gain might be automatic suggestions that respect union break rules.

Managers use this vocabulary to avoid building for the wrong job executor. RelayOps initially demoed to IT managers who cared about security checklists. Revenue appeared when they reframed for operations leaders whose bonus tied to utilization and SLA (service level agreement, promised response or arrival times).

Problem severity, frequency, and budget hooks

Not every pain becomes an opportunity. Three filters appear repeatedly in venture and corporate innovation gates: severity, frequency, and budget hook.

Severity asks how bad failure is when the job goes poorly. Missed same-day medical refrigeration repair is severe. Slightly slower email templates is not. Severity is contextual. For a 200-technician HVAC firm, a 12 percent rise in missed appointment windows can mean six-figure monthly revenue leakage and reputational damage in subscription maintenance plans.

Frequency asks how often the pain appears in a typical week. One-off annual pains are hard to sell unless severity is extreme. RelayOps targeted pains that appear on peak days (heat waves, Monday backlog) and every afternoon (last-minute cancellations). High frequency keeps the problem salient in buyer memory during your sales cycle.

Budget hook asks whether money already moves to cope with the pain. Payroll for dispatcher overtime, legacy software modules, consulting projects, and outsourced call centers are hooks. If buyers spend nothing and assign no labor, you may be inventing a problem. RelayOps looked for existing spend on overtime, aftermarket scheduling modules, and manual "firefighter" dispatch roles.

Investors shorthand this as "hair on fire" versus "vitamin." Vitamins sound nice; hair-on-fire problems get checks when you show credible relief. Your job in framing is honest classification, not hype.

Beachhead, wedge, and expandable market

Beachhead segment is the narrow group you serve first with overwhelming fit. RelayOps beachhead: independent HVAC and plumbing firms with 80 to 200 technicians, multi-skill crews, and same-day demand volatility. Not every field-service company. Not national enterprise chains with custom ERP (enterprise resource planning, integrated software for finance, supply chain, and operations).

Wedge is the specific entry point that beats incumbents on one dimension for the beachhead. RelayOps wedge hypothesis: same-day rebalance with skill-aware assignment in under two minutes, integrated to the mobile board dispatchers already stare at. The wedge is not "full ERP replacement." It is a painful daily workflow slice incumbents treat as an upsell module with clunky UX (user experience, how easy and sensible the product feels to use).

Expandable market is the path from beachhead to adjacent segments after you win trust. RelayOps expansion logic: win HVAC/plumbing dispatch → add electrical contractors with similar patterns → integrate parts availability signals → broaden to facilities maintenance. Opportunity vocabulary keeps you honest: if the wedge does not win beachhead, expansion is fantasy.

Corporate product teams use the same trilogy. A payroll company might beachhead on 200-employee manufacturers with shift differentials, wedge on overtime compliance reporting, then expand to time-attendance hardware integrations.

Evidence types and strength hierarchy

Discovery vocabulary includes evidence types ranked by strength for opportunity selection:

1. Paid behavior: customer already pays for partial solutions, overtime, or workarounds.
2. Repeated workflow pain: multiple independent accounts describe the same failure mode unprompted.
3. Structured interview patterns: consistent ranking in top pains across a sample.
4. Intent statements: "I would buy if..." useful but weak alone.
5. Opinions: friendly encouragement, social media likes.

RelayOps treats level 4 and 5 as explore signals only. Validate stage requires level 2 and preferably level 1. This hierarchy prevents founders from counting demo applause as validation.

Leading indicators are early measurable signals (interview pattern density, pilot signup rates). Lagging indicators are outcomes after adoption (retention, net revenue retention, payback period). Opportunity framing should name which leading indicator you will track in the next 30 days.

Stakeholder map for B2B problems

B2B opportunities involve multiple roles. Vocabulary must name them:

Problem framing that speaks only to users may win praise but lose budget. RelayOps problem statements include dispatcher pain and COO overtime exposure. Multi-stakeholder framing is not optional in mid-market SaaS.

RelayOps drafted an early pitch deck. Translate each slide phrase into discovery vocabulary and rate evidence strength.

Part A: Before table

Part B: Rewritten problem statement using vocabulary

Beachhead: 80-200 technician HVAC/plumbing firms in Sun Belt metros.

Job: Keep same-day appointment promises while absorbing absenteeism and demand spikes.

Top pains: (1) skill-location mismatch on reroutes, (2) triple-entry across phone, whiteboard, legacy CRM, (3) overtime when board visibility lags.

Budget hooks: Overtime premiums, aftermarket scheduling module fees, extra dispatcher headcount.

Wedge: Skill-aware same-day rebalance under two minutes on mobile board.

Leading indicator: Eight of ten ops leaders rank same-day rebalance in top three pains.

Check: each element maps to a vocabulary term from the lesson. ✓

Part C: Stakeholder read

Dispatcher (user) cares about fewer angry phone calls. COO (buyer) cares about overtime line and SLA fines on commercial contracts. IT (blocker) cares whether mobile app meets MDM (mobile device management, corporate policy controls on phones) policy. A problem frame that only cites dispatcher clicks fails budget review.

Part D: Managerial implication

Investors should ask RelayOps which evidence is level 1 or 2 versus level 4. Operators should ask whether beachhead is narrow enough to dominate references in one metro vertical. Vocabulary discipline turns a pitch into a test plan.

Switching costs, status quo bias, and incumbent gravity

Opportunity vocabulary must include switching costs: time, money, risk, and political capital required to change behavior. RelayOps prospects often admit dispatch pain while defending incumbent suites because migration feels dangerous. "We already pay for ServiceSuite" is not willingness to pay for RelayOps. It is a switching-cost statement that opportunity selection must record explicitly.

Status quo bias means buyers overweight the pain they know versus the pain of change. Vocabulary training helps founders separate latent pain (real but tolerated) from active pain (real and funded). RelayOps asks in every interview: "When did you last try to fix this? What stopped you?" Answers reveal IT backlog, training fear, sunk license fees, and dispatcher revolt risk. Without those blockers named, your beachhead definition is incomplete.

Incumbent gravity is the pull of bundled suites. Scheduling modules may be weak, but finance, payroll, and parts live in the same vendor. RelayOps wedge assumes CRM read integration, not full ERP displacement. Vocabulary without switching-cost awareness produces false opportunities: large pain, zero motion. Investors recognize this pattern when founders cannot name what budget line competes with their proposal.

Problem statements as contracts with your team

A problem statement is a contract engineering, design, sales, and customer success can repeat and use to reject work. RelayOps contract after vocabulary alignment: "When same-day demand spikes and absenteeism hits before noon, operations leaders cannot reassign skill-matched crews fast enough; missed first-visit slots and overtime follow." Contracts include exclusions: no enterprise multi-region rollouts, no permit-aware electrical scheduling, no generic digital transformation pitches.

Exclusions prevent vocabulary drift when prospects say "we need AI." RelayOps translates to job, pain, or gain terms before scheduling follow-ups. Teams that share vocabulary argue about evidence, not definitions. A product manager can reject a feature request by asking which clause of the problem statement it serves. That discipline is how vocabulary becomes operational, not academic.

Corporate product committees benefit from the same contract. When everyone agrees the problem is "shift differential compliance reporting for 200-employee manufacturers," roadmap debates shorten. Opportunity vocabulary is the grammar of those contracts.

RelayOps ran a 90-minute internal workshop to align vocabulary before Gate 2 interviews.

Part A: Misaligned terms before workshop

Part B: Agreed definitions

Part C: Problem statement read-aloud test

Five team members read the problem statement to a recorded role-play. Four passed without inserting product nouns. One failed; revised after coaching.

Part D: Managerial read

Workshop cost 90 minutes; saved an estimated two sprint weeks of misfit features. Vocabulary is pre-work for opportunity selection, not optional culture work.

Check: definitions map to Lesson 2 tables ✓

A RelayOps prospect says: "We need better optimization." The dispatcher mentions overtime; the IT director mentions API security; the COO mentions customer reviews.

1. Label each speaker's vocabulary layer (job, pain, gain, constraint).
2. Rewrite one sentence per role using RelayOps agreed terms.
3. Which role should be interviewed first for opportunity evidence and why?
4. What evidence strength (1-5) is the phrase "better optimization" alone?

Solution

1. Labels: Dispatcher overtime → pain; IT API security → constraint; COO customer reviews → gain/outcome; "better optimization" → idea.

2. Rewritten sentences:

• Dispatcher: "Last Tuesday I spent eleven minutes per reroute because skills live in a different tab."
• IT: "Any mobile dispatch app must pass MDM and read-only CRM access before pilot."
• COO: "If missed arrival windows rise, maintenance plan renewals drop within 60 days."

3. Interview order: Dispatcher first for job story ground truth; COO second for budget hook; IT parallel for constraints.

4. Evidence strength: Level 1 (vendor jargon without behavior).

Check: translation enables Gate 2 interview plan ✓

A RelayOps competitor hypothesis targets electrical contractors only with "permit-aware scheduling." You have six interview notes: three mention permit delays as top pain; two mention dispatch; one mentions neither.

1. Define beachhead, wedge, and job for the electrical-only hypothesis in problem-first language.
2. Classify each of the six interviews by evidence strength for permit pain.
3. Given the sample, should RelayOps pivot beachhead from HVAC/plumbing to electrical? State kill criteria and recommendation.
4. Write one sentence each for user, champion, and buyer roles for the electrical hypothesis.

Solution

1. Definitions:

• Beachhead: Mid-market electrical contractors (60-180 technicians) in cities with strict inspection backlogs.
• Job: Schedule inspection-dependent jobs without cascading delays to downstream crews.
• Wedge: Permit-status-aware board that blocks impossible sequences before dispatch confirms.

2. Evidence classification:

• Three permit-top-pain interviews: strength 3-4 (structured pattern, not yet paid behavior).
• Two dispatch-focused: strength 3 for dispatch, 1-2 for permit as primary.
• One neither: strength 1 for permit hypothesis.

3. Recommendation: Do not pivot beachhead yet. Permit pain shows signal but sample is small and split. Kill criteria: if fewer than five of next twelve electrical interviews rank permit delays in top three and cite budget impact, stay on HVAC/plumbing dispatch beachhead. Explore electrical as secondary track with six more calls.

4. Role sentences:

• User (dispatcher): Needs to see inspection dates before promising crew arrival.
• Champion (ops director): Needs fewer canceled crew-days from permit surprises.
• Buyer (owner): Needs protected margin on commercial projects with penalty clauses.

Check: 3/6 permit signal = 50%, below confident pivot threshold. ✓

Key takeaways

• JTBD vocabulary ties opportunities to progress, pains, and gains in context.
• Severity, frequency, and budget hooks filter real opportunities from anecdotes.
• Beachhead, wedge, and expansion path keep selection strategically narrow.
• Rank evidence strength; paid behavior and repeated patterns beat polite interest.
• B2B framing must speak to users, champions, and economic buyers together.

1. Take a problem you are exploring and label job, pains, gains, beachhead, and wedge in one page.
2. Audit your last five customer conversations: what evidence strength did you actually collect?
3. Continue to Lesson 3: Frameworks for Analyzing Opportunity Selection and Problem Framing.