How we work
You will always know what is happening, and how to leave.
Five stages, eleven months, a predictable weekly rhythm, and a visible exit. The engagement is built so the operating layer can be taken in-house at the end. Here is exactly how it works, week by week.
The Diagnostic
Ninety-minute structured conversation. The system assesses tools, workflows, KPIs, and bottlenecks. Written diagnostic output returned within five working days. No deck. No obligation.
Tailored proposal
If the Diagnostic surfaces work the system layer can absorb, a written engagement proposal follows • scope, priorities, timeline, price. The operation decides whether to proceed.
First 30 days
Tool audit, KPI inventory, first SOPs drafted, first dashboard prototype shipped. By day thirty, the operating layer is in motion.
Months 2 through 11
Predictable weekly cadence. Operations stabilise. Dashboards mature. Recurring problems become productised system state. The operating layer compounds.
Handover
By month eleven, the operation owns the system state • SOPs, dashboards, policies, automations. Renew, transition to maintenance, or take it all in-house.
- 01
The Diagnostic
Ninety-minute structured conversation. The system assesses tools, workflows, KPIs, and bottlenecks. Written diagnostic output returned within five working days. No deck. No obligation.
- 02
Tailored proposal
If the Diagnostic surfaces work the system layer can absorb, a written engagement proposal follows • scope, priorities, timeline, price. The operation decides whether to proceed.
- 03
First 30 days
Tool audit, KPI inventory, first SOPs drafted, first dashboard prototype shipped. By day thirty, the operating layer is in motion.
- 04
Months 2 through 11
Predictable weekly cadence. Operations stabilise. Dashboards mature. Recurring problems become productised system state. The operating layer compounds.
- 05
Handover
By month eleven, the operation owns the system state • SOPs, dashboards, policies, automations. Renew, transition to maintenance, or take it all in-house.
The Diagnostic • system entry point.
System state at end of phase
A ninety-minute structured conversation, conducted by the founder of Operon. The system asks specific questions about tools, workflows, KPIs, and bottlenecks. This is not a sales call. It is listening.
Within five working days, the written diagnostic output is delivered. Three to five concrete operational observations, each with the symptom, the root cause, and the impact (time, money, or risk). A recommended priority order for the first 90 days. An indicative engagement scope and price band • written, not verbal.
No deck. No obligation. The Diagnostic is useful regardless of whether the engagement proceeds.
Trust is earned through one Diagnostic, not through ten case studies that do not exist.
If the Diagnostic surfaces work the system layer can absorb, a proposal follows.
System state at end of phase
The proposal is written, not pitched. It contains: scope across all three pillars, ranked priorities for the first 90 days, monthly retainer pricing scaled to team size and complexity, the engagement timeline, and the contract draft.
The operation reads it on its own time. No pressure close. If it is a fit, signature and start within two weeks. If it is not, the parting is clean • and the diagnostic output stays with the operation regardless.
Week one to week four: the operating layer starts moving.
- Week 1
Diagnostic deep-dive, tool audit, KPI inventory, founder interview.
- Week 2
Written priorities ranked. First quick-win identified and shipped (usually a tool consolidation or a credential cleanup).
- Week 3
Workflow mapping for the highest-friction process. SOP drafting begins.
- Week 4
First dashboard prototype delivered. Weekly cadence established. Monthly decision report scheduled.
System state at end of phase
By end of month one: a written diagnostic, two to three SOP drafts, one shipped quick-win, a dashboard prototype, and a cadence rhythm that does not depend on the founder to maintain.
Predictable cadence. Compounding value.
System state at end of phase
Each week follows a predictable rhythm. Monday • sync on operational priorities and incidents from the prior week. Tuesday and Wednesday • execution: workflow builds, dashboard updates, SOP drafting, automations. Thursday • QA on anything going live. Friday • written weekly update with what shipped, what is in flight, and the recommended decision for the following week. Plus async support throughout.
Month-over-month, system state compounds. By month four, recurring problems are getting productised by PPPC. By month six, dashboards are mature enough to drive decisions without translation. By month nine, the operating layer is reinforcing itself • TOS load drops because PPPC has eliminated most recurring incidents.
By month eleven, the operation owns the system state.
System state at end of phase
Three options at the end of the engagement. One • renew at a higher tier, since by then the operation has typically grown. Two • transition to a lighter-touch maintenance engagement; by then the operating layer mostly runs itself. Three • take the system state in-house. Every SOP, dashboard, policy, and automation is documented and owned.
The system is designed for option three from day one. If the operating layer cannot be taken in-house at the end, the system has not done its job.
Where we draw the line
What we commit to. What we won’t promise.
What we commit to
- Process • what the system ships, when, and in what format.
- Weekly written updates, on the same day every week.
- A named accountable person for every system output.
- Three-month review with structured exit clause.
- Full documentation transfer at month eleven.
What we won’t promise
- Specific revenue or growth outcomes • those depend on the operation’s adoption of the system state.
- That AI will absorb every operational problem.
- That every recommended change will be easy.
- That Operon is the right system layer for every organization that asks.
Common questions
Common questions about the engagement.
Why eleven months?+
Long enough for SOPs, dashboards, and policies to stop being shiny new artefacts and start being reflexive system state. Shorter engagements ship decks. Eleven months ships an operating layer that runs.
What if the system state isn’t improving by month three?+
The three-month review is contractual. If by month three the agreed system state has not shipped, the engagement can exit with thirty days’ notice and a pro-rata refund. The clause is kept visible because it is the only honest way to ask for an eleven-month commitment.
Who owns the IP at the end?+
The client owns everything client-specific • SOPs, dashboards, policies, automations, integrations. Operon retains its frameworks and reusable IP. Every system output is designed for handover from day one.
Can a single pillar be purchased?+
No. The three pillars are bundled because the system requires all three. Better to lose the deal than ship a fragmented engagement that won’t actually work.
What does a typical week look like?+
Monday sync on priorities and incidents. Tuesday and Wednesday for execution. Thursday QA on anything going live. Friday written update with what shipped, what is in flight, and the recommended decision for the following week. Async support throughout.
How is this different from a fractional COO?+
A fractional COO is one person, one or two days a week. Operon is a system layer across operations, data, and control with implementation included. The fractional model gives guidance; Operon installs the operating layer itself.
What is the catch with the Diagnostic?+
None. The Diagnostic is how the system surfaces whether the layer fits, and how the operation evaluates the engagement. The written diagnostic output is delivered regardless of what comes after.
The next step
Ready to start?
The diagnostic is the door. Ninety minutes, structured, written assessment back within five working days. No obligation.