Costs
Part of Martech strategy in practice, not on slides
Martech strategy checklist for the careful reader (2027 update)
A portfolio review of martech spend, privacy profiles and platform decisions that ends in invest, repair, contain, consolidate, replace or retire calls.
What to take away
- Every tool in the stack leaves the review with one callinvest, repair, contain, consolidate, replace or retire.
- The register is the deliverable. One row per toolcall, owner, due date, acceptance test, recovery route, budget line.
- Reconcile media, software, data movement, storage, agency, production and internal effort against approved budget before judging performance.
- Default cadence is quarterly, plus a mandatory pass 60 days before any renewal date.
- Scope covers the United States and Canada, so both sets of privacy and procurement rules land in the same register.
A MarTech strategy review earns its keep when it produces portfolio decisions. Run it with the people who own budget, platforms, data and customer outcomes.
Six calls, one register
Every tool, integration and contract leaves the review in one of six states. The call is a decision, not a description of health.
When it applies
- Invest
- The tool carries revenue or a control you cannot replace
- Repair
- The capability is right, the configuration or ownership is not
- Contain
- The tool is failing but a contract or dependency blocks exit
- Consolidate
- Two tools do the same job and one can absorb the other
- Replace
- The capability is needed and the vendor is not
- Retire
- Nobody can name the decision the tool supports
What it costs
- Invest
- Added licence, implementation or headcount
- Repair
- Rework time, not new spend
- Contain
- Monitoring effort until renewal
- Consolidate
- Migration effort, one cancellation
- Replace
- Procurement cycle, data migration, retraining
- Retire
- Cancellation and archive
[figure 1]
Six calls and their costs
Call
- Invest
- Carries revenue or control
- Repair
- Capability right, config wrong
- Contain
- Failing but contract blocks exit
- Consolidate
- Two tools, one can absorb
- Replace
- Capability needed, vendor is not
- Retire
- No nameable decision supported
When it applies
- Invest
- Licence, implementation, headcount
- Repair
- Rework time, not new spend
- Contain
- Monitoring until renewal date
- Consolidate
- Migration effort, one cancellation
- Replace
- Procurement, migration, retraining
- Retire
- Cancellation and archive
What it costs
- Invest
- Repair
- Contain
- Consolidate
- Replace
- Retire
Ten tools means ten rows, seven fields each.
- Tool name, contract end date and the renewal notice window.
- Call, with the trigger that forced it.
- Owner with authority to spend or cancel.
- Due date.
- Acceptance test that closes the action.
- Recovery route if the action fails.
- Budget line the money moves from or to.
Contain is the call teams skip. A tool that fails its acceptance test inside a twelve month term is not repaired by wishing. Contain it, name a monitor, and set the review date before renewal.
Example: one tool through the six calls
A 40 person marketing team runs a marketing automation suite and a separate email tool writing into one database. The suite passes its acceptance test. The email tool duplicates it, and nobody can name the decision it supports.
- Quarter one, contain. A processing clause blocks exit mid-term, so the tool stays with a named monitor and a review date. Cost: monitoring hours only.
- Quarter two, consolidate. Move 11 active journeys into the suite. Typical effort for that migration is four to eight weeks of one operations specialist, plus a one-time licence step-up. Fit decides this work more than feature count, as these notes on marketing operations tools argue.
- Quarter two, repair. Consent capture fails its acceptance test after the migration. Cost: rework time, no new spend.
- Quarter three, retire. Cancel the email contract, archive its templates and remove the integration.
Budget reconciliation before performance claims
Attributed credit is a model based reporting result, not proof of causation. Reconcile cost first, so performance arguments start from the same numbers.
- Media spend against the approved plan, by channel and month.
- Software usageseats paid against seats active, tier against actual volume.
- Data movement and storageevents ingested, profiles stored, overage rate per contract.
- Agency, production and support invoices against the scope they were bought for.
- Internal efforthours lost to manual exports, reconciliation and workarounds.
[figure 2]
Reconcile cost before judging results
- Media spend against approved plan, by channel and month
- Seats paid for against seats active
- Events ingested, profiles stored, overage rate
- Agency, production and support invoices against scope
- Hours spent on manual exports and workarounds
Write ratios in variables and let the owner substitute. Cost per active profile equals platform fee divided by active profiles. Vendor rates move, so cite the pricing page and the date you checked it.
Privacy profile comparison, not compliance evidence
NIST's Privacy Framework 1.1 usage guide sets a current profile against a target profile as present and desired outcomes. The gap between them supports prioritization, buying and communication across an ecosystem. Checked January 2027.
The largest gap between where you are and where you intend to be becomes the first project. A profile is a planning artifact, not compliance evidence, and it does not transfer between organisations.
For procurement, the CISA software acquisition fact sheet covers development practice, supply chain exposure, deployment and vulnerability management. Those questions belong in the vendor review, not in a local approval decision.
A deletion request is not a rollback of reporting history. Google's Analytics documentation says a property editor can request deletion of selected collected text, and that affected events may remain counted after replacement. Verify identity paths, timing, backups and exports separately.
Check that your customer data platforms keep identity models consistent across every connected system, or a deletion in one place leaves the same person live in another.
Cadence, ownership and jurisdiction
Run the full register quarterly, plus a mandatory pass 60 days before any renewal date. Renewal is the forcing function that makes a call real.
One accountable person per row, with authority to spend or cancel. Shared ownership produces no decision.
American teams work to FTC guidance and state privacy law. Compare consent rules in this piece on CAN-SPAM rules and automation workflows before writing opt-in logic into a workflow. Canadian teams work to PIPEDA, and the OPC's PIPEDA compliance help covers consent and marketing obligations. CASL governs commercial electronic messages. Checked January 2027.
