• LinkedIn
• Twitter
• Instagram
• YouTube
• RSS Feed

Apple •Spotify• Pocket Casts •Youtube •Overcast •RSS

What’s up everyone, today we have the pleasure of sitting down with David Joosten, Co-Founder and President at GrowthLoop and the co-author of ‘First-Party Data Activation’.

Summary: David learned that martech transformation begins with proof people can feel. Early in his career, he built immaculate systems that looked impressive but delivered nothing real. Everything changed when a VP asked him to show progress instead of idealistic roadmaps. From that moment, David focused on momentum and quick wins. Those early victories turned into stories that spread across the company and built trust naturally. Architecture became his silent advantage, shaping how teams worked together and how confidently they moved.

In this Episode…

• Earning The Right To Transform Martech
• Why Internal Roadshows Make Martech Wins Stick
• Architecture Shapes How Teams Move and What They Believe
• Bring Order to Customer Data With the Medallion Framework
• The Real Enemy of Martech is Fragmented Data
• Stop Calling Your CRM the Source of Truth
• Building the Tech Stack People Rally Behind
• Why Most CDP Failures Start With Organizational Misalignment

About David

David is the co-founder of GrowthLoop, a composable customer data platform that helps marketers connect insights to action across every channel. He previously worked at Google, where he led global marketing programs and helped launch the Nexus 5 smartphone. Over the years, he has guided teams at Indeed, Priceline, and Google in building first-party data strategies that drive clarity, collaboration, and measurable growth.

He is the co-author of First-Party Data Activation: Modernize Your Marketing Data Platform, a practical guide for marketers who want to understand their customers through direct, consent-based interactions. David helps teams move faster by removing data friction and building marketing systems that adapt through experimentation. His work brings energy and empathy to the challenge of modernizing data-driven marketing.

Earning The Right To Transform Martech

Every marketing data project starts with ambition. Teams dream of unified dashboards, connected pipelines, and a flawless single source of truth. Then the build begins, and progress slows to a crawl. David remembers one project vividly. His team at GrowthLoop had connected more than 200 data fields for a global tech company, yet every new campaign still needed more. The setup looked impressive, but nothing meaningful was shipping.

“We spent quarters building the perfect setup,” David said. “Then the VP of marketing called me and said, ‘Where are my quick wins?’”

That question changed his thinking. The VP wasn’t asking for reports or architecture diagrams. He wanted visible proof that the investment was worth it. He needed early wins he could show to leadership to keep momentum alive. David realized that transformation happens through demonstration, not design. Theoretical perfection means little when no one in marketing can point to progress.

From then on, he started aiming for traction over theory. That meant focusing on use cases that delivered impact quickly. He looked for under-supported teams that were hungry to try new tools, small markets that moved fast, and forgotten product lines desperate for attention. Those early adopters created visible success stories. Their enthusiasm turned into social proof that carried the project forward.

Momentum built through results is what earns the right to transform. When others in the organization see evidence of progress, they stop questioning the system and start asking how to join it.

Key takeaway: Martech transformations thrive on proof, not perfection. Target high-energy teams where quick wins are possible, deliver tangible outcomes fast, and use that momentum to secure organizational buy-in. Transformation is granted to those who prove it works, one visible success at a time.

Back to the top ⬆️

Why Internal Roadshows Make Martech Wins Stick

An early martech win can disappear as quickly as it arrives. A shiny dashboard, a clean sync, or a new workflow can fade into noise unless you turn it into something bigger. David explains that the real work begins when you move beyond Slack celebrations and start building visibility across the company. The most effective teams bring their success to where influence actually happens. They show up in weekly leadership meetings for sales, data, and marketing, and they connect their progress to the company’s larger mission. That connection transforms an isolated result into shared purpose.

“If you can get invited to those regular meetings and actually tie the win back to the larger vision, you’ll bring people along in a much bigger way,” David said.

The mechanics of this matter. A martech team can create genuine momentum by turning their story into a live narrative that other departments care about. Each meeting becomes a checkpoint where others see how their world benefits. Instead of flooding channels with metrics, show impact in person. When people see faces, hear real stories, and feel included in the mission, adoption follows naturally.

David has seen that the most credible voices are not the ones who built the system, but those who benefited from it. He encourages marketers to bring those users along. When a sales manager or a CX leader shares how a workflow saved hours or unlocked new visibility, trust deepens. One authentic endorsement in a meeting will do more for your reputation than a dozen slide decks.

Momentum also depends on rhythm. Passionate advocates move ideas forward, not mass announcements. David’s playbook involves building a few strong allies who believe in your work, keeping promises, and maintaining a consistent drumbeat of delivery. Predictable progress creates confidence, and confidence earns permission to take bigger swings next time.

Key takeaway: Wins that stay private fade fast. Present them live, in front of the right rooms, and connect them to the company’s shared mission. Bring along the people most impacted to tell their side of the story, and focus on nurturing a few genuine allies instead of broadcasting to everyone. That way you can turn one early success into a pattern of momentum that fuels every project that follows.

Back to the top ⬆️

Architecture Shapes How Teams Move and What They Believe

Technology architecture does more than keep the lights on. It defines how much teams trust each other, how quickly they adapt, and how confidently a brand competes. David describes it as invisible scaffolding, the kind that quietly dictates how an organization moves. Once the systems are in place, the defaults harden into habits. Those habits shape behavior long after anyone remembers who set them.

“People can get used to almost anything,” David said. “You acquire habits from architectural decisions made long ago, and it’s not conscious. You just walk into the context and act within it.”

That pattern shows up inside every marketing organization. Data teams often build for accuracy and control, while marketers push for agility and access. The architecture decides which side wins. When the design prioritizes risk management, marketers spend months waiting for queries to be approved. When it prioritizes freedom without governance, trust breaks down the first time a campaign misfires. Neither version scales.

Composable systems offer a third path. By layering data environments, companies can give marketers access to clean, pre-approved data without compromising control. The data team manages the upstream layers; defining what is reliable and how customer identities connect across systems. The marketing team operates within a sandbox where every dataset is ready for use. That way you can move fast with confidence, not hesitation.

David has seen organizations go a step further by assigning dedicated “data democratization” leads. These people translate between the builders and the users, guiding marketers on what’s safe, how to test ideas, and when to escalate issues. It turns governance into a living relationship instead of a rulebook. Over time, that structure builds more than just efficiency. It builds trust. Trust in data, trust in process, and trust between teams.

Key takeaway: Architecture shapes culture. When you design systems that balance safety with self-service, you create an environment where trust compounds and agility scales. Treat every configuration decision as strategic leverage, because the structure you build today determines how confidently your organization competes tomorrow.

Back to the top ⬆️

Bring Order to Customer Data With the Medallion Framework

Every marketing team talks about building a single customer view, but few manage to make it real. David’s medallion framework gives them a way to do it without chaos. It turns vague goals about “data alignment” into a repeatable structure that connects technical discipline with organizational trust.

The system moves through three layers.

The bronze layer is where everything lands first. It holds unfiltered data from CRMs, transactional systems, ad platforms, and loyalty programs. Nothing is cleaned or shaped yet. It is a pure record of how the business actually operates, which creates a reliable foundation.

Next comes the silver layer, where data becomes meaningful. Teams deduplicate records, define entities, and decide how customers, products, and engagements connect. It is where assumptions are tested and shared definitions take form. In a B2B setting, it might mean linking product SKUs to company hierarchies or mapping web and app interactions back to a single account. That way you can give data engineers and analysts a structure they can work with while keeping business logic transparent.

“Bronze is where data lands raw. Silver is where it starts to tell a story. Gold is where everyone else can finally use it.”

The gold layer is the payoff. It delivers refined, governed, and easy-to-consume tables for marketing, operations, and leadership. Instead of a thousand event-level logs, you get summaries that answer business questions quickly. For example, you can see how many mobile sessions a customer had in the last 30 days and decide whether to reach them by app or email. These gold views are pre-computed to save both time and cloud costs while keeping everyone aligned on the same definitions.

When every team works from gold, confusion fades. Finance, marketing, and analytics stop arguing over whose numbers are right. The same data powers campaign targeting, executive reporting, and machine learning. Meetings shift from debating metrics to improving performance. The medallion framework works because it gives technical and business teams a shared source of truth they can trust.

Key takeaway: Use the medallion framework to bring order and trust to your customer data. Load raw inputs into bronze, shape meaning in silver, and distribute usable data through gold. That way you can eliminate cross-team confusion, cut reporting waste, and help your organization act on data with confidence instead of debate.

Back to the top ⬆️

The Real Enemy of Martech is Fragmented Data

Marketers tend to hold onto their CRMs like safety blankets. They live inside them, organize their days around them, and treat them as the ultimate record of customer truth. David has seen this play out across dozens of teams, and the pattern rarely changes.

“Those systems represent the truth of your team,” he says, “but they stop being useful the second you try to share what’s inside them with anyone else.”

The moment another department asks for data, exports start flying, spreadsheets multiply, and confidence in the numbers starts to decay.

“As soon as you want to communicate what’s happening in your marketing system to other teams, you’re forced to export. That’s when trust erodes.”

Each marketing system tells its own story about the customer. Marketo frames everything around B2B pipelines and leads. Braze and Klaviyo think in terms of engagement and triggers. Those design choices shape how data is modeled, stored, and interpreted. When a company operates across multiple products or audience types, these conflicting worldviews create noise instead of clarity. The data lake cuts through that noise by housing every record under one schema that the company controls. It replaces assumptions with structure and gives every team the same baseline to work from.

Centralizing truth in the warehouse is not an abstract concept. It is a practical investment in shared understanding. Once the data layer becomes the foundation, every downstream system becomes a reflection of it. That way you can feed campaigns, dashboards, and automations with confidence, knowing they all draw from a single, governed source.

David calls this the composable model: a structure that connects analytics and activation without locking anyone into one vendor’s logic. “Having a tight link between marketing and analytics used to be an edge,” he says. “Now it’s table stakes.”

For teams trying to modernize without chaos, David recommends a simple sequence:

1. Mirror your marketing automation schema inside the warehouse.
2. Rebuild your marketing data model to match that structure.
3. Feed your automation platform from the warehouse instead of multiple disconnected sources.

That way you can maintain familiar workflows while quietly upgrading the plumbing underneath. Once the automation tool starts pulling from the lake, you gain the ability to add fields, create calculated metrics, and expand reporting without losing data integrity.

“It’s about walking the path together toward a more extensible future,” David says.

Key takeaway: Treat your CRM as a surface for action, not as the foundation for truth. Move your customer data to the warehouse, mirror the schemas marketers already know, and let that become the shared layer for every system. That way you can reduce fragmentation, increase trust, and finally make analytics and activation part of the same conversation.

Back to the top ⬆️

Stop Calling Your CRM the Source of Truth

The industry’s obsession with declaring a “single source of truth” has turned into a guessing game. Some teams swear by their CRM because that is where deals close and campaigns launch. Others have shifted their loyalty to the data warehouse, which quietly powers everything behind the scenes. As David explains, the CRM might record the interaction, but the warehouse holds the heartbeat. It captures context, relationships, and the reliability that CRMs rarely maintain at scale.

“Marketers don’t care how the sausage is made,” David said. “But they care a lot when the sausage explodes.”

That tension defines most marketing operations. Marketers crave speed, and they should. Velocity keeps ideas fresh and momentum high. But the faster things move, the easier it becomes for bad data to slip through unnoticed. A single broken filter or sync issue can derail a campaign. When that happens, the conversation quickly turns from creative ambition to data reliability. Teams stop debating campaign concepts and start chasing down which field failed to update.

David described a problem that anyone managing complex integrations will recognize.

In systems like Marketo, verifying what data actually lives in the platform can be painfully slow. “Their APIs are opaque,” he explained. “It’s hard to know what’s actually in there without going record by record.”

Engineers call this the “two generals problem,” where two systems exchange messages but can never be entirely sure that the other side received them. Modern data warehouses solve this problem elegantly. They let you confirm the exact state of data at any time. That visibility builds confidence for the data team and predictability for marketing.

When teams operate from that shared trust, everything moves faster. David described how self-service workflows give marketers direct visibility into the data that powers their targeting. A marketer can:

• Test filters before activation
• View audience size and spend potential instantly
• Understand engagement patterns without waiting for SQL queries

That level of autonomy reduces conflict and restores creative energy. Marketers feel ownership of their work again because they can move from idea to activation without a tug-of-war over data access.

Key takeaway: Treat your data warehouse as the anchor for marketing truth, not the hidden plumbing behind it. Reliability creates trust, and trust accelerates execution. Build systems that let marketers preview, validate, and experiment safely without waiting in a queue. The faster your team can confirm what is true, the faster they can create work that matters.

Back to the top ⬆️

Building the Tech Stack People Rally Behind

Marketers love the fantasy of a perfect stack, polished and future-proof, where every integration hums in sync and every dashboard updates in real time. David calls that fantasy a trap. The perfect stack keeps changing, shifting every few months as new tools and trends rewrite what “best in class” even means. The stack worth building is the one your team believes in enough to use, fix, and grow.

“There’s probably a perfect tech stack out there somewhere,” David said, “but even if it exists, it changes every six to twelve months. You’ll never catch it.”

David argues that leaders waste too much energy chasing technical purity instead of team alignment. A system that’s theoretically flawless but impossible to maintain becomes dead weight. The teams that win start with what they need to deliver outcomes today, then design for adaptability tomorrow. That means embracing the 80 20 rule: focus on the 80 percent of use cases where batch processing works, and layer in real time only where it truly matters.

He uses “real time everything” as a prime example of misplaced ambition. Real time pipelines sound impressive in a boardroom, but in practice they are expensive, fragile, and hard to reason about. Audience counts never stabilize, metrics fluctuate by the minute, and decision-making slows down because the data never stops moving. The obsession with speed erodes clarity. Meanwhile, teams that accept a few hours of latency gain stability, accuracy, and confidence.

A tech stack should feel alive, evolving with the people who depend on it. That means prioritizing usability, transparency, and cost discipline over theoretical perfection. You can always add new layers later, but you cannot rebuild trust once it’s gone.

Key takeaway: Build systems people believe in. Anchor your stack in the 80 percent that drives real outcomes, and extend it only where real time precision earns its keep. That way you can create a stack that teams rally around; stable enough to trust, flexible enough to grow, and practical enough to finish.

Back to the top ⬆️

Why Most CDP Failures Start With Organizational Misalignment

CDP projects rarely collapse because of bad software. They fail because teams never aligned on ownership, purpose, or politics. David has seen this story unfold too many times. A marketing VP reallocates ad dollars to buy a platform without looping in data. A data leader installs a warehouse-first system that marketing cannot operate. Six months later, the integration limps along, people stop logging in, and the CDP becomes another expensive ghost in the tech stack.

“The sale has to happen for all the key stakeholders sooner or later,” David said. “If you skip that step, you’re just scheduling your failure for later.”

His point is that objections do not disappear with contracts. They simply resurface after implementation, when the stakes are higher. Bringing every stakeholder to the table early is the only way to avoid political landmines later. That means asking the difficult questions upfront: Who controls identity resolution? Who approves schemas? Who maintains compliance? It is better to argue now than to stall later.

Composable architecture helps because it distributes control instead of concentrating it. Teams can choose their preferred tools while still sharing a single data foundation. Marketing keeps its automation stack. Data governs the warehouse. Sales runs its CRM. Everyone connects through a common source of truth. That way you can avoid the zero-sum fights that plague monolithic platforms.

Momentum depends on the believers. David focuses on finding small, hungry teams inside large companies who have the most to gain. They tend to move faster because they have no alternatives. When those groups see their first campaign activate in hours instead of weeks, they become vocal champions. Their wins create social proof that spreads across departments. David’s teams often use short, intense proof-of-concept cycles: two weeks of focused collaboration followed by a shared readout; to build early conviction and keep everyone engaged.

Key takeaway: Composable CDPs succeed when alignment comes before architecture. Pull every decision-maker into the process early, target the teams with the most urgency, and prove value fast. Build trust through visible wins, shared ownership, and flexible systems that let each team work the way they want while contributing to the same source of truth.

Back to the top ⬆️

Why Tough Conversations Strengthen Lifecycle Marketing

Lifecycle marketing teams often inherit problems they did not create. David has watched companies spin up these teams because the competition has them, not because leadership understands what they are for. Then churn increases and the lifecycle team becomes the scapegoat. The root problem is usually upstream in acquisition or product. When companies bring in the wrong customers or make promises that do not match the product experience, no retention campaign can repair that mismatch.

“One of the biggest problems with retention,” David said, “is acquisition. If you acquire the wrong customers or make the wrong promises, the relationship may just not be salvageable.”

These are the conversations most teams avoid, but they are the ones that define real alignment. David advises lifecycle leaders to start with uncomfortable questions before a single email goes out:

• Why does this team exist in the company’s structure?
• Which customer problems are within our control to fix?
• Who owns which part of the customer message when multiple departments want to speak at once?

In one company David worked with, the product team flooded customer inboxes with updates and release notes. Lifecycle messages disappeared in the noise. “It was like shouting into a hurricane,” he said. The fix was not another clever campaign but a boundary. Product had to recognize that every message they send occupies space that someone else loses. Marketers need to defend that space with data and clarity. Customer communication is finite, and every email or push notification has a cost.

At Google, David’s team learned that the first 90 days of spend predicted long-term success for AdWords users. At Indeed, he saw that the first sponsored job post determined whether an employer would stay active. These insights came from working cross-functionally, not in isolation. Lifecycle teams that act like growth partners, not service providers, drive lasting results. They share metrics with acquisition and product, build experiments around shared goals, and treat retention as a company-wide responsibility.

Key takeaway: Start tough conversations early. Define why the lifecycle team exists, clarify shared ownership of customer communication, and align on one or two core metrics that reflect true business health. That way you can turn lifecycle marketing into a collaborative growth engine instead of a reactive clean-up crew.

Back to the top ⬆️

Why Experimentation Culture Strengthens Martech Leadership

Architecture shapes how teams move, make decisions, and earn trust. David argues that the best leaders in martech are not the ones who understand every technical detail, but those who recognize the downstream consequences of architectural choices. Every system design, data flow, and privacy safeguard eventually becomes a cultural decision. Leaders who connect those dots see architecture as leverage, not plumbing.

He advises future marketing leaders to develop curiosity, not code mastery. Curiosity drives better decisions because it helps you anticipate the long-term effects of short-term choices. David encourages teams to spend time with peers who handle different technologies, read broadly, and constantly ask how system design influences the customer experience two years from now. In his view, the leaders who thrive are the ones who understand the implications of technology rather than its mechanics.

“You don’t have to understand all the nitty-gritty of the technologies,” David says. “But you do have to understand the implications of it.”

David believes experimentation culture turns that understanding into momentum. He describes three layers that make experimentation sustainable:

1. Process experimentation, where teams adjust how they collaborate and automate.
2. Technical experimentation, where new integrations or data flows are tested safely.
3. Cultural experimentation, where people are encouraged to prototype, even without guaranteed outcomes.

He points to GrowthLoop’s quarterly hackathons as a proof point. These events free the team from daily metrics and encourage them to explore the edges of what is possible. Many of GrowthLoop’s most creative features started in these sessions, built by people who finally had permission to think beyond roadmaps. When people experiment without fear, they create systems that evolve naturally instead of being forced into change.

Politics, in David’s world, is a lot more empathy in practice than manipulation. Moving big ideas through a company requires understanding what keeps other departments awake at night. Data teams worry about accuracy, finance wants to manage risk, and marketing teams crave creative autonomy. Building influence means learning how each group defines a “good day.” David’s advice is to walk through those perspectives until you can speak their language fluently.

Key takeaway: Technical mastery is secondary to architectural empathy. The best martech leaders create systems that evolve through safe experimentation and shared understanding. They design environments where curiosity drives iteration, where every stakeholder feels seen, and where trust compounds over time. When experimentation and empathy align, architecture becomes a living system that scales with confidence.

Back to the top ⬆️

How to Use a North Star to Stay Focused in Leadership

Most leaders claim they value focus, but few actually protect it. David says everything starts with asking why before saying yes. Too many executives live inside their inbox, running from one “urgent” request to the next, mistaking activity for momentum. Problems come flying in from every direction, and without a clear destination, days evaporate into reaction.

“You can literally fill your days only responding to problems without having a North Star you’re working toward,” David explains.

He learned that lesson the hard way while guiding early customer implementations at GrowthLoop. Every client brought an avalanche of edge cases: feature ideas, hypotheticals, future-proofing requests. Instead of chasing each one, he anchored every discussion in purpose. What outcome did we agree mattered most? Does this new idea help us get there faster? That habit created alignment, speed, and trust.

David treats his personal life with the same level of design. Time with his kids or a weekend outdoors is not random downtime. It’s intentional investment. He thinks about what each activity means for his children, his wife, and himself. The goal is not to squeeze productivity out of family life, but to make time feel deliberate, full, and mutual.

Most people chase balance with systems and scheduling hacks. David’s version starts with clarity and ends with boundaries. Focus is the byproduct of saying no to everything that isn’t connected to purpose. It is the discipline of returning, again and again, to the reason you started.

Key takeaway: Protect your attention like it’s equity. Write down your North Star, share it with your team, and measure every decision against it. That way you can spend your time building toward outcomes that matter, instead of drowning in noise that doesn’t.

Back to the top ⬆️

Episode Recap

David Joosten learned that transformation happens through proof, not plans. After leading a massive project that connected hundreds of data fields but produced no visible results, he shifted focus to quick wins. He found small, eager teams, delivered impact fast, and used those stories to earn trust across the company. Visible progress built belief, and belief created momentum.

He turned those wins into company-wide stories by bringing real users into leadership meetings. Hearing a sales manager explain how a new workflow saved hours carried more weight than any metric. Proof mattered more than polish.

Over time, David saw how architecture shapes culture. His medallion framework—bronze for raw data, silver for structured, gold for usable—gave teams shared definitions and ended arguments over whose numbers were right. He focused on reducing fragmentation by moving truth to the warehouse so every tool pulled from the same source.

He abandoned the idea of a perfect stack. Tools change too fast. The best system is the one people believe in and can maintain. He learned that CDP projects fail because of misalignment, not technology. Bringing every stakeholder in early and proving value quickly prevents that collapse.

At GrowthLoop, he made experimentation part of the culture through hackathons that encouraged curiosity and safe failure. His philosophy is simple: transformation grows from small wins, clear systems, and environments that make people feel confident to try again.

Listen to the full episode ⬇️ or Back to the top ⬆️

Follow David👇

• LinkedIn
• Book: First-Party Data Activation: Modernize your marketing data platform
• GrowthLoop

✌️

—
Intro music by Wowa via Unminus
Cover art created with Midjourney (check out how)

Apple •Spotify• Pocket Casts •Youtube •Overcast •RSS

Related tags

🔎 Search for an episode

Search

See all episodes

Future-proofing the humans behind the tech

Apple •Pocket Casts•Google •Overcast •Spotify •Breaker •Castro •RSS

• LinkedIn
• Twitter
• Instagram
• YouTube
• RSS Feed