“We can build the syncs ourselves”
Head of Data Engineering · Customer data platforms
A data engineering lead who says the syncs are just a few pipelines is usually right about the first version. The cost is in keeping them running. Don't argue about difficulty. Cost the build, then the upkeep: ask who maintains the pipelines when a destination changes, and what the team would otherwise be building.
What the buyer says
My team can build the audience syncs ourselves. It's just a few pipelines.
How to handle it
Listen
Listen for the scope they have in mind. "A few pipelines" suggests they're thinking of the first two or three destinations, not every channel the business will want.
Acknowledge
Agree that their team could build it. Questioning their ability loses the room.
Explore
Ask how many destinations marketing will want within a year, who fixes a sync when a destination changes, how customers are matched across sources, and how consent is applied. Ask what's on the team's roadmap that this work would push back.
Respond
Compare the ongoing cost of building and maintaining with the cost of your platform, using their numbers. Position your platform as giving the team its time back, not replacing its skills.
Say this
“That's fair. Your team could build the first few, no question.”
Say this
“Who maintains them when a destination changes, or marketing asks for a new one?”
Say this
“What's on your roadmap that this work would push back?”
Variations
- CTO: “We have engineers. We don't buy what we can build.”
- Head of Data: “We'll just push audiences out of the warehouse ourselves.”
Questions people ask
How do you respond when a data team says they can build the syncs themselves?
Agree they could build the first version, then cost the upkeep: maintaining pipelines when destinations change, matching customers across sources, applying consent and adding new channels. Compare that ongoing effort with your platform, using their numbers.
What's often missed when teams plan to build audience syncs in-house?
Ongoing maintenance when destinations change, matching customers across sources, enforcing consent, and the steady stream of new channels marketing will ask for.
More objections in Customer data platforms
- “It's all in our data warehouse”
- “Our marketing cloud already includes one”
- “It's another consent risk”
- “We don't have enough first-party data”
Practise it before the real call
Free to start. No credit card.
