Ask a manufacturing leader how the plant runs and you will get a precise answer: stations, sequences, tolerances, handoffs, owners. Ask the same leader how the commercial function runs and the answer gets vague, because the plant was engineered and the commercial function was not. Yet the commercial function has an operating model anyway. It is just an accidental one, assembled over years, varying by rep, and written down nowhere. A Target Operating Model is the decision to design it on purpose.
Operating model, defined
A Target Operating Model, or TOM, describes how the commercial function should work: the motions you run, the roles that run them, the stages a deal passes through, the criteria that move it forward, the handoffs between marketing and sales and delivery, the data captured at each step, and the governance that keeps it honest. It is the blueprint of the engine. Not the technology, not the org chart alone, but the design of how revenue gets produced.
Why the accidental model fails
When the model is implicit, every rep runs a slightly different version of it. That sounds harmless until you try to forecast, coach, onboard, or scale. You cannot forecast a process that changes by person. You cannot coach against a standard that does not exist. You cannot onboard a new hire into knowledge that lives only in veterans' heads. The accidental model is not a small inefficiency. It is the ceiling on everything you want to do next.
What a designed TOM gives you
A designed operating model makes the commercial function legible. Stages mean the same thing to everyone. A qualified opportunity has a definition the whole team shares. Handoffs have criteria instead of hope. Because the model is explicit, it can be measured, and because it can be measured, it can be improved deliberately rather than through another motivational push. It also becomes teachable, which is how institutional knowledge stops being a retirement risk.
Where it fits in the work
In Revenue Flow Architecture, the Target Operating Model is the output of the Strategize phase. Diagnose tells you the truth about where you are. Strategize defines where you should be, given the real constraints of your business, your buyers, and your channel. Only then do Plan and Execute translate the model into process maps, playbooks, and the technology configured to serve it. The order matters. Architecture before automation means the operating model is designed before any tool is asked to enforce it.
Not a binder, a working design
A TOM is not a document that goes on a shelf. It is the reference the whole commercial organization runs against, the thing that makes adoption follow naturally because the system finally matches how the work is actually done. Design the model first, and the technology, the metrics, and the coaching all have something solid to attach to.
You already have an operating model. The only question is whether you designed it. A Revenue Flow Snapshot shows you the model your data reveals you are actually running today, which is usually the first time leadership sees it clearly.
