Martech, explained · Managing your stack · 1:43
Who owns each tool in your stack?
Ask who owns a tool and you get three answers: the team that asked, the budget that pays, the person who set it up. None of them is the owner
Embed this film
Paste this where the film should play. It links back here.
The short answer
The owner is one named person who answers when the tool breaks, knows what it is for, what feeds it and when it renews, and can say no to a new connection or a second tool. A team can hold a tool, but one name is the one you call. Put the owner on the stack itself.
Questions this answers
Who owns a tool: the team that asked for it, the budget, or the person who set it up?
None of them, on their own. All three matter, but the owner is the person who answers when it breaks: one name, not a team, a cost centre or whoever configured it three years ago.
What does the owner of a martech tool actually do?
They know what the tool is for, what feeds it and when the contract renews. They answer when it breaks. And they can say no: to a new connection, a new field, or a second tool that does the same thing.
Do integrations need an owner too?
Yes. A sync between two tools has one owner, agreed before it breaks. Otherwise the first sign of trouble is a post in a support channel that Marketing passes to IT and IT passes to the agency.
How do you spot a tool nobody owns?
From the outside: nobody knows who logs in, the renewal arrives unannounced, and every fix starts with "does anyone know?" Those three signs are enough to find the gaps without an audit.
Where should ownership be written down?
On the stack itself, where everyone looks: every tool in a team, every team with a lead. Colour the stack by owner and the tools nobody holds stand out at once. Before the next tool goes in, put one name on every box you already have.
Transcript
Every chapter as text. Click a time to play the film from there.
0:00 Late Friday
Late Friday, your web forms stop reaching the CRM.
Someone posts in the support channel. Marketing thinks it's an IT problem. IT thinks the agency built it.
An hour later, nobody has picked it up. Nobody was asked by name.
0:19 Three answers
Ask who owns a tool, and you often get three answers.
The team that asked for it. The budget that pays for it. And the person who set it up, three years ago.
All three matter. None of them is the owner.
0:34 What an owner does
The owner is the person who answers when it breaks. A team can hold the tool, but one name is the one you call.
They know what it's for, what feeds it, and when the contract renews.
And they can say no: to a new connection, a new field, or a second tool that does the same thing.
Connections need the same. Each sync between two tools gets one name, agreed before it breaks.
1:00 Spotting the gaps
You can spot a missing owner from the outside.
Nobody knows who logs in. The renewal arrives unannounced. Every fix starts with, does anyone know?
1:12 One name per box
Put the owner on the stack itself, where everyone looks: every tool in a team, and every team with a lead.
Color the stack by owner, and the tools nobody holds stand out at once.
Before the next tool goes in, put one name on every box you already have.
Then next Friday, someone picks up.
Learn more at Martech Stack Builder, or build your own.