The CMA Method
Most consultants advise. We have a method for finishing the work.
“Strategy meets execution” isn’t a tagline — it’s a discipline. Every CMA engagement runs in three moves: Embed, Build, Transfer. Four principles decide how we work inside them, and a four-step arc takes a problem all the way to something your team owns.
Embed · Build · Transfer
Three moves, in this order, every time.
The order is the point. Embedding before building is what stops us from automating a process that should have been deleted, and scoping the transfer at the start is what stops the engagement from becoming a dependency.
-
Move 1
Embed
We work inside the operation, not across a table from it.
We watch the work as it actually runs rather than as the org chart describes it: who touches each step, where the handoffs break, which numbers disagree, and what the current arrangement costs in hours and errors. That baseline is written down before anything is proposed, because every later claim gets measured against it.
What exists at the end
- A map of the work as it truly runs
- A measured baseline in hours and errors
- A ranked list of what to fix, cheapest fixes first
-
Move 2
Build
We ship the thing, rather than recommending that you ship it.
The fix gets built: automation on the tools you keep, a system that replaces the ones you should not, a financial model, a plan a lender can underwrite. It is built against the baseline, with humans kept in the loop at every step where a wrong answer would be expensive, and it goes into production rather than into a deck.
What exists at the end
- Working software or a working document, in production
- Human-in-the-loop controls where they matter
- The measurement repeated against the baseline
-
Move 3
Transfer
You end up owning it, and able to run it without us.
Documentation, training and handover are scoped from the start, not improvised at the end. You own the system and the data, and you choose whether to run it yourself or have CMA run it. The intended outcome of an engagement is that you do not need the next one.
What exists at the end
- The system and the data, owned outright
- Documentation and a trained team
- A running arrangement you can change or end
The transfer is the test
Most of this category sells the first two moves. The one that decides what you are left holding is the third, so it is worth being precise about what survives the engagement: what you keep when the work is done. The smallest way to start is the $500 Workflow Map.
The four principles
What decides how we work.
01
Embed, don’t advise
We work inside the business, not from across a table. The plan, the model, the systems — we build them with your team, so the work actually ships instead of sitting in a deck.
02
Evidence over assumption
Every recommendation traces back to a real number or a real source. We replace “we think” with “here’s the case” — because that’s what survives a lender, an investor, or a hard quarter.
03
Build to transfer
The goal is a business that runs without us. We document the machine and hand it to your team — no dependency, no retainer you can’t leave. Independence is the deliverable.
04
Fixed scope, real accountability
Published pricing. Scope in writing before we start. One firm owning the outcome end to end — not a hand-off chain where no one’s accountable.
The arc of an engagement
From the real constraint to something you own.
Step 1
Diagnose
Find the real constraint — the one thing holding growth back.
Step 2
Build
Construct the plan, model, or system that resolves it.
Step 3
Ship
Implement it in the business, alongside the team.
Step 4
Transfer
Hand over something your team can run and improve.
See the arc applied, stage by stage, in how we work — or the principles in action across real engagements.
FAQ
Questions about the CMA Method
What is the CMA Method?
Embed, Build, Transfer. We embed in the operation to see how the work actually runs and set a baseline, build the system or document that fixes it, then transfer it to your team with the documentation and training to run it without us. The same three moves apply whether the engagement is a business plan, an automation build or a full operating platform.
How is that different from normal consulting?
The second and third moves. Advisory work usually stops at a recommendation and leaves implementation to you, which is where most engagements quietly fail. Here the build is the deliverable and the handover is scoped from the start, so the end state is a running system your team owns rather than a document describing one.
How long does each phase take?
Embed is days, not months: a focused audit of the work, typically 60 to 90 minutes of live observation per workflow plus the analysis. Build depends on scope — most Essential platform builds go live in two to four weeks. Transfer runs alongside the back half of the build rather than as a separate phase at the end.
What does it cost to start?
A focused way to start an operations engagement is the $500 Workflow Map: one workflow, watched end to end and written down, credited against an Operations Audit ($2,500) if you go further. Scope and price are fixed in writing before any work begins, and the ladder is published on the pricing page.
Do you have to be on site?
On site is the method working at full strength, and CMA is based in downtown Dallas, so Dallas-Fort Worth engagements get in-person working sessions as standard. We also travel to Houston, and to El Paso and Corpus Christi, for the embed phase and the working sessions that need a room, with the travel written into the scope up front rather than added to an invoice later. Nationwide work runs remotely, which is honest about the trade-off rather than pretending video calls are the same thing.
A method you can hold us to.
Start with the business readiness scorecard, see a sample operating dashboard, and review what an engagement delivers. For the buying decision, compare execution-led and traditional consulting.
Bring the problem. We’ll bring the method — and the firm that finishes the work.