Building an AI-powered team & why narrowing our ICP doubled our win rate (w/ Guido Schmitz)

Why your growth is stalling and what to actually do about it (w/ Asia Orangio)

Most SaaS founders assume a growth plateau means something is broken with the product or the marketing. Asia Orangio has spent eight years helping over a hundred SaaS companies figure out what is the actual reasons for stalls in growth. Asia is the founder of DemandMaven, a growth consulting firm focused on bootstrapped SaaS companies. Her whole approach to growth is holistic, looking at team structure, retention, segmentation, and product together, not one layer at a time. In this conversation we get into why growth stalls at predictable moments, why NRR is the metric that actually tells you what's going on, and how to figure out which customer segment is worth doubling down on.  🧠 What you'll learn in this episode: 0:00 - Why acquisition is the least efficient growth lever and what to focus on instead 1:41 - How Asia began work in holistic growth consulting and why the shift happened 6:24 - The three ARR milestones where SaaS growth most commonly stalls 7:22 - How Asia diagnoses a growth plateau using pirate metrics, team structure, and processes 8:39 - Why the founder is almost always the bottleneck at a million ARR 10:06 - Why NRR is the most important metric and what below 80% actually means for your growth 14:31 - What team structure looks like at a million ARR versus three to five million 16:17 - Why the founder being the bottleneck is a structural problem, not a personal one 21:59 - The time tracking company stuck at four million and why their flat org made it nearly impossible to grow 24:20 - The clinic management company with four senior marketers and no one actually leading marketing 35:57 - Why 12-month churn is scarier than monthly churn and why it should keep you up at night 39:23 - How to decide which customer segment to focus on when you have competing options 43:12 - The clinic management case study where one segment had three times the NRR of everyone else 47:45 - How Ben Chestnut built NRR cohort reports by hand at Mailchimp to find his best customers 53:00 - Why not everyone on your team is wired to seek out and use new information 1:02:37 - Why Asia is obsessed with Granola and how she uses it with Claude to query her meetings 1:05:02 - The Mangomint activation experience and what it teaches about building for your actual audience 💡 Actionable takeaways from Asia Steal these quick wins: 1. Pull your NRR report right now and look at it by segment If you have ProfitWell, you already have an NRR chart. Asia's suggestion is to go look at it today, not next quarter. The number you're looking for is 12-month net revenue retention by customer cohort. If it's below 80% for your primary segment, that's the thing to fix before anything else.  2. Run a cohort analysis to find your best customer, not your most common one Ben Chestnut used to build NRR cohort reports by hand at Mailchimp, flipping through different customer attributes until he found which segments had the strongest retention. That process told him who to focus the whole company on. Asia recommends doing the same: look at which segments have the best NRR, whether the team actually likes working with those customers, and whether you have a compelling enough story to attract more of them.  3. Treat a growth plateau as a diagnostic problem, not an execution problem When Asia comes into a new engagement, the first thing she does is look at baseline pirate metrics, team structure, and how the team operates. The instinct for most founders is to push harder on marketing or ship more features. What she usually finds instead is that either the founder is the bottleneck, the team isn't structured to own the work, or the company is building for the wrong segment. Knowing which of those is true changes everything about what you do next. 4. Don't restructure your roadmap until you know which segment actually stays Asia's story about the clinic management company is worth sitting with. Ninety percent of their customers were solo practitioners, but when she ran the retention analysis, the segment with staff had three times the NRR. Before you decide who to build for, pull the retention numbers by segment. The answer is usually already there. 5. Look at your 12-month churn number, not just your monthly one Asia is direct about this: your monthly churn number might look fine while your 12-month churn is quietly killing growth. The customers who leave at month eight, ten, and twelve are the ones who tried to make the product work and couldn't. That churn shows up in NRR and it compounds. She recommends making 12-month retention a standing metric you review regularly, not something you check when growth slows down.

Building an AI-powered team & why narrowing our ICP doubled our win rate (w/ Guido Schmitz)

A lot of SaaS teams are adding AI to their stack and hoping it shows up in output. This episode is about what it actually looks like when you build the whole workflow around it and why the thinking behind it matters as much as the tooling. Guido Schmitz is the CTO and co-founder of OneTeam, a mobile platform that helps hospitality and retail companies connect, engage, and develop their frontline workforce. They've been building for 11 years and are shipping faster than ever without growing headcount to do it. In this conversation, we get into how they use AI across every department, how they think about product quality and delight in B2B software, and what actually happened when they stopped selling features and started selling outcomes. 🧠 What you'll learn in this episode: 0:00 - What Love at First Try is about and who it's for 0:55 - How Guido started OneTeam at 19 and what problem they were solving 5:24 - Who OneTeam is built for and why the ICP is so specific 10:30 - What the employee experience looks like before OneTeam, and why onboarding matters more than most companies think 17:10 - The €3,000 cost of losing an employee and why reducing turnover by 1–2% pays for the tool many times over 19:23 - The aha moment for new employees: introducing yourself before your first shift and getting welcomed by colleagues 21:57 - How OneTeam thinks about empty states, animations, and the small details that make B2B software feel less like a chore 25:30 - The growth challenge that comes with building a multi-product platform and how messaging for a broad product is genuinely hard 26:11 - How going from feature selling to outcome selling and narrowing the ICP doubled their win rate 34:32 - The SaaS apocalypse debate and why vibe coding your way out of a $100/month subscription usually doesn't make financial sense 40:55 - How OneTeam adopted Cursor two years ago and why they're seeing roughly 7x the code volume per developer 42:16 - How Guido uses Lovable to prototype feature improvements and get real customer feedback in two to three days 44:26 - The agentic workforce running in Slack: a marketing agent, product agent, engineering agent, analyst, and sales ops agent — and what each one actually does 46:23 - The error-monitoring agent that researches bugs, proposes fixes, runs tests, and opens pull requests for developer review 47:22 - The competitor intelligence report that lands every Monday morning — and why it would have taken five or more people before 1:01:34 - The mental model behind it all: ask what you'd do with 10x the team, then figure out if you can do it agentically 1:05:34 - How AI is changing the design process, and why the idea is now the constraint — not the execution 💡 Actionable takeaways from Guido Steal these quick wins: 1. Start your agentic setup with one scoped job, not a big rollout A good entry point is a single, specific job like a competitor intelligence report that runs every Monday morning. Define what the agent should look at, what it should extract, and where it should drop the output. Build confidence there before you add more. 2. Give new employees a social introduction before their first shift OneTeam built a feature where new hires introduce themselves on the company's social timeline before they even start, and colleagues respond with a high five or a welcome message. It's one of the strongest early signals of belonging you can create, and it costs almost nothing. 3. Narrow your ICP before you touch your messaging If your win rates feel stuck, the problem might not be how you're describing your product. It might be who you're describing it to. OneTeam went from "any company with non-desk employees" to a very specific type of hospitality brand. The messaging got sharper because the audience got sharper.  4. Flip the question when thinking about AI and headcount Instead of asking "what can AI help us with?", ask "what would we do if we had 10x the team?" Then figure out which of those things can be done agentically. OneTeam is processing thousands of prospects a week with an agent that would have needed five or more SDRs before. The constraint isn't capability. It's imagination.

Taste, quality and what it actually takes to build software people love (w/ Bob Baxley)

A lot of SaaS products ship fast and skip the thinking. This episode is about what happens when you don't, and why that actually matters for growth. Bob Baxley spent 35 years designing software at Apple, Yahoo, Pinterest, and ThoughtSpot. Products he worked on have been used by hundreds of millions of people. He's one of those people who has spent a long time thinking carefully about what makes software genuinely good, not just functional, and why so few companies get there. In this conversation, we get into how to build a culture where quality is the standard, how to get your whole company to care about design without a single presentation, and how the decisions you make at the conceptual level shape everything downstream.   🧠 What you'll learn in this episode: 0:00 [https://www.youtube.com/watch?v=in95y6B0Pew] - Why the tech industry is in a speed race and what that means for product quality 7:37 [https://www.youtube.com/watch?v=in95y6B0Pew&t=457s] - How Bob fell in love with computing at 11 years old and why that shaped everything after 12:31 [https://www.youtube.com/watch?v=in95y6B0Pew&t=751s] - Why timing matters as much as talent when it comes to what you can build 13:58 [https://www.youtube.com/watch?v=in95y6B0Pew&t=838s] - How economic pressure from VCs is changing the pace of design work inside companies 24:36 [https://www.youtube.com/watch?v=in95y6B0Pew&t=1476s] - The real difference between sales-led and product-led companies, and why it never changes after founding 27:05 [https://www.youtube.com/watch?v=in95y6B0Pew&t=1625s] - Why design teams have hurt themselves by hiding their process from the rest of the company 30:00 [https://www.youtube.com/watch?v=in95y6B0Pew&t=1800s] - How Bob's team ran an internal influence campaign at ThoughtSpot using weekly Loom videos 35:49 [https://www.youtube.com/watch?v=in95y6B0Pew&t=2149s] - What a head of design actually does on a sales call and why it worked 37:42 [https://www.youtube.com/watch?v=in95y6B0Pew&t=2262s] - Design tenets vs. design principles, and which one actually helps teams make decisions 42:30 [https://www.youtube.com/watch?v=in95y6B0Pew&t=2550s] - What choreography over control looks like in practice for a design leader 47:51 [https://www.youtube.com/watch?v=in95y6B0Pew&t=2871s] - The difference between micromanagement and being in the details, and why it matters 54:55 [https://www.youtube.com/watch?v=in95y6B0Pew&t=3295s] - How to think about quality within constraints instead of chasing world class as a target 1:00:46 [https://www.youtube.com/watch?v=in95y6B0Pew&t=3646s] - Why taste is hard to compete on, and which layer of the market you actually need to nail first 1:01:15 [https://www.youtube.com/watch?v=in95y6B0Pew&t=3675s] - A simple exercise to raise the taste level of your engineering team 1:06:08 [https://www.youtube.com/watch?v=in95y6B0Pew&t=3968s] - The three stages every market goes through before design becomes a competitive advantage 1:12:36 [https://www.youtube.com/watch?v=in95y6B0Pew&t=4356s] - What it really means to design for the person on the other side of the glass 1:16:57 [https://www.youtube.com/watch?v=in95y6B0Pew&t=4617s] - Why user research needs to be a ritual, not a one-time sprint 1:20:44 [https://www.youtube.com/watch?v=in95y6B0Pew&t=4844s] - The Post-it note observation that turned into a multi-billion dollar company 1:24:29 [https://www.youtube.com/watch?v=in95y6B0Pew&t=5069s] - Bob's favorite apps and what they got right at the conceptual model level 💡 Actionable takeaways from Bob Steal these quick wins: 1. Run the "three favorite apps" exercise with your team Ask everyone to name their three favorite apps .Not the ones they use most, their actual favorites. Getting your team to sit with that question starts a real conversation about what quality actually means versus what just has good distribution.  2. Show the work before it's done Bob's team at ThoughtSpot made a 22-minute Loom video every week for 35 weeks, showing projects at every stage and sent it to the whole company. It shifted how every department understood and valued design work, without a single big presentation or formal pitch. If your team feels invisible inside the company, this is a low-cost way to change that. 3. Replace your design principles with tenets Principles like "be clear" or "feel responsive" don't help anyone make a decision because nobody argues the opposite. A tenet is a hard-edged statement your team agrees on once so they stop relitigating the same debate.  4. Go watch your users outside the context of your product When Bob was asked about ZenMaid, his recommendation was to visit cleaning business owners and understand how they think and run their business, not just how they use the software. Watching how someone actually works, before you introduce your product into the conversation, gives you better ideas than any feature interview. 5. Ask an LLM you've been using regularly: "What outdated mindset am I holding onto that's no longer serving me?" The answer Bob got shifted how he thought about control and leadership. His suggestion is to run it with an LLM that has enough context on you to give a real answer, not a generic one.

Positioning is a decision, not a tagline & the truth behind the AI hype (w/ Anthony Pierri)

If you're a SaaS founder who keeps rewriting your homepage and it still doesn't feel right, this episode is for you. Anthony Pierri is the co-founder of Fletch PMM. He and his team have run their 2-week positioning sprint around 500 times for B2B software companies, which probably makes them the most experienced positioning consultancy out there. He's also one of the clearest, least jargon-filled voices on LinkedIn when it comes to marketing. We spent an hour going deep on what positioning actually is (and isn't), why so many founders are stuck running five go-to-market motions at once without realizing it, and what happens when you make a real repositioning bet — with stories from Klaviyo, Anthropic, a trucking analytics company, and even Taylor Swift. We also got into AI — specifically, what Anthony discovered when he stopped using chatbots and went deep into Claude Code. His take is the most grounded I've heard in months. No fluff. No frameworks for the sake of frameworks. Just one of the sharpest operators in B2B marketing talking shop. 💡 Steal these quick wins from Anthony 1. Test your positioning by putting it on the homepage Not a Google Drive deck. Not a Notion page. The homepage. It's the one asset everyone in the company has to live with publicly, which is exactly why agreement on it sticks. If your team can't agree on what should go on the homepage, you don't have a positioning problem — you have an unresolved strategic decision. 2. Stop defining your target market by firmographics Company size, headcount, geo — none of these signals tell you whether a company actually needs your product. If you're trying to win five use cases inside one customer segment, you're running five different go-to-market motions in parallel. Pick the one that ladders into the biggest opportunity and lead with it. 3. Don't validate a reposition by asking your best customers They came to you for the old story. They'll tell you not to change. Customer research is one input — not the only one. The bet sometimes requires alienating who you have to win who you want. 4. Stop treating chatbot output as real work Anthony's experiment: dropping 20 sales call transcripts into a chatbot got him a summary in 10 seconds. Looked great. Then he wrote a detailed instruction file for the AI on exactly how to summarize one call — took 2 hours to build, 5 minutes to run on a single call. The realization: the fast chatbot version was producing something that looked plausible without doing the work. If you're using AI for anything where accuracy matters, the painstaking version is the real version. 5. Build for where the AI is going to actually be useful: smarter automation Don't build your strategy around AI replacing your team. Build it around AI replacing the slow, manual workflows that already exist (the stuff you'd otherwise build in Zapier or hire a junior to do). That's where the real productivity lives today.

Designing for delight, reducing design debt & using AI to prototype faster (w/ Alicja Suska)

Alicja Suska has been designing SaaS products for 10 years. She's worked at Toggle, Sourcegraph, and now leads product design at Buffer. What caught my attention: she comes from an artistic background — illustration and animation. That shapes how she designs. Colors, composition, how elements work together — it comes more intuitively. But she admits the process is harder to explain: "I can reason why something is good, but I work more intuitively." 🧠 What you'll learn in this episode: 0:00 - Jim's intro  0:25 - Who is Alicja and her journey through Toggle, Sourcegraph, and Buffer 3:00 - Designing for vastly different users: solo creators vs enterprise teams 5:24 - How to define taste as a designer (and why delight is more practical) 9:44 - Why delight only works after you've solved the core problem 10:26 - How an artistic background shapes product design thinking 15:33 - Sketching and showing rough work early (not polished mockups) 17:45 - Using AI in the design process: what works and what doesn't 21:30 - Prototyping Buffer Insights with Claude: 40+ concepts in one project 29:24 - The shiny object syndrome: wasting time on overhyped AI tools 31:41 - Designing AI features without screaming "this is AI" 39:15 - Enterprise vs consumer: when to be transparent about AI usage 40:04 - Onboarding philosophy: get users into the product as soon as possible 43:12 - Buffer's experiment: showing the UI before asking users to connect channels 46:18 - Credit card upfront vs free trial: what the data actually showed 49:18 - Time to value: identifying the real aha moment (it might not be what you think) 52:09 - Design debt: how navigation bloat quietly kills your product 55:01 - Why you need a dedicated designer who owns the product long-term 58:57 - Process hack: weekly time-to-value brainstorming sessions 1:04:38 - "Release what you're proud of" — Buffer's shift away from shipping fast 1:08:46 - Alicja's favorite products right now and why 💡 Steal these quick wins from Alicja: Show the product UI before asking for commitment. Buffer stopped blocking users with "connect your channel" upfront. Now they show the calendar first. Users explore, then connect when ready. Less friction, more trust. Design your empty states like onboarding screens. Most users skip onboarding anyway. They land on an empty screen that wasn't designed for being empty. Make your empty states guide users to the next action — not just fill space. Run a monthly "time to value" session. Alicja blocks 1-2 hours monthly to brainstorm: how can we shorten time to value? No big project commitment. Just one brainstorm + one small dev task. Fixes pile up over time. Use Claude to prototype before devs write code. Alicja brainstormed 40+ feature concepts with Claude, then had it generate interactive HTML prototypes using Buffer's design system. The team could experience features before any code was written. Audit your navigation every time you add a feature. The default pattern is "add another tab at the top." Eventually you run out of space and unimportant things sit at the same level as critical ones. Review navigation with every addition.