Humans of Martech
Humans of Martech

Humans of Martech

Phil Gamache

Overview
Episodes

Details

Future-proofing the humans behind the tech. Follow Phil Gamache and Darrell Alfonso on their mission to help future-proof the humans behind the tech and have successful careers in the constantly expanding universe of martech.

Recent Episodes

215: How to find hidden job opportunities (The Martech job hunt survival guide, part 1)
APR 14, 2026
215: How to find hidden job opportunities (The Martech job hunt survival guide, part 1)
What's up everyone, today we kick off part 1 of a 3 part series we’re calling The Martech Job Hunt Survival Guide. Part 1 is: How to find hidden job opportunities.In This Episode:(00:00) - Intro (01:23) - In This Episode (01:59) - Sponsor: Knak (03:06) - Sponsor: MoEngage (04:49) - Why Getting Laid Off Is Always a Business Decision (08:52) - Building Career Security Before You Need It (10:51) - Networking Before You Need Anyone's Help (24:29) - Building Your Dream Company List Before the Job Search Starts (27:04) - Sponsor: Mammoth Growth (28:07) - Sponsor: RevenueHero (29:01) - Why AI Side Projects Give You a Real Edge in Job Interviews (34:50) - The 2026 Martech Job Market Reality Check (42:18) - The Ashby Search Hack and Why Referrals Beat Job Applications (49:58) - Hidden Job Boards and Staffing Firms Most Candidates Ignore (53:52) - Finding Martech Jobs at Stealth Startups Using VC Funding Alerts (55:31) - Why Fast-Growing Martech Agencies Are an Underrated Hiring Path Summary: This episode is a full playbook for martech and marketing ops professionals navigating 1 of the toughest job markets in years. Phil and Darrell cover what to build before you ever need a job: network, dream company lists, freelance income, AI side projects. Then it shifts to the tactical mechanics of finding roles most candidates never see. From the Ashby Google search hack to VC job boards, staffing firm pipelines, and stealth startup cold outreach, the counterintuitive moves are the most useful ones here. If you're currently employed, the early chapters are for you. If you're already searching, skip ahead.Why Getting Laid Off Is Always a Business DecisionBeing laid off in 2025 wasn't rare. It was practically routine. Amazon cut thousands. Friends pinged Darrell with news of their own layoffs while he was still processing his own. He knew what was happening across the industry. He was prepared. And then it happened anyway, and prepared turned out not to mean what he thought it meant.What comes next is something anyone who's been through it will recognize. Identity goes first. The role you've spent years building, the thing that answers "so what do you do?" at every party, just disappears overnight. Then the financial math kicks in. Darrell got 4 months of severance, which is a genuinely good outcome, and it still wasn't as much as it sounded like when he heard the number. But underneath all of it is the worst part: the replay loop. If only you'd been more visible. If only you'd taken a different project. If only you'd made that 1 relationship work. Darrell puts it plainly. Being laid off is a business decision, full stop, regardless of your performance, your visibility, or who liked you. The evidence arrived a few weeks later, when he found out that top performers across his entire organization had been cut, including his direct manager, someone who was by any measure visible, impactful, and doing everything right. When your boss gets laid off, there was nothing you could have done."If you've never been laid off before, you can't help but think it's your fault. The big feeling is: if only I had done something different, if only I was more visible, if only I had taken a different project. And that is just 100% not true. It is all business decisions."Phil's been there. He's been let go in his own career and knows exactly how the severance window tricks you. You have a little runway, so you tell yourself you'll take a month to decompress before getting back into it.That's the trap. The best advice Darrell got came from friends who had already navigated their own layoffs, and it was blunt: don't take a break. His instinct was to take a month off, maybe 2, then ease back in. The people who'd lived it told him something he didn't want to hear: it's going to take exactly that long just to get into pipelines. And while you're recovering, everyone else with the same resume and the same experience is making the same choice. You're competing against thousands of people who were also good at their jobs and also got laid off. Darrell ran full steam ahead instead. He ended up with 2 offers.How quickly you start matters more than how long you prepared. The people who figure that out in the first 48 hours have a real structural advantage over everyone else grieving on their couch.Key takeaway: Start your job search the week you're laid off. Reach out to friends who've been through it, get your materials ready, and get into pipelines immediately. Everyone else is planning to take a few weeks off first, and that gap is your only real competitive edge right now.--Building Career Security Before You Need ItMost people don't think about their next job until they lose the current 1. Full-time employment gives you a title and a salary, but career security is something you build separately, independent of any employer. You have benefits, recurring income, and a professional identity anchored to a single org chart, and the company can end any of that without notice.Here's how Phil thinks about it: an active network you can activate, something generating income outside your primary job, and a professional reputation that doesn't disappear when the org chart does. The companies that describe themselves as families are also the ones making headcount decisions when the numbers stop working. Your actual family is at home.This leads to 3 strategies Phil argues everyone in martech should be pursuing whether or not they're actively looking. First: nurture your network. Second: follow your dream companies. Third: do something outside your 9 to 5, whether freelancing, a side project, or anything with even a small amount of income attached. These aren't strategies for when you're in trouble. They're strategies for ensuring you never are. Roles in martech and marketing ops are among the first cut when companies reduce overhead. Operators who treat their current employment as permanent are more exposed than they realize."I've always been a fan of this stoic concept called the pre-mortem. In good times, imagine the worst-case scenario and work out what you'd do. I had always thought: what would happen if I lost my job? I knew I had a big network. So I wasn't as worried. But for many people, networking isn't something you do regularly."Key takeaway: Treat career security as a separate goal from job security. Map 3 building blocks: an active network, at least 1 income source outside your employer, and a professional identity that exists independent of your title. Start with whichever is weakest right now.--Networking Before You Need Anyone's HelpThe most common networking advice is to reach out when you're looking for work. Darrell's approach is the opposite: build and maintain relationships constantly, so the network already exists before you ever need it."I'm always asking for help. If you're figuring out how to integrate a tool, if you're figuring out why your database is so messed up, how are you not reaching out to people in a similar job and saying, hey, what are you doing? Because that, to me, is just a waste of time not to do that."His entry point is the Stoic concept of the pre-mortem. In good times, imagine the worst case scenario and work out what you'd do. For Darrell, that meant regularly asking himself what would happen if he lost his job tomorrow. Because he'd been building across martech and marketing ops communities for years before his layoff, the answer was already in place. He acknowledges most people don't approach it this way.What his version of ongoing networking looks like is less grand than the concep...
play-circle icon
57 MIN
214: Austin Hay: Claude Code is creating a new class of elite marketers and the mental models that make it click
APR 7, 2026
214: Austin Hay: Claude Code is creating a new class of elite marketers and the mental models that make it click
What's up everyone, today we have the pleasure of sitting down with Austin Hay, Martech, Revtech, and GTM systems advisor, AND – AI builder, writer, and ex-founder. In This Episode:(00:00) - Austin-audio (01:16) - In This Episode (01:54) - Sponsor: RevenueHero (02:48) - Sponsor: Mammoth Growth (04:09) - How Code-Driven AI Workflows Outperform Chat-Based Prompting (14:55) - How to Start Building With Claude Code When You Have No Time (19:45) - The Programming Concepts Non-Developers Need to Build With Claude Code (23:49) - How to Turn Repeating Prompts Into Automations That Run Themselves (31:11) - Sponsor: MoEngage (32:07) - Sponsor: Knak (33:37) - Why Spending All Your Time in Meetings Is a Career Liability (36:28) - Why the Best First Claude Code Project Is the Task That Already Annoys You (40:22) - Why T-Shaped Marketers With Claude Code Will Cover the Work of Entire Teams (46:27) - Why Marketing Taste Matters More Than Technical Skill in the AI Era (49:43) - How Early-Career Professionals Build Judgment When Entry-Level Work Gets Automated (53:14) - How Austin Hay Runs His Career as a Flywheel Austin Hay has spent 15 years moving between the technical and strategic ends of marketing, starting as the 4th employee at Branch, building and selling a mobile growth consultancy that was acqui-hired by mParticle, and eventually rising to VP of Growth before moving on to Ramp as Head of Martech. He later co-founded Clarify, a CRM startup he took from zero to $100K+ ARR while completing a Wharton MBA. Today he works as a fractional advisor to scaling companies on martech, revtech, and GTM systems, teaches thousands of practitioners through his Martech course at Reforge, and writes the Growth Stack Mafia newsletter on Substack.Austin spent months as a chatbot skeptic before Claude Code changed his view entirely. In this conversation, he maps the gap between using AI through a chat interface and wielding it as code in your actual environment, explains why meeting-heavy schedules are a compounding career liability, and makes the case for a new class of professional he calls the white collar super saiyan.---## How Code-Driven AI Workflows Outperform Chat-Based PromptingMost marketers use AI the same way they used Google in 2005. Open the interface, type something in, read what comes back, copy it somewhere. Austin Hay did this for months. He was not an early Claude Code adopter. He says this upfront, almost as a confession. He thought it was another chatbot.What broke him was specific. He was querying financial data at his startup, Clarify, through Runway, an FP&A platform connected to QuickBooks. Every SQL change required the same round trip: write the query in terminal, copy it to Claude, get feedback, paste it back, run it. He built a folder just to manage the back-and-forth. The model couldn't see his local files. The chat UI had upload limits. He was stuck in what he calls a world of calling and answering. Functional. But slow. And bounded in a way you eventually stop ignoring.Claude Code gave him access. When you type claude in a terminal, the model reads your actual files — the data as it lives in your repository, not a paste you copied, not a summary you wrote. It runs commands against your system, observes what happens, and acts on the result. The round trip ends. You stop relaying information and start working in the same environment. That is a different thing than a smarter chatbot.The shift combined with several unlocks arriving at once: Opus as a model, MCPs that worked reliably, a Max plan that made unlimited credits economical, and an agent architecture built around memory files and commands. All of it hit critical mass for Austin in January. He says the last 6 months felt like 3 years. You can hear in how he talks about it that he means it.The 2 chasms he had written about in his newsletter turned out to be real and distinct. Adopting AI at all is chasm 1. Crossing from chat to code is chasm 2. Most practitioners have cleared the first. Almost none have cleared the second. And the view from the other side, Austin says, is unrecognizable.> "It's this culmination of many things that I think really hit this critical mass in about January of this year."Key takeaway: Install Claude Code, open a terminal, point it at a folder with files you actually work with — SQL queries, drafts, data exports, notes — and run a real task on them. The gap between giving AI access to your environment and describing your environment through a chat window is immediate and felt, and that feeling is what changes the mental model.---## How to Start Building With Claude Code When You Have No TimeThe time problem is real. You have a 9-to-5. Your weekends disappear. Nobody at your company is running AI hackathons. "Learn the command line" is not advice you can act on between your Thursday syncs.Austin doesn't dismiss this. But he points at the part most people miss: they know step 1 (chat interface) and they see step 3 (Claude Code in terminal) and they conclude the gap is too wide. Step 2 exists. And step 2 is where everything clicks.Anthropic's rollout is layered deliberately. Chat first: ask a question, read the answer, copy the output. Cowork space second: Claude works inside a folder on your computer, local or cloud-based, and you're giving it real files to act on. Coding interface third: terminal, commands, agents. The cowork space is a distinct step with its own payoff. It's where the model stops being a question-answering machine and becomes an environment you work inside.> "Once people understand that Claude lives in a folder on your computer and you can throw stuff in that folder and have it work for you — that's the next step."When you upload documents inside a Claude project and ask it to work on them, you learn something you can't get from chat: Claude lives in a folder. It acts on what's in front of it. That sounds obvious. It does not feel obvious until you've done it. And once you feel it, the jump from cowork to terminal starts feeling like a small step forward rather than a cliff.Where this leads, eventually, is automation that runs without you. A cron job fires at 6am. A script processes your data. A workflow runs in the cloud while you're on a call or asleep. Austin maps the progression clearly: folder on your machine, then a local cron, then a cloud-deployed process that runs continuously. The people building now are building the muscle memory to get there faster. You don't have to start in the deep end. But you have to start somewhere.Key takeaway: Start in Claude's cowork space, not the terminal. Upload a folder of documents you already work with regularly — meeting notes, a newsletter draft, recurring reports, templates — and ask Claude to perform a real task on them. That interaction builds the foundational mental model before you write a single line of code.---## The Programming Concepts Non-Developers Need to Build With Claude CodeAustin has been saying "learn the command line" for a decade. That advice predates AI by years. The reason it matters now is completely different from the reason it mattered then.The 3 foundations: command line (how computers work), object orientation (how APIs work), one programming language (how the web works). You don't need to master any of them. You need to understand them. Because without that base layer, you can use the tools that exist today, but you can't evaluate what Claude does when it uses them on your behalf.> "When you have those 3 things, you can teach yourself anything."That's the real value. When you...
play-circle icon
62 MIN
213: John Whalen: The next marketing advantage is pre-testing ideas on synthetic users
MAR 31, 2026
213: John Whalen: The next marketing advantage is pre-testing ideas on synthetic users
What’s up everyone, today we have the pleasure of sitting down with Dr. John Whalen, Cognitive Scientist, Author, and Founder at Brilliant Experience.Summary: John has spent his career studying how people actually think, and his conclusion is uncomfortable for anyone who believes their marketing decisions are more rational than they are. In this episode, John explores how synthetic users built from cognitive science principles can fill the massive research gap that most teams quietly ignore, and why removing the human interviewer from the room might be the fastest way to finally hear the truth.In this Episode…(00:00) - Intro (01:13) - In This Episode (04:31) - What Are Synthetic Users and Why Do They Matter? (10:00) - How Synthetic Users Make Stakeholders Hungry for Real Human Research (15:56) - Pre-Testing on Synthetic Users: Shortcut or Smart Step? (18:53) - How to Actually Build a Synthetic User: Tools, Layers, and Agentic Systems (40:51) - Is the Average Persona Dead? Scale, Diversity, and the World Model (43:01) - Asking the Uncomfortable Questions: What AI Agents Reveal That Humans Won't (49:30) - Ending the Quant vs. Qual Debate with Statistically Relevant Qualitative Data (56:37) - Mining the 'Why' Behind Silent Behavioral Data with Synthetic Users (01:02:31) - Designing for Agent Users: The Coming Shift to Human-and-Machine-Centered Design (01:05:28) - The Happiness Question: Dogs, Nature, and Staying Analog About JohnDr. John Whalen is a Cognitive Scientist, Author, and Founder of Brilliant Experience, where he applies cognitive science principles to help organizations design products and experiences that align with how people actually think and make decisions. He’s also an educator, teaching two AI customer research courses on Maven.His work explores the intersection of human psychology and marketing, including the emerging practice of pre-testing ideas on synthetic users to give brands a faster and more informed competitive edge. He is also the author of a book on the science of designing for the human mind, bringing academic rigor to practical business challenges.How Synthetic User Research Works and When to Trust ItSynthetic user research sounds like something creepy out of a dystopian science fiction film, and John is the first to admit the terminology does nobody any favors. When asked about what synthetic users actually are and what they mean for research, he admited: if he had been on the branding team, he would have pushed hard for something like “dynamic personas” instead. The name creates unnecessary friction before the conversation even starts. And that friction matters when you’re trying to get skeptical executives or methiculous researchers to take the whole thing seriously.Under the hood, specialized AI tools simulate how a defined audience segment would respond to a question, concept, or stimulus, without recruiting, scheduling, incentivizing, or waiting on real human participants. John runs a class where he collects genuine human data first, then feeds comparable inputs into these tools to benchmark accuracy head-to-head. The results are pretty wild. AI-generated responses align with real human findings somewhere between 85% and 100% of the time on major topics and consumer needs. That is not a peer-reviewed clinical trial, and John is not pretending otherwise. But 85% alignment is enough signal to stop reflexively dismissing the method and start asking harder, more specific questions about exactly where it fits into a research stack.So what does this mean for you and your company though? Think all the decisions that currently live in a black hole of zero structured input. How many product calls, campaign concepts, and messaging pivots happen with nothing more than a conference room full of people who all read the same talking heads on LinkedIn? John argues that low cost, round-the-clock accessibility, and minimal public exposure make these tools a natural fit for precisely those moments: pressure-checking a hypothesis at 11pm, testing whether a pitch direction even makes sense before it touches a client, or deciding whether a concept deserves the time and money required for proper validation.“If these are only going to keep getting better and better, which they are, then logically, what kinds of decisions right now go completely by gut and no research, and what could we use to help us frame that?”One of the more underappreciated angles John raises is global inclusivity. Large organizations routinely test in the US and Western Europe, then extrapolate those findings to markets in Southeast Asia, Latin America, or Sub-Saharan Africa because local research budgets simply do not exist. Big nono. Synthetic personas trained on broader, more representative data could at minimum provide directional signals for those markets, making research more geographically honest without a proportional spike in spend.The early AI bias problem, where models essentially mirrored the worldview of a narrow, tech-adjacent demographic slice, was real and valid and well-documented. But training data keeps expanding, and the gap between “Silicon Valley assumption” and “what people in Nairobi or Jakarta actually think” is narrowing in ways that deserve acknowledgment.Key takeaway: Synthetic user research earns its place not as a replacement for real human data, but as a low-cost, always-available pressure valve for the enormous volume of decisions that currently happen with no research input at all, so before you dismiss it as gimmicky, ask yourself honestly how many of your last ten strategic calls were backed by anything more rigorous than internal consensus.How Synthetic Users Make Stakeholders Want More Real Human ResearchThos big hairy static research decks have a fundamental limitation that anyone who has sat through a stakeholder presentation already understands. You hand over a slide deck, someone reads it, and then three days later they have five more questions you can’t answer without going back to the field. Brutal feeling.Interrogating a Live PersonaJohn argues that synthetic users solve this problem in a surprisingly indirect way: when a stakeholder can keep interrogating a live AI persona, the conversation never closes. They start poking at the model, asking things like “would you like this?” or “why would you feel that way about that?” and somewhere in that process, something shifts. They stop treating research as a report and start treating it as a living, always-on thing.What John has observed across a half-dozen client engagements is that this interactivity makes leaders ravenous for it. His team positions synthetic user outputs as directional, explicitly not as data, closer to hypothesis generation than validation. But still cray valuable. When a stakeholder gets genuinely excited about a pattern they’re seeing in a synthetic persona, the natural next thought tends to be “if this could actually be true, we need to go test it with real humans.” The synthetic user functions as a preview of the variance you might find in the field, not a substitute for going there.“Think of this as almost a preview of what you could have with your humans. So you’re being more prepared for what might be to come, what might be the distribution of different responses.”Instant ReactionsThere’s a second use case John describes, about discovering new questions. When a stakeholder first sits down to scope a research project, they often don’t know what they’re actually asking. Spinning up a synthetic user in the room and throwing that rough, half-formed question at it live tends to produce a response the stakehold...
play-circle icon
68 MIN
212: Tobias Konitzer: The Causal AI revolution and the boomerang effect in marketing decision science
MAR 24, 2026
212: Tobias Konitzer: The Causal AI revolution and the boomerang effect in marketing decision science
Summary: Tobi challenged marketing’s fixation on prediction. He has built highly accurate LTV models, but accuracy alone does not move revenue. Marketing is intervention. Correlation shows patterns; causality tells you what happens when you pull a lever. That shift reshapes experimentation, explains why dynamic allocation can outperform static A B tests, and highlights how self learning systems can backfire or get stuck in local maxima. It also fuels his skepticism of unleashing agentic AI on historical data without a causal layer. If you want to change outcomes instead of forecast them, your systems need to understand levers and log decisions you can actually audit.(00:00) - Intro (01:22) - In This Episode (04:07) - Why Predictive Models Fail Without Causal Inference (09:49) - How to Validate Causal Impact on Customer Lifetime Value (13:04) - Reducing Uncertainty Around Causal Effects by Optimizing Levers, Not Labels (17:01) - Why Dynamic Allocation Works Better Than Fixed Horizon A B Testing (31:54) - The Boomerang Effect and Why Uninformed AI Sabotages Early Results (40:15) - Escaping Local Maxima and The Failure of Randomly Initialized Decisioning (44:04) - Why Agentic AI Trained on Data Warehouse Correlations Reinforces Bias (49:00) - The Power of Composable Decisioning (53:06) - How Machine Decisioning Transcends Marketing (01:01:41) - Why Clear Priority Hierarchies Improve Executive Decision Making About TobiasTobias Konitzer, PhD is VP of AI at GrowthLoop, where he’s chasing closed-loop marketing powered by reinforcement learning, causality, and agentic systems. He’s spent the past decade focused on one core problem: moving beyond prediction to actually influencing outcomes.Previously, Tobi was Chief Innovation Officer at Fenix Commerce, helping major eCommerce brands modernize checkout and delivery with machine learning. He also founded Ocurate, a venture-backed startup that predicted customer lifetime value to optimize ad bidding in real time, raising $5.5M and scaling to $500K+ ARR before its acquisition. Earlier, he co-founded PredictWise, building psychographic and behavioral targeting models that drove over $2M in revenue.Tobi earned his PhD in Computational Social Science from Stanford and worked at Facebook Research on large-scale ML and bias correction. Originally from Germany and based in the Bay Area since 2013, he writes frequently about causal thinking, machine decisioning, and the future of marketing.Why Predictive Models Fail Without Causal InferencePrediction dominates most marketing roadmaps. Teams invest months refining churn models, tightening confidence intervals, and debating which threshold deserves a campaign. Tobi built an entire company on that logic. His team produced highly accurate lifetime value predictions using deep learning and granular event data. The forecasts were sharp. The lift curves were clean. Buyers were impressed.Then lifecycle marketers asked a more uncomfortable question: what action should follow the score?A predictive model encodes the current trajectory of a customer under existing policies. It describes what will likely happen if nothing changes. Marketing changes things constantly. The moment you intervene, you alter the system that generated the prediction. The forecast reflects yesterday’s conditions, not tomorrow’s strategy.> “Prediction tells you the future if you do nothing. Causation tells you how to change it.”Consider the Prediction Trap.On the left, the status quo labels a person as high churn risk. The function is observation. The outcome is a description of what happens if you leave the system untouched. On the right, a lever gets pulled. The function is intervention. The outcome is directional change.That shift in function changes how you work.Prediction thinking centers on segmentation:Who is likely to churn?Who is likely to buy?Who looks like high LTV?Causal thinking centers on levers:Which incentive reduces churn?Which sequence increases repeat purchase?Which offer raises lifetime value incrementally?Tobi often uses an LTV example to expose the trap. Suppose high LTV customers frequently viewed a specific product early in their journey. A team might redesign the onboarding flow to feature that product more aggressively. The correlation looks persuasive. The causal effect remains unknown.Several alternative explanations could drive the pattern:The product may correlate with a specific acquisition channel.The product may have been highlighted during a limited campaign.The product view may signal prior brand familiarity.Only an intervention test can estimate incremental impact. Correlation can guide hypothesis generation, but it cannot validate the lever itself.Tobi also highlights a deeper issue. Acting on predictions introduces compounding uncertainty across multiple layers:The predictive model carries statistical variance.The translation from model features to campaign strategy introduces interpretation bias.The experiment introduces sampling error.Execution introduces operational noise.Each layer adds variability. When teams treat prediction accuracy as the goal, they lose visibility into where uncertainty enters the system. When teams focus on intervention impact, they concentrate measurement on the lever that drives revenue.Boardrooms already operate in causal language. Incremental ROI is causal. Budget allocation is causal. Executives care about what caused growth, not which segment looked promising in a dashboard. Prediction can inform prioritization. Causal inference determines what to scale.If you want to move in that direction, adjust your operating model:Start every initiative with a controllable lever.Define the action before defining the segment.Design experiments that isolate the incremental effect of that lever.Randomized or adaptive allocation both estimate causal lift.Report impact in revenue, retention, or contribution margin.Tie every experiment to a business outcome.Document assumptions and uncertainty.Build institutional memory around what caused change.Prediction remains useful. Intervention drives growth. Teams that understand that distinction build systems that learn through action instead of watching the future unfold from the sidelines.Key takeaway: Anchor your marketing engine in causal experiments. For every predictive score, define the specific action it informs, test that action against a control, and quantify incremental lift tied directly to revenue or retention. Replace segment rankings with lever performance dashboards that show effect size, confidence, and business impact. When every campaign answers the question “What did this intervention cause?” your team shifts from observing trajectories to shaping them.How to Validate Causal Impact on Customer Lifetime ValueMost teams treat high LTV segments as proof of where to spend. The model ranks customers. The top decile looks profitable. Budget flows upward. Tobi described asking the head of CRM at a billion dollar outdoor brand what he does when a model predicts someone will be high LTV. The answer came instantly: Spend more on them, no?That instinct feels responsible. It also confuses observation with intervention. Introducing the high LTV Fallacy:On the right side of the chart, you see a dense cluster labeled high LTV customers. Revenue increases with marketing spend. The correlation line slopes upward. It looks clean and convincing. They were going to buy anyway. That cluster may represent customers with higher income, stronger brand affinit...
play-circle icon
64 MIN
211: Jenna Kellner: Overcoming frankenstacks and AI uncertainty with first principles and business judgement
MAR 17, 2026
211: Jenna Kellner: Overcoming frankenstacks and AI uncertainty with first principles and business judgement
What’s up everyone, today we have the pleasure of chatting with Jenna Kellner, VP Marketing at Workleap.(00:00) - Intro (01:14) - In This Episode (04:30) - How to Manage Marketing Tech Debt During Rapid Growth (10:10) - How to Prioritize RevOps Tech Debt Without Perfect ROI Models (14:23) - Reasoning Through Broken Systems and Imperfect Data (19:23) - How High Performers Progress Anyway (24:28) - How to Build Confidence With AI Through Small Experiments (33:06) - How to Use Exit Planning and Cost Benefit Analysis for AI Tool Selection (35:57) - First principles matter more than tools (38:59) - Why Staying Close to Execution Improves Marketing Leadership (45:13) - Why Critical Thinking Skills Drive Marketing Career Growth (49:33) - How to Build Business Judgment in Technical Marketing Roles (53:03) - Why Confidence Without Humility is Dangerous (55:47) - How Revenue Leaders Prioritize Daily Energy (59:49) - Growing up (01:01:10) - Book rec Summary: Jenna is a VP of marketing that can talk about the weeds of messy systems, uncertain decisions, and personal growth. You can’t hide from it, every company accumulates tech debt as teams rush to hit revenue targets. She frames tech debt as a leadership responsibility and urges executives to reinvest in core systems when patchwork begins to outweigh building. If leadership doesn’t get it, the best way to prioritize it is to shape it as an opportunity cost and lost leverage that will drain revenue the longer we wait. In the face of AI uncertainty, she argues that judgment compounds faster than technical knowledge, and that the marketers who become indispensable blend business awareness, proximity to execution, and decisive action grounded in humility.About JennaJenna Kellner is Vice President of Marketing at Workleap and a revenue-focused marketing leader who has spent more than a decade building marketing teams and scaling companies. She brings experience across Enterprise, SMB, D2C, SaaS, two-sided marketplaces, venture studios, and other high-growth environments.Her career spans senior leadership roles at Minerva, On Deck, RBCx, and Ownr, where she led marketing, growth, and revenue functions inside complex, evolving organizations. At RBCx, she served as Chief Growth Officer for Ampli and directed marketing and growth initiatives within a large financial institution setting. She has also co-founded communities such as GrowthToronto and Little Traders, reflecting her commitment to building networks and businesses in parallel.Jenna operates with a strong sense of ownership and accountability, grounded in her belief that every challenge ultimately becomes her responsibility to solve. Recognized as a WXN Top 100 Women in Canada, she focuses on developing high-performing teams that connect strategy to execution and translate marketing into measurable revenue impact.The Frankenstein Reality of Managing Tech Debt: How to Manage Marketing Tech Debt During Rapid GrowthYou know it.. Most marketers are operating inside half-connected systems. No company has a pristine, perfectly synchronized tech stack. Even if they think they do, it doesn’t last. Growth creates pressure, and pressure produces shortcuts. Jenna has seen the same cycle in startups and enterprise environments. In the early days, teams build whatever gets the job done. They start in spreadsheets, layer on point solutions, wire tools together with lightweight integrations, and move fast because revenue matters more than architecture.Those early decisions never disappear. They compound. Years later, larger organizations inherit layers of systems that were added at different stages of maturity. Tools do not scale in sync. One platform gets upgraded. Another stays frozen because a team depends on it. Reporting becomes an exercise in orchestration. Jenna recalls walking into an organization where a sales leader pulled her weekly report from eight separate tools. That routine consumed time, drained energy, and normalized operational friction.“You have to Frankenstein your way through them to get the answers you need.”That sentence captures the daily reality inside many marketing and revenue teams. Quarter-end reporting still happens. Board decks still go out. The numbers get assembled through exports, CSV files, manual joins, and late-night reconciliation. Leadership often tolerates the strain because revenue continues to land. But the cost isn’t super visible:Reporting cycles stretch longer each quarter.Forecast confidence erodes.Team morale dips as manual work expands.Strategic decisions rely on partial or inconsistent data.So how do we get out of this mess? Jenna views this as a leadership obligation. Someone has to decide that cleaning house earns priority alongside pipeline generation. She describes working with a founder who paused other initiatives to repair core systems. The work moved slowly. It required budget discipline and uncomfortable trade-offs. It rebuilt trust in data and freed leaders from cobbled-together dashboards. She compares the stack to a house. Repairs never end, but neglect guarantees structural damage. Leaders choose whether maintenance becomes routine or deferred risk.Key takeaway: Treat marketing and sales tech debt as a leadership responsibility, not an ops inconvenience. Schedule deliberate cleanup cycles, secure executive buy-in early, and protect time and budget to rebuild core systems before the drag on revenue, morale, and reporting compounds beyond control.Prioritizing RevOps Tech Debt Without Perfect ROI ModelsJust get buy-in to fix all of our tech debt… myeah… sounds great. Good luck convincing your leadership team who’s off chasing the next AI tool they just read about on LinkedIn. Just assign a dollar figure to it, doesn’t have to be perfect, just guestimate it. Someone is building a report by hopping across eight tools, copying fields, reconciling numbers. You can measure the hours. You can attach a salary. You still miss the real cost.Jenna takes a different approach. She’s not a fan of squeezing every system fix into an artificial ROI model. She focuses on the role RevOps plays in revenue creation. She says it directly:“The job is to enable sales and marketing to find patterns, to hunt better, to run better campaigns and plays, to drive stronger revenue.”When RevOps becomes a reporting service desk, capacity shrinks. The team spends its energy on maintenance rather than momentum. The opportunity cost compounds quietly. High leverage work stalls, including:Designing sharper segmentation models.Identifying conversion bottlenecks across funnel stages.Equipping sales with data driven plays that improve win rates.You feel the drag in slower experiments and reactive decision making. Pipeline velocity flattens. Leadership wonders why growth feels harder than it should.The urge to quantify every hour saved can trap teams in defensive mode. You start arguing over whether saving ten hours per week justifies a cleanup project. You try to forecast the dollar value of future pattern recognition. That debate rarely captures the structural risk of lagging systems. Jenna frames it as a leadership judgment call grounded in timing and context. If headwinds are rising, if competitors are shipping faster, if your team spends more time patching than building, the signal is strong enough.She points to industries that invested early in overhauling core systems. Airlines that modernized their tech stack gained operat...
play-circle icon
62 MIN