First move · Six-week sprint

Validate behavior, not enthusiasm.

Published research says the problem category is real. It does not say which buyer will trust a new specialist firm, approve the proposed scope, or pay the proposed price. This sprint compares two narrow segments and ends with paid decisions—not a pile of agreeable interviews.

20–24 qualified interviews 5 offer reviews 2 paid purchase paths

The decisions

Eight questions must be answered

Segment and job

Which microsegment has the strongest pain, urgency, budget, reachability, and outsourcing fit? Which recent event makes that buyer act now?

Wedge and price

Will the buyer fund a read-only-first Reliability Baseline and then a $25k–$45k managed project? Do both follow real budget and approval paths?

Trust and coverage

What proof and access controls are required? Is co-managed business-hours coverage enough, or does the target buyer require primary 24/7 response?

Delivery, recurrence, and channel

Can projects clear a 55% gross-margin floor? Which post-project work is temporary versus recurring? Does the founder sell directly or through a credible partner?

A completed interview is not a success metric. A recent event, prior spend, budget-owner access, proposal review, and paid commitment form an evidence ladder.

— Commercial research rule

Sampling design

Two cohorts, analyzed separately

Broad vertical lists create false averages. Each cohort needs at least eight qualified interviews before results are pooled or compared.

Cohort A · 10–12 interviews

B2B software and software-enabled services

75–300 employees and 10–60 engineers
Customer-facing production product
Azure material; AWS acceptable
No mature platform team
CTO, VP/Head of Engineering, or infrastructure leader with budget context

Cohort B · 8–10 interviews

Regulated services with an in-house software estate

Healthcare, insurance, or fintech services
Material internally operated application or data platform
Comparable company and team size where possible
Recent audit, customer, availability, or recovery obligation
Buyer who understands both the consequence and approval process

Up to four additional interviews may cover leaders who bought, rejected, or replaced a similar service in the last 24 months. Those interviews are labeled separately and do not inflate pain frequency.

A trigger is required before outreach

Platform role open 45+ days Recent incident Audit or enterprise-customer deadline Cloud-budget pressure Migration or Kubernetes adoption AI workload entering production One overloaded infrastructure owner

Evidence hierarchy

Buyer behavior carries more weight than buyer opinion

Level	Evidence	What it means
0	Opinion about the category	Useful language; no demand evidence
1	General complaint	Pain may exist, but may never earn priority
2	Specific event in the last 12 months	The problem is concrete and recent
3	Quantified consequence, deadline, or executive escalation	The problem competes for attention
4	Prior spend, active budget, or failed attempt	The organization has acted before
5	Budget-owner introduction or offer review	The buying system is opening
6	Procurement starts or a paid baseline is approved	Commercial demand

Interview method

Past events first. The offer comes last.

Thirty minutes are booked and twenty-five planned. The proposed offer is shown only in the final four minutes, after the buyer’s real situation and buying process are understood.

1 · Qualify the operating system (3 min)

What runs in production? Who owns cloud, deployments, observability, incidents, and recovery? Which of those areas can this participant approve spend for?

2 · Reconstruct the trigger (8 min)

Walk through the last incident, failed release, audit request, or budget surprise. Capture who lost time, revenue, confidence, or sleep—and what happened next.

3 · Examine alternatives (5 min)

What did the team try: hiring, MSP, consultant, tooling, or internal re-prioritization? What did it cost? What remained unresolved?

4 · Map buying and trust (5 min)

Who owns budget and veto? What proof is required for read-only access and production change? Is primary 24/7 response mandatory?

5 · Review the baseline and managed project (4 min)

Show one page with the $12k–$18k baseline and $25k–$45k managed-project follow-on. Ask which budgets and buyers apply, what would be unsafe, and what should be removed. Then ask which activities would be needed for only 90 days and which would be needed indefinitely. Ask for the next real action—not “would you buy this?”

Captured within 15 minutes

Demand

Trigger, date, consequence, deadline, attempted alternatives, prior spend.

Purchase

Budget owner, category, approval path, trust requirements, price-path evidence.

Next action

Offer feedback, stakeholder introduction, security review, proposal, or paid start.

Analytics

Compare demand and deliverability

Opportunity score

Frequency20%
Severity20%
Urgency / forcing event15%
Prior spend or budget15%
Outsourcing fit15%
Founder credibility and reachable channel10%
Repeatable delivery potential5%

Commercial dashboard

Recent-trigger and quantified-consequence rates
Prior-spend or active-budget rate
Interview → offer review → committed next step
24/7 requirement and trust-blocker rates
Expected sales cycle and acquisition channel
Modeled baseline, managed-project, and stabilization hours and gross margin
Temporary versus recurring post-project work

Every percentage includes a cohort denominator: “6 of 10 qualified Cohort A interviews,” not an unqualified “60%.”

Schedule

Six weeks, with commercial pressure by week three

Week	Work	Evidence target
1	Safeguards, assets, tracker, 80-name list, first outreach	Balanced cohorts; a trigger for every prospect
2	4–5 interviews, second outreach wave	First trigger and trust patterns
3	5–6 interviews, first synthesis, start offer reviews	10+ cumulative; first cohort comparison
4	5–6 interviews, partner input, price-path testing	16+ cumulative; three offer reviews
5	Final interviews and commercial follow-ups	20–24 interviews; five offer reviews; economic model
6	Findings brief, paid asks, decision memo	Two paid paths or an explicit pivot

After the first projects

Productize inside the delivery team

Discovery can approve the first baseline and project. It cannot justify a separate subscription team. The people doing the work must remain responsible for learning what repeats.

Core-team responsibility

Reserve 10–15% for productization

Build templates, automation, acceptance checks, onboarding, change control, handoff, and effort classification from real delivery—not an imagined service catalog.

90-day bridge

Use stabilization to observe recurrence

Measure which tasks repeat, how often they occur, the skill and coverage required, incident load, and margin. End the retainer when the need is temporary.

Dedicated-team gate

Four to six similar clients

Do not split the team until 70–80% of work is standardized and recurring gross profit funds two engineers plus a 20% coverage buffer.

Operational proof

Retention, handoff, margin, and runway

Require two renewal cohorts, at least 55% gross margin, proven escalation and backup coverage, six months of payroll runway, and no client above 25% of recurring revenue.

Decision gates

The sprint ends with a decision

Green · Sell baseline + project

One cohort has eight qualified interviews; 60% report a recent event; 40% show spend, budget, or deadline evidence; five offer reviews yield two paid paths; co-management works; and modeled baseline/project gross margin is at least 55%.

Yellow · Extend one test

Pain is strong but scope, price, buying path, or channel is unclear. Run 8–10 more interviews in one cohort and change only one major variable.

Red · Reshape

Fewer than two paid paths; body-only demand dominates; primary 24/7 is mandatory; trust is unattainable; or realistic project economics fall below the 55% floor. This rejects investment in a recurring team—not necessarily a project consultancy.

What a pivot could preserve

Project-only consultancy

Keep the diagnostic and bounded remediation as the business without forcing a recurring model.

Channel-only practice

Deliver reliability work through an established MSP with existing trust and coverage.

Narrower Azure offer

Focus on recovery readiness, cost governance, or another repeatedly funded job.

The standard is paid evidence.

The sprint is successful if it identifies a segment and earns two real purchase paths—or rejects the current model early enough to preserve time and capital. A separate recurring team is a later operating decision, not a discovery-stage commitment.

Return to the company concept →