Opportunity Selection and Problem Framing: Applied Business Decisions

From worksheets to commitments

Frameworks and vocabulary are worthless if they do not change what you do on Monday morning. Applied opportunity selection means choosing a beachhead, publishing a problem statement your team can test, allocating interview capacity, and saying no to tempting distractions. This capstone lesson of Unit 1 walks through the decision sequence RelayOps uses to commit to a validation track.

You have learned why selection is capital allocation (Lesson 1), the vocabulary of jobs and evidence (Lesson 2), and the canvases and scorecards to compare hypotheses (Lesson 3). Now you integrate them into decisions an operating manager would defend: which segment first, which problem statement on the website, which metrics on the discovery dashboard, and which opportunities enter the kill pile.

RelayOps remains our anchor: B2B SaaS dispatch and scheduling for mid-market field-service companies. Founders Maya Chen and Jordan Okonkwo enter Week 6 with 18 interviews completed, a score of 89/100 on the dispatch rebalance hypothesis, and two secondary explores (invoice documentation, permit-aware electrical scheduling) that scored below 60.

The opportunity decision memo

Serious teams document selection outcomes in a one- to two-page opportunity decision memo. The memo is not a pitch deck. It is an internal contract that aligns founders, advisors, and early hires on what is in scope and what is out of scope for the next 90 days.

A decision memo contains:

Decision: promote, pivot, or kill each hypothesis.

Primary beachhead: segment definition with inclusion and exclusion rules.

Problem statement: problem-first, rung 4-5 on the Reframe Ladder, no product nouns in the first sentence.

Evidence summary: sample size, strongest quotes categorized by evidence strength, existing spend examples.

Assumptions to test next: falsifiable statements with owners and dates.

Resource plan: interviews, shadowing hours, prototype scope, integration discovery calls.

Kill criteria: numeric thresholds for the next review.

RelayOps Week 6 decision: promote primary hypothesis H1 (same-day dispatch rebalance); explore H6 documentation as attach feature only; kill H5 invoice disputes as beachhead; defer electrical permit wedge until HVAC/plumbing reference wins exist.

Managers inside corporations write the same memo before funding a discovery squad. The memo prevents the squad from drifting into "innovation tourism" across disconnected ideas.

Translating problem frame into operating constraints

Once selected, the problem frame becomes operating constraints for product, marketing, and sales.

Product constraint: RelayOps will not build general ledger, payroll, or full CRM in the first release. Features must shorten same-day rebalance time or prove measurable overtime reduction in pilot.

Marketing constraint: Website hero copy references missed first-visit slots and heat-week overtime, not "AI platform."

Sales constraint: First 10 customers must match beachhead employee and vertical profile; no enterprise logos that pull roadmap toward custom API (application programming interface, standardized software connection) projects.

Interview constraint: Two new interviews per week minimum until pattern density plateaus; half must include economic buyer or COO delegate.

Constraints feel restrictive. They are how you buy speed. Every exception (chasing a 800-technician enterprise logo) taxes learning velocity and pollutes evidence.

Portfolio balance: core path and option bets

Applied selection rarely puts 100 percent of resources on one bet. RelayOps uses an 80/20 rule: 80 percent of founder time on H1 validation, 20 percent on tightly bounded option bets that could become modules. Documentation photos (H6) sit in the 20 percent bucket with a cap of four interviews per month.

Option bets need explicit ceilings. Without ceilings, option bets become stealth pivots. RelayOps policy: no option bet receives engineering beyond clickable prototype until primary hypothesis hits commit gate (defined below).

Corporate analog: a bank's digital team might allocate 85 percent to mobile check deposit friction for retail users and 15 percent to exploratory voice access, with voice killed if security review exceeds 30 days.

Commit gates: when exploration becomes building

RelayOps defines three gates:

Gate 1 (Explore → Validate): 10+ conversations, pain in top three for 40%+ of sample, problem-first statement recognized by 3+ buyers without prompting.

Gate 2 (Validate → Commit pilot): 20+ conversations, scorecard ≥ 80, three existing spend examples, two willing pilot LOIs (letters of intent, non-binding statements of planned purchase if conditions met), integration path credible within 45 days.

Gate 3 (Commit pilot → Scale build): Pilot shows ≥ 8% overtime reduction or ≥ 10% fewer missed first-visit slots over 8 weeks, retention of daily active dispatch users ≥ 70%.

Applied business decision at Week 6: RelayOps passes Gate 1, approaches Gate 2 (score 89 but only one LOI), so decision is accelerate LOI and integration discovery, not full engineering hire.

Communicating decisions to stakeholders

Founders must communicate selection decisions to candidates, advisors, and early customers without sounding scattered. Template:

"We are solving same-day dispatch rebalance for 80-200 technician HVAC and plumbing firms. We are not pursuing invoice documentation as a lead wedge. If your pain differs, we appreciate intros but may not build for you in 2025."

Clarity reduces wrong-customer drag. Early adopters who mismatch beachhead will request features that fail Gate constraints.

Investor read: Clear kill statements signal discipline. Candidate read: Engineers know scope. Customer read: Serious vendors admit who they are for.

Unit 1 integration checklist

Before Unit 2 (customer segments and jobs), RelayOps completes:

Unit 2 deepens who within the beachhead and which job to prioritize first. Unit 1 decided which opportunity earns that deeper work.

Part A: Decision memo excerpt

Decision: Promote H1 to primary validation track. Kill H5 as lead. Defer H7 reminders.

Beachhead: Independent HVAC/plumbing, 80-200 field techs, Sun Belt + Midwest metros, residential + light commercial mix.

Problem statement: When same-day demand spikes and absenteeism hits before noon, operations leaders cannot rebalance skill-matched crews fast enough; missed first-visit slots and overtime follow.

Evidence: 18 interviews; 14 match segment; 9 rank pain top three; 10 cite overtime/module spend.

Next assumptions: (A) COO funds if pilot shows 8% overtime drop; (B) IT approves mobile in 45 days; (C) dispatchers adopt if rebalance < 2 minutes.

Part B: Resource allocation (hours/week)

Check: 32 hours ≤ 2 founder FTE capacity at 40h with slack ✓

Part C: Dashboard metrics (leading)

Part D: Managerial read

Board question: "Why not expand to electrical now?" Answer: electrical permit explore lacks score and LOIs; distraction risk threatens Gate 2. Operator question: "What do we tell the 800-tech enterprise prospect?" Answer: polite deferral unless they fit beachhead; exception requires founder vote and written roadmap impact.

Publishing constraints so GTM cannot drift

Operating constraints fail when only founders know them. RelayOps publishes a one-page constraint card after the opportunity decision memo: product nouns allowed in sales deck, segments eligible for pilot, integration scope, and feature requests auto-declined. Customer success uses the card to decline custom ERP work without founder escalation.

Marketing constraint example: paid ads may reference overtime and missed first-visit slots; they may not claim "full field service platform." Sales constraint example: opportunities above 250 technicians require written exception with services timeline impact. Engineering constraint example: sprints must map to rebalance loop seconds or overtime dashboard metrics tied to insight I3.

Drift happens when a well-meaning AE books a logo outside beachhead to hit quota. Applied opportunity selection gives AEs a polite deferral script tied to memo language, not ad hoc founder judgment. Operators respect vendors who admit who they are for; they distrust vendors who promise everything.

Decision memo review cadence and amendment rules

Decision memos are living documents with amendment rules. RelayOps amends memo only at forcing function reviews (every two weeks in validate) or when kill criteria trigger. Amendments require: what evidence changed, which constraint updates, and whether gates move.

Without amendment rules, teams silently widen beachhead after one exciting prospect. RelayOps Week 8 amendment example: widen technician upper bound from 200 to 250 only after second shadow match at 230-tech firm, documented in memo version 1.1. The amendment cites evidence, not enthusiasm.

Board members and lead investors receive memo diffs, not full rewrites. Diffs build confidence that selection discipline persists. Corporate innovation councils can use the same diff format for discovery squad charters.

Part A: Product constraints

Build only features that reduce rebalance loop time or document overtime change for COO review. Defer next-day optimizer, Spanish UI, and standalone reminders.

Part B: GTM constraints

Eligible: 80-250 tech HVAC/plumbing, residential-heavy, Sun Belt and Midwest metros. Ineligible: PE rollups >500 tech without division fit, electrical-only permit wedge leads.

Part C: Services constraints

Implementation cap six weeks; no custom ERP integrations in pilot; services hours target under 30 per logo.

Part D: Managerial read

AE with 1,200-tech rollup uses deferral script from card; saves 120 founder hours per Unit 2 case. Check: constraints trace to memo ✓

RelayOps memo says kill H7 reminders. A pilot customer requests SMS reminders as condition to renew.

1. Is this a memo amendment or a one-customer exception?
2. Write decision rule for one-customer exceptions.
3. Update constraint card entry for communications features.
4. What gate metric would reminders module threaten if built prematurely?

Solution

1. One-customer exception unless 3+ pilots request same module with budget offer.

2. Exception rule: Founder vote + written roadmap delay impact + sunset if not requested by second customer within 60 days.

3. Constraint card: "No standalone reminders; evaluate as H1 attachment only after 70% dispatcher DAU for 4 weeks."

4. Gate metric threatened: Prototype task time median (I2) if engineering shifts to reminder infrastructure.

Check: exception path prevents stealth pivot ✓

Gate reviews as calendar events

RelayOps schedules Gate 1, 2, 3 reviews as calendar events with required attendees: both founders, lead advisor, customer success lead once hired. Gate packets include decision memo, scorecard, assumption register excerpt, and LOI status. Missing packet items postpone gate; enthusiasm does not override.

Gate 2 at Week 6 showed score 89 but only one LOI. Decision: accelerate LOI and integration discovery, defer engineering hire. Calendar discipline prevented declaring victory because score crossed 80.

Communicating kills externally without brand damage

Killing H5 invoice lead wedge internally was easy; explaining focus externally required care. RelayOps website FAQ: "We focus on same-day dispatch rebalance for mid-market HVAC and plumbing; documentation features may follow once core loop proves value." Clarity attracts right customers and repels wrong ones without sounding negative about finance pains.

Ninety-day resource planning as a discovery budget

Applied opportunity selection ends in hours allocated, not slogans. RelayOps Week 6 resource plan assigned Maya 12 interview hours, Jordan 6 shadow hours, and capped advisor calls at 2 per week. Hours are currency; unfunded hypotheses die.

Discovery budget ties to gate milestones. Gate 2 requires three LOIs; budget shifts from explore channels to LOI acceleration: COO overtime PDF requests, pilot term sheets, integration discovery workshops.

Corporate squads use the same hours budget. A bank discovery team allocating 200 hours without gate linkage will wander across use cases until politics picks one.

Exception handling without destroying gates

Exceptions happen: 230-tech firm matches job stories. RelayOps exception policy requires written impact on integration assumption, services hours forecast, and segment denominator rules before accepting.

Exceptions without documentation become new beachhead by accident. Memo version 1.1 documented conditional widen to 250 technicians with second shadow requirement.

Investors prefer explicit exception log over hidden pipeline of misfits.

Part A: LOI gap

One LOI signed; need two more in 45 days.

Part B: Actions

COO benchmark offer; integration workshop series; reference pilot pricing at $2,800 Core.

Part C: Hours reallocation

Cut electrical explore to zero; add 4 COO hours weekly.

Part D: Managerial read

Gate 2 date slips 30 days max; not indefinite. Check: LOI target 3 ✓

RelayOps Gate 2 at Day 75: score 88, two LOIs, IT median 52 days.

1. Pass Gate 2? If conditional, state conditions.
2. Resource shift for next 15 days?
3. Write exception rule for 280-tech firm with identical shadow.
4. Dashboard metric to watch?

Solution

1. Conditional pass: proceed pilot commit with IT derisk parallel; full Gate 2 complete at 3 LOIs and IT median ≤50 on next 3 calls. 2. Shift: +6 IT hours, +4 COO LOI hours; pause marketing experiments. 3. Exception: allow if ≥65% residential mix and 6-week services cap signed; else defer. 4. Metric: LOI count and IT median days.

Check: conditional pass documented ✓

You advise RelayOps. A well-known PE (private equity, investment firms that buy and operate companies)-backed plumbing rollup with 1,200 technicians wants a pilot, but they demand custom ERP integration and multi-region roll-out in 90 days.

1. Does this prospect fit beachhead? Apply inclusion/exclusion rules.
2. Write a three-sentence stakeholder communication accepting or declining pursuit.
3. If founders want to take the deal, what Gate constraints must they rewrite? List two risks.
4. Update the 90-day dashboard: which metrics could this deal distort?

Solution

1. Fit: No. Exceeds 80-200 technician profile; demands enterprise scope and timeline incompatible with Gate 2 integration assumptions.

2. Communication: "Thank you for the interest. RelayOps is focused in 2025 on 80-200 technician independent HVAC and plumbing firms with a narrow same-day rebalance pilot. We cannot commit to multi-region ERP integration in 90 days. We welcome a re-visit when our reference phase completes or if a division matches our beachhead size."

3. If taken anyway: Rewrite integration timeline assumption and pilot success metrics (rollup metrics may hide dispatcher adoption). Risks: roadmap hijack, false positive on overtime (rollup accounting masks site variance), founder time bankruptcy.

4. Distorted metrics: LOI count inflates without beachhead fit; prototype task time irrelevant if custom build; interview pattern density polluted for core segment.

Check: decision protects Gate 2 integrity ✓

Key takeaways

• Opportunity selection ends in a decision memo, not a brainstorm wall.
• Problem frames become operating constraints across product, marketing, and sales.
• Use 80/20 portfolio rules with ceilings on option bets.
• Commit gates translate evidence into build/no-build with numeric thresholds.
• RelayOps commits to HVAC/plumbing dispatch rebalance and kills distracting lead wedges.

1. Draft a one-page opportunity decision memo for your venture or RelayOps with kill criteria for the next 90 days.
2. Publish three operating constraints your team must enforce this month.
3. Return to the unit page for the Unit 1 knowledge quiz, then begin Unit 2: Customer Segments and Jobs to Be Done.