Designing an Approach to Operational Scale and Process Design

Design is a method, not a workshop poster

Value stream maps fail when rolled out once and forgotten. Process design at RelayOps requires a repeatable approach: discover, define, pilot, measure, scale, and govern. Lesson 1 stated principles. This lesson gives the design methodology leaders use for onboarding, release management, billing ops, and support triage.

RelayOps context: $9.2 million ARR (annual recurring revenue), forty-nine-day onboarding, seventy-one percent SLO (service level objective) actual vs eighty-five percent target, NRR (net revenue retention) 118 percent, gross margin 79 percent, eighteen-logo commit cap, template project funded $420K.

Phase 1: Discover with evidence

Discovery combines qualitative gemba (go and see, observing work where it happens) and quantitative data. RelayOps discovery team shadows five onboardings, tags timestamps, interviews six customers who churned in year one.

Findings: configuration step has eleven sub-steps, four redundant; customer IT access median fourteen days; sales CRM notes missing in 38 percent of tickets.

Discovery resists jumping to software purchases. RelayOps nearly bought $200K CPQ (configure, price, quote) tool before discovery showed missing handoff data, not quoting.

Phase 2: Define target state and design principles

Target state specifies measurable outcomes: blended onboarding thirty-five days, first-time-right config 92 percent, utilities on exception path only.

Design principles for RelayOps onboarding:

1. Single system of record for customer config from contract
2. No custom API without paid services SOW (statement of work)
3. Parallel IT and config where possible
4. Automated readiness gates before go-live
5. Capacity-linked sales commits

To-be process documented as swimlane with RACI (Responsible, Accountable, Consulted, Informed) per step.

Phase 3: Pilot with bounded WIP

Pilots test process changes on narrow slice before company-wide rollout. RelayOps pilots HVAC template on ten customers max concurrent WIP, separate queue from legacy path.

Pilot success criteria:

Pilot duration eight weeks. Kill if rework >15% after week four.

Bounded WIP prevents pilot success hidden by cherry-picking only easy customers. Random assignment of eligible deals required.

Phase 4: Measure and iterate

Measurement plan lists SLIs weekly, SLO monthly, financial impact quarterly. RelayOps uses cohort charts by process version (v1 legacy vs v2 template).

Statistical caution: small samples noisy. Use run charts over eight weeks before declaring victory.

Iteration example: pilot showed IT access still fourteen days; added customer IT escalation playbook at day seven, reducing median to eleven.

Phase 5: Scale with training and change management

Scaling a process means training, tooling, metrics embedded in WBR (weekly business review), and updating compensation guardrails. RelayOps trains sales on exception criteria, implementation on template library, customer success on new readiness gates.

Change management addresses fear: implementation team worried templates reduce billable hours. RelayOps reframes: hours shift to expansion and utilities learning, not unemployment.

Adoption metric: percent new customers on v2 path. Target 35 percent by December, 60 percent by March.

Phase 6: Govern with owners and sunset rules

Governance assigns process owner (Omar for onboarding), review cadence quarterly, and sunset rules for temporary steps. Steps older than two quarters without metric justification get removed.

Change control: material process changes need one-page decision memo with risk and rollback plan.

Part A: Pilot charter

Scope: HVAC standard ICP, ≤150 techs, no custom API. Max ten concurrent. Duration eight weeks. DRI: Implementation Director.

Part B: Resource and cost

Two implementers 50% time, product manager 25%, engineer 30% for tooling. Cost ≈ $68K over eight weeks within $420K budget.

Part C: Expected throughput gain

Config days 21→14 saves 7 days × 10 customers = 70 customer-days capacity freed → ~2 additional onboardings/month capacity equivalent.

Check: 70/35 ≈ 2 ✓

Part D: Scale decision rule

If pilot CSAT ≥4.3 and rework <8%, scale to 35% of new logos in month 3 with marketing to sales enablement training complete.

James designs release train biweekly with error budget gate from Unit 1.

Pilot two releases; measure incident rate and deploy stress. Scale to all teams if incidents do not rise.

RelayOps designs billing ops process for usage-based dispatch overage charges.

Facts: 12% customers hit overages; 40% disputes; dispute handling 6 hours avg; $3.2M ARR in usage fees annually.

1. Which discovery data would you collect first?
2. Define one target state metric.
3. Pilot design: scope and kill criterion.
4. Who should own ongoing governance?

Solution

1. Dispute reason codes, invoice clarity CSAT, time from usage event to invoice, error rate in metering data.

2. Dispute rate <15% within 60 days of pilot.

3. Pilot on 50 customers with clearest usage pattern; kill if dispute rate >35% after 30 days.

4. Finance operations DRI with RevOps consulted; Omar informed on customer comms.

Key takeaways

• Process design runs discover-define-pilot-measure-scale-govern phases with evidence.
• Target states need numeric outcomes and explicit design principles.
• Bounded WIP pilots with kill criteria de-risk rollout.
• Scale requires training, adoption metrics, and change management.
• Governance with owners and sunset rules prevents bureaucracy debt.

1. Write a one-page pilot charter for one process improvement at your company.
2. List three design principles for RelayOps onboarding target state.
3. Continue to Lesson 3: Common Risks and Failure Modes in Operational Scale and Process Design.

Change management for process rollout

Pilot n equals ten accounts, compare defect rate and cycle time to control group, document before/after with statistical humility (small n). Rollout waves: ten, fifty, all. Each wave includes thirty-minute training and office hours. Skipping change management reproduces old failures with new checklists.

Capture employee feedback after rollout week two. If CSMs report checklist absurdity on edge cases, refine rather than defend. Sustainable process adapts with evidence.

Integration with product roadmap

Top three integration productization items must appear on product roadmap with engineering points, not live only in services backlog. CTO and COO joint OKR: reduce custom integration percent. Operations-product alignment prevents permanent services company trajectory inside SaaS.

Additional applied depth: designing an approach to operational scale and process design

RelayOps remains at post-PMF, pre-Series B scale: $9.2M ARR, 92 employees, 340 customers, $11.2M cash, ~$655K monthly net burn after Q4 allocation, 118% NRR, 79% gross margin, 13-month CAC payback, 7-week median onboarding, 23 customers in onboarding WIP, CEO Maya Chen preparing Series B in 9-12 months. Managers at this stage must translate concepts into weekly decisions, not annual slogans. Review your unit metrics in the next operating cadence and assign one DRI, one leading indicator, and one kill criterion tied to this lesson's frameworks. Document the decision in writing so board and investors can see learning accumulate across quarters rather than resetting after each all-hands.

When stakes rise, teams debate anecdotes. Frameworks and numbers discipline the debate. Practice the workbook problems with RelayOps figures first, then substitute your organization's data. The logic transfers when the mechanics (WIP, runway, scorecards, gates) are measured honestly.

Tradeoffs are permanent at scale. You are always choosing what not to do. Explicit deferrals (utilities vertical, EU entry, AE surge) protect the company's ability to finish what it started. Sustainable scale is cumulative completion of sequenced commitments, not simultaneous pursuit of every opportunity the market whispers.

Additional applied depth: designing an approach to operational scale and process design

RelayOps remains at post-PMF, pre-Series B scale: $9.2M ARR, 92 employees, 340 customers, $11.2M cash, ~$655K monthly net burn after Q4 allocation, 118% NRR, 79% gross margin, 13-month CAC payback, 7-week median onboarding, 23 customers in onboarding WIP, CEO Maya Chen preparing Series B in 9-12 months. Managers at this stage must translate concepts into weekly decisions, not annual slogans. Review your unit metrics in the next operating cadence and assign one DRI, one leading indicator, and one kill criterion tied to this lesson's frameworks. Document the decision in writing so board and investors can see learning accumulate across quarters rather than resetting after each all-hands.

When stakes rise, teams debate anecdotes. Frameworks and numbers discipline the debate. Practice the workbook problems with RelayOps figures first, then substitute your organization's data. The logic transfers when the mechanics (WIP, runway, scorecards, gates) are measured honestly.

Tradeoffs are permanent at scale. You are always choosing what not to do. Explicit deferrals (utilities vertical, EU entry, AE surge) protect the company's ability to finish what it started. Sustainable scale is cumulative completion of sequenced commitments, not simultaneous pursuit of every opportunity the market whispers.

Additional applied depth: designing an approach to operational scale and process design

RelayOps remains at post-PMF, pre-Series B scale: $9.2M ARR, 92 employees, 340 customers, $11.2M cash, ~$655K monthly net burn after Q4 allocation, 118% NRR, 79% gross margin, 13-month CAC payback, 7-week median onboarding, 23 customers in onboarding WIP, CEO Maya Chen preparing Series B in 9-12 months. Managers at this stage must translate concepts into weekly decisions, not annual slogans. Review your unit metrics in the next operating cadence and assign one DRI, one leading indicator, and one kill criterion tied to this lesson's frameworks. Document the decision in writing so board and investors can see learning accumulate across quarters rather than resetting after each all-hands.

When stakes rise, teams debate anecdotes. Frameworks and numbers discipline the debate. Practice the workbook problems with RelayOps figures first, then substitute your organization's data. The logic transfers when the mechanics (WIP, runway, scorecards, gates) are measured honestly.

Tradeoffs are permanent at scale. You are always choosing what not to do. Explicit deferrals (utilities vertical, EU entry, AE surge) protect the company's ability to finish what it started. Sustainable scale is cumulative completion of sequenced commitments, not simultaneous pursuit of every opportunity the market whispers.

Additional applied depth: designing an approach to operational scale and process design

RelayOps remains at post-PMF, pre-Series B scale: $9.2M ARR, 92 employees, 340 customers, $11.2M cash, ~$655K monthly net burn after Q4 allocation, 118% NRR, 79% gross margin, 13-month CAC payback, 7-week median onboarding, 23 customers in onboarding WIP, CEO Maya Chen preparing Series B in 9-12 months. Managers at this stage must translate concepts into weekly decisions, not annual slogans. Review your unit metrics in the next operating cadence and assign one DRI, one leading indicator, and one kill criterion tied to this lesson's frameworks. Document the decision in writing so board and investors can see learning accumulate across quarters rather than resetting after each all-hands.

When stakes rise, teams debate anecdotes. Frameworks and numbers discipline the debate. Practice the workbook problems with RelayOps figures first, then substitute your organization's data. The logic transfers when the mechanics (WIP, runway, scorecards, gates) are measured honestly.

Tradeoffs are permanent at scale. You are always choosing what not to do. Explicit deferrals (utilities vertical, EU entry, AE surge) protect the company's ability to finish what it started. Sustainable scale is cumulative completion of sequenced commitments, not simultaneous pursuit of every opportunity the market whispers.

Additional applied depth: designing an approach to operational scale and process design

RelayOps remains at post-PMF, pre-Series B scale: $9.2M ARR, 92 employees, 340 customers, $11.2M cash, ~$655K monthly net burn after Q4 allocation, 118% NRR, 79% gross margin, 13-month CAC payback, 7-week median onboarding, 23 customers in onboarding WIP, CEO Maya Chen preparing Series B in 9-12 months. Managers at this stage must translate concepts into weekly decisions, not annual slogans. Review your unit metrics in the next operating cadence and assign one DRI, one leading indicator, and one kill criterion tied to this lesson's frameworks. Document the decision in writing so board and investors can see learning accumulate across quarters rather than resetting after each all-hands.

When stakes rise, teams debate anecdotes. Frameworks and numbers discipline the debate. Practice the workbook problems with RelayOps figures first, then substitute your organization's data. The logic transfers when the mechanics (WIP, runway, scorecards, gates) are measured honestly.

Tradeoffs are permanent at scale. You are always choosing what not to do. Explicit deferrals (utilities vertical, EU entry, AE surge) protect the company's ability to finish what it started. Sustainable scale is cumulative completion of sequenced commitments, not simultaneous pursuit of every opportunity the market whispers.

Additional applied depth: designing an approach to operational scale and process design

RelayOps remains at post-PMF, pre-Series B scale: $9.2M ARR, 92 employees, 340 customers, $11.2M cash, ~$655K monthly net burn after Q4 allocation, 118% NRR, 79% gross margin, 13-month CAC payback, 7-week median onboarding, 23 customers in onboarding WIP, CEO Maya Chen preparing Series B in 9-12 months. Managers at this stage must translate concepts into weekly decisions, not annual slogans. Review your unit metrics in the next operating cadence and assign one DRI, one leading indicator, and one kill criterion tied to this lesson's frameworks. Document the decision in writing so board and investors can see learning accumulate across quarters rather than resetting after each all-hands.

When stakes rise, teams debate anecdotes. Frameworks and numbers discipline the debate. Practice the workbook problems with RelayOps figures first, then substitute your organization's data. The logic transfers when the mechanics (WIP, runway, scorecards, gates) are measured honestly.

Tradeoffs are permanent at scale. You are always choosing what not to do. Explicit deferrals (utilities vertical, EU entry, AE surge) protect the company's ability to finish what it started. Sustainable scale is cumulative completion of sequenced commitments, not simultaneous pursuit of every opportunity the market whispers.

Additional applied depth: designing an approach to operational scale and process design

RelayOps remains at post-PMF, pre-Series B scale: $9.2M ARR, 92 employees, 340 customers, $11.2M cash, ~$655K monthly net burn after Q4 allocation, 118% NRR, 79% gross margin, 13-month CAC payback, 7-week median onboarding, 23 customers in onboarding WIP, CEO Maya Chen preparing Series B in 9-12 months. Managers at this stage must translate concepts into weekly decisions, not annual slogans. Review your unit metrics in the next operating cadence and assign one DRI, one leading indicator, and one kill criterion tied to this lesson's frameworks. Document the decision in writing so board and investors can see learning accumulate across quarters rather than resetting after each all-hands.

When stakes rise, teams debate anecdotes. Frameworks and numbers discipline the debate. Practice the workbook problems with RelayOps figures first, then substitute your organization's data. The logic transfers when the mechanics (WIP, runway, scorecards, gates) are measured honestly.

Tradeoffs are permanent at scale. You are always choosing what not to do. Explicit deferrals (utilities vertical, EU entry, AE surge) protect the company's ability to finish what it started. Sustainable scale is cumulative completion of sequenced commitments, not simultaneous pursuit of every opportunity the market whispers.