ARCSET GUIDE

How an Embedded Operations Engagement Actually Works

Short answer: a consultant studies your business, hands you a report, and leaves you to do the work. An embedded operator does the opposite, gets into your business, builds the systems himself, and stays to run them until they hold on their own. An Arcset engagement is the second kind. We don't drop off a deck and bill you; we diagnose what's leaking, build the systems to fix it, then run them with you until your business keeps moving without us in every decision.

Last updated: 2026-07-07 · By Mathieu Carbone, Arcset · Québec, Canada

Consultant vs. embedded — why we don't hand you a deck

A classic consultant is paid for the analysis. The deliverable is the report, and the implementation is your problem. That's where most engagements die: the binder sits on a shelf, the team goes back to how it always worked, and three months later nothing has changed. We work the other way. The deliverable is a working system, not a slide. We get into the actual job, build the thing, and stay long enough to make sure it holds under real load. You're paying for what gets fixed and runs, not for advice you then have to execute yourself.

How a mandate runs: diagnose → build → run

Three phases, in order. Diagnose: we get into the numbers and the day-to-day, find where revenue leaks, where the bottleneck sits, and what's running only because it's in your head. No 40-page report, just the short list of what's actually costing you. Build: we put the systems in, one source of truth, the few processes that matter written down, automated follow-ups, the dashboards your team reads. Run: we stay in the seat with you, hold the cadence, fix what breaks, and tune it against real use until it holds on its own. The mandate is done when the business runs without us, not when a document is delivered.

What actually gets built

Concretely, the deliverables are systems, not documents. A CRM set up around how your service work actually flows (quotes, jobs, follow-ups, invoicing) so nothing falls through. Automations that handle the follow-ups and handoffs your team keeps forgetting, so revenue stops slipping while everyone's busy. Business intelligence and dashboards so you and your crew read the same picture, what's coming in, what's at risk, where the margin went. And an operations cadence, the short weekly rhythm that keeps the whole thing honest instead of drifting back to chaos. Each piece is built to keep working after we step back.

Scope, pricing, and what you own at the end

Scope is set against your bottleneck, not a fixed package. We agree on what we're fixing first, what success looks like, and how long the run phase lasts, usually a few months of embedded work, billed monthly at a fraction of a full-time executive's cost, not by the hour. Everything we build is yours. The CRM, the automations, the dashboards, the written processes, they live in your accounts and stay when the mandate ends. There's no lock-in and no black box: the point is to leave you with a business you can run, not a dependence on us. When the systems hold on their own, the embedded phase winds down.

Is this you?

This fits a Quebec service business, paving, exterior maintenance, insulation, cleaning, doing $2M to $15M with a strong operator at the helm and not enough systems underneath. The tell: revenue's up but your take-home isn't, everything runs through you, and you can't take two weeks off without the work stalling. If you want the systems built and run, not just diagnosed, this is the engagement. If you're still figuring out whether you even need fractional operations leadership, read our guide on what a fractional COO is first, it covers the definition and the when; this page is about the how.

One more piece that sets us apart: the engagement is paired with Autopilot, the platform that reads your business every morning and surfaces what's limiting growth. The embedded work fixes what software can't; Autopilot keeps the gains in place between sessions, so the improvements don't fade the month after the mandate ends. If that's the shape of business you're running, the next step is a conversation, not a contract.

See what Autopilot does and what it costs — features and pricing.

Talk to us →

Frequently Asked Questions

In three phases: diagnose, build, run. We get into your numbers and day-to-day to find where revenue leaks and where the bottleneck sits, then build the systems to fix it (CRM, automations, dashboards, a written operations cadence), then stay embedded and run them with you until they hold on their own. Billed monthly at a fraction of a full-time executive's cost, not by the hour. The mandate is done when the business runs without us, not when a report is delivered.

A classic consultant analyzes and recommends, then leaves you to implement. Fractional means an experienced operator in the seat part-time, ongoing, for a fraction of a full-time salary, that's the model, and our guide on what a fractional COO is covers the definition. Embedded is how we deliver it: we don't just advise, we build the systems ourselves and stay to run them until they hold. For a $2M–$15M business that needs things actually fixed, not just diagnosed, embedded delivers far more than a report.

The deliverables are working systems, not documents: a CRM set up around how your service work actually flows, automations for the follow-ups and handoffs your team forgets, business intelligence and dashboards so everyone reads the same picture, and a weekly operations cadence. All of it is yours, it lives in your accounts and stays when the mandate ends. No lock-in, no black box. The goal is to leave you with a business you can run, not a dependence on us.

Scope is set against your bottleneck, not a fixed package, we agree on what we're fixing first, what success looks like, and how long the run phase lasts (usually a few months of embedded work). It's billed monthly at a fraction of a full-time executive's cost, not by the hour, so you're paying for what gets built and runs, not for time. When the systems hold on their own, the embedded phase winds down. The first step is a conversation, not a contract.