Skip to main content

Definition

An operating model is the set of processes, rhythms, accountabilities, and decision structures that enable a company to convert strategy into repeatable, scalable output. Execution is how that model performs under real conditions: under resource constraint, market uncertainty, and team change.

When it matters

Operating models matter most when a company is moving from founder-led selling and delivery to a repeatable system. The transition from “it works because of this specific person” to “it works because of this process” is where most early-stage companies stall.

How it works

A functional operating model has three layers. The commercial layer defines how the company finds, qualifies, and closes buyers. The delivery layer defines how it fulfils reliably and at margin. The management layer defines how decisions are made, priorities set, and performance reviewed. Execution quality is determined by cadence — how frequently the team reviews its priorities, surfaces blockers, and adjusts — and by accountability — whether each critical outcome has a clear owner.

Practical steps

  1. Map the current commercial and delivery process as it actually works, not as intended.
  2. Identify the three to five steps where the most delays or errors occur.
  3. Define accountable owners for each critical output.
  4. Set a review cadence: weekly for pipeline and blockers, monthly for commercial performance.
  5. Create a simple dashboard that tracks metrics that predict revenue, not vanity metrics.
  6. Run sprint-based execution cycles of 5 to 10 days for commercial focus and immediate pipeline action.

Examples

A fintech at 500k ARR trying to reach 2m ARR typically has informal commercial processes that worked for the first customers but do not scale. The operating model shift involves: defining the ICP precisely, creating a repeatable sales process with qualification criteria, and setting a weekly pipeline review where every deal has a next action and a date.

What is the A-minus proposition?

The A-minus proposition is a concept from the Lessons from a Fintech series. It is the smallest, narrowest version of a product that is still strong enough to be bought and valued. It forces focus by solving one painful problem for one clear buyer — creating proof and revenue before expanding into a broader vision. Most founders build an A-plus product (everything they can imagine) when what they need is an A-minus: a product that is “good enough to be bought and valued” but narrow enough to prove quickly. The gap between the two is where most runway is wasted. The A-minus discipline works because it converts faster. A narrow proposition with proven outcomes beats a broad proposition with theoretical benefits in every enterprise sales cycle.

What does a founder’s weekly operating cadence look like?

The founder operating cadence provides a specific weekly rhythm for founders in long-cycle markets:
  • Book traction blocks first. Revenue-moving work (demos, discovery calls, commercial meetings) gets the best energy slots, before internal meetings or building.
  • Protect decision windows. Make strategic decisions only when rested. Avoid late-night “dopamine decisions” made for relief rather than outcomes.
  • Friday is Truth Day. Review pipeline reality, log decisions, and capture evidence for the Proof Library.
This cadence treats execution as a system rather than a set of ad hoc activities. See the founder operating cadence page for the full breakdown.

Common mistakes

  • Treating execution improvement as a technology problem rather than a process and accountability problem.
  • Reviewing performance monthly when the commercial cycle requires weekly attention.
  • Having no clear owner for key commercial metrics.
  • Adding complexity before the simple process is working reliably.

Key takeaways

Operating models are not organisation charts. They are the cadence and accountability structure that makes a strategy executable. Get the simple version working before adding complexity.