What Does a MarTech Consultant Actually Deliver? Artifacts, Reports, and What "Done" Looks Like
A consulting engagement is paid for in deliverables. Not slides — deliverables you can act on, reference six months later, and hand to a new hire. This is the artifact catalog from the engagements I run as an independent MarTech consultant: what you get, what it contains, what it isn't, and how the team uses it after I exit. If you're shopping a MarTech consultant, this is the comparison set.
Why deliverables matter more than slides
Slides die when the deck is closed. The decision presented in a slide gets remembered for a quarter, then the team rotates and the reasoning is lost. Written briefs survive a re-org because they live in the brand's tooling and are referenced when the next decision builds on the first.
Decks present decisions. Deliverables enable decisions. The consultant's job is to leave deliverables behind — artifacts the team will still use after the engagement closes. A consulting engagement that produced no written artifact produced no value, only a feeling. Feelings don't survive the next budget cycle.
For broader context on what consulting engagements look like inside the work, see what does a MarTech consultant actually do.
The seven core deliverables
Every engagement I run produces some subset of these seven artifacts. Which ones depend on the engagement shape — see the section below on how deliverables differ by engagement.
1. The audit brief
Format: 8–15 page written document, delivered as PDF and as a Notion or Confluence page in the brand's tooling.
What it contains: A current-state map of the stack, five to eight named gaps with severity ratings, the recommended sequence of fixes, and the cost-of-inaction for each gap.
What it isn't: A 90-slide consulting deck with three layers of executive summary and twenty pages of "current state" diagrams that nobody asked for.
How the team uses it after handover: As the team's roadmap reference for the next twelve months. The named gaps become tickets. The recommended sequence becomes the quarter plan. The brief is referenced in budget conversations and in hiring decisions.
The audit brief is the centerpiece of a MarTech architecture review — for most engagements that start with strategy, it's the first artifact produced.
2. The vendor selection memo
Format: 4–8 page written document.
What it contains: Scoring of three to five vendors against the brand's specific use cases, the primary recommendation with the reasoning behind it, the secondary fallback, and the named risks of the recommended choice.
What it isn't: An analyst-style scorecard with forty dimensions, half of which don't apply. The memo doesn't pretend objectivity it can't deliver — it commits to a recommendation.
How the team uses it after handover: As the basis for the SOW negotiation with the chosen vendor. The named risks become the redlines in the contract.
3. The event taxonomy spec
Format: A structured table or YAML file containing thirty to eighty events plus eight to twenty user properties.
What it contains: Event names, properties, types, validation rules, owner per event. Versioned. Often paired with a sample-payload file showing the expected shape of each event in flight.
What it isn't: A single-purpose tracker for one campaign or one platform. Not a list of "events we currently send" — a contract for what events should look like going forward.
How the team uses it after handover: As the source of truth for every new event added in the future. New event proposals reference the spec. New analytics requests get checked against the spec before implementation.
The taxonomy spec is the central artifact in any server-side tracking implementation.
4. The identity model document
Format: Two to four page document combining a diagram with a written narrative.
What it contains: Identity sources (CRM, login, ESP, anonymous web cookie, mobile device ID), merge rules between them, ID precedence, the handling of anonymous-to-known transitions when a user authenticates.
What it isn't: A generic "user 360" diagram. The identity model is specific to the brand's actual sources and the actual decisions that need to be made when two profiles look like they might be the same person.
How the team uses it after handover: As the architectural reference for any future stack change. When a new system is added, the identity model is what determines how that system's IDs map into the existing graph. The identity model is the most-referenced document I produce — it pays back its writing cost many times over. For more on how this fits into a CDP rollout specifically, see the MarTech consultant's role in a CDP rollout — and the deliverable lives within the CDP implementation engagement.
5. The data flow map
Format: A diagram (Whimsical, Lucidchart, or Mermaid in version control) plus an accompanying written narrative.
What it contains: Every source, every transformation, every destination. The consent state of each (consent-required vs. always-on). The data residency of each. The sensitivity classification.
What it isn't: A vendor architecture diagram showing the vendor's product in the middle and arrows pointing in. The data flow map is brand-centric, not vendor-centric.
How the team uses it after handover: When a new system is added, this is what's updated to keep the model of the stack current. When a privacy review happens, this is the document the privacy team references. When a vendor is replaced, this is what guides the migration.
6. The runbook
Format: 6–12 page Notion or markdown document.
What it contains: The recurring operations the team needs to perform — adding a new event, debugging a stuck destination, rotating credentials, investigating a discrepancy between two reports. Each operation is described step-by-step with screenshots or commands.
What it isn't: A vendor's documentation reference. The runbook is brand-specific — it covers the procedures unique to the brand's stack and conventions.
How the team uses it after handover: Anyone in the team can execute a known operation without escalating to a senior engineer. The runbook reduces the marginal cost of operations work and is the artifact that most reliably outlasts the original engagement.
7. The handover transcript and open-questions register
Format: 1–2 page written document plus a small spreadsheet.
What it contains: What was done in the engagement, what was deferred and why, the open questions and who owns each. Signed off by both sides.
What it isn't: A "what we'd do next if you keep paying us" pitch. The handover is the formal close, not a sales document for the next phase.
How the team uses it after handover: As the formal end-of-engagement record. When questions surface six months later about what was decided and why, the handover is the answer.
Three optional deliverables (engagement-dependent)
Beyond the seven core artifacts, three more show up depending on the engagement shape.
- The strategic brief. When the engagement starts at strategy: a one-page brief with the question, the answer, the implications, the next steps. Written for a board meeting or a leadership decision. The brief is the only artifact in a strategy sprint engagement that's written for an executive audience — everything else is built for operators.
- The training session deck. When the engagement ends with a team handover: a deck used in a sixty-to-ninety minute live training session with the team. Recorded so future hires can reference it. The deck is structured around the runbook, not around the platform — operators need to know how to execute, not how the platform was built.
- The executive summary. When the engagement crosses functions: a one-page summary of the audit brief written for non-technical leaders — usually the COO, CFO, or CMO. Stripped of platform-specific language; framed in business outcomes.
What "done" looks like — three signals
A consulting engagement is done when three things are true at once. Any one of them on its own isn't enough.
- The team can answer the original question without me in the room. If the team still needs to escalate to me to answer the question that triggered the engagement, the work isn't done.
- Every deliverable is owned by someone internal. Owners are named in the handover transcript by name and role. Anonymous ownership is no ownership.
- The acceptance criteria from the SOW are signed off, in writing, by both sides. Verbal sign-off is not sign-off. The signed document is what closes the project.
If those three signals are true, the engagement is done. If any of them are missing, the engagement is incomplete — and continuing to bill against it is a service I am not willing to provide.
How deliverables differ by engagement shape
The seven core deliverables don't all show up in every engagement. The mix depends on the engagement shape — see how I scope engagements for the full menu.
- Strategy sprint. Audit brief + strategic brief + executive summary. No implementation artifacts. The output is a decision, written down, with the receipts. Typical duration: three to six weeks.
- Implementation lead. Event taxonomy spec + identity model + data flow map + runbook + handover transcript. Audit brief included if discovery is in scope. The output is a system, in production, with documentation. Typical duration: twelve to twenty-six weeks.
- Fractional MarTech advisor. Monthly written notes, a decisions log, contributing edits to existing artifacts the team owns. No new "deliverables" — the value is the standing seat at the table. The fractional advisor doesn't write artifacts in the way an implementation lead does; the fractional advisor reviews and amends what the team produces.
What I refuse to deliver
A short, deliberately uncomfortable list. Stating these openly is the credibility unlock — and protects the engagement from drifting into the patterns I won't ship.
- A 90-slide deck instead of a 12-page brief. Deck culture is a defensive posture; written briefs are the artifact that outlives the engagement.
- A retainer scope without exit criteria. Open-ended retainers serve the consultant, not the brand. Every retainer I run has a renewal review and a defined exit shape.
- Verbal-only handovers with no written artifact. If the brand can't reference what was decided after the engagement closes, the engagement didn't deliver.
- "Insights" untethered to a specific decision. A finding without a recommendation is a slide, not a deliverable. Every named gap in an audit brief comes with a recommended action and a sequence.
How the deliverables end up in the brand's tooling
A deliverable in a Drive folder I own is not delivered. The tooling it lives in determines whether it survives.
- Notion workspace. Most common. Survives re-orgs because it's the brand's wiki, not the consultant's. Searchable, linkable, easy to extend.
- Confluence plus Google Drive. When the brand's tooling is Atlassian-anchored. Slightly heavier process but works the same way.
- GitHub repo. When the brand has a strong engineering culture and the deliverables are versioned alongside code (event taxonomy YAML, runbook markdown). My preferred tooling when the brand can support it — version control is the cleanest possible audit trail.
- Never email-only. Email artifacts get lost in six months. Anything that lives only in an email thread is anything that's about to be re-discovered the hard way.
FAQ
Will I get a deck or a written report?
A written report. I do produce a closing presentation when the audience is executive-level — but the artifact of record is the written brief, in the brand's tooling, that outlasts the meeting. The deck is a presentation aid, not the deliverable.
Who owns the deliverables after the engagement ends?
The brand. All artifacts produced during the engagement are the brand's property and live in the brand's tooling — Notion, Confluence, GitHub, whatever the brand's standard is. I keep working copies for my own reference; the brand's copy is canonical.
Are deliverables included in the day rate or charged separately?
Included. Day-rate or fixed-fee scope covers the deliverables produced during the engagement. There are no separate charges for "documentation," "handover materials," or "training session prep." If a deliverable is in scope, it's in the price.
Can I see a sanitized example of an audit brief?
Yes. After a discovery call, when the engagement shape is clear, I share a sanitized version of an audit brief from a previous client (with all client-identifying details removed) so you can see the format, depth, and writing style before committing.
If you want to see what an audit brief looks like for your situation, a 30-minute discovery call is the place to start.