Operations is where the company makes good on what sales sold — and where CTS is currently leaving real MRR on the floor while customers wait. This system rebuilds the engine room on two disciplines: Musk's algorithm for what we run, Jensen's flat structure for what we see. Cycle time is the only metric that matters.
Onboarding, deployment, Day 2, accounting, and IT are not five separate problems. They're one problem in five places — handoffs are not first-class objects in our operating model. Every transition without a named artifact and a named owner-on-each-side decays into rework, IOUs, and silent revenue leakage.
The same five symptoms keep recurring across functions. They look like five problems. They're not.
Speed in operations is a deletion problem, not an addition problem. Most CEOs respond to slow ops by adding process — that's exactly backwards.
Each part is modular. Implement in sequence or start with the pillar where you bleed most cycle time today (for most CTS teams, that's Pillar 04 — Handoffs).
Six stages from Sold to Renewal with explicit entry/exit criteria, SLAs, owners, and handoff artifacts at every transition.
Pipeline · Stage Gates · SLAsQuestion, delete, simplify, accelerate, automate — applied monthly to one process. The required output is one deletion. Not flagged. Deleted.
5 Steps · Monthly CadenceT5T from every ops-facing role. Group feedback, no scheduled 1:1s for ops leadership. The CEO sees the field through the field's eyes.
T5T · Flat · Group FeedbackFive critical handoffs at CTS — each with a named owner on both sides, an artifact (not a meeting), an SLA, a failure mode, and a detection signal.
★ The Star PillarDaily, weekly, bi-weekly, monthly, quarterly forums. Each with one decision mandate. None where they overlap with sales cadence.
Daily · Weekly · MonthlyTen operating rules for the COO and ops leaders. Time allocation. Stop-doing list. The standard for what good looks like.
10 Rules · Time AllocationSix stages. Each stage has explicit entry/exit, an SLA, a named owner, and — critically — a handoff artifact at every boundary. Click any stage to inspect it. Stage 4 (Stabilization) is the valley of death; that's where speed dies most often.
Five steps. The order is non-negotiable. Optimizing before deleting is the most common mistake in operations — it's how we end up with sophisticated, fast versions of work that shouldn't exist.
Attach a person's name to every requirement. "We need this because policy" is not a name. If no one will own the requirement, it doesn't exist.
Remove more than feels safe. If you don't add 10% back later, you didn't delete enough. Most ops processes can lose 30–50% of their steps and gain quality.
Only after deletion. Never simplify what should be eliminated. Simplifying preserves the existence of the process; deleting questions it.
Speed up what survives the first three steps. Find the cycle-time bottleneck. Halve it. Then halve it again. Cycle time is the metric.
Last. Automating a broken process makes you faster at the wrong thing. Most "automation projects" should have been deletion projects in disguise.
A 47-field intake form spread across HubSpot, ServiceNow, and Odoo, two manual handoffs, one shared spreadsheet stitching them together. Average completion: weeks — often months on complex deals. Constant rework when fields conflict between systems.
A 9-field charter in HubSpot as the single source of truth. Sales completes 5 fields, deployment completes 4 at scope-lock. ServiceNow project record auto-creates from the charter; Odoo reads from HubSpot for billing. Average completion: 2–3 business days.
A 12-day Odoo close with four sequential reconciliations. Day 2 scope changes sit in ServiceNow tickets and only reach Odoo at month-end batch. AR aging reviewed monthly. Revenue leakage typically discovered the following month.
A rolling close in Odoo. Billable scope lives in HubSpot as the single source of truth and updates within 24h of any change. ServiceNow tickets that change scope post back to HubSpot automatically. Odoo reads from HubSpot. Weekly scope diff catches leakage in 7 days, not 30.
Three queues (Service Desk, Internal IT, Provisioning), two escalation paths, no published SLAs. Many requests come via Slack/text/hallway and never get logged. IT can't see total queue depth, can't prioritize, becomes the perceived bottleneck.
One queue, four named categories with named owners and published SLAs. Slack/text requests are politely redirected to the form. IT becomes a partner with visible capacity, not an opaque queue.
The Sales OS uses T5T from sellers; the Operations OS uses T5T from the people closest to the customer's reality after the sale — deployment engineers, service desk leads, account managers, IT, accounting. Different signal, same discipline. The CEO sees the field through the field's eyes.
Information that travels through three people gets distorted; information that travels through five gets discarded. Jensen's flat structure is the antidote — but the principle (not the 60-direct-reports number) is what travels to ops.
Same Monday cadence as sales, different signal. Ops T5T captures real-time customer experience, handoff friction, recurring tickets, internal blockers. The CEO reads every one Sunday night and responds personally.
Sales T5T captures market signal and deal motion. Ops T5T captures execution friction and silent failure modes. Different patterns. Same priority for the CEO.
The same problem hits week after week without anyone naming it as a system issue
The phrase that signals a Musk Step 1 candidate — a requirement with no living owner
"I asked X, no one knew, I asked Y" = the handoff artifact is missing or stale
Day 2 absorbs work that should be billed; the signal arrives long before the invoice does
Five handoffs at CTS quietly determine whether the company scales smoothly or grinds. Each one needs a named owner on each side, an artifact, an SLA, a known failure mode, and a detection signal you can actually monitor. An artifact here means a single document — the Charter, the Gate, the Scope Sheet — that captures everything the next owner needs (scope, status, decisions, contacts, gaps) so the work transfers cleanly whether or not the people meet. Click any handoff to expand.
One page in CRM. Auto-generated from the deal record at signature, completed by AE within 24 hours. Includes signed scope, commitments not in SOW (the IOUs — what AE promised verbally), known risks, success metrics, client stakeholders + their day-0 expectations, first 30-day milestones.
Failure: AE moves to next deal; verbal commitments surface 60 days later as "scope creep" or an unhappy customer. Deployment ends up doing unbudgeted work to keep the customer whole.
Detection: Any deployment ticket in week 4+ that references a commitment not in the charter. Should be zero. Track weekly. Three in a month = tighten the AE manager review on Stage 4 deals.
Multi-page sign-off package. Sections: what is live (every contracted scope item with checkbox), what is deferred (out-of-scope-for-now with target date), known issues + workarounds, runbook links, customer escalation tree, billing scope confirmed by accounting, first-30-day SLA targets.
Failure today: Day 1 → Day 2 takes 60–120 days. ServiceNow's ~100-item checklist treats every step as equally blocking; the vast majority document for compliance or audit, almost none actually block customer service. The customer expects service the day deployment ends; we make them wait two-to-four months. Faith erodes during the wait — "we sold them service they can't get yet" — and at typical CTS account sizes, every 30 days of delay is real five-figure MRR lost forever. You don't get those months back.
Detection: One number, tracked weekly per account: days from project completion to first day of billable Day 2 MRR. Current 60–120. Target ≤5 business days. The Day 2 Gate deep-dive below shows how the deletion target gets there.
Single source of truth in HubSpot (not Odoo, not a parallel spreadsheet). Lives on the customer record. Sections: contracted MRR, scope items, expansions logged with date, out-of-scope work flagged for billing review. ServiceNow scope changes post back to HubSpot automatically; Odoo reads from HubSpot for invoicing.
Failure: Day 2 absorbs work as "support" that should be billed. Accounting bills stale numbers because the source of truth lives in someone's head. Revenue leakage of 5–15% goes undetected for months.
Detection: Weekly delta between "shipped this week" (per Day 2) and "billed this week" (per accounting). A >2% delta is a red flag, not a rounding error. Trend the leakage rate as a published ops metric.
5 fields, no narrative. Category (provisioning · access · system change · support), requestor, affected user(s), deadline, business reason. Slack/text/hallway requests are politely redirected to the form. Published internal SLAs by category.
Failure: Requests via Slack/text/hallway with no record. IT can't prioritize because it can't see the total queue. IT becomes opaque, then becomes the bottleneck, then becomes the org's villain — though the real problem is the lack of an intake artifact.
Detection: Compare request count per week (informal estimates from function leads) to ticket count in the system. Delta = informal channel volume. Aim to drive the delta below 10% within 60 days.
Published to the customer in the Day 2 transition gate. Default: Account Manager owns the relationship. Day 2 issues: Service Desk owns. Internally, every inbound is owned within 24h or escalated. The customer's mental model is simple: "one person to call."
Failure: Customer sends to AE who sold the deal 8 months ago. AE forwards to Service. Service forwards to Deployment. Nothing happens. Customer escalates to CEO. The whole org has now been dragged into one ticket.
Detection: Track inbound emails forwarded more than once. Should be near zero. Spike is a signal that the convention isn't being communicated to customers (usually because the Day 2 gate document is stale or skipped).
At CTS today, this transition takes 60–120 days between project completion and the first day of billable Day 2 MRR. ServiceNow's ~100-item checklist is the bottleneck — most items document for compliance or audit; almost none actually block the customer from receiving service. Customers expect service the day deployment ends; we make them wait months. That ambiguity is where MRR — real, recurring, five-figures-per-account-per-month MRR — dies. The gate exists to compress 60–120 days down to ≤5 business days.
A gate is held within 5 business days of go-live. It is a meeting and a document — but the document is the deliverable. The meeting is just the moment when the document is signed. This gate replaces the existing 100-item ServiceNow checklist; it does not add to it.
The current ~100-item checklist is the cycle-time killer. Most items exist for documentation or audit reasons; very few actually prevent the customer from receiving service. Audit the existing checklist against three categories and act accordingly. The goal is not a perfectly documented handoff. The goal is a fast handoff that lets us bill MRR.
"This is what we delivered."
"We accept and will run it."
"We can bill what's described."
"Customer relationship is intact."
"We agree on what's live."
Five recurring forums, each with a single decision mandate. Hard agendas. Pre-reads required. The forums for ops are deliberately separate from sales cadence — different signal, different decisions, different room.
15 minutes. Deployments in flight only. Each lead names blockers and asks. No project updates — those live in the system. If there's no blocker, the standup is short.
Stage 3–5 customers only. Pre-reads required. Every at-risk deployment ends with a named owner and a committed date. Mirrors the Sales War Room cadence.
The only meeting where Deployment, Service, IT, and Accounting are in the same room. Agenda: handoff health, recurring friction, Algorithm Audit candidates.
One process. Apply the 5 steps. Required output: one thing deleted. Not "flagged." Deleted. If nothing is deleted, the session failed; name it.
Top 10 accounts by NRR + churn risk. Each account's Service Manager owns the read. Outputs: at-risk accounts, expansion ready, retraining needs, billing leakage flagged.
Where are we hiring vs. automating. Capacity model vs. forecast deployments. Algorithm Audit deletion log reviewed. Re-baseline cycle-time targets.
Both functions earn their reputation as bottlenecks because the rest of the org doesn't see how they work. Publishing internal SLAs and operating models converts opacity into partnership.
Ten rules for the COO and ops leadership. These are non-negotiable behavioral standards, not suggestions. They exist to make the right action obvious in the moment when speed is at stake.
Every transition has a named owner on each side, a document, an SLA, and a known failure mode. If a handoff requires a meeting to function, the handoff is broken.
"Policy" is not a person. If no one will own it, it doesn't exist. This is the precondition for Step 1 of Musk's algorithm.
Order is non-negotiable. Automating a broken process makes us faster at the wrong thing. Most "automation projects" should have been deletion projects.
No "soft launches" with informal handover. The gate is a five-signature artifact within 5 business days of go-live, or it's not live.
If accounting can't price it, sales can't sell it. Every line item has a billable scope and a service definition before the SOW is signed.
Once is bad luck. Twice is coincidence. Three times is a system. Add it to the next Algorithm Audit and resolve it.
Opacity creates the bottleneck. Visibility creates the partnership. If we miss a published SLA three weeks running, it's a capacity decision, not a performance issue.
Not throughput. Not utilization. Cycle time per stage, per handoff, per customer. Halve it. Then halve it again. Speed compounds.
If work flows around the org chart, the chart is wrong. Edit the chart, don't route around it. This is Jensen's principle made literal.
Algorithm Audit produces one removed step, every month, without exception. If the session ends without a deletion, name the failure publicly and rerun within 7 days.
The Operations OS is the sister system to the Revenue OS. Together they cover the full customer lifecycle — sales gets the yes; operations makes the yes worth something. Both are operated by the same discipline: T5T as signal, deletion as default, handoffs as artifacts, cycle time as the metric.
Suggested rollout sequence: Week 1 — Algorithm Audit on the cross-system intake (HubSpot → ServiceNow → Odoo); delete fields, name owners. Week 2 — publish the Deployment Charter template; require it for the next deal that closes. Week 3 — audit the ServiceNow Day 2 checklist against the keep/delete framework; collapse to ≤10 items. Week 4 — hold the first Day 1 → Day 2 Gate on the next go-live; target ≤5 business days from project completion to billable MRR. Week 5 — launch ops T5T from Deployment Leads, Service Manager, IT, Accounting. By day 90, all five handoffs are operating as artifacts and the Day 1 → Day 2 cycle is measured weekly per account.