Humans of Martech

What's up everyone, today we have the pleasure of sitting down with Aditya Vempaty, VP of Marketing at Coram AI.(00:00) - Intro (01:07) - In This Episode (05:05) - Why Expansion Revenue Beats New Logos When Channels Are Saturated (06:07) - Why Customer Empathy Means Knowing What Gets Your Buyer Promoted (12:38) - How to Tell If Your Case Study Makes the Customer the Hero (18:16) - Why Single Channel Attribution Hides the Journey That Closed the Deal (22:00) - How to Find Real Customer Problems by Paying for 30 Minute Interviews (30:29) - The 3 Levels That Connect Marketing Strategy to Tactical Execution (36:32) - Why Implementation Speed Is the Real Answer to a Migration Objection (42:12) - The ABM Play You Can Build From Your Closed Won List Today (48:46) - How Marketing Leaders Get a Team to Actually Adopt an AI Tool (53:26) - How Marketing Leaders Decide What Deserves Their Energy Summary: Aditya has built marketing functions and named categories from nothing at Synthego, Amplitude and Nutanix, and he shows up here to argue that the loud top of funnel work is now the cheaper half of the job. He takes apart the make your customer the hero cliche with a test you can run on any case study in about 4 seconds, then explains why he pays customers $100 for 30 minutes before he will even look at the product he was hired to market. There's a story about harvesting a competitor's free tier badge off customer websites, a telco onboarded in 6 weeks, and a VP of marketing spending 15 minutes making a poster so his team would actually use AI. He also has a very short answer for what your ChatGPT persona document is worth. Stick around for the part where 95% product parity turns into the only argument that reliably wins a migration deal.About Aditya VempatyAditya Vempaty is the VP of Marketing at Coram AI, an AI physical security platform running across more than 1,500 locations. Before that he spent 3 years as VP of Marketing at MoEngage, where the company grew from $58M to $100M in ARR. Earlier in his career he built the marketing function and named the category at Synthego, Amplitude and Nutanix, work that spans 2 IPOs and several unicorns.He also invests as an angel, mentors at First Round Capital, and is known for 2 rules he repeats often: market the problem first, and distribution is the strategy.Why Expansion Revenue Beats New Logos When Channels Are SaturatedEvery marketing team has a number on the board for new logos. Far fewer have one for what happens to a customer 6 months after the contract gets signed. That made sense when acquisition was cheap and a paid dollar reliably bought you a lead. Channels are crowded now, budgets are flat, and the math has moved.Aditya has spent his career at the loud end of marketing. He helped name the product analytics category at Amplitude. He helped define the agentic customer engagement platform at MoEngage. Those are top-of-funnel plays, the kind where you plant a flag and get the industry to repeat your words back to you. So it's a fair question why the category creation guy now spends his time talking about heroes, lifecycle and retention.His answer is arithmetic.For a marketer defending a budget, the second half of that sentence matters more than the first. Cheaper is the obvious part. Easier to show impact is the part that should change how you plan. Every acquisition attribution fight you've ever lost, where the CFO wants to know which of your 6 channels made the lead buy, goes away when the account is already in the building and you can see exactly what they did and didn't adopt.The shape of the products matters too. Amplitude and MoEngage are both multi-product suites. Customers land on one thing, get value, and then expand into the rest. So the second, third and fourth sale are already sitting inside your customer base, and nobody has to be convinced you exist. Aditya points to HubSpot's version of this, where the funnel is a loop rather than a line, and treats the loop as the actual revenue machine instead of a diagram in a deck.Here is the uncomfortable version. Most B2B marketing orgs are staffed and measured around the most expensive, least provable part of the job. If expansion is where the margin actually is, the demand gen team should carry a retention or adoption number, and most demand gen teams would fight you hard on that.Key takeaway: Pull the last 4 quarters of revenue and split it into new logo, expansion and renewal. If expansion is the bigger line and nobody in marketing carries a number against it, claim it before the next planning cycle starts. Pick the one product line your existing customers adopt second and build the campaign for that.Why Customer Empathy Means Knowing What Gets Your Buyer PromotedCustomer empathy is the most repeated phrase in B2B marketing and the least examined one. It shows up in every kickoff deck, every messaging workshop, every values page. Ask what it produced and you usually get a persona document nobody has opened since it was made.Aditya spent years on the vendor side of exactly this, at 2 companies that sit in the middle of the funnel where marketing ops and lifecycle people live. He saw how the sausage gets made, and he came out of it with a low opinion of the word.What replaced it is much more specific and much more useful. Sitting inside those companies taught him that the thing worth understanding about a buyer is their job justification. How does this person prove they were worth their salary this year? How do they get promoted? Your product either helps them say that sentence out loud or it does not.At Amplitude the answer was retention. Product managers in B2C couldn't track what they were doing and couldn't justify their own existence and investment. The industry was obsessed with mobile acquisition at the time, so the question that actually kept a PM up at night was how to keep the users they had already paid for and how to show the product was giving those users value. Amplitude built the whole marketing motion around that metric because that metric was the PM's career.At MoEngage the pain had moved. Retention was table stakes by then and everyone was already on mobile and web. The problem had become execution across channels, and the version Aditya describes is painfully familiar to anyone who has run campaigns at a big company. You have every channel available to you and no ability to say what you actually did. He describes marketers who legitimately can't come back and report which campaign hit, where it hit, and which users it reached across the full cycle. Teams operated as channel owners rather than as one coordinated effort.Then he gives the number that makes it real. One customer took 6 weeks to launch a campaign, because getting the segments required 20 people on a SQL query team pulling across 5 databases. 6 weeks. For a campaign. That's the daily texture of the job for the person you're selling to, and no amount of empathy language on a website touches it.Here is the payoff. When your product lets someone explain their value in a simple way that other people understand, they stop being a customer and start being an advocate. As Aditya says, they will rave about you because you made their life easier and their job explainable.Most vendor positioning is aimed one level too high. It addresses the company's pain, churn and efficiency and cost, while the person signing the order form has a smaller and more urgent problem, which is that they can't prove what they did last quarter. That mismatch is why so much martech messaging reads as true and lands as nothing.Key takeaway: Write down the exact sentence your champion would say in ...

What's up everyone, today we have the pleasure of sitting down with Mary Keough, Fractional Demand Gen for B2B at DemandLoops.(00:00) - Intro (01:12) - In This Episode (04:30) - How to Write LinkedIn Posts That Hit a Nerve Without AI (06:39) - How to Run an Honest Goal Setting Conversation With Your Founder (14:46) - Why Marketing Always Catches the Scope Creep at Startups (18:39) - How New Marketing VPs Establish Credibility in Their First Month (28:30) - How Women in Marketing Leadership Get Out of the Marketing Girl Box (33:49) - How to Tell if a Founder Who Doesn't Get Marketing Will Trust You (36:54) - What a VP of Marketing Job Description Should Actually Say (39:12) - When to Fight for a Broken Marketing Role and When to Leave (44:43) - Why Fractional Marketing Leadership Works as a Stopgap and Fails Long Term (49:53) - How to Vet a Marketing Role by Talking to People Who Left (53:17) - How to Use a Family Value System to Decide What Deserves Your Energy Summary: Mary wrote a LinkedIn post listing every fear a senior marketer has about taking a VP of Marketing job, and it hit a nerve loud enough to become this entire episode. We take the fears apart one at a time: the goalpost that moves the week after your team clears it, the executive dinner that quietly becomes 6 more events, the launch strategy your boss never opens. Then we build the other side of it, including the 3 sentence job description she'd sign tomorrow and the written SLA that stops sales from eating 4 days of your designer's week. She also explains why the fractional model everyone is rushing toward is a stopgap, and why her own contracts are designed to end. Stick around for the performance review where nothing went wrong and it still nearly took her out.About Mary KeoughMary Keough is a fractional demand gen marketer at DemandLoops, where she builds B2B demand programs that are designed from day one to be handed back to a permanent hire. She has spent 15 years across B2B SaaS and industrial manufacturing marketing, most recently as Director of Demand Generation at CoLab Software, and before that as Head of Marketing at Map My Customers and Senior Marketing Strategist at Gorilla 76.Her roots are in industrial and manufacturing demand gen, a niche she cut her teeth on at Spraying Systems Co. and still speaks about at events like the Industrial Marketing Summit. She's built an audience of roughly 30,000 on LinkedIn writing candid, fundamentals-first posts, and she co-hosts the Purposeful Marketing Podcast.How to Write LinkedIn Posts That Hit a Nerve Without AIYou can spot them before you finish the first line. Same hook shape, same clipped one-line paragraphs stacked into a wall, same closing question nobody answers. B2B LinkedIn has gotten very good at producing posts that read like posts, and the feed is worse for it.Then something like Mary's shows up. Her post about VP of Marketing roles was a stacked list of fears, one after another, written against the line founders keep repeating about not being able to find good candidates. It went around because a lot of senior marketers had been carrying those fears for years without the words for them. That feeling of reading your own thought in someone else's sentence is rare, and it's almost never something a hook formula produces.Originality is the entire filter for her, and applying it kills most content calendars on contact. Mary doesn't pre-plan posts. An idea sits with her for a while, usually something that's been bothering her that she can't quite name yet. Then a conversation does it: a marketer venting, a thread she can't scroll past, a call with a potential client. Something tips her over the edge and the post writes itself.Not a single one of her posts has been written with AI. She says it flatly, and you can tell from the drafts: the scar tissue is right there on the page, and the sentences go where an editor would have smoothed them. The cost of that is inconsistency. She posts when she has something, and only then. The return is that when she does post, it carries the one thing a language model cannot manufacture, which is the specific irritation of a person who has actually lived the problem.The volume play is finished. When any competitor can generate a competent, on-brand, keyword-aligned post in 30 seconds, competence stops being a differentiator and originality becomes the only moat left. Most B2B content operations are structurally incapable of producing it, because they're built to hit a cadence rather than to publish the thing only their company could say.Key takeaway: Run every idea on your content calendar through Mary's filter before it gets assigned: if 10 other companies in your category could publish the same piece, kill it. Replace the slots you clear with a standing prompt to your team, asking what has annoyed them at work this month that they can't fully explain yet. Those are the posts that travel.How to Run an Honest Goal Setting Conversation With Your FounderMarketing targets in most startups get set the way weather forecasts get set in a bad novel, which is to say somebody decides what would sound good and then everyone agrees to act surprised when it doesn't happen. The CMO needs a board-friendly story. The investor update needs an AI angle. Almost none of it starts from historical numbers, and the marketing leader gets handed the result and asked to commit.Mary's diagnosis starts a layer above the number. Companies keep saying they need a great VP of Marketing, an awesome VP of Marketing, an amazing director of demand gen. Very few of them are willing to do the work that makes a great one want the job. And the work starts with a company vision that has actual business goals underneath it.The version she wants runs down a ladder. There's the grand vision, the thing that got the company funded in the first place. Under it sits a 1-year and a 3-year picture of what changes in the market if the company wins. Under that sit the business goals that get you there, segmented by department, so product, marketing, and sales each know what they own.She walks through it with an attribution example, mostly because it's easy and partly because she can't resist. Say the company vision is to get founders, CEOs, and marketers to start caring about attribution. Fine. Now what does product build in the next 12 months to make that true? What does marketing publish? What does sales say on calls? Every function can answer that question, and the answers can be checked against each other.That ladder is almost completely gone from the startups she sees. What's left is the revenue multiple, which is a wish, and a set of quarterly targets that get reverse-engineered from it. Marketing is usually the first function asked to sign for the gap.The line that stuck with me is her framing of the whole discipline: everything about marketing is simple and fundamentals driven, and simple has nothing to do with easy. The hard part isn't figuring out what to do. The hard part is that you're doing it inside politically driven motivations, shifting strategies, and goalposts that move whenever the board asks a new question.How to Push Back When Product Wants to Change the ICPAnyone who has worked at a startup knows the move. You spend a year building a content engine around marketers, the quarter goes well, product decides the real opportunity is salespeople, and suddenly your entire library is pointed at the wrong buyer. Product changes a few things in the roadmap. Marketing starts over, and the results of that restart won't show up for 12 months.Mary's honest about the limits here. Preventing the shift is difficult, so you mitigate it...

What's up everyone, today we have the pleasure of sitting down with Julie Beynon, Head of Analytics at Augment Code.(00:00) - Intro (01:07) - In This Episode (04:13) - Breaking Into Data Without A Computer Science Background (06:05) - Why AI Made Building Cheap But Maintenance Expensive (09:25) - How To Push Back On AI Projects Without Killing Momentum (12:28) - Building AI Agents That Multiply A Two Person Data Team (16:29) - When Not To Reach For AI At Work (22:23) - Running A Lean Data Team As A Force Multiplier (27:28) - The Spreadsheet Test For Keeping Your Data Stack Simple (31:49) - How To Prove The Value Of Invisible Data Work (39:14) - Why Data Analytics Is Becoming GTM Operations (41:47) - What Part Of The Data Analyst Job AI Is Replacing (47:15) - The Data Skills AI Can't Replace (52:07) - How To Decide What Deserves Your Energy Summary: Julie Beynon came into data sideways from content marketing, got cut down to 2 words by a CEO, and turned that into a 15-year career running lean data teams. In this episode she breaks down how she cloned her best analyst into an AI agent named JimBot, why she pushes back on AI projects without ever saying no, and how she gets companies to fund the invisible foundation work nobody claps for. She makes the case that AI knocked down the SQL wall, so the real bottleneck moved to the data model underneath, and that simple is now the hardest skill in the room. There's a spreadsheet test, a team of 2 that runs like 10, and a surprisingly hopeful take on AI making us more human. Stick around for the part where she explains why the boring option takes the most nerve.About Julie BeynonJulie Beynon is the Head of Analytics at Augment Code, an AI coding assistant company, where she runs a lean data team and builds AI agents that let the whole company self-serve trusted answers. She's spent roughly 15 years in data and go-to-market analytics, previously leading data at Census and analytics at Clearbit, with earlier stops at Customer.io and other startups.She's self-taught and came into data sideways from content marketing, with no computer science background. Alongside the day job she writes a series of short essays on data, AI, and the discipline of knowing when not to reach for a tool.Breaking Into Data Without A Computer Science BackgroundMost people assume the path into data analytics runs through a computer science degree or at least a few years buried in SQL. Julie's route looked nothing like that. She started as a content marketer, and by her own account she was bad at it. Her CEO once edited a piece of her writing down to 2 words.That kind of feedback breaks a lot of people. It did the opposite for her. Getting cut down that hard built a habit of raising her hand for whatever nobody else wanted to do, and the thing nobody wanted to touch was data. The real turn came at Customer.io, where a new tool called dbt showed up and someone offered to train her on it. She figured saying yes would be silly to pass up, and within a few sessions the whole job changed shape.The moment she describes is the one every self-taught analyst recognizes. You take a pile of raw rows nobody trusts, run it through a model, and suddenly you're holding something a whole company can use. She calls it realizing what power she had just yielded. The intuition that makes her good now got built out of the failures that came first, then an open door she was willing to walk through. Coming at data from content rather than engineering is why she reads the business side so well, because she learned the questions before she learned the syntax.Key takeaway: Volunteer for the messy, unowned work on your team, especially the data nobody wants to clean. Pair it with one modern tool you can learn hands-on, like dbt, and get a colleague to walk you through a real project rather than a tutorial. The reps you build on work nobody else will do become the skill set that's hardest to replace later.Why AI Made Building Cheap But Maintenance ExpensiveAI has made it trivial to spin something up. A dashboard, a workflow, a scrappy internal tool, all of it now takes an afternoon and a few prompts. The problem is that the fun part and the expensive part were never the same part. Julie's been making this argument since before AI showed up, in a build versus buy post she wrote 5 years ago, and the tooling change only sharpened it.Here's the trap she watches teams fall into. Someone builds a slick dashboard because they can, everyone's impressed, and then 6 months later sales walks up asking why a number moved. There's data drift, nobody remembers how the thing was wired, and the person who built it isn't the one who has to answer for it. She's the one who answers for it. So before anything gets built on her watch, she runs it through a short set of questions:Is this mission-critical, or just fun to make?, Who owns it and who maintains it when it breaks?, Is there an off-the-shelf tool that costs less per month than the tokens it takes to build and run this?That last one lands hard. You can burn $1,000 building something that replaces a tool costing $5 a month, and feel productive the whole time. The cheap build is a real cost hiding as a win. Maintenance never got cheaper, which means the discipline that matters now is refusing to build the thing you're perfectly capable of building.Key takeaway: Before you build anything with AI, price the maintenance, not the build. Ask who owns it in 6 months, whether it's mission-critical, and whether a paid tool would cost less than the tokens you'll spend building and running your own version. If the honest answer is that you're building it because it's fun, buy the tool instead.How To Push Back On AI Projects Without Killing MomentumOps and data people carry a reputation as the team that says no. Every shiny new tool, every "we should build this," runs into someone whose job is to point out that you already own 2 things that do the same job. That instinct matters more than ever now that anyone can build anything. It also curdles fast into being the person nobody wants to bring ideas to.Julie's answer is to almost never say no at the door. There's a real constraint underneath her patience, since on the data side you have an actual duty to protect the data and the security around it, so some requests genuinely can't fly. Outside of that, she lets people run.That quote comes from a specific win. One of her engineers built a proof-of-concept dashboard for a new product. It worked. Instead of telling him to stop, she treated it as a starting pad and let him take the first pass as far as he wanted. AI helped him productize and visualize what he was thinking. Then, when the question became how to make it sustainable, she stepped in and rebuilt it as a stable dashboard in their BI tool with observability and role-based access control baked in. The engineer knew every data point and how it was tracked, so she pulled the context straight out of his code instead of extracting it from him in a meeting. She calls it one of the most productive data cycles she's had. Letting someone go a few steps before you take the wheel turns pushback into a handoff, and the person feels seen instead of shut down.Key takeaway: When someone brings you an AI-built prototype, resist the reflex to kill it. Let them take the first pass all the way, then offer to productize it yourself, pulling the logic and context out of their code rather than dragging it out of a meeting. Reserve your hard no for genuine security and data-protection lines, and treat everything else as a draft you can finish.Building AI Agents That Multiply A Two Pers...

What's up everyone, today we have the pleasure of sitting down with Stéphane Hamel, Founder and Product Architect at MANTIS.(00:00) - Intro (01:07) - In This Episode (04:07) - How To Audit Which Trackers Are Firing On Your Website (07:00) - Why Nobody On Your Team Owns The Tags Firing On Your Site (11:22) - Why Your Consent Banner Does Not Match What Your Site Actually Does (16:45) - Does Server Side Tagging Actually Improve Privacy Governance (22:30) - Why Loading A Third Party Script Is Already A Privacy Risk (27:30) - What Happens When You File A Privacy Complaint In Canada (36:42) - Why AI Output Is Useless Without Domain Expertise (41:58) - Is AI Removing The Training Path For Junior Marketers (44:16) - When Vibe Coding Works And When It Falls Apart (47:56) - Why Marketing And IT Still Fight Over Who Maintains The Stack (52:02) - How To Decide Which Projects Deserve Your Energy Summary: Stéphane Hamel built the first web analytics QA tool back in 2006, watched an ad blocker quietly borrow his logic, and spent the next 20 years learning that tracking got harder to see every year while the industry got better at documenting it. Now he's building MANTIS, a privacy observability platform that watches what a website actually does instead of what its policy claims. Along the way he audited his own credit bureau account after a breach, found trackers from companies that no longer exist sitting on the page displaying his credit file, and spent 2 years fighting to get them removed. He also coined the term vegetative AI, sold his house and furniture after one good vacation in the Rockies, and will tell you your consent banner is a receipt for a transaction nobody actually agreed to. Wait until you hear what a third party script collects before it fires a single tag.About Stéphane HamelStéphane Hamel is the founder and product architect of MANTIS, a privacy observability platform built to show what a website actually does at runtime rather than what its policy claims. He's spent 35 years across the full arc of digital analytics, building WASP in 2006 as the first web analytics quality assurance tool, publishing the Digital Analytics Maturity Model in 2009, and creating Da Vinci Tools, which was later acquired by Supermetrics.He teaches MBA and EMBA students at Université Laval and advises privacy tech startups including Supermetrics, Caden, and Masthead Data. He's currently writing his first book on digital analytics concepts, and having been a victim of 2 of Canada's largest data breaches, he treats privacy as a trust problem rather than a legal one.How To Audit Which Trackers Are Firing On Your WebsiteOpen the network tab on your own company's homepage and count the outbound requests. Most marketers who try this land somewhere between 40 and 100 calls going to domains nobody on the current team approved. In 2006 that number was small enough to check by hand, and the only question worth asking was whether your analytics tag fired on the right page at the right moment.That's the question Stéphane built WASP to answer. He was on the technical side back then, implementing trackers on client websites, and nobody in the room was talking about privacy or where any of this data ended up. The tool checked whether tags fired when they were supposed to and whether they collected the right information. It was quality assurance work, and it was the first tool of its kind.That shift wasn't academic. Stéphane got hit by data leaks more than once, watched fraud follow, and spent 35 years consulting and teaching through every generation of the tracking stack. MANTIS is what came out the other side, and it asks a very different question than WASP did.The new question has 3 parts:What is actually loading on this website in terms of trackers, Whether any of those trackers fire without consent, What kind of data each one collects once it doesThe hard part is the chain. Websites include third party scripts that load other scripts, a pattern Stéphane calls piggybacking, and every hop moves further from anything a marketer ever approved. Fingerprinting rides along in the same traffic. By the time a script 4 hops deep does something it shouldn't, nobody on the marketing team can name what triggered it or say where the data went.So MANTIS is built for people who don't read network waterfalls for a living. Marketers, decision makers, privacy specialists, and the technical folks stuck doing QA on tags all need to see the same picture, and right now they each see a different slice of it. The industry spent 20 years getting very good at deploying tags and almost no time getting good at watching them. That gap is why most privacy programs audit documents instead of traffic, and why the documents keep passing while the traffic keeps failing.Key takeaway: Run your own homepage through a network inspector before you click anything on the consent banner, and write down every third party domain that already received a request. Compare that list against the vendor list your consent management platform declares. Any domain in the first list that's missing from the second is a gap you own right now.Why Nobody On Your Team Owns The Tags Firing On Your SiteAnyone can inspect a page now. Right click, open the debug console, watch the calls go out live. That was exotic in 2006 and it's table stakes today, which raises a reasonable objection to the whole category of tag surfacing tools. If the browser already shows you everything, what's left to build?Stéphane's answer is that the console shows you the calls and tells you nothing about who authorized them. Working with technical people for 35 years, he's watched the gap widen. The traffic is visible. The accountability is gone.There's a story from the WASP years he still turns over. Someone messaged him saying the tool should block the tags it found. He said no, that's not the purpose, the purpose is quality assurance. Shortly after, ad blockers took off, and he found some of his own logic sitting inside one of the very first ones. He had no way to prove it and no means to enforce anything. He was one guy solving his own problem, and the industry took the idea somewhere he hadn't intended.20 years on, the reason tags go unowned has less to do with technology than with how many people handle a single pixel on its way to production. Stéphane walks through the cast:The marketer, who asks for something and moves on, The software engineer, or the data engineer, depending on which fancy name the org uses this year, Legal, who reviews the words and doesn't get the technical constraints, The consent management platform vendor, whose position is that they provide a tool and don't provide legal adviceThat's 4 groups, and not one of them can describe the whole system. That's before you count the agency your marketing lead handed tag manager access to, the one that said trust us, we know what we're doing, we're just going to put a tag on your website. Then somebody runs an audit 2 years later and finds tags firing that nobody recognizes.Here's the part that should bother you more than it probably does. Every single tag is a privacy risk and a security risk at the same time. The moment you put third party JavaScript on your site, you've given someone else write access to your users' browsers, and that script can change tomorrow without telling you. It might start recording keystrokes. It might start fingerprinting. Stéphane notes that vendors coming out of the US tend to be particularly greedy about collection, and none of that requires a new contract or a new conversation.What MANTIS does about it is draw a timeline. You got consent at t...

What's up everyone, today we have the pleasure of sitting down with Kelsie Dube, Director of Marketing Operations and Automation at Unanet.(00:00) - Intro (01:09) - In This Episode (05:31) - Why New Marketing Ops Leaders Should Audit Before They Act (10:09) - How to Run a Marketing Ops Audit When You Join a Company (16:04) - How to Balance a Full Audit Against Your Boss's Priorities (19:00) - How to Spot a Process Problem Disguised as a Tool Problem (23:41) - How to Surface Shadow Processes and Duplicate Tools in an Audit (31:08) - How to Choose a New Martech Tool With a Tiger Team of Power Users (35:30) - How to Turn a Marketing Ops Audit Into a Prioritized Roadmap (41:20) - How to Align Your Team on a Measurement Philosophy (44:22) - What Happens to Junior Marketing Ops When AI Eats the Entry-Level Work (49:26) - How to Turn Marketing Ops From Ticket-Takers Into Business Partners (52:40) - How to Use One Interview Question to Screen for Team Fit (56:57) - How a Marketing Ops Leader Decides What Deserves Her Energy Summary: Kelsie Dube joined Unanet and did the one thing most new ops leaders are too nervous to do: nothing, at least at first. In this episode she breaks down the 30-day audit she runs before changing a single tool, how she sorts 30-plus problems into big rocks, quick wins, and parked FY27 headaches, and why she'd rather build a "digital twin" to argue with than buy another platform. She gets into the tiger-team playbook that makes tool replacements actually stick, the measurement fight every team should have out loud, and what happens to junior marketers when AI eats the entry-level rung. It's a full field guide to walking into a new company and earning trust before you change anything, plus the interview question she uses to know if you'll thrive on her team.Kelsie's Marketing Operations Assessment Framework: https://drive.google.com/file/d/1x3IJf9tHku4-fASS9AQE_F6sJ1FLK3PN/view?usp=sharingLiza Adam's Digital Twin: https://www.linkedin.com/pulse/smartest-ai-teammate-youll-ever-build-liza-adams-c7rnc/About Kelsie DubeKelsie Dube is the Director of Marketing Operations and Automation at Unanet, where she joined in 2026 to rebuild the company's measurement and reporting foundation. Before that she spent 7 years at Sophos, climbing 5 roles from Marketing Operations Specialist to Director and leading the team through much of that run. She started her career in data entry, scrubbing lead lists and learning the VLOOKUPs she still uses most days, and that ground-floor view shapes how she thinks about the craft.Outside of work she's a mom of 2, an amateur basketball player, and a snowboarder who guards the hours between 5 and 7 for her kids.Why New Marketing Ops Leaders Should Audit Before They ActThe first 90 days at a new company come with a quiet dare. Ship something. Plant a flag. Prove they were right to hire you. Most new marketing ops leaders answer that dare by ripping out a tool they never liked and installing one they used at their last job, all inside the first 2 weeks.Kelsie did the opposite when she joined Unanet. Her first move was to change nothing.The reasoning was twofold. Without a real map of how work gets done, any change you make is a guess, and you'll probably aim it at the wrong target. And Unanet had said in the job description that they wanted someone who'd slow down and understand the business first, which is part of why she took the role. For a marketer who came up through ops and now leads it, that patience is the whole point. You have to understand what's happening well enough to be dangerous, she says, before you can tell anyone what to actually fix.The harder version of this is resisting your own experience. A new CMO walks in and wants a different marketing automation platform because they used one at the last company. Kelsie feels that pull too, since she's learning a few systems here for the first time. Her answer is to make the existing stack work before spending a dollar to replace it. Right now she's rebuilding how campaigns get captured and tagged to campaign members, and she's solving it with a Salesforce workflow or Power Automate instead of a purchase. Replacing the tool would cost more and probably solve less.Then comes the part nobody warns you about, the clock. Listening mode has a shelf life, and everyone, including you, is quietly counting the days until you produce something. Kelsie gave herself a hard deadline of 30 days to finish the audit, then engineered small wins into every week so the learning never looked like stalling. New hires have one thing veterans don't, an empty calendar, and she guarded it. A recurring block every Friday at 2:00 to turn that week's discoveries into something usable. One of those blocks became a 30-minute campaign taxonomy diagram she walked the leadership team through, a quick and visible proof that better structure meant better reporting down the line.The instinct to ship in week one is the most expensive habit in operations, because a fast fix aimed at the wrong problem still has to be undone later. The operators who compound value are the ones who can sit in not-knowing long enough to find the actual bottleneck.Key takeaway: Give yourself a fixed audit window, 30 days is a reasonable default, and block a standing hour each week to turn what you've learned into one small, visible win. Keep a running log of quick wins as you find them so you always have something to ship while the deeper work is still in progress.How to Run a Marketing Ops Audit When You Join a Company"Do an audit" is the most repeated and least defined phrase in marketing ops. Everyone nods along. Almost nobody can tell you what's actually in one, which funnel stages it covers, or where it starts on a Monday morning.Kelsie's version starts before day one. The moment she accepted the Unanet offer, she began mapping ownership lines: what marketing ops owns, what rev ops owns, what IT owns. She wrote out the questions she had and sent them to her leader ahead of her start date, partly out of genuine excitement and partly to get a head start on the RACI.From there it's a series of conversations that snowball. She interviews everyone from her own team to her peers to the level above to her business partners, and she ends every conversation the same way: who else should I talk to? The list never stops growing, but the patterns start to show. Along the way she confirms the systems in her swim lane against the job description, asks what she's missing, and books dedicated working sessions where someone walks her through a live task like a lead import. She records those sessions, then feeds the transcriptions to an LLM to pull out the patterns, a tip she picked up from a mentor that turns hours of shadowing into a usable roadmap.She also runs the work herself.Joining a much smaller team than she was used to, she asked people to hand her a lead import and a campaign creation task so she could run them personally. Part of it was capacity, since a director who can still execute is extra hands when the team is slammed. Part of it was fluency. As she says, a director isn't really a "do-rector," but being right there in the work is how you understand it well enough to change it later.Data privacy rides shotgun through all of this. Coming out of the cybersecurity world, she asks about data retention and opt-in policies early, then files them under "needs struct...