What a marketing operations consultant is hired to do
A marketing operations consultant is an independent specialist, a freelancer or a practice inside an agency who is brought in to improve how a marketing team works rather than to produce the marketing itself. The work falls into the three disciplines the marketing operations pillar describes. On process it is the campaign workflow, the written procedures and the handovers. On systems it is where work is tracked, the asset library and the campaign taxonomy. On governance it is the approval matrixA table that says which reviews each type of marketing work needs, such as legal, brand or budget, and who gives each, matched to the risk of the work., the claims records and the charter.
Three things stay with the business whichever kind of provider is hired. The first is the purpose: what operations is for and who sponsors it, which a provider can help to draft and cannot sign. The second is accountability: every decision has one role in the business that answers for it, and a provider can do the work behind a decision without deciding it. The third is the evidence: stage history, returns from review and the error log are the team's own records, which a provider reads and reports on without replacing them with a story of its own.
Choosing tools and connecting them is a stack decision. A provider who sets up and operates the software itself is the subject of the technology partner hiring guide; this guide is for the provider whose product is the process, the rules and the records around the tools. Whether to buy this kind of work at all is a question the in-house versus agency comparison decides for one type of work at a time, and the agency selection guide covers the cycle an agency relationship runs through, from selection and scope to review and exit.
One risk deserves a name before anyone is appointed. The key-person guide lists a supplier among the fixes for work only one person can do, and says a supplier still depends on a written procedure and the right access. A consultant who becomes the only person who understands the workflow has moved the problem outside the business, which is why so much of what follows concerns where things are written down and who can run them with the provider out of the room.
What stays with the business
Settle this before the first proposal is read, because it decides what proposals are asked to deliver. The table groups what an operations provider handles, notes what to agree before work begins and sends each row to the page that owns the subject.
| What the provider handles | Agree before work begins | Where the site covers it |
|---|---|---|
| The decisions and who answers for them | Every decision has one accountable role held by a person in the business. The provider may draft but is not accountable, and the sponsor and the leads of the teams served sign the result | The charter tutorial writes decision rights as rows with one accountable role each |
| The approval matrix and the reviews it sets | Each row is agreed with the reviewing function it names, and the reviews stay with the business's reviewers, so a provider does not approve a price claim, a consent question or an accessibility decision | The approvals and compliance guide sets out how the matrix is built from risk |
| Claims and their evidence | The provider may collect and format entries. Each entry is approved by the reviewer the matrix names, and whether the evidence supports a claim is for legal or compliance to judge | The claims library tutorial |
| Procedures and their owners | Each procedure has a process owner inside the business, and the documents sit in the business's own library with a version and a change log | The SOP tutorial |
| The taxonomy and the naming rules | The taxonomy has one home, an owner and a change log inside the business. The provider can build the naming builder but does not own the list of allowed values | The data operations guide |
| The asset library and its rights records | Files, status, rights and expiry are held by the business, and the provider works through a named account limited to the sections its work needs | The asset library tutorial |
Two notes belong under the table. As general practice, a document that exists only inside the provider's own workspace may not be there to open on the day the work ends, so ask for the documents to sit in the business's library from the first draft rather than being transferred at the close. And the work system itself, with its administrator seat, is the business's too; the accounts, credentials and copies around any tool belong to the technology partner guide, which this page does not restate.
A provider asked to audit a contact list or read a suppression list is handling personal dataAny information relating to an identified or identifiable living person, such as a name, email address, location data or an online identifier. on the business's behalf, and the GDPRThe EU regulation setting the rules for processing personal data, including its principles, lawful bases, individuals' rights and breach duties. treats a supplier acting for the business in that way as a processor. This guide goes no further into the law. The business's data protection owner decides what the provider may see, and the terms of any processing contract are for the business's legal adviser. None of this is legal advice.
Scoping: diagnose, build or run
As general practice, give diagnosis, build and run work scopes of their own, agreed ahead of the engagement, and open with a diagnosis or one small build rather than the full operating model.
| Type of work | The business receives | The scope states |
|---|---|---|
| Diagnose | A written set of findings drawn from real work: a map of how recent items actually moved, a sampled check of approvals, a record of who can run each recurring task. Nothing live changes | Which process, which period and which sample; who grants access to the work system and the records; which findings the people named in a row see before the report is final; and that the provider changes nothing |
| Build | A defined set of artefacts, such as the workflow and its gates, procedures, the matrix, the claims library, the asset library, an onboarding pack or the charter | Which artefacts, which guide's steps each follows, the owner of each inside the business, where each will live and which check accepts it |
| Run | The function operated for a stated period: triage of requests, audits, naming checks and access reviews | The accountable role in the business, the route for requests, which decisions the provider settles by itself and which it only advises on, how each is recorded and the end date |
Diagnose. The approval audit tutorial asks for someone who did not approve the sampled work and for the reviewers to see what was found before the report is final, and an independent provider can offer both. The mapping tutorial supplies the method for tracing recent items through the process as it really ran, with its waits, loops back and workarounds. A diagnosis shows what the build should contain before any of it is built.
Build. Choose artefacts from what the diagnosis found, not from a catalogue: a claims libraryA record of every marketing claim in its exact approved wording, with the evidence behind it, the conditions and markets it is approved for and the approver. follows a diagnosis that found claims with no evidence behind them, and a written procedureThe written way of doing one recurring task: who owns it, what starts it, the steps in order, checks and exceptions, so anyone qualified gets the same result. follows one that found a task nobody else could repeat. The prioritising guide keeps one backlog of operations work sorted by effect, risk and effort, and a proposal should read as a slice of that backlog taken in that order. Scope each artefact to the guide that teaches it, so that acceptance has a standard to check against. As the process hub puts it, each stage or check exists because a recurring failure costs more than the step does, so a provider who adds a gate should name the failure it prevents.
Run. A provider can carry out the work in an area of operations while the accountable role in the business answers for how that area is designed and kept up. Put the split into a RACI matrix that gives each row one accountable role, and decide in advance which decisions the provider may settle alone, which it only recommends and which it is consulted on, the three groups the charter uses for operations' own decisions.
Writing it down. The provider's statement of workA supplier's written confirmation of what it will deliver, by when, at what price and how it will invoice, against which the order is raised. is what later work and invoices are checked against, so the agreed scope goes into it. The agency scope of work template provides fields for approvals, for account and data ownership and for exit, and the rows of the table above can be copied into them. Fee models follow the selection guide, which matches a retainerA standing fee paid regularly to an agency or supplier for continuous work with a stable scope, as distinct from project fees, time and materials or commission. or a project fee to the work. For a provider's own use of AI tools, the AI rules guide for agencies and contractors applies: agree the permitted uses and the treatment of the business's data before work starts.
Questions to ask before appointing
Questions on the team, cover, references and fees sit with the selection guide; the ones here are specific to operating work. Add them to the written request each candidate answers, for example the agency RFP template, so that replies can be set side by side. The right-hand column sketches a careful answer and is not a rule.
| Question | A careful answer includes |
|---|---|
| What will you start from: our records or your own template? | Reading the business's stage history, returns and errors and mapping a few recent items before proposing a change. Any outside figure is named with its source and its fit, and no benchmark is presented as a target |
| Which decisions will you want us to take, and who signs each? | A named role in the business for every decision, the provider responsible for drafting and not accountable, and a sponsor who agrees the result |
| How will you show that a procedure works? | A test by someone who has not done the task before, following the document alone on a real or test item, with every hesitation turned into a fix |
| How will you deal with the reviewers' rows of the matrix? | Each row agreed with the reviewing function it names, with no judgement by the provider on claims, consent or accessibility |
| Where will the documents live, and in what format? | The business's own library from the first draft, a format its people can edit, and an owner, a version and a change log on every procedure |
| Which personal data will you see, and which tools will it pass through? | A short list limited to what the work needs, named staff and tools, as decided by the business's data protection owner, and any AI use inside the business's rules for agencies |
| How will you tell us whether it worked? | Measures taken from the team's own records before any change, such as time to live by stage, returns by reason and work clearing its gates at the first attempt, reported for the team, not individuals |
| How does it end, and could someone else run what you built? | A handover record of everything the provider holds, a new owner for each item, and a run of a procedure and an audit by the business's own people before access ends |
Compare the replies in a weighted scoring matrix, following the framework page for its criteria, weights, evidence and gates. Two gates suit this appointment: the documents live in the business's own library from the first draft, and every decision has its accountable role inside the business. A proposal that fails a gate drops out whatever it would have scored, and re-running the ranking under other plausible weights shows whether the order survives them.
Warning signs in a proposal
These warning signs are general practice.
- A method installed as it comes. A proposal that arrives with the stages, gates and templates already decided has skipped the mapping. The business's own items should shape the process, not a slide the provider used before.
- Targets borrowed from elsewhere. A turnaround, a rework figure or a headcount ratio quoted as the standard should name its source and say why it fits this team. The site cites no benchmark for these measures, and borrowed numbers measure someone else's process.
- The provider in the approval path. A proposal that has the provider reviewing claims, prices or consent questions puts a judgement with someone who cannot answer for it.
- Documents that live in the provider's workspace. If the only copy sits in the provider's system, or in a format only its tools open, the business has bought a view of the work and not the work.
- Everything routed through the provider. A design in which requests, changes and audits all pass through one outside person recreates the single point of failure the key-person guide sets out to remove.
- Measures framed as individual targets. Goodhart's law explains why a measure that becomes a target is pushed in ways that damage the goal. Cycle time or rework held against a person invites skipped gates and early closures.
- Exit and data left for later. A proposal that is silent on the data the provider will handle, the AI tools it will use and the way the engagement stops leaves those questions to be settled after work has begun.
Accepting the work
Acceptance asks whether the business can use, change and defend what was delivered with the provider out of the room. As general practice, the business's signatory is someone other than the builder, and each check borrows its test from the guide that teaches the artefact.
| Delivered | Accept when |
|---|---|
| A process map | The people who do the work agree it matches the last few real items, with the waits, loops back and workarounds shown as they ran |
| A procedure | Someone who has not done the task before completes it from the document alone on a real or test item, every hesitation is fixed, and the process owner and the task owner are named, the task owner as a role, with a version and a change log |
| The approval matrix | Each row is triggered by something the intake form can ask about, the function named in the row has agreed it, it fits on one page and a first audit sample, run by someone other than the builder, finds it applied |
| The claims library | A sample of entries each carries the exact wording, dated evidence, the approver's name and a recheck date, and no entry was approved by the provider |
| The asset library | Pick assets that are live now: each can be found in the library with its status, version, rights and expiry, and its record of use says where it runs |
| The taxonomy and the naming rules | Someone other than the builder creates a campaign name from the controlled values, the launch check compares the live name with the work item, and the business's own owner runs the first audit |
| Service levels and reports | The levels were set from the team's own stage history, as the service levels tutorial asks, with duties on both sides and no figure lifted from another team, and someone in the business can produce time to live by stage and returns by gate from the work system's records |
| The charter | The sponsor and the leads of the teams served have signed it with dates, and a review date is set |
Judge improvement against the baseline taken before the work began, reading cycle timeThe elapsed time from an accepted request to live work, read stage by stage to show where work waits; a process measure, not a target for individuals. and reworkThe share of items sent back from a review or launch gate to an earlier stage; each return carries a reason, so the pattern points to the step that failed. together: faster work with rework climbing or gates skipped is a figure being defended, not a process improving. The site cites no benchmark for either measure, so compare with the team's own earlier period, and report both for the team as a whole, not as targets for the people inside it.
Ending or changing the engagement
The agency offboarding checklist covers the end of any engagement, from account ownership through to access removal. What operating work adds can be requested on day one. As general practice, put the date the provider's access ends in the statement of work, together with the conditions to meet first: every document in the business's library, every procedure with a process owner inside the business, the accountable roles confirmed and each decision the provider recommended recorded with the reason for its outcome.
The handover tutorial is written for a leaving marketer: it hands over first and removes sign-in second, with a handover recordOne document, kept by a coordinator, listing everything a departing marketer owns: tasks, open work, accounts, suppliers and know-how, each with a new owner. that holds one row per item and a new owner for each. As general practice, the same record can carry a provider's open work, accounts, files and unwritten know-how. The access review tutorial matches supplier access against live engagements, so the provider's accounts leave the list once the engagement has ended.
As general practice, run the key-person test on the way out. Ask who would change the workflow or a procedure tomorrow if the provider could not be reached. If the answer is the provider, update the coverage matrix and close that gap before access ends. If the provider stays on a standing arrangement, review it ahead of its renewal date against the measures taken at the start, as the renewal review tutorial describes. Notice periods, fees and other contractual points are for the business's legal adviser.
A cooperage appoints its first operations consultant (illustrative)
Thodral Cooperage appoints a consultant for a first operations project
Thodral Cooperage, an invented maker of oak casks for craft distillers and cider makers and of barrel-stave planters for households, has a marketing team of 6 and no operations role. Three launches in a row reached customers with an out-of-date price. Approval was given in email, and one campaign carried 4 different names in its ads, reports and CRM. The marketing lead wants outside help for a first project and wants to keep every decision.
She writes the scope before asking anyone: a diagnosis of the last 4 launches and a sample of 12 live items, then a build limited to what the diagnosis finds. She asks 3 providers the same written questions and fixes the gates and the weights before opening any reply. The two gates are that the documents live in the business's own library from the first draft and that every decision has its accountable role inside Thodral; the weighted criteria are whether the work starts from the business's own records (40%), how procedures are tested (30%) and what stays behind (30%).
| Criterion | Provider A, a large agency practice | Provider B, a freelance operations consultant | Provider C, a boutique consultancy |
|---|---|---|---|
| Documents in the business's own library from the first draft (gate) | Fails: documents would sit in the agency's platform until the end | Passes | Passes |
| Every decision has its accountable role inside Thodral (gate) | Not assessed | Passes | Passes |
| Starts from the business's own records (40%) | Not scored | 5 | 3 |
| How procedures are tested (30%) | Not scored | 4 | 3 |
| What stays behind (30%) | Not scored | 4 | 2 |
| Weighted total, out of 5 | Not scored | 4.4 | 2.7 |
Provider A is set aside at the gate before any score is added. Re-scoring the others with equal weights gives Provider B 4.3 and Provider C 2.7, so the order survives; Thodral appoints Provider B for the diagnosis and one small build.
The diagnosis traces the 4 launches from the work records and the inboxes. In the approval sample, 5 of the 12 items had no recorded review by the right role, 3 pages carried a claim about sustainably sourced oak with no evidence on file, the campaign with 4 names had no list of allowed values behind it, and only one person had ever published a product page. The marketing lead and the sales director agree one small build of four documents: a one-page approval matrix, a claims library that starts with that claim, a procedure for publishing a product page and a short list of controlled campaign-name values. Provider B drafts all four. The legal adviser Thodral already uses approves each claim entry and the matrix row for claims, and Provider B approves nothing.
At acceptance, a new marketing executive who has never published a product page follows the procedure alone and stalls at 3 steps, which are rewritten. The marketing lead builds a campaign name from the controlled values, the launch check catches a typed variant of it, and she then runs the first audit of campaign names as the owner of the list. The sales director, who did not build the matrix, samples recent launches and finds it applied, and each claim entry shows its exact wording, dated evidence, the legal adviser as approver and a recheck date. Every decision in the scope has a named job at Thodral as its accountable role, with the consultant only responsible. At the end, the handover record lists 9 items, each with a new owner at Thodral, and the consultant's sign-in is removed once every owner has confirmed. Over the next quarter, measured from the same stage history, the median time from accepted request to live fell from 21 to 16 working days with rework no higher than before.
The governance hub covers the decision rights, approvals and operating model that this guide draws on.
Common mistakes
- Hiring before the problem is traced. Without a diagnosis of the team's own records, proposals describe a method and not a need, and cannot be compared.
- Letting the provider approve. A reviewer's judgement on a claim, a price or a consent question belongs with the business's reviewers, and a consultant in that path leaves the business unable to approve without it.
- Copying someone else's targets. A turnaround or rework number taken from elsewhere reflects another team's route; set levels and goals from this team's own records.
- Accepting on the strength of a presentation. A presentation shows what the provider meant to build, so run the new-starter test, the sampled audit and the naming check with people who were not involved in the build.
- Making the provider the only person who can change the process. If nobody inside can edit a procedure or the matrix, the key-person risk has moved outside rather than gone.
- Leaving the legal terms to the scope. The scope says what the provider was asked to do; clauses, notice and similar terms are for the business's legal adviser.
