Podcasts about b2c

Salesforce renamed Commerce Cloud to Agentforce Commerce and calls this its biggest release in years. Rebrand, or substance? Nitin Mangtani makes the case.Every enterprise vendor is bolting "agentic" onto its roadmap this year. Salesforce went further and renamed the whole product. Nitin Mangtani, who runs Commerce and Retail Cloud, came on to defend the release line by line.We get into Storefront Next, the new storefront meant to serve both the merchant who wants clicks and prompts out of the box and the developer writing code with AI-native tools. The agentic layer: a search engine built on shopper intent instead of keywords, native chat, a ChatGPT catalog integration going live in June, and a shopper agent that's supposed to behave like the associate you'd get in a good store. The B2B story the B2C headlines tend to bury, including round-trip quoting, multicart, and a buying flow that runs on WhatsApp. And modern POS, where the bet is that systems nobody has rethought in twenty years are finally worth rebuilding.Nitin came in through the PredictSpring acquisition two years ago and ran Google's shopping team back in the early 2000s, so he's watched the discovery layer move before. His line throughout: technology for its own sake is worthless. Tie it to ROI and a better customer experience, or don't ship it.So I pushed on the question every merchant on the platform is actually asking. Hear Agentforce Commerce, Storefront Next, and a ChatGPT integration in the same week, and what changes for you, and how soon? Listen and decide whether the rebrand earns the airtime.The Watson Weekly interview is sponsored by Avalara - the agentic AI platform automating global tax and compliance for leading eCommerce brands. For more details: https://avalaratax.watsonweekly.com.

Growing your own machinists and orchestrating robots across four continents, is this what the future of manufacturing looks like? This live episode from Hapa's Brewing in the Bay Area features two panels of people who have built careers at the intersection of mechatronics, automation, and industrial innovation. First up, Vinod, Kevin, and Adam get into what it takes to build a skilled workforce from the ground up, talking about apprenticeships, college partnerships, and growing your own talent in-house. Then we get into the bigger picture with our founder panel Kim, Glenn, Nick, and Florian on what Silicon Valley gets wrong about manufacturing, and what manufacturers are missing by not paying closer attention to what's being built there. In this episode, find out: How Vinod bootstrapped an automation company in the Bay Area while raising a family and why his wife had something to do with it What Kevin learned from a 3-year German apprenticeship that he thinks more US manufacturers should be paying attention to How Adam solved his machinist shortage by bringing the training programme in-house and partnering with a local college How Kim thinks about leading companies through inflection points when there are no guardrails or safety nets Why Glenn believes manufacturers who aren't paying attention to what's being built around them won't even know when it's too late How Nick's B2C background completely changed the way he thinks about building software for frontline manufacturing workers Why Florian ignored his investors and opened a public-facing robotics storefront on the main street of Mountain View Enjoying the show? Please leave us a review here. Even one sentence helps. It's feedback from Manufacturing All-Stars like you that keeps us going! Tweetable Quotes: “You don't have that mechanical job anymore that's done by one person. You need support, whether it's software support or you need a robot at your side.” – Kevin Toomer, Product Manager at Sumitomo Drive Technologies “In automation, you don't need a master's or a PhD to be successful. Just getting creative and having that experience in mechanical engineering really helped me in my career.” – Vinod Anandarajah, Co-Founder and CEO at Kanavu Automation ”In Silicon Valley, we tend to love disruption because to us it represents something new and something better. But when you get on a manufacturing floor, they tend to want predictability.” - Kim Losey, Founder and CEO at NextLine Group Links & mentions: Kanavu Automation, bringing value to manufacturing clients via a strategic focus on machine automation and robotics MaintainX, empowering maintenance professionals to reduce unplanned equipment downtime and boost production capacity NextLine Group, architecting what is next in robotics engineering Sumitomo Drive Technologies, providing engineered solutions to industrial power transmission customers Beluga Navigation Systems, building deep tech navigation solutions for vehicle and vessel navigation InOrbit.AI, leading AI-powered robot orchestration platform, driving software-defined operations at scale Hapa's Brewing Company, craft brewery and taproom located in San Jose, CA Make sure to visit http://manufacturinghappyhour.com for detailed show notes and a full list of resources mentioned in this episode. Stay Innovative, Stay Thirsty.

Priya has 20 years of experience in PR, Corporate Communications and Marketing with an emphasis in B2B technology (real estate, telecom, security, finance, manufacturing, power and energy, medtech, biotech, digital health and more) and experience in B2C (mobile, interior design, entertainment, sports, philanthropy, and fashion).  Her work spans Fortune 500 corporations to niche boutique agencies, with strong capabilities in external and internal communications, full-circle strategic planning, campaign development and execution, and content development.   Tune in to hear how Priya took the leap from Corporate and leveraged her thought leadership and talents to build a PR firm that's wrestling its way to the top!  Connect with Priya https://arkivepr.com/

Enterprise marketing teams struggle with AI implementation at scale. Patrick Brown, Vice President of Growth Marketing & Insights at Adobe, explains how AI transforms marketing operations across global B2B and B2C segments. He outlines Adobe's three-pillar framework for AI adoption: delivering personalized experiences, measuring performance with advanced analytics, and building foundational marketing technology tools. Brown also identifies the limitations of AI in forward-looking projections and emphasizes the importance of human judgment in strategic decision-making.See Privacy Policy at https://art19.com/privacy and California Privacy Notice at https://art19.com/privacy#do-not-sell-my-info.

Enterprise marketing teams struggle with AI implementation at scale. Patrick Brown, Vice President of Growth Marketing & Insights at Adobe, explains how AI transforms marketing operations across global B2B and B2C segments. He outlines Adobe's three-pillar framework for AI adoption: delivering personalized experiences, measuring performance with advanced analytics, and building foundational marketing technology tools. Brown also identifies the limitations of AI in forward-looking projections and emphasizes the importance of human judgment in strategic decision-making.See Privacy Policy at https://art19.com/privacy and California Privacy Notice at https://art19.com/privacy#do-not-sell-my-info.

RJ Talyor is the Founder and CEO of Backstroke a AI for eCommerce generative content platform for email marketers. Instantly create on-brand, high-performing email subject lines, preview text, mobile push notifications, and SMS messages.Summary of PodcastPodcast introduction and guest backgroundGraham and Kevin introduce the Next 100 Days Podcast and welcome RJ Talyor from Indianapolis. RJ describes Indianapolis as offering the best of a big city with a small-city feel, with about a million people, great sports, culture, food, and good cost of living. He has traveled extensively but always enjoys returning home.Backstroke's AI email generation platformRJ introduces Backstroke.com, which generates performant email campaigns for e-commerce retailers selling clothes, pet food, furniture, and other products online and in-store. E-commerce brands typically expect 20-50% of revenue from email marketing while sending 3-5+ emails weekly, with customers spending 8-12 hours per campaign. Backstroke reduces this to approximately 15 minutes while personalising content so each customer receives a different message tailored to their interests and behaviour.Personalisation through data and engagement Backstroke personalises emails using multiple data layers: subscriber status, past engagement (opens, clicks, conversions), and appended third-party data revealing demographics like age, location, and gender. When additional data is unavailable, the platform uses progressive profiling—analysing engagement patterns to infer preferences. For example, if a customer consistently clicks on men's content over women's content, or prefers dark-coloured shirts over light ones, AI identifies these patterns to drive personalisation, which is more effective than manual analysis.Real-world personalisation: from negative to advocateGraham shares a personal story about Son of a Tailor, a Portuguese apparel brand, where his initial experience was poor—they sent him a shirt too short for his frame. However, the company responded exceptionally well, ultimately creating a monogrammed, high-quality shirt that transformed him into an advocate. RJ explains this is valuable data: AI can flag customers who experienced negative-to-positive journeys as potential super-fans or loyalty advocates, a pattern most marketers miss because they lack time to identify such nuanced customer experiences.AI pattern recognition beyond traditional metricsTraditional RFM (Recency, Frequency, Monetary) models reduce customers to transactional data, but AI can extract signal from unstructured data to identify complex patterns. For instance, AI can recognize when a customer buys different sizes (suggesting purchases for others) or when multiple preferences exist within one account—like RJ's Spotify feed where his children's music preferences mix with his own. AI discerns these overlapping patterns that aren't immediately obvious to humans, enabling more sophisticated segmentation.Team expertise and company historyRJ co-founded Backstroke with his wife Allison, who holds a PhD in deep data analysis and chemical reagents, bringing statistical rigour and predictive modelling expertise. RJ's background includes starting Pattern89 in 2016, an AI company predicting Instagram and Facebook clicks using computer vision and natural language processing, which he sold to Shutterstock. Many Pattern89 team members joined Backstroke, bringing 10 years of AI-based marketing experience, while the team continuously innovates with new foundational models from Anthropic and OpenAI.Implementation results and Surge featureBackstroke achieves an average 30% uplift in conversion rates for new clients. Implementation typically takes about a month for full transformation, but recognising customer demand for faster results, the company launched "Surge," enabling campaigns to launch in 48 hours. This rapid-deployment feature demonstrates predictive capabilities quickly, satisfying customers who want immediate proof before committing to full onboarding.Email variants and human approval at scaleWhile technically capable of generating 10,000+ unique email variants, Backstroke has found that customers require human review of every variant version. Current implementations range from 60-100 variants, with combinations of hero images, subject lines, and templates creating exponential possibilities. The company is building QA agents to enable scaling to millions of variants while maintaining human oversight, recognizing that creative teams ultimately bear responsibility for brand representation.Brand guidelines versus performance metricsA fundamental tension exists between brand teams (who enforce guidelines like "models must face forward" or "only use this colour") and performance marketers (who know "shirts perform better laid on a bed than on a human"). RJ explains this is often gut-feel decision-making based on outdated tests—teams cite tests from a year ago by employees who've since left, creating stale guidelines. AI enables rapid testing of creative variations to identify incremental opportunities, but requires organisational willingness to experiment beyond established brand rules.Customer selection philosophyRather than trying to convince resistant customers to embrace AI, RJ focuses on the "one in 10" truly innovative marketers willing to change. He learned from his previous business that most prospects claim interest but quickly reveal organizational barriers requiring approvals. His strategy is to identify customers genuinely committed to transformation and willing to pay, directing others to resources instead. This approach conserves energy for high-potential partnerships where AI can deliver real impact.Backstroke's core value propositionBackstroke solves the "what" problem: what content, subject line, preview, template, hero image, product display, and offer to send to each person. The platform knows that 46% of clicks occur in the first 400 pixels, so it optimizes that space differently for men versus women, loyal customers versus new ones, and geographic regions. This focused specialization on content optimization is Backstroke's primary value, distinct from solving "when" (send time) or "who" (segmentation) problems.Practical tips for email marketersFor marketers using standard LLMs without specialised platforms, RJ recommends uploading all previous email data and creative assets, then asking the machine to identify winning creative dimensions. This approach reveals patterns in subject lines, imagery, copy length, and offers without requiring subscriber-level analysis, enabling better-than-average results for those without access to specialised tools.Email frequency paradox and engagementKevin raises frustration with receiving excessive emails from companies he likes, asking if AI can enable sending less email while achieving better results. RJ explains that higher engagement with personalised content could theoretically reduce frequency, but email is fundamentally a frequency game—brands send multiple emails weekly to stay top-of-inbox when customers are ready to buy. However, deliverability depends on engagement (opens, clicks), so sending irrelevant content backfires. Backstroke solves the "what" problem, but send-time optimisation and segmentation (the "when" and "who") remain separate challenges.Market focus and customer examples Backstroke focuses exclusively on B2C e-commerce in North America due to language complexity and GDPR privacy requirements in Europe. The platform serves impulse-purchase categories (apparel, furniture, bedding) differently than considered purchases (mattresses, cars), with separate trained models for each. Notable customers include Third Love (women's intimates), Cozy Earth (bedding), Helix (mattresses), and Emile Henry (cookware), representing the apparel and home goods verticals where Backstroke has developed deep expertise.Future roadmap: predictive marketing agentsRJ's 18-month roadmap focuses on building predictive marketing agents that complete marketing tasks generatively while humans serve as brand stewards and strategists. This vision extends beyond email to SMS, apps, and landing pages, with personalisation as a core feature. Graham notes the challenge of making such systems intuitive enough for non-technical users, reflecting the broader industry shift toward AI-augmented rather than AI-replaced marketing roles.European expansion and compliance strategyWhile Backstroke is currently North America-focused, RJ is open to European partnerships but wants to be proactive about compliance. GDPR itself isn't a blocker, but European customers require security documentation and certifications that Backstroke hasn't yet obtained. The company recently achieved SOC 2 compliance (required by enterprise businesses) and plans to secure necessary privacy certifications before entering European markets, avoiding disqualification during sales cycles.Podcast analysis and key takeawaysIn the wrap-up, RJ praises the podcast for getting past fluff into real marketing challenges, appreciating the nitty-gritty discussion of how marketers actually work. Graham and Kevin reflect that the conversation revealed AI's potential to solve the "what" problem while highlighting remaining challenges in "when" and "who" decisions. They note that Kevin's observation about sending less email...

When most people think of Land O'Lakes, they think of the butter in their fridge. But the reality is a $17 billion agribusiness powerhouse that feeds 100 million animals a day and touches every single point of the food value chain. In this episode, Heather Malenshek, SVP and CMO of Land O'Lakes, sits down to look beyond the dairy aisle. She dives deep into the company's unique cooperative model, the delicate balance of marketing across both B2B and B2C landscapes and why legacy brands hold a unique kind of cultural power. Malenshek also breaks down the Modern Rural Collective and Repicturing Rural initiative — a partnership with Getty Images born out of the stunning stat that two-thirds of rural Americans feel entirely misunderstood by mainstream advertisers. From busting myths about rural entrepreneurship to changing how the media portrays modern agriculture, Malenshek shares how Land O'Lakes is rewriting the narrative of America's heartland. campaignlive.com Music - Take you Out by Lucid Tides, courtesy of Triple Scoop. What we know about advertising, you should know about advertising. Start your 1-month FREE trial to Campaign US. Hosted by Simplecast, an AdsWizz company. See pcm.adswizz.com for information about our collection and use of personal data for advertising.

Dans cet épisode de « Ça vient des RH », nous recevons Emmanuelle Loye, directrice de Staffbase France, experte à l'intersection des RH et de la communication interne depuis 20 ans.Aujourd'hui, 60 à 70 % des salariés mondiaux n'ont pas accès à un ordinateur au quotidien. Entre l'infobésité générée par la multiplication des outils (Slack, Teams, e-mails) et l'isolement numérique des travailleurs de terrain, comment garantir que l'information stratégique arrive vraiment jusqu'au "dernier kilomètre" ? Cet épisode décrypte comment transformer la communication interne en un levier d'engagement et de performance.Nous abordons notamment :Le piège de l'outil vs l'intention : Pourquoi l'accumulation de plateformes ne règle pas le sentiment de déconnexion et l'importance d'une gouvernance claire pour éviter l'amoncellement de contenus.Inclure les "Deskless Workers" : Le défi de toucher les salariés sans bureau. Retour sur le cas de DHL (600 000 collaborateurs) et l'utilisation de formats adaptés comme le podcast pour les chauffeurs-livreurs.Le tandem RH et Marketing : Pourquoi le DRH doit s'allier à la communication pour adopter les codes du B2C (vidéos courtes, formats mobiles) et mieux cibler ses messages.La communication comme acte politique : Éviter que le CSE ne s'attribue tous les succès RH et redonner au manager son rôle de relais essentiel pour donner du sens à l'information.L'équité par l'information : Comment l'accès aux ressources devient le socle de l'inclusion et comment l'IA peut aider à personnaliser l'information selon le métier.Un épisode indispensable pour les professionnels RH et les communicants qui souhaitent remettre l'utilisateur final au centre de leur stratégie.Tu as aimé cet épisode ? Fais-le savoir : like, partage, commente. C'est ce qui nous aide le plus à grandir.

A lot of teams hit January with energy and end Q2 running on fumes. In this Office Hours episode, Danny opens the doors to Optidge's internal playbook with Operations Director Kelly A. Garcia and Head of People Operations Lauren Friedman. Together, they break down how the agency prevents midyear drift, what it actually looks like to build a culture of transparency in a remote-first environment, and the frameworks Optidge uses to keep teams unified and accountable year-round.An Optidge "Office Hours" EpisodeOur Office Hours episodes are your go-to for details, case studies, how-to's, and advice on specific marketing topics. Join our fellow Optidge team members, partners, and sometimes even 1:1 teachings from Danny himself, in these shorter, marketing-focused episodes. Get ready to get marketing!Episode Highlights:This discussion unpacks why momentum fades mid-quarter, not mid-year, and how Optidge builds intentional reset points four times a year to reignite it.Lauren details the “Share the Legos” concept: why giving away knowledge and process is the only real way to scale, and how to shift the team mindset to embrace it.Kelly shares the two key KPIs she watches every day, and what they tell her about when a mid-year pivot is actually necessary.The pair reveals how and why Optidge uses letter grades, single quarterly rocks, and clearly defined "done" criteria to keep goals from becoming noise.This episode emphasizes why context is non-negotiable in a remote agency, and what happens when leaders fill the silence instead of leaving teams to fill it themselves.Episode Links: Digital Marketing Mentor Podcast: Optidge.com/tdmmConnect with Kelly A. Garcia on LinkedIn: Kelly A. GarciaConnect with Lauren Friedman on LinkedIn: Lauren FriedmanSend us Fan MailFollow The Digital Marketing Mentor:Website and Blog: thedmmentor.comInstagram: @thedmmentorLinkedin: @thedmmentorYouTube: @thedmmentorInterested in Digital Marketing Services, Careers, or Courses? Check out more from the TDMM Family:Optidge.com - Full Service Digital Marketing Agency specializing in SEO, PPC, Paid Social, and Lead Generation efforts for established B2C and B2B businesses and organizations.ODEOacademy.com - Digital Marketing online education and course platform. ODEO gives you solid digital marketing knowledge to launch/boost your career or understand your business's digital marketing strategy.

I denne episode af EDB 5.0 får vi besøg af Janne Jul Jensen, medstifter af Henosia. Janne er uddannet softwareingeniør og har en ph.d. i UX. Hos Henosia er hun med til at udvikle et vibe coding værktøj til app generation, hvor medarbejdere beskriver den løsning, de har brug for, og Henosia så bygger applikationen for dem, så arbejdsgange kan automatiseres og manuelt arbejde reduceres. I episoden taler vi om, hvordan vibe coding kan give medarbejdere mulighed for selv at bygge værktøjer til opgaver som KPI-rapportering, rejseafregning og interne workflows, mens IT stadig sætter rammerne for datasikkerhed, datakilder, adgang og go live. Vi kommer omkring sikkerhed, integrationer til eksisterende systemer, adoption i organisationer og hvordan Henosia arbejder med deres AI agent, datalag og fremtidige funktioner. Shownotes 00.00-13.06: Introduktion til Janne, vibe coding og Henosia 13.06-46.39: Sikkerhed, integrationer, adoption, use cases, proces for at bygge, sammenligning med Lovable og Claude Code samt pivotering fra B2C til B2B 46.39- 52:28: Fremtiden for Henosia, datalag og persongalleri Vært Mathias Mengesha Emiliussen

In this episode, Krista sits down with Janelle Hardy, a memoir writer and somatic healing practitioner, to break down how she used virtual summits in a creative, B2C niche to grow her email list and turn that growth into six-figure course sales. Janelle shares her journey from hosting her very first summit to running repeatable events that now fuel premium course launches year after year. You'll hear what changed over time, how she built momentum without sponsorships, why list growth mattered more than conversion rates early on, and how she aligned her summits with high-touch, higher-ticket offers without pressure-based marketing. If you've ever wondered whether summits could work for a non-traditional audience or support a more values-driven business model, this conversation will expand what you think is possible. For show notes, head to https://summithosthangout.com/324

This week, Sarah Segal, Jaci Russo, and Lena McGuire tackle a question many service business owners face: Which is the bigger risk—an employee who feels overburdened or a client who feels neglected? The discussion begins with Sarah explaining why she's had to reestablish boundaries with some clients who were texting and calling her employees after hours and bypassing the systems her agency has put in place. Sarah wants her team to be able to disconnect at the end of the day, and she wants clients communicating with the entire team assigned to their account—not developing overly close relationships with individual employees. In her view, protecting employees from burnout ultimately leads to better service for clients.Jaci approaches the challenge very differently. Her creative staff rarely communicate directly with clients. Instead, account managers serve as the sole point of contact, much like restaurant servers relaying orders between diners and the kitchen. The goal is to protect specialists from interruptions, keep them focused on their work, and ensure that client communication remains clear and consistent. The result is a lively conversation about competing priorities, client expectations, employee well-being, and the hidden risks that can emerge when clients become too dependent on individual employees. Plus: Have you ever had an employee leave and take clients with them?

This week, Dave speaks with Dean McElwee, ecommerce and digital transformation leader and author of Ecommerce for CEOs.Dean shares what he's learned working across global brands, complex categories, and digital shelf transformation — including why DIY and home improvement require a very different ecommerce content playbook.In this episode, Dean breaks down the challenges of managing SKU complexity, spec data, mobile legibility, B2B and B2C shopper needs, and content workflows across retailers. He also shares his perspective on It'sRapid Optix, and why analytics should help teams understand not just what needs to be fixed, but why those fixes matter in the shopper decision process.The conversation also explores how AI and creative automation are helping ecommerce teams refresh content more efficiently, reduce manual work, and focus on doing the digital shelf basics brilliantly.Connect with Dean on LinkedInFollow Beyond the Shelf on LinkedInLearn More about It'sRapidGet the It'sRapid Creative Automation PlaybookTake It'sRapid's Creative Workflow Automation with AI surveyEmail us at sales@itsrapid.io to find out how to get your free AI Image AuditTheme music: "Happy" by Mixaud - https://mixaund.bandcamp.comProducer: Jake Musiker

Did you know that 92% of B2B buyers enter a formal evaluation with a vendor already in mind?   In this episode of Digital Marketing From The Coalface, Julie and Dave dive deep into the hidden realities of the modern B2B buyer journey. With 70% to 80% of the purchase process completed before a prospect even speaks to a vendor, your website needs to do much more than simply capture leads.   We explore why obsessing over B2C-style Conversion Rate Optimisation (CRO) and button colours is a trap for B2B marketers. Instead, learn why your focus must be on building credibility, offering case studies for social proof, and making the 6 to 10 decision-makers involved in a deal feel completely "safe".   The conversation then unpacks a 2024 Forrester Report that proves B2B buyers are making up their minds about your business before you even know they exist. To help you adapt, Julie and Dave explain how to use Google and LinkedIn ads as a rapid "fishing exercise" to test product demand and search volume before committing six months to an organic SEO strategy.   We also cover the latest in digital visibility, specifically Google's rollout of separate AI impressions in the UK Search Console. You will learn how to use AI content graders to ensure your writing is specific and "non-commodity," which forces AI search engines to link back to your website rather than just regurgitating your hard work.   Finally, Dave and Julie share their own successes and frustrating hallucination failures using tools like Claude to automate tedious daily tasks.   Tune in to learn how to adapt your digital strategy for the highly-researched, AI-assisted B2B buyer!

What's up everyone, today we have the pleasure of sitting down with Lindsay Rothlisberger, Director of GTM Innovation at Zapier.(00:00) - Intro (01:23) - In This Episode (02:00) - Sponsor: Knak (03:08) - Sponsor: MoEngage (05:49) - How Zapier's RevOps Team Built Its AI Foundation (19:43) - Why Visibility Has to Come Before Governance in AI Adoption (24:58) - Sponsor: GrowthBench (25:58) - Sponsor: GrowthLoop (29:48) - How Zapier Fights Context Rot in Its AI Shared Brain (35:55) - How Zapier Governs Shared AI Skills from Review to Long-Term Ownership (39:27) - What Happens to RevOps When Everyone Around Them Can Build (45:05) - The Director of GTM Innovation Role and the Sharing Problem Nobody Has Solved (50:47) - What Keeps Lindsay Grounded in the Middle of All This Change (52:00) - Lindsay on Getting Buy-In and What She's Reading Summary: When a startup claimed in April 2026 that it invented the marketing engineer role and that RevOps professionals "just do tool integrations," Lindsay Rothlisberger had heart palpitations. Her team at Zapier had been building AI into GTM workflows for years before the announcement. In this episode, she walks through the 6-component AI governance model she published publicly: a golden path to Cursor, a structured shared brain in Google Drive, data policies built with the security team, a visibility layer powered by a custom Zapier agent, a context engineering strategy that fights context rot, and a red-yellow-green skills review gate. She also names the part of the model that's still broken, and it's more honest than most AI governance conversations allow. If your team is figuring out how to govern AI at scale without killing the momentum, this is the inside view from someone who's done it.About Lindsay RothlisbergerLindsay Rothlisberger is Director of GTM Innovation at Zapier, where she leads the company's AI-powered GTM transformation internally and works alongside customers navigating the same shift. She spent 4 years building Zapier's RevOps function from zero, scaling it into a cross-functional engine covering AI, systems, analytics, planning, and enablement, and growing ACV 10x in that time. Before moving into the innovation role, she led marketing operations and lifecycle programs at UNiDAYS across B2B and B2C markets. She writes on LinkedIn about what Zapier is actually shipping, what works, and what doesn't.How Zapier's RevOps Team Built Its AI FoundationMost RevOps teams doing serious AI work have been doing it longer than the current conversation suggests. The tools are newer and the terminology has changed, but building automated workflows that take unstructured data and produce structured, actionable outputs for salespeople and marketers? That's exactly what good RevOps teams were doing before anyone put a trending name on it.Lindsay's team at Zapier started experimenting with AI several years ago, when it was first becoming accessible. Zapier gave its RevOps team the tools to experiment early, and rather than waiting for a strategy to materialize, they picked a specific, annoying problem: sales handoffs. Salespeople were going into first calls without enough context about the lead. The team pulled all the relevant unstructured data, engagement records, support tickets, email threads, and used AI to generate clean, contextualized briefing materials. The result was a measurable lift in lead-to-opportunity conversion rates, and a pattern the team has used ever since: find something specific that's visibly broken, prove AI fixes it, then apply that logic somewhere else.That early foundation matters now because the landscape has shifted in a way that affects RevOps directly. Claude Code, Cursor, and similar tools have made it possible for people with no engineering background to build real things. Sales managers are writing AI skills that generate quarterly revenue strategies for reps. CS reps are building account monitoring tools. Lindsay's read on this is that the RevOps team's job isn't to slow that down. It's to give it a governance structure so it can scale without creating a mess, and to be the team that built the foundation those builds are operating on.At Zapier, that governance structure is anchored by an AI center of excellence led by a chief AI officer. The architecture is a hub-and-spoke model: the central team sets the frameworks, the guidelines, and the enablement resources; Lindsay serves as the spoke into go-to-market, with a partner who works alongside her. The 2 of them act as a feedback loop between what's happening on the ground in sales, marketing, and CS and what the central team needs to know. The center of excellence is small, just a handful of dedicated people, but it reaches into every function through the spoke structure.The first thing the center of excellence built for non-technical GTM employees was the golden path to Cursor. Cursor had already been adopted by Zapier's product and engineering teams. For GTM, the barrier wasn't the technology itself; it was the setup. Someone who's spent their career in spreadsheets and CRM doesn't automatically know how to configure a development environment. The golden path is step-by-step onboarding: from installation through a fully configured Cursor environment with the right MCP connections (Databricks, Zapier), the right rules, and the right context already loaded. The whole point is removing the 2-hour configuration overhead that otherwise kills adoption on day 1.That context is the shared brain: a structured Google Drive hierarchy with company-level, department-level, team-level, and working group-level folders. The first iteration meant converting existing documentation into markdown files and organizing them into a folder structure that agents could traverse predictably. Lindsay describes the experience of setting it up as oddly satisfying for an ops person who has spent years wishing the organization's institutional knowledge lived somewhere findable instead of scattered across a Google Drive that nobody had cleaned up in years. The goal of the initial build wasn't completeness. It was a working foundation that gave people enough context to get value from their agent setup without needing to build from scratch.The companies operating furthest ahead in AI adoption right now are the ones that treated the shared brain as infrastructure rather than a side project. Getting every GTM employee configured, context-loaded, and working from a shared knowledge base is unglamorous work, but it's the layer every other build depends on.Key takeaway: Before anyone on your GTM team builds anything with AI, create a centralized setup guide that handles environment configuration, approved MCP connections, and context loading from a structured knowledge base. Start with the tools your technical teams are already using and build a version of that golden path for non-technical employees. The 2-hour configuration friction that stops people on day 1 is a solvable problem, and solving it once prevents you from solving it individually for every person who tries to onboard.How Long It Actually Takes to Build a Shared BrainThe shared brain question that comes up in every version of this conversation is a practical one: how long does it actually take? Zapier's first rollout was a 4-week sprint, and the design of that sprint was deliberate about scope. Rather than trying to capture everything the organization knew, the team focused on what Lindsay calls the slow layer of context: things that don't change often. Company strategy documents. Ideal customer profile definitions. Lead and opportunity definitions. Basic playbooks. These documents already existed. The sprint was mostly ...

Enterprise marketing teams struggle with AI implementation beyond basic automation. Patrick Brown, SVP of Global Marketing at Adobe, shares his perspective on scaling AI across complex B2B and B2C marketing operations. Brown discusses why AI excels at content summarization and synthesis but falls short on predictive forecasting, and outlines Adobe's three-pillar framework for integrating AI into experience delivery, measurement systems, and foundational marketing tools.See Privacy Policy at https://art19.com/privacy and California Privacy Notice at https://art19.com/privacy#do-not-sell-my-info.

Enterprise marketing teams struggle with AI implementation beyond basic automation. Patrick Brown, SVP of Global Marketing at Adobe, shares his perspective on scaling AI across complex B2B and B2C marketing operations. Brown discusses why AI excels at content summarization and synthesis but falls short on predictive forecasting, and outlines Adobe's three-pillar framework for integrating AI into experience delivery, measurement systems, and foundational marketing tools.See Privacy Policy at https://art19.com/privacy and California Privacy Notice at https://art19.com/privacy#do-not-sell-my-info.

 EPISODE DESCRIPTION I sat down with Brian Gerrard, founder of PaySlice, who spent seven years living across Latin America before building one of the most human-centered fintech startups I have come across. Brian started by connecting friends in emerging markets with remote jobs, then realized they were losing massive chunks of their income to inflation and bad exchange rates. That led him to build PaySlice , a platform that lets workers access their earned wages daily and get paid in stablecoins instead of a depreciating local currency. We talk about how he grew to nearly 10,000 users mostly through word of mouth, why he chose payroll over remittances, how he is embedding PaySlice into gaming and credit apps with zero customer acquisition cost, and where he sees this going as one point two billion people receive a paycheck every month. This is a real conversation about real problems, real traction, and what it actually takes to build something that matters. DISCLAIMERNothing mentioned in this podcast is investment advice and please do your own research. It would mean a lot if you can leave a review of this podcast on Apple Podcasts or Spotify and share this podcast with a friend. Be a guest on the podcast or contact us - https://www.web3pod.xyz/ CONNECT PaySlice Website: https://www.payslice.comBrian Gerrard LinkedIn: https://www.linkedin.com/in/brianjgerrard/Brian Gerrard Email: mailto:brian@payslice.comWeb3 with Sam Kamani: https://www.web3pod.xyz/ KEY POINTS WITH TIMESTAMPS • [00:01] Sam introduces Brian Gerrard from PaySlice and the show's focus on payment infrastructure innovation• [01:36] Brian shares his background , leaving San Francisco to explore Latin America, which turned into a seven-year journey• [02:59] How Brian's staffing agency workers in Argentina, Colombia, and Jamaica asked to be paid daily and in USD, sparking the PaySlice idea• [03:58] PaySlice launches and grows to nearly 10,000 employees on the platform• [05:04] Why stablecoins have real product-market fit , stablecoin transaction volumes now surpassing Visa and Mastercard combined• [07:18] The B2C and B2B sides of PaySlice and which industries are gaining traction, including staffing agencies and payroll companies• [09:30] How traditional payroll tools force-convert currencies and silently take 3.5% from employees without employers knowing• [12:08] How PaySlice acquired most of its users through word-of-mouth and a referral boost mechanic• [13:21] Plans for a physical card launch in 18 countries in Q3 or Q4• [16:34] Brian's growth marketing background at Twitch, where he scaled to 25 million monthly active users• [17:44] Using paid advertising in English and Spanish to target the US-Latin America remittance corridor• [19:08] How analyzing user transaction data via Plaid led to zero-CAC distribution deals with credit repair and mobile gaming companies• [21:03] Companies Brian admires , Revolut and Wise for solving currency frustration at scale• [22:22] The most misunderstood part of crypto-powered payroll and why employers need more empathy toward employees in unstable currencies• [23:05] Founder advice: listen to the market, hold beliefs loosely, and recognize the difference between good struggle and the wrong fit• [30:29] Brian's 10-year vision , getting 1.2 billion monthly paycheck recipients paid every day instead of once a month• [31:27] PaySlice's current seed raise, embedded finance partnership opportunities, and revenue share model

Trae Sterling is a seasoned executive with more than three decades of experience spanning real estate, home warranty,  and insurance. Known for driving revenue growth, building high-performing teams, and executing strategic expansion initiatives, Trae has consistently delivered results across both B2B and B2C organizations. Currently serving as Executive Vice President and National Sales Director for Real Estate at Choice Home Warranty, Trae leads the company's national growth strategy within the real estate sector, leveraging a strong consumer foundation to expand market share and deepen industry partnerships. Throughout his career, Trae has held senior leadership roles with organizations including Home Warranty of America, Entitle Direct Group, First American Home Warranty, and American Home Shield. He has successfully led multi-state operations, managed large sales organizations, and implemented scalable growth strategies—earning recognition such as "Manager of the Year" and delivering consistent year-over-year performance gains. Trae's core strengths include integrated sales strategy, leadership development, performance management, and business expansion. He is widely respected for his ability to motivate teams, build strong partnerships, and translate complex business objectives into actionable results. A licensed real estate broker in Tennessee, Trae remains deeply connected to the industry that shaped his career. He is also actively involved in community service, supporting organizations such as Youth Villages and St. Jude Children's Research Hospital.    In this episode, Karen and Trae discuss: Success Story of Trae Commit to Get Leads The fundamentals will still work. Use the technology and tools that are now available, like CRMs and automations, but you still have to go to the people who are producing to make contacts.  Consult to Sell Teach your consumers how you can solve their problems, even the ones they don't realize are a problem yet.  Connect to Build and Grow Utilize your database. Drip on your database every single month with information of value.  Success Thinking, Activities, and Vision Empower your team by asking what they want and putting them in the best spot to be able to do that.  Sweet Spot of Success   "I think one component that sometimes gets lost is if you're not having fun, you shouldn't do it." - Trae Sterling   Connect with Trae Sterling: Website: https://chwpro.com/  Email: tsterling@chwpro.com  LinkedIn: https://www.linkedin.com/in/trae-sterling-2448709  Instagram: https://www.instagram.com/silvertrae/  Facebook: https://www.facebook.com/trae.sterling    About the Podcast Join host Karen Briscoe each month to learn how you can achieve success at a higher level by investing just 5 minutes a day! Tune in to hear powerful, inspirational success stories and expert insights from entrepreneurs, business owners, industry leaders, and real estate agents that will transform your business and life. Karen shares a-ha moments that have shaped her career and discusses key concepts from her book Real Estate Success in 5 Minutes a Day: Secrets of a Top Agent Revealed. Here's to your success in business and in life!   Connect with Karen Briscoe: Facebook: 5MinuteSuccess Website: 5MinuteSuccess.com Email: Karen@5MinuteSuccess.com   5 Minute Success Links Learn more about Karen's book, Real Estate Success in 5 Minutes a Day Karen also recommends Moira Lethbridge's book "Savvy Woman in 5 Minutes a Day." Subscribe to the 5 Minute Success Podcast   Spread the love and share the secrets of 5 Minute Success with your friends and colleagues!     Audio production by Turnkey Podcast Productions. You're the expert. Your podcast will prove it.

Your blog will never earn an audience. Ever. That's not me — that's Melissa Rosenthal, who ran the SEO content engine at ClickUp, built media at BuzzFeed and Cheddar, and is now co-founder of Outlever building the playbook that replaces it. In this episode, Melissa makes the case that the SEO blog era is collapsing in real time, that one strategic LinkedIn poster will out-perform 150 employees doing employee advocacy, and that while every other B2B operator is betting on AI, she's betting on humans — and using AI to do it. She's also dogfooding the entire thesis with her new publication, The State of Brand, which hit a million unique views in three weeks.   What you'll learn • Why the SEO blog was a 'slot machine' — and what survives the AI search collapse • The two-month consistency rule that separates real owned media from content theater • Why one strategic LinkedIn poster beats 150 employees doing employee advocacy • The one-to-one distribution playbook replacing mass organic traffic • How Melissa's State of Brand publication converts at ~40% to demo on banner ads (yes, banner ads) • Why product parity is now enough to beat 15-year incumbents — if your brand, service, and POV are sharper   Connect Melissa Rosenthal on LinkedIn The State of Brand Outlever Marketing Trends   Chapters • 0:00   The SEO blog era is over • 1:30   What's lighting Melissa up: State of Brand hits 1M views in 3 weeks • 4:30   BuzzFeed → Cheddar → ClickUp: why B2B needs B2C instincts • 7:33   Why Outlever built its own publication (and dogfooded the thesis) • 13:00  How to make B2B content go viral without AI slop • 18:50  Quality vs quantity: the false binary killing content teams • 22:14  Why one strategic poster beats 150 employees • 25:37  The two-month consistency rule • 26:33  'Your blog will never earn an audience' • 30:17  Everyone says video-first. She's going text-first. • 32:24  Melissa is excited about banner ads (yes, really) • 37:00  'Figma should be a little worried' • 40:04  You don't need a better product to beat a 15-year incumbent • 43:14  Betting on humans while everyone else bets on AI • 53:44  $50B incumbents can be beaten in 18 months   ----Mission.org is a media studio producing content alongside world-class clients. Learn more at mission.org. Hosted by Simplecast, an AdsWizz company. See pcm.adswizz.com for information about our collection and use of personal data for advertising.

Snap Inc.'s Sid Malhotra makes the case that the platform most brands wrote off as "babies and teens" has quietly grown up. Now, commerce is migrating into these private, conversational spaces where nearly one billion users actually spend their time. We dig into why the traditional funnel no longer holds consumers' nuanced behaviors, how creators and chat shape decisions long before the last click, and what AI Sponsored Snaps mean for brands willing to be the answer rather than just another link. Where Are Your Next New Customers? Key takeaways: Snapchat's earliest users grew up; nearly one in four Snapchatters is now aged 35+. Purchase decisions increasingly occur in private chat, not on public feeds or in search. "Last-click jail" hides where customers actually decide. It's imperative that brands measure the full journey. AI Sponsored Snaps let brands run their own agents inside the chat feed. This is conversational commerce, in context. Authentic, creator-led, low-fi content beats polished commercials on the platform. Key quotes: [03:57] "We've come into the age where people are loving a few services and are hanging onto them and are creating their own personal community within those… And that brings me to the final question that Snapchat is trying to answer for businesses and brands worldwide: Where are your next first customers? Where are your next new customers?" — Sid Malhotra [16:27] "Last-click measurement systems are great at telling [you] where the purchase took place. But it doesn't tell you much more than that. It's kind of like trying to watch a movie by just watching the last scene…Sure, you know how the movie ended, but you have no idea what the main characters were doing, what the plot line was, and what got them here." — Sid Malhotra [19:55] "Working with influencers and community is closer to B2B commerce than B2C commerce…B2B has done a really good job of building real relationships, engaging with people where they're at, and finding the things that they care about in the process of selling to them." — Brian Lange Associated Links: Check out Future Commerce on YouTube Check out Future Commerce Plus for exclusive content and save on merch and print Subscribe to Insiders and The Senses to read more about what we are witnessing in the commerce world Listen to our other episodes of Future Commerce Have any questions or comments about the show? Let us know on futurecommerce.com, or reach out to us on Twitter, Facebook, Instagram, or LinkedIn. We love hearing from our listeners! Hosted by Simplecast, an AdsWizz company. See pcm.adswizz.com for information about our collection and use of personal data for advertising.

IN CLEAR FOCUS: June's Bigeye Book Club selection is "Neuromarketing: Practical Insights for Improving Customer Engagement." Author Katie Hart explains why, when 95 percent of purchase decisions are non-conscious, traditional research often asks the wrong questions. Learn how neuromarketing reveals real consumer behavior, why the brain processes images faster than text, and the physiological impact of 2D screens. We also discuss Katie's practical framework for transforming B2B and B2C strategies.

Send us Fan MailOne of Gorilla's franchisees runs his entire business from a cruise ship in Greece — nine vans, all from his phone. That's not a gimmick. It's the model. This week the team sits down with Andrew Edwards, owner of Gorilla Property Services,  to break down what might be the most overlooked home services franchise in the market: a high-tech, 100% mobile exterior cleaning and maintenance brand built on B2C and B2B recurring revenue. Gorilla bundles eight essential services — pressure washing, window and gutter cleaning, roof cleaning, dryer vent cleaning, graffiti and snow removal — into a single "one call" relationship, much of it required by insurance carriers and local bylaws. That's demand that doesn't disappear in a downturn. Andrew is the rare franchisor who's actually been a franchisee — he built and sold a business before reshaping Gorilla into a system designed to make owners better operators, not buy them a job. In this episode: The proprietary, AI-powered CRM (Gorilla Pro) that runs the whole business from a phoneWhy recurring revenue made Jack & Jill's Pinks exit sell for ~10x netThe B2B vs. B2C cash-flow balance every home services owner needs to understandWhy this model is largely insulated from AI disruptionRealistic numbers: per Gorilla's Item 19, Canadian franchisees averaged $666,233 in revenue and $162,388 in net income (Jan–Dec 2024) at a 49% gross margin. U.S. results may differ — see the FDD.Low investment, highly scalable, home-based, and VetFran-approved. If you've been waiting on BizBuySell for the "perfect business," this is the conversation that reframes the math. Some markets are already gone — Chicago, Tampa, Boca Raton. Check if yours is still open:

If you're running a B2C business and you're not on LinkedIn - you're leaving serious money on the table. And I'm not just talking about a few missed connections. I'm talking about referrals, speaking gigs, media features, and high-ticket clients who found you, vetted you, and said YES - all because of one thing: your LinkedIn presence. In this episode, I'm breaking the myth that LinkedIn is only for corporate types or B2B brands. Whether you're a coach, consultant, service provider, or creative - if relationships and trust drive your business, LinkedIn is your secret weapon. Here's what you'll learn: Why affluent buyers vet you on LinkedIn before they ever reach out How LinkedIn referrals compound over time - even while you're at the beach The difference between attention (Instagram) and authority (LinkedIn) Why your content works harder and longer on LinkedIn than anywhere else 5 simple action steps you can take this week to start building your LinkedIn presence Ready to stop being invisible online? Grab a pen - your homework is at the end.   Resources Mentioned In The Episode: Monetize Your Magic Karen's FREE weekly training on LinkedIn strategy https://www.thelinkedupcollective.com/masterclass  Visibility SalonKaren's signature program for building LinkedIn visibility and authority https://www.thelinkedupcollective.com/visibilitysalon/ Good Girls Get Rich Podcast Weekly podcast hosted by Karen Yankovich www.KarenYankovich.com/podcast  BSchool by Maria Forleo Business training program for online entrepreneurs https://www.marieforleo.com/bschool Karen Yankovich on LinkedIn www.linkedin.com/in/karenyankovich   Magical Quotes From The Episode: "The women who win in the next decade aren't necessarily the ones posting the most content. They're the ones becoming known, trusted, referenced, and recommended." "Visibility without credibility just creates more noise. Visibility with positioning - that's where the real opportunities happen." "Your goal isn't to become internet famous. Your goal is to become professionally unforgettable."   Help Us Spread The Word! It would be awesome if you shared the Good Girls Get Rich Podcast with your fellow entrepreneurs on Twitter. Click here to tweet some love! If this episode has taught you just one thing, I would love if you could head on over to Apple Podcasts and SUBSCRIBE TO THE SHOW! And if you're moved to, kindly leave us a rating and review. Maybe you'll get a shout out on the show!   Ways to Subscribe to Good Girls Get Rich: Click here to subscribe via Apple Podcasts Click here to subscribe via PlayerFM Good Girls Get Rich is also on Spotify Take a listen on Podcast Addict

Bob Verlaat and Nick Nijhof are Amsterdam-based entrepreneurs and Co-Founders of Hears, the fast-growing hearing protection brand redefining earplugs through premium design and industry-leading sound clarity. Prior to Hears, the duo successfully scaled luxury sleep wellness brand Dore & Rose to $30M in revenue, building deep expertise in branding, Ecommerce, and consumer behavior. Their entrepreneurial journey has been shaped by creating products that solve real consumer problems while building emotionally resonant brands. After Bob experienced hearing damage and persistent tinnitus from loud music, the pair became increasingly aware of the global problem of noise-induced hearing loss and the lack of earplugs people actually wanted to wear. Existing products compromised sound quality, looked unattractive, and failed to fit seamlessly into modern lifestyles. Driven by that personal frustration, Bob and Nick spent 1.5 years researching and developing Hears from scratch, investing in patented filter technology and an award-winning heart-shaped design focused on preserving natural sound while protecting hearing. Since launching in 2024, Hears has generated $7M in first-year revenue, won the Red Dot Design Award, and partnered with globally recognized brands and venues including Yves Saint Laurent and Pacha Ibiza. In This Conversation We Discuss: [00:32] Intro [00:58] Launching products with clear positioning  [01:31] Solving everyday problems through Ecommerce  [03:14] Leveraging past mistakes to scale faster  [06:33] Episode Sponsor: Klaviyo [08:32] Finding product ideas through personal pain  [09:49] Testing creatives to accelerate growth  [11:01] Balancing brand building with direct sales  [11:57] Leveraging organic content before paid scaling  [13:51] Episode Sponsor: Intelligems [15:52] Optimizing products for global scalability  [19:14] Episode Sponsor: Electric Eye [20:23] Designing products customers instantly notice  [22:20] Protecting products through patented innovation  [23:25] Callout [23:34] Using social proof to increase conversions  Resources: Subscribe to Honest Ecommerce on Youtube Engineered for maximum sound blocking, reduce disruptive noise, helping you fall asleep faster, stay asleep longer and wake up fully rested hears.com/ Follow Bob Verlaat linkedin.com/in/bobverlaat/ Follow Nick Nijhof https://www.linkedin.com/in/nicknijhof/ Book a demo today at intelligems.io/ Migrate and grow more klaviyo.com/honest  Schedule an intro call with one of our experts electriceye.io/connect If you're enjoying the show, we'd love it if you left Honest Ecommerce a review on Apple Podcasts. It makes a huge impact on the success of the podcast, and we love reading every one of your reviews!

In this episode of Medsider Radio, we sat down with Karthik Ganesh, CEO of OnMed.OnMed is the healthcare technology company behind OnMed CareStation, a “Clinic-in-a-Box” designed to expand access to primary and urgent care. Before OnMed, Karthik served as CEO of EmpiRx Health, leading the company through rapid growth and a successful private equity transaction in 2021. Throughout his career, he's held leadership roles at QualCare, CareAllies, and Aetna, and advised healthcare organizations through Deloitte and EY.In this interview, Karthik discusses why hybrid care models still require a human touch, how enterprise healthcare buyers evaluate value propositions differently, why brand and culture should shape execution early, and how operating under constraints can sharpen innovation.Before we dive into the discussion, I wanted to mention a few things:First, if you're into learning from medical device founders and CEOs and want to know when new interviews are live, head over to Medsider.com and sign up for our free newsletter.And if you're ready to level up your medtech game, you should check out Medsider Courses — 8-week masterclasses covering topics like fundraising, M&A and exit planning, design and development, clinical and regulatory strategy, and commercialization.These courses, featuring hard-earned lessons from elite medtech CEOs, can be purchased individually or come free with our All-Access Pass.If you'd rather read than listen, here's a link to the full interview with Karthik Ganesh, which includes a link to ScottBot — an AI version of host Scott Nelson trained on every Medsider interview and playbook. Feel free to ask ScottBot any questions you'd like!KEY MOMENTS FROM THE INTERVIEW(03:04) - Karthik's obsession with healthcare access, and the “broken doorway” problem behind OnMed (05:51) - How OnMed combines telemedicine and brick-and-mortar care into a “Clinic in a Box” (09:04) - The OnMed metrics that surprised Karthik most, including a 37% patient return rate, and the reasons behind the company's success (09:22) - What OnMed designed differently after realizing that patients approach healthcare with their guard up (15:27) - The pitfalls of B2C healthcare and how OnMed was built as a B2B company by intention (22:01) - How Karthik reshaped OnMed around clarity, structure, and high performers (30:23) - What “brand” actually means to Karthik (39:37) - How OnMed tailored its value proposition for payers, providers, employers, and universities (45:45) - Karthik's fundraising philosophy: constraints keep companies inventive

Most scaled independents looked at Grapevine.ai during the sale process and didn't get it. They couldn't process the economic model. They didn't know how to assess the technology. Justin Hayashi leaned in and won.Recorded at Possible 2026 in the Unplugged Collective pavilion, Christian Hassold and Ayelet Shipley sat down with Justin Hayashi, CEO of NewEngen, one of the most tech-forward independents in the market to break down how he thinks about acquisitions, what makes NewEngen genuinely different from its peers, and what he's looking for next.NewEngen started in 2016 as a tech company trying to dethrone Marin Software, among others. It evolved into the agency their clients always said they were and built a platform around content, creator marketing, and measurement that most of their competitors can't replicate.What we cover: The origin story; from Zulily's IPO to trying to build a bidding algorithm to accidentally building an agency, how three acquisitions in the content and creator space shaped NewEngen's differentiated positioning, the Grapevine.ai deal thesis and why beating an aggressive forecast during diligence was the final proof of conviction, how NewEngen handles integration with a "do no harm" philosophy while keeping brands like Donut Studios intentionally separate, and the buy box for what comes next: social, content, measurement, and commerce.⏱️ TIMESTAMPS00:12: Cold open: does the YC target on agency backs keep you up at night?1:08: Welcome and guest intro: Justin Hayashi, CEO of NewEngen, at Possible 20261:19: The backstory: from Zulily IPO and billion-dollar sale to Qurate, to founding NewEngen2:25: The original thesis: dethrone Marin Software and Kenshoo — and why it didn't work3:58: The pivot: from SaaS company (that clients kept calling an agency) to what NewEngen is today4:28: Tech-enabled DNA: what survived the pivot and what defines NewEngen now5:54: What scaled independents are getting wrong — and where NewEngen differentiates6:45: Three acquisitions in the content and creator space: why content was always the bet7:23: The Grapevine.ai deal: why most scaled independents walked away and NewEngen stepped up8:04: Why Caroline's conviction and operator mindset won the first filter9:00: 900 vetted, high-performing creators vs. seven million claims — the quality argument10:29: Two lenses: founder CEO conviction vs. PE underwriting — how Justin navigated both11:06: The aggressive forecast, the bottoms-up conviction, and what actually happened11:30: Zuckerberg's earnings calls as diligence data: short-form video growth 20% → 30% YoY12:43: What made Grapevine.ai hard for strategic buyers: long-tail revenue and small contracts13:37: How Caroline's client migration story played out in real time during diligence15:19: Donut Digital acquisition: "do no harm" integration and why they kept the brand16:45: LT Partners vs. Acorn Influence vs. Donut Studios: three different integration approaches17:57: The hardest integration lesson: get alignment on goalposts before you close18:59: Buy box: social/content, measurement, commerce, B2C only, $3-12M revenue sweet spot21:02: Closing take: NewEngen is the software-led agency ready to take on Silicon Valley

What if the resume — that document we've built our entire hiring process around — is the wrong place to start? Jason P. Carroll makes a compelling case that it is. Drawing on research from the 1980s and 90s, he points out that prior skills, experience, and formal education have almost zero predictive value for success in a new role. Add AI-generated resumes to that picture, and the traditional hiring process starts to look like a relic. Jason's company, Aptive Index, approaches the problem differently. Rather than measuring what someone has done, it measures what drives them — motivators, emotional resonance, internal activation, cognitive style. The platform pairs that psychometric data with Aria, a behavioral AI that knows your team's profiles and can guide everything from hiring decisions to conflict resolution to job description writing. The conversation takes some unexpected turns. Jason shares stories of clients using Aria as a personal growth tool — including two CEOs who credited it with saving their marriages. He talks about a CEO forum where Aria identified, in real time, that one member felt like an outsider in the group — and was right. And he opens up about a B2C mental health companion product he's developing but hasn't launched yet, and why he's looking for the right co-founder to help bring it to life. Running through all of it is a theme that fits squarely in the Coffee and Change ethos: self-awareness as the foundation for change — in how we hire, how we lead, how we relate to the people around us, and ultimately how we understand ourselves. Curious what Aptive Index would reveal about you? Jason has set up a dedicated link for Coffee and Change listeners to take the assessment and get a preview of Aria: https://assessment.aptiveindex.com/s/sH5bgSZVQVy0 The assessment takes about ten minutes. At the end, you'll get a preview of Aria and the chance to ask her a few questions based on your results. Connect with Jason Aptive Index: aptiveindex.com B2C / Mental Health Companion (coming soon): aria.com — Jason is actively looking for a co-founder with B2C experience. If that's you, reach out.

Sign Up For Relay through My Referral Link: ⁠https://join.relayfi.com/partner/?referralcode=temporaryhousingmeetup&utm_source=events&utm_medium=…⁠In this eye-opening episode of In The Lab, Ruben breaks down one of the biggest misconceptions in entrepreneurship and real estate investing: confusing an asset class vs. building an actual business. Too many people say they want to “quit their W2 through real estate,” but never stop to ask the deeper question… are they trying to become an investor or build a business machine that produces cash flow at scale?Throughout the episode, Ruben unpacks the difference between long-term investing, operating a real estate business, and using business income to fund wealth-building assets. He explains why most successful entrepreneurs didn't get wealthy from the asset class itself first, but from the business engine behind it. From wholesalers and flippers to coaches, syndicators, and short-term rental operators, Ruben challenges listeners to study how people actually made their money instead of blindly copying the final product.He also dives deep into the importance of context when making business decisions. Instead of asking generic questions like “What's the best strategy?” Ruben explains why better outcomes come from reverse engineering your goals based on your skills, location, liquidity, lifestyle, time availability, and long-term vision. The episode also explores why B2B businesses create leverage faster than B2C models, and why AI may be the greatest business opportunity window modern entrepreneurs have ever seen.Tune in now to learn why “the math has to math,” how to stop chasing misleading business models, and why understanding the difference between owning assets and operating a business could completely change your financial future.#EntrepreneurMindset #BusinessGrowth #RealEstateInvesting #WealthBuilding #AssetVsBusiness #QuitYourW2 #B2BStrategy #AIForEntrepreneurs #FinancialFreedom #InTheLab

What This Episode Is About You've invested in a sales strategy. You've done the training. So why aren't you getting the results you expected? In this episode of the Selling to Corporate® podcast, Jess Lorimer reveals the single most important skill that professional salespeople use to create consistent, replicable results - and it's almost certainly not what you'd expect. Jess makes the case that the gap between coaches, consultants and professional salespeople isn't intelligence, experience or even strategy. It's one surprisingly simple skill that most business owners overlook, underestimate or quietly choose to ignore. This episode explains exactly what it is, why it matters more than any tactic or technique and what happens to your sales process when you don't use it. Who This Episode Is For Coaches, consultants, trainers, speakers, and done-for-you service providers selling to corporate clients Anyone who has invested in a sales strategy or programme and felt it 'didn't work' Business owners who find themselves constantly tweaking, adjusting, or second-guessing their sales process Those who are great at selling one offer or to one type of client, but struggle to replicate that success elsewhere Anyone who suspects their sales process isn't producing consistent results but isn't sure why Questions This Episode Answers What is the most important skill in B2B sales? Why does a sales strategy that worked stop working over time? How do professional salespeople create replicable results across different industries and offers? What's the difference between buying a sales strategy and actually executing one? Why does tweaking a sales process - even slightly - make results impossible to measure or replicate? Key Takeaways  1. The Most Important Sales Skill Is Following Instructions The single most important skill professional salespeople possess is the ability to follow instructions precisely and consistently. Not prospecting. Not objection handling. Not closing. Following instructions. Jess is direct: in her experience working with thousands of professional salespeople and thousands of coaches, consultants, speakers, trainers, and done-for-you service providers, the difference in results almost always comes down to this. Professional salespeople follow a proven process exactly as written. Most coaches and consultants - however intelligent and however well-intentioned - don't. This isn't a criticism of intelligence. In fact, Jess argues that high intelligence can be a liability here. Smart people are more likely to spot what feels 'wrong' about a set of instructions, more likely to rationalise a small adjustment and more likely to believe their version of the process is 'good enough'. It usually isn't. 2. Any Proven Strategy Has the Ability to Work - If It's Executed Properly Jess teaches seven different methods of B2B lead generation. She has clients who generate all of their corporate revenue from cold email outreach. She has clients who generate all of their revenue from networking alone - a method she personally dislikes. The method is not the determining factor. Execution is. The two reasons a sales strategy fails are almost always the same: The strategy being used is not proven. It was built in an AI tool, borrowed from a B2C context or sold by someone without hands-on B2B sales experience. The strategy is proven but it is not being followed correctly. Steps are skipped, wording is changed, volume is reduced or the process is quietly adjusted whenever something feels uncomfortable. If your sales process is not producing results, the first question to ask is not 'what strategy should I try next?' It is 'am I executing my current proven strategy exactly as intended?'   3. Small Changes to a Sales Process Create Big Problems One of the most common patterns Jess sees with experienced clients is a gradual drift away from the original process. It rarely starts as a conscious decision to change strategy. More often it starts with a lost deal, a knock to confidence, and a small adjustment made under pressure to 'save' the next opportunity. That one small change leads to another. The language shifts. The attachment changes. The objection handling softens. The reassurance given increases. None of it feels significant in the moment. But cumulatively, the process becomes unrecognisable - and critically, it becomes impossible to measure, troubleshoot or improve. Standardisation is not a constraint on creativity. It is what makes it possible to know whether your sales process is working, identify where it is breaking down, and fix the right thing. When every part of the process is slightly different, there is nothing consistent to evaluate. 4. Sales Should Be Boring - Creativity Comes in the Conversation Jess uses the analogy of Picasso: before he painted eyes on the sides of heads, he spent years learning the rules of perspective, line and composition. The creative leaps came after the foundations were mastered, not instead of them. The same principle applies to B2B sales. Your lead generation process, your outreach approach, your proposal structure, your pricing framework - these should be repeatable, measurable and consistent. They should feel a little boring, because boring is what makes them scalable. The creativity, the consultative problem-solving, the bespoke solution-building - all of that happens in the sales conversation itself, and in the delivery of the work. That's where you get to be brilliant and distinctive. Your process is what gets you to that conversation in the first place. 5. Following Instructions Builds the Confidence That Creativity Cannot When a sales process is followed precisely, it produces predictable metrics. Those metrics tell you what is working and what is not - early enough to make useful adjustments rather than emergency ones. That predictability is what gives professional salespeople confidence, even in difficult markets. When a process is modified and the results decline, the person executing it has no way of knowing which change caused the problem. That uncertainty erodes confidence and often leads to further changes, making the situation worse. Following instructions is therefore not just a technical requirement - it is the foundation of sustained confidence in your own sales ability. 6. Replicatable Success Requires Transferable Process, Not Transferable Luck Jess draws on her own sales career across jewellery, recruitment, tech, and sales training - including becoming the top diamond salesperson in her region at 16, and a top performer within her first year at a company operating across 30 countries - to make a specific point: success that can be replicated across industries, offers, and client types is built on process, not personality. If you are excellent at selling one particular offer but cannot replicate that success with other offers or other types of decision maker, it is a signal that your results are not yet built on a transferable process. They are built on familiarity, repetition or relationship - which are not scalable. A proven, correctly executed process is what creates results that transfer. Key Quotes "The most important skill professional salespeople have in their arsenal is following instructions." "Literally any proven strategy has the ability to work if it's being done properly. The problem is that most people aren't using proven strategies - or they're not following the instructions for the ones they have." "Your sales process shouldn't be where you feel creatively satiated. It should be where you are able to replicate a clear process and be given consistent metrics so you know what is working and what isn't." Resources + Links Mentioned in This Episode Cold -> Closed The self-paced B2B sales experience for coaches / consultants / speakers / trainers and done-for-you service providers who want scalable, sustainable sales from brand new corporate clients in 90 days or less. https://smartleaderssell.thrivecart.com/-cold-to-closed-product/ Join the B2B Sales Edit: Busyness to Business Weekly newsletter for coaches and consultants; sharing the real B2B sales techniques that have taken over 30,000 sales processes from busy -> balanced and profitable. https://magic.beehiiv.com/v1/988ac64b-5875-4924-9d10-50faad2aa4ad?email=%EMAIL% Episode Sponsored by The Expert Services Directory Access The Expert Services Directory here and use code PODCAST for a special bonus. https://bit.ly/ExpertServicesDirectory A curated directory that proactively markets your services to corporate decision makers every month. Standard listings reach 1,000+ decision makers per month; Directory Plus listings reach 2,000+. Only 10 suppliers per category. Standard listing: 1,000+ decision makers per month Directory Plus listing: 2,000+ decision makers per month Application required — not all applications are accepted If You've Enjoyed Listening to The Most Important Skill Professional Salespeople Have, Check Out These Episodes STC159 - Mindset Wobbles That Stop Your B2B Sales Progress (and How to Fix Them!) https://bit.ly/SellingToCorporate159 STC162 - 3 Things That Will Help You Maximise Any Sales Training You're Embarking On https://bit.ly/SellingToCorporate162 STC171 - The Simple Sales Technique I Use to Sign Corporate Clients Every Month https://bit.ly/SellingToCorporate171   Content Disclaimer The information contained above is provided for information purposes only. The contents of this article, video or audio are not intended to amount to advice and you should not rely on any of the contents of this article, video or audio. Professional advice should be obtained before taking or refraining from taking any action as a result of the contents of this article, video or audio. Jessica Lorimer disclaims all liability and responsibility arising from any reliance placed on any of the contents of this article, video or audio.  

Imagine having the power of an entire engineering team right from your browser without writing a single line of complex code. In this episode, we dive into how everyday consumers are building autonomous systems and personal cloud servers to automate their lives.   Jake Aaron Villarreal sits down with Ben Guo, the visionary founder and president of Zo Computer, to explore the platform being called the AWS for everyday people. After spending eight years scaling developer platforms at Stripe, Ben is now on a mission to democratize cloud computing by giving non-technical users root-level access to their own private infrastructure.   We explore the fascinating pivot from a B2B inference platform to a B2C consumer product that recently closed a Series A funding round. Ben shares how intuitive tools like Zo are replacing complex setups like OpenClaw, allowing users to host personal websites, automate backend accounting, and run autonomous agents with zero technical barriers.   Whether you are a solopreneur, a small business owner, or someone who wants true ownership over their data and digital presence, this conversation reveals the next major evolution in the internet. Discover how you can stop renting space on the web and start owning your very own home on the internet.   Chapters 00:00 Introduction and Guest Background 01:11 Ben Guo's Career Journey from Venmo to ZoComputer 02:19 Building Stripe Terminal and Early Product Development 04:37 Pivoting from B2B to B2C with AI Focus 07:03 The Vision for Democratizing Cloud Computing 09:22 Zo's User-Friendly Platform for Non-Technical Users 11:06 Getting Started with Zo and Infrastructure Setup 13:41 Security, Data Privacy, and Infrastructure Control 19:22 Market Focus and Growth Strategy 22:09 Team Building and Company Milestones 32:13 Community Building and Ambassador Program 34:05 Zo's Sales and Growth via Community Engagement 35:06 Closing Remarks and Contact Information   Host: Jake Aaron Villarreal leads the top AI recruitment firm in Silicon Valley, www.matchrelevant.com, uncovering stories of funded startups and going behind the scenes to tell their founders' journeys. If you are growing an AI startup or have a great story to tell, email us at: jake.villarreal@matchrelevant.com

Dave and Julie record with the office doors wide open to enjoy an unusually hot day here in royal Deeside, and a quick run for cold drinks sparks an unexpected marketing lesson about the "famous brand rule". The discussion flows naturally toward the topic of the power of social proof in the B2B space. Unlike world-renowned B2C brands such as Adidas, lesser-known B2B companies must rely heavily on case studies, certifications, and social proof to make buyers feel safe. We discuss the dangers of using confusing, engineering-led product names and turned out Dyson's intricate model numbers was a perfect illustration of that, often leaving consumers unable to make an easy choice.   On the second half od this episode, the conversation shifts to a deep dive into Google's recent major announcements, including their plan to weave sponsored product ads directly into conversational AI responses. Will this turn out to be an innovative move or just an unimaginative reaction to losing search traffic to ad-free platforms like Claude...? Julie also touches on the transition from dynamic search ads to AI Max, which aims to offer advertisers more control over their assets, and Google's new focus on tracking "qualified future conversions" to better accommodate long B2B sales cycles.   The episode wraps up with staggering statistics on AI search adoption, noting that AI mode now boasts over one billion monthly users with increasingly long follow-up queries.   Dave and Julie record with the office doors wide open to enjoy an unusually hot day here in Royal Deeside, where a quick run for cold drinks sparks an unexpected marketing lesson about the "famous brand rule". The discussion flows naturally toward the power of social proof in the B2B space. Unlike world-renowned B2C brands such as Adidas, lesser-known B2B companies must rely heavily on case studies, certifications, and social proof to make buyers feel safe.   Discussing the dangers of using confusing, engineering-led product names, Dave and Julie bring up Dyson's intricate model numbers that serve as a perfect illustration of this, as they often leave consumers confused and unable to make an easy choice.   In the second half of the episode, the conversation shifts to a deep dive into Google's recent major announcements, including their plan to weave sponsored product ads directly into conversational AI responses. Julie and Dave debate whether this will turn out to be an innovative move, or just an unimaginative reaction to losing search traffic to ad-free platforms like Claude. Julie also touches on the transition from dynamic search ads to AI Max, which aims to offer advertisers more control over their assets, and Google's new focus on tracking "qualified future conversions" to better accommodate long B2B sales cycles.   The episode wraps up with some staggering statistics on AI search adoption, noting that AI mode now boasts over one billion monthly users who are typing in increasingly long follow-up queries.   And as plugged multiple times throughout the show, be sure to go and listen to the Uncensored CMO podcast to hear the full conversation with Rory Sutherland and Tom Goodwin.

Purna Virji is back on the Digital Marketing Mentor for a second round, and this time she's talking about the intersection of AI strategy and executive content, two elements of content marketing that are transforming consumer trust and loyalty.Since Episode 62, Purna has expanded her role at LinkedIn to Applied AI Strategy Lead, and she brings that lens to a conversation about why human storytelling has never been more valuable. Plus, she details how AI fits into the equation without replacing the voice behind it.Episode Highlights:Purna shares why the rise of AI has made human storytelling more valuable, not less, and what the salary data on executive content roles actually signals about where the industry is heading.This discussion uncovers specific stats behind well-executed founder-led marketing: more leads, larger deal sizes, and faster pipeline when executives show up consistently.Purna shares three executive story types that work across all stages of the buyer journey, from completely unaware to ready to buy.She gives insights into extracting high-quality content from a time-strapped executive without asking them to write a single word.Purna revisits a topic she shared in her previous episode with Danny, diving deeper into why repurposing content isn't repetitive, and why reformatting content across channels is both an instructional design principle and a practical reach strategy.Episode Links: Episode 62 with Purna Virji: The Queen of Content SolutionsPurna on LinkedIn: linkedin.com/in/purnavirjiHigh Impact Content Marketing: AmazonFounder-Led Sales and Marketing Never Ends (Playbook): Download on LinkedInSend us Fan MailFollow The Digital Marketing Mentor:Website and Blog: thedmmentor.comInstagram: @thedmmentorLinkedin: @thedmmentorYouTube: @thedmmentorInterested in Digital Marketing Services, Careers, or Courses? Check out more from the TDMM Family:Optidge.com - Full Service Digital Marketing Agency specializing in SEO, PPC, Paid Social, and Lead Generation efforts for established B2C and B2B businesses and organizations.ODEOacademy.com - Digital Marketing online education and course platform. ODEO gives you solid digital marketing knowledge to launch/boost your career or understand your business's digital marketing strategy.

In this episode of the Sports Tech AllStars Podcast, we present Juan Fuentes Fernandez, Director at GSIC Valencia and Co-Chair of EBAN Sports, the sports vertical at the European Business Angel Network.The conversation explores why European sports tech investment remains fragmented, why industry insiders and experienced investors rarely occupy the same room, and what Juan is building across two organisations to close that gap from a testing lab in Valencia certifying pre-market technologies to a pan-European angel network connecting deal flow across borders.TakeawaysSports tech has two separate worlds - industry insiders who understand the market and experienced investors who have done exitsGSIC Valencia is a testing lab that certifies sports technologies across up to 60 metrics in cooperation with 58 Valencian sports federationsThe GSIC certification carries real commercial value - it helps startups raise capital and sell to sports organisations that already trust the brandMost business angels invest locally by default - EBAN Sports exists to break down the regulatory and knowledge barriers that prevent cross-border early-stage investment in EuropeThere are not yet enough sports tech unicorn exits to attract experienced investors organically - EBAN Sports is accelerating that by bringing seasoned angels into the spaceAthletes are an underutilised capital source - GSIC is developing bootcamps to help athletes become investors and entrepreneursJuan's investment thesis centres on B2C emerging sports like CrossFit and running, founders with an international mindset, and companies with product-market fit that need help expanding globallyA founder who gets on a plane to raise money in foreign markets is already demonstrating the mentality needed to scale internationallyTo learn more about GSIC: https://sport-gsic.com/ To learn more about EBAN Sports: http://www.eban.org Get in touch with Juan Fuentes Fernandez at: https://www.linkedin.com/in/juanfuentesfernandezHosted by ⁠Rohn Malhotra⁠ from ⁠SportsTechX⁠ - Leading source of Investment and Innovation insights in sports. As promised, here's your small surprise:Unlock your 30-day growth plan (worth €49) on the SportsTechX Intelligence Hub for free!Simply verify your company details and you get access to 1,500+ investors, programmes, initiatives and events in the sportstech ecosystem.Here's how to get set up and if you'd like a walkthrough of the platform, feel free to book a call here.More from SportsTechX:Explore the SportsTechX Intelligence Hub, an interactive database of over 8,000 sports tech companies, 8,000+ deals, 1,000+ investors, programs and events - HEREDownload the latest Global Sports Tech Ecosystem Report - HERESign Up for the Sports Tech Weekly Newsletter for more news, features & insights on Sports Tech - HERE Stay Connected and follow for more:LinkedInYouTubeSpotifyApple PodcastChapters00:00 Introduction02:31 Who Is Juan Fuentes Fernandez - Executive, Investor, Ecosystem Builder04:02 What GSIC Valencia Is and Why It Was Launched05:51 GSIC's Three Chapters 06:33 How the GSIC Testing Lab Works and What Certification Means07:27 Who Can Apply 09:39 How Much Does GSIC Certification Cost and What Is the Process10:49 Upcoming GSIC Initiatives11:57 What EBAN Sports Is and Why Juan Co-Founded It12:45 The Fragmentation Problem in European Sports Tech Investment17:34 Two Worlds That Don't Meet: Industry Insiders vs Experienced Investors18:20 Why Sports Tech Needs Both to Grow20:20 A Year of EBAN Sports 21:07 How Investors and Startups Can Join EBAN Sports23:04 What Is Coming Up on the EBAN Sports Event Calendar23:54 Juan's Personal Investment Thesis 26:00 Nine Portfolio Companies and What Juan Looks for in Founders27:33 How to Connect With Juan on LinkedIn28:09 Favourite Sporting Moment

Elyrea sells a kind of tour no traveler would think to search for, and Jean-Vladimir Deniau built the whole company around that fact.Jean-Vladimir Deniau is the founder of Elyrea, a French company that builds character-based immersive performances for the tourism market. The format is specific: a professional actor embodies a historical figure, Coco Chanel near Place Vendôme, Hemingway around Montparnasse, a GI on Omaha Beach, and walks a small group through that figure's neighborhood telling the story of their life. Deniau does not call himself a tour operator. He calls Elyrea a "Lego brick" that DMCs and tour operators build into the experiences they sell. The company has 15 of these performances running, almost all in France, and there is a structural problem at the center of it: nobody knows to ask for a tour with Coco Chanel, so the business cannot wait for B2C search demand. That one fact shapes how Elyrea picks its characters, how it sells, and how it funds itself.Mitch and Deniau cover the business behind the tours. Why Elyrea sells to the trade first and keeps its strongest tours off OTAs entirely. The capital-light model that built 15 tours with no outside investor. The four design rules behind a 90-minute performance, starting with the claim that you win or lose the audience in the first minute. And the recruitment problem of training an actor who learns the whole show, performs twice, and quits because the street is not the theater. Deniau also names the advice he would give any operator building an emotional experience: stay true to the place, do not overplay it, and keep the technology out of the way.Resources:Elyrea: elyrea.comLive actor booking for trade partners: elyrea.com/booking"The Colossus of Marousi" by Henry Miller, the travel book Deniau cites as the original spark

In this podcast episode recorded live at the COVESA meeting, host John Heinlein interviews Roger Lanctot about how the automotive industry can leverage vehicle data to transition from a B2B to a B2C model, prioritizing driver personalization over data monetization to enhance customer engagement and loyalty.Chapters:0:00 Introduction to Vehicle Data and Personalization1:12 Introducing Roger Lanctot3:11 Personalization not Monetization5:23 Engagement Strategies of New Automakers6:27 Case Study: Chevy Equinox Connectivity Experience9:57 The Cost of Customer Acquisition and Retention12:11 Ensuring Privacy14:47 Emerging Trends in Vehicle Diagnostics15:45 The Evolution of Usage-Based Insurance18:43 Real-Time Feedback and Driver Engagement19:59 The Future of Personalization in Automotive21:06 Changing the Dealer Engagement Model22:13 Conclusion and Future Perspectives

In this episode, Salena coaches Cathy, the owner of an online gifting business, through one of the most common struggles in retail and ecommerce - spending too much time and money on customers who may never become profitable. Cathy shares how she has been sending free gifts with purchase to customers in an effort to get people to try her products, along with the challenges she faces when corporate customers continually negotiate on price. Salena unpacks why customer experience strategies need to be backed by real data and ROI, and why retailers need to stop making decisions based on emotion alone. The conversation dives into the difference between B2C and corporate customer strategies, why customer qualification matters, and how low-value leads can quietly drain time, energy, and profit from a business. Salena explains the importance of understanding customer value, protecting profit margins, and focusing on the customers who are most likely to generate long-term growth. If you've ever felt busy but not profitable, struggled with discount shoppers, or found yourself saying yes to customers who drain your time, this episode will help you rethink where your attention and energy should really go.

How much business are you losing simply because you're not staying in consistent contact with your audience? Most companies don't have a sales problem—they have a follow-up problem. And follow-up isn't about chasing people…it's about staying top of mind with value, relevance, and consistency. That's why my interview with Smita Wadhawan, CMO of Constant Contact, on the THINK Business – What Are You Good At? series hit on a hard truth—consistency is the new marketing advantage. Here are 5 takeaways that stood out: ✅ Mindshare → Market Share People can't buy from you if they forget you exist. Marketing isn't optional—it's oxygen. ✅ Consistency builds trust Trust isn't built in a moment—it's built in the follow-up moments people rarely do. ✅ Simple wins Customers don't want clever. They want clear. They want fast. They want relevant. ✅ Start now—then scale Stop overthinking platforms, funnels, or brand perfection. Start small. Ship. Learn. Improve. ✅ AI is here to help, not replace Use AI to automate repetitive work—so you can stay human where it matters most.   Smita Wadhawan Verma Global Chief Marketing Officer | Top 50 CMO | PayPal | Intuit | GoDaddy | Visa | SaaS | HealthTech | FinTech Award-winning Chief Marketing Officer with experience at GoDaddy, PayPal, Intuit, VISA, and SimplePractice — across SMB/consumer, SaaS, HealthTech, and FinTech. Global teams and global leadership at EcoVadis. Scaled and led businesses from a mid-size company to a $32B established brand, with budgets up to $175M. Expertise in growth marketing, product marketing, B2B and B2C marketing, lifecycle marketing, PR and comms. Smita has built and led teams of 150+ people in highly matrixed, cross-functional organizations across the US, Europe, Africa, Japan and India. She has partnered with top agencies like Koto, Instrument, Razorfish, TBWA, Highwire PR — and managed award-winning internal creative teams. Under Smita's leadership, her teams have won Digiday Awards and several Webby Award nominations. Smita is well known as a culture champion and recognized as a highly influential and inclusive C-Suite leader who can inspire teams to deliver outstanding results. Recognized as a 2024 Top 50 CMO in the US. Connect with Jon Dwoskin: Twitter: @jdwoskin Facebook: https://www.facebook.com/jonathan.dwoskin Instagram: https://www.instagram.com/thejondwoskinexperience Website: https://jondwoskin.comLinkedIn: https://www.linkedin.com/in/jondwoskin Email: jon@jondwoskin.com Get Jon's Book: The Think Big Movement: Grow your business big. Very Big! Connect with Jeff Gunsberg:Website: https://title-connect.com Connect with Smita Wadhawan:LinkedIn: https://www.linkedin.com/in/smitawadhawan/ *E - explicit language may be used in this podcast.

John Horn is the CEO of StubGroup, a digital advertising agency and a premier Google ad agency. Subgroup has helped over 2000 clients, across 15k campaigns, with their paid ads and suspension issues. They have generated over half a billion dollars in revenue for their clients across many different verticals including ecommerce, lead generation, B2B, B2C, local services, and more. Connect with Jon Dwoskin: Twitter: @jdwoskin Facebook: https://www.facebook.com/jonathan.dwoskin Instagram: https://www.instagram.com/thejondwoskinexperience/ Website: https://jondwoskin.com/LinkedIn: https://www.linkedin.com/in/jondwoskin/ Email: jon@jondwoskin.com Get Jon's Book: The Think Big Movement: Grow your business big. Very Big! Connect with John Horn:Website: www.stubgroup.com X: https://twitter.com/stubgroup Instagram: https://www.instagram.com/stubgroupadvertising/ LinkedIn: https://www.linkedin.com/in/johnjhorn1/ Facebook: https://www.facebook.com/StubGroup/     *E - explicit language may be used in this podcast.

These episodes of #thePOZcast, live from Transform 2026 in Las Vegas, are proudly brought to you by our friends at PIN. AI recruiting tools that automate candidate sourcing, screening, and scheduling across 850M+ profiles. Built for recruiters, agencies, and hiring teams. Learn more and check out a demo:  https://www.pin.com/book-a-demo?via=adam-posner Thanks for listening, and please follow us on Insta @NHPTalent and www.youtube.com/thePOZcast For all episodes, please check out www.thePOZcast.com   TAKEAWAYS:  1. Full Disconnection on Leave Is a Culture Signal, Not a Personal Choice Ariana's ability to fully disconnect during five months of maternity leave wasn't just personal discipline — it was enabled by a company culture that explicitly supports and expects it. Greenhouse has a caregiver community, respects the whole person, and understands that genuine recovery and presence during leave leads to a better return. Companies that say they support leave but create implicit pressure to stay connected are signaling something important about how they see their employees. 2. Institutional Knowledge Is the Best Return-to-Work Advantage What made Ariana's return from leave smooth wasn't a structured onboarding plan — it was nearly 11 years of context. She knew the Q4 rhythms, the relationships, the unwritten rules. For companies managing returning employees, this is a reminder that the investment in long tenure pays dividends at the most vulnerable moments. 3. The Candidate Experience Has to Be Half the Product Greenhouse's mission — make hiring work for everyone — isn't just a brand statement. It's a product design imperative that extends to the job seeker experience, not just the recruiter experience. In a market that is genuinely brutal for candidates right now, companies and platforms that design for both sides of the hiring equation will win trust from both. 4. Dream Job Signals Cut Through AI-Generated Noise Greenhouse's My Greenhouse platform — which lets candidates designate companies as dream job targets and signal genuine intent once a month — is a direct response to the noise problem created by AI mass-application tools. In a world where volume no longer equals signal, deliberate intent becomes the most valuable data point in the funnel. 5. The Market Is Shifting Toward Behavioral Hiring Over Background Matching Greenhouse is redesigning its own interview architecture around specific defined behaviors — 'make good decisions fast,' 'invent the future,' 'be entrepreneurial' — rather than experience checkboxes. The implication for candidates: the ability to demonstrate how you think and decide is becoming more important than where you've worked. Portfolio career holders take note. 6. The STAR Method Is Fully Gameable — and Everyone Knows It Traditional structured behavioral interviewing was built for a world where candidates had to recall and articulate their own experiences. AI second-screen tools have made that world obsolete. Real-time answer coaching during live interviews is happening right now, at scale, and the recruiting teams that haven't redesigned their interview approach for this reality are operating on outdated assumptions. 7. AI Offense and AI Defense Is the Most Useful Interview Framework in This Series Ariana's team ran a workshop that split into two tracks: AI defense (how do we design questions that are more AI-resistant and require genuine human judgment to answer?) and AI offense (how do we explicitly screen for AI mindset, curiosity, and capability as a positive qualification?). Both are necessary. Neither alone is sufficient. This framework is immediately replicable. 8. 'How Do You Use AI Personally?' Is One of the Most Revealing Interview Questions Right Now Asking candidates how they use AI in their personal or professional lives — not to catch them using it wrong, but to surface genuine curiosity and self-direction — is becoming one of the sharpest signals available in an interview. The candidates who have been experimenting, iterating, and developing their own AI workflows are showing you something important about how they'll operate in roles that don't yet have defined playbooks. 9. Portfolio Careers Need Behavioral Framing to Land Adam's candid share about feeling 'unhirable' after 10 years running his own business is a common experience for independent professionals re-entering corporate environments. Ariana's coaching: the shift toward behavioral hiring is actually an advantage for portfolio career holders — because the behaviors that make someone successful in an entrepreneurial context (making decisions fast, inventing solutions, operating without consensus) are exactly the behaviors companies are now explicitly hiring for. 10. The Best Conference Value Is the Hallway Conversation, Not the Session Ariana didn't attend a single formal session at Transform and still left with more actionable intelligence than most attendees. The real value — for her and for the industry — is in the one- to-one conversations between practitioners comparing notes on what they're actually building and experimenting with. Conference organizers should design more space for that. Attendees should prioritize it.   CHAPTERS:  00:00 – Welcome Back: Motherhood & the Return Adam reunites with Ariana Moon — last seen 8 months pregnant — and gets the update on baby Leo, sleep training, and how a strong support village made the first year survivable. 02:30 – Taking 5 Months of Leave — Fully Disconnected What it looks like to actually step away: Greenhouse's culture of respecting leave, why full disconnection is both supported and expected, and why Ariana has zero guilt about it. 05:30 – The Timing Was Right: Checking Out During the AI Gold Rush Her leave coincided with peak AI hype saturation. Stepping away while the market worked itself out turned out to be exactly the right call. 07:30 – Coming Back After Leave: The Real Reimmersion Story How 11 years of institutional knowledge, strong internal relationships, and knowing exactly what Q4 looks like made the return smoother than it would have been for anyone else. 10:00 – What It Means to Recruit at a Recruiting Platform The unusual dual role: running a great recruiting team while also serving as a live feedback loop for the product and staying connected to how the market is evolving. 13:00 – The Candidate Experience Nobody Talks About Enough Greenhouse's mission — make hiring work for everyone — and why it has to extend beyond the recruiter to the candidate side. The market is brutal for job seekers right now. 15:30 – My Greenhouse: The Dream Job Feature How Greenhouse's B2C platform lets candidates designate dream job companies, signal genuine intent once a month, and give recruiters a quality signal in a market flooded with AI-generated noise. 18:30 – Portfolio Careers & How to Position Them Adam gets personal about feeling 'unhirable' after 10 years of entrepreneurship — and Ariana's coaching on positioning portfolio skills in a behavioral hiring market. 21:30 – Behavioral Hiring: The Shift Toward Interpersonal Skills How Greenhouse designs interviews around defined behaviors — 'make good decisions fast,' 'invent the future' — and why the shift toward behaviors over background may be the biggest structural change in recruiting right now. 24:30 – AI Killed the STAR Method. Now What? Traditional structured interviewing is fully gameable by AI second-screen tools. Ariana's team ran a workshop to directly confront this — and built something new. 27:00 – AI Offense and AI Defense: The Framework The two-part workshop: AI defense (questions that require genuine human judgment) and AI offense (explicitly testing for AI mindset and capability as a positive qualification). 30:00 – Testing for Curiosity as a Hiring Signal Why "how do you use AI personally?" is becoming one of the most revealing interview questions — surfacing genuine curiosity and self-direction rather than catching people out. 32:30 – What's Lighting Ariana Up at Transform 2026 Ariana didn't attend a single session — and that's the point. The value of Transform is the one-to-one conversations about what people are actually doing, building, and experimenting with right now. 35:00 – Connect With Ariana & the Vegas Advocate Where to find Ariana on LinkedIn — and her unexpectedly enthusiastic case for why Las Vegas is actually a great place to live.  

Can you build a B2C app to 6 million users with no advertising? Colin Hodge did it when he co-founded Bang with Friends — a dating app that went viral purely through word of mouth — because he understood the psychology of his users so precisely that they couldn't help but share it. In this episode, Sophia Matveeva speaks with Colin Hodge — entrepreneur, growth expert, and author who has scaled businesses to over 100 million users. He co-founded a viral dating app, served as Chief Growth Officer for 17Live, Asia's leading live-streaming app, and re-acquired his own startup after selling it, growing it into a top 5 US dating app. But this episode is not really about dating apps. It is about the one thing that separates products that grow from products that stagnate: understanding your users deeply enough to build something they cannot stop sharing. You'll learn: The overnight pivot that took a failing startup to a million users in three months Three practical techniques for getting inside the mind of your user, even if you are nothing like them Why the best user interviews feel like anthropology rather than sales Why critiquing your own product before user interviews makes you a dramatically better listener Timestamps:  00:00 - Introduction: How Bang with Friends went from zero to 1 million users 04:51 - How a bad date launched Colin's biggest business success 08:48 - The pivot: From friends of friends to "Who has a crush on me?" 11:07 - Reaching 1 million users in 3 months with zero ad spend 14:36 - Lessons for boring businesses from a scandalous dating app 18:35 - Three methods to understand users who aren't like you 20:59 - Method 1: The method acting technique - Live your user's life 22:50 - Method 2: Build detailed personas beyond demographics 26:55 - Method 3: User research as an anthropologist, not a salesperson 27:52 - How to suppress your founder instinct and actually listen Free AI Mini-Workshop for Non-Technical Founders: Learn how to go from idea to a tested product using AI — in under 30 minutes. Get free access here: techfornontechies.co/aiclass Follow and Review: We'd love for you to follow us if you haven't yet. Click that purple '+' in the top right corner of your Apple Podcasts app. We'd love it even more if you could drop a review or 5-star rating over on Apple Podcasts. Simply select "Ratings and Reviews" and "Write a Review" then a quick line with your favorite part of the episode. It only takes a second and it helps spread the word about the podcast. Listen to our podcast on: Apple Spotify YouTube Audible Pandora Transcript: https://www.techfornontechies.co/blog/304-how-one-founder-went-from-zero-to-6-million-users-with-no-ad-spend

Take the 2026 AI Engineering Survey and get >$2k in credits and AIE WF tickets!This was recorded before Railway suffered a major GCP outage on May 19, despite being a multi-AZ, multi-zone mesh ring, with HA fiber interconnects between their Metal GCP AWS, because workload discoverability was unintentionally still tied to GCP. All has been resolved with a post-mortem.Railway did not start as an AI infrastructure company.It was founded in 2020 years before agents became the default way people thought about deploying software. Jake Cooper, formerly at Bloomberg and Uber, started Railway with a simple obsession: the activation energy to ship something to production should be near zero. Push code, get a URL, iterate. No Docker files, no Kubernetes manifests, no Ansible scripts stacked on Ansible scripts.For years, this was a slow grind. Railway spent its first 18 months hand-acquiring its first 100 users with Jake personally greeting every Discord signup on a second monitor.Today, Railway has raised $124m and is growing very fast. A 35-person team supports 3 million users, adding roughly 100,000 signups a week. Their bare metal data centers have a 3-month payback period vs. renting in the cloud, with 70% margins funding aggressive cloud bursting when needed. The servers they own have actually appreciated in value as RAM prices have climbed basically meaning the value of their hardware now exceeds the capital they've raised.From rebuilding Railway's network overlay over a weekend to moving the vast majority of workloads onto its own bare metal data centers, Jake Cooper is trying to build a new cloud for an agent-native world. In this episode, Railway's founder and “conductor” joins swyx and Alessio to unpack why the next era of software infrastructure is not just “Heroku but newer,” what agents need that humans did not, and why the old deployment loop of Git, PRs, CI/CD, and static cloud resources may be heading for a rewrite.We go deep on Railway's infrastructure stack: own-metal data centers, three-month cloud payback periods, cloud bursting, data center debt, Railpack, Nixpacks, Temporal, feature flags, Central Station, content-addressable filesystems, agent-safe production forks, and why the CLI may become more important than the canvas in an agent world. Jake also shares the founder journey behind Railway, how the company survived losing $500K/month, why it now serves millions of users with only 35 people, and why he believes the pull request is dying.We discuss:* How Railway went from a slow six-year grind to adding 100,000 users a week* How Railway thinks about agents as the next dominant software species* Why agents need version control, observability, compute, storage, and orchestration at 1000x scale* The economics of Railway's own-metal data centers and three-month payback* How Railway uses cloud bursting while scaling its own infrastructure* Why data center debt can be a better tool than venture debt for infra startups* Central Station, Railway's internal system for clustering customer feedback and incidents* Why responsible disclosure and over-communication matter for platforms* Why feature flags, progressive rollouts, and shadow traffic are essential for agents* Temporal's strengths, pain points, and why workflows matter for agents* Railpack, Nixpacks, Nix, and lazy-loaded content-addressable filesystems* Why “cattle, not pets” may change if you can clone the pets* Why Railway is building a new cloud from scratch instead of copying hyperscalers* The solo founder path, focus, writing, and how Jake thinks about company buildingRailway:* Website: https://railway.com/* X: https://x.com/RailwayJake Cooper:* LinkedIn: https://www.linkedin.com/in/thejakecooper/* X: https://x.com/JustJakeTimestamps00:00:00 Introduction: What Is Railway?00:02:07 Jake's Path to Railway00:06:13 Railway's Six-Year Growth Story00:08:52 Rebuilding the Business After the Free Tier00:11:17 Agents as the Next Software Platform00:13:29 Railway's Infrastructure Philosophy00:15:42 Bare Metal, Cloud Economics, and the Compute Crunch00:17:22 Cloud Bursting and Five-Cloud Networking00:20:20 Data Center Debt and Infra Financing00:23:31 Data Centers in Space00:25:24 What Agents Need From Infrastructure00:28:24 CLIs, Canvas, and Agent-Native UX00:35:15 Central Station, Incidents, and Responsible Disclosure00:40:30 Safe Rollouts, SRE Agents, and Production Forks00:45:00 AI SRE, Specs, Code, and Tests00:48:24 Self-Replicating Infrastructure and the New Serverless00:53:18 Heroku, Temporal, and Workflow Engines01:04:07 Railpack, Nixpacks, and Lazy-Loaded Filesystems01:06:01 Coding Agents, Token Spend, and Roadmap Acceleration01:10:56 The Pull Request Is Dying01:12:28 Feature Flags and the Agent-Era SDLC01:16:15 Cattle, Pets, and Cloning Machines01:19:29 Solo Founder Lessons01:24:12 Focus, GPUs, and Building a New Cloud01:28:20 Closing ThoughtsTranscriptAlessio [00:00:00]: Hey, everyone. Welcome to the Latent Space Podcast. This is Alessio, founder of Kernel Labs, and I'm joined by Swyx, editor of Latent Space.Swyx [00:00:10]: Hey, hey, hey. Today we're in the studio with Jake Cooper of Railway.Alessio [00:00:14]: Conductor of Railway.Swyx [00:00:15]: Conductor at Railway. Yeah.Alessio [00:00:16]: Choo-choo.Swyx [00:00:17]: Do you actually have that anywhere, like on your business card?Jake [00:00:20]: We call some of our volunteer moderators conductors. I don't have a business card. We're not that big yet. At some point I will. I got handed a nice business card from the Supermicro folks, and I was like, “Damn, this is pretty official.”Swyx [00:00:30]: Business cards are coming back.Jake [00:00:32]: They're cool. They're hip. The conductor thing is good. We're trying to figure out what we want to call each other internally. Some people think it's super cringe and say, “You don't need a name for people internally.” Some people want to call each other something. We still don't have a really good one.Jake [00:00:55]: We've got New Railcrews, Trainiacs. Nothing has stuck yet.Swyx [00:01:00]: I like Trainiac. Trainiac sounds good. Railwayians. For those who don't know, what is Railway? Let's give people a crisp definition up front.Jake [00:01:09]: Railway is the easiest way to ship anything. You go to the canvas, or you talk with Claude, and you say, “Deploy a Postgres instance, deploy my GitHub repository, run this code,” and you're off to the races.Swyx [00:01:22]: You've got a nice animation on the landing page.Jake [00:01:24]: Thank you. None of my work, by the way. They don't let me touch the design stuff anymore.Jake [00:01:25]: We want to make it trivially easy not just to deploy things, but to evolve applications over time. Most tooling right now stacks entropy on top of entropy: Docker, Kubernetes, Ansible scripts, and all these other things. If we can version all of your software and keep track of all the changes, then we can make it trivial to clone environments, fork into a parallel universe, get copies of production data, get copies of any services, make changes, validate them, and collapse them back in without reproducing everything across a staging environment.The Railway Origin Story: From Uber Systems to a New CloudSwyx [00:02:07]: I was looking at your background: Bloomberg, Uber. Nothing immediately stands out as, “This guy is going to found the next great platform as a service.” What prepared you for Railway?Jake [00:02:21]: It was curiosity to keep going deeper. I started out on front-end stuff, working on Wolfram Mathematica and porting it over. Then I briefly moved to Bloomberg, then toward Uber and distributed systems, taking the Jump Bikes systems and moving them to a distributed system built on top of Cadence, the pre-Temporal Temporal.Swyx [00:02:44]: Which, by the way, I'm happy to talk about, pros and cons.Jake [00:02:48]: Totally.Swyx [00:02:51]: But let's do the Railway story.Jake [00:02:52]: It has been a continual step of wanting an experience. Whether it's walking up to a bike, unlocking it, and having it work frictionlessly, or something else, the depth required to make that happen follows from the experience. A lot of the work I do, and a lot of the team does, is in service of that experience. We fundamentally don't care how deep we have to go. We will swim to the bottom of the swimming pool to get the experience.Jake [00:03:17]: I don't have a physics PhD. I did an EECS degree. It has always been about figuring out the next step: how do we get there? That's what led to starting Railway for that experience and then moving all the way to bare metal data centers. I was adding patches to the kernel this week to get the experience there because I can see how much better it can be.Swyx [00:03:49]: Other patches to the Linux kernel this week?Jake [00:03:51]: Yeah. Not upstream. Our fork.Swyx [00:03:52]: That's a flex. Railpack? No, this is different. This is the OS on top of Railpack?Jake [00:03:57]: No, this is an actual kernel patch. It's always literally: what do we have to do to get that experience? Then figure it out. Anything is figureoutable.Swyx [00:04:10]: Would you send the patch upstream, or does it not fit other use cases?Jake [00:04:13]: Maybe. We have to work out the experience internally. It has to do with the storage layer we're building for some of the agentic stuff. Maybe it'll be useful upstream, but it's deeply useful for us internally.Open Source, Forks, and Non-Deterministic VersioningSwyx [00:04:29]: You mentioned open source before. How do you think about starting from open source, and then coding agents letting you do a lot more from forks of it?Jake [00:04:38]: GitHub's original sin is that it's almost a series of broken pointers. You have this thing, then you clone it, and now you've lost the whole upstream. How do we make it trivial for people to modify really small pieces of it?Jake [00:04:51]: We think of Git in a discrete sense: I've either made a change and merged upstream, or I haven't. What would it look like if it were percentage-based, a little more non-deterministic, or a stream of changes that users traverse as a percentage rolled out in general and then rolled all the way up?Jake [00:05:13]: We have the open-source kickback program and let you deploy templates because we want to make it trivial for people to version these shards over time. It solves a large problem around authentication, authorization, and security. NPM has a way to define, “Don't take any new packages.” The ideal end state is that you roll out progressively to users with the minimum impact zone and continue rolling up. JPMorgan should probably be the last one on the patch line, for all our sakes, because our money and livelihoods are there.Jake [00:05:53]: It's okay if Johnny Vibe Coder gets a broken patch because there's so much entropy in the system that the rubber has to meet the road at some point. You have to test at varying levels.The Long Grind: First Users, Free Tier, and Making the Business WorkSwyx [00:06:13]: I wanted to pull up this glorious chart, which is your usage or number of daily signups?Jake [00:06:22]: Daily signups, I think.Swyx [00:06:24]: You started six years ago. It was a slow grind, and now you're on a rocket ship. You say, “Don't doubt your fight and don't quit.” Maybe pick out certain points that were key inflections for the company.Jake [00:06:40]: At the start, it's about getting your first 100 users, hell or high water. We had a website and a support link. The support link was the Discord channel. I had notifications on with two monitors: the monitor I was working on and the other monitor with Discord. If anybody came in, I was immediately like, “Hey, how's it going?” It was rare, so getting those first 100 users to come back was the start.Jake [00:07:14]: Then you build a consultancy factory because users want all these things. You have to go back to the board and ask, “What is the actual product offering I want to build on top of this?”Jake [00:07:28]: VCs want charts that always go up and to the right, but in reality you don't necessarily want charts that look like that. For us, there have been periods of expansion where we add features to test use cases, and periods of compaction where we ask, “If the experience we have is good, how do we make it significantly better?” Maybe we strip out features that don't fit our ICP anymore.Jake [00:07:57]: The boom from 2022 to 2023 came from the free tier. Everybody under the sun was using it.Swyx [00:08:09]: A lot of Reddit bots and Discord bots.Jake [00:08:12]: And crypto miners. When you build an open product on the internet where anybody can sign up, the internet is a horrible place with so many things. You go through periods of asking, “How do I reach as many people as possible?” Then, “How do I fit the exact use case for the people who really matter and are really excited about this specific thing?”Jake [00:08:39]: Then there was a two-year period of making the actual business work. During the free-tier era, we were losing about half a million dollars a month.Swyx [00:08:59]: On a $20 million bank account.Jake [00:09:02]: On a $20 million bank account with maybe $50,000 a month in revenue. That's a horrible business. I don't know how anybody invested. But you have to go through it and say, “We have an experience people love, but the business has to work.”Jake [00:09:17]: There are two schools of thought. You can run the horrible business all the way up with bad margins, or you can go back and make it work. We've always wanted a super lean team. We're 35 people right now. It's very small.Swyx [00:09:36]: Supporting three million already?Jake [00:09:38]: Yeah. We're adding 100,000 users a week right now, so it's growing fast. We don't want to add headcount for the sake of headcount or throw bodies at problems. We want to build systems. It's hard to build systems during expansion because you're adding things to the system because people are asking for them or things are breaking.Jake [00:10:00]: We had to cut off the free users for a little while, rebuild the business, and make sure it worked. We want to reach as many people as possible because software is important. It's become difficult to create things in the physical world, so it's important to make it easy for people to build in the virtual world and have access to creation. But there are legs to that journey.Jake [00:10:30]: You can see divots in the charts. If you follow between 2025 and 2026, it's either summer or winter. People go on holiday with family.Swyx [00:10:50]: It affects that much?Jake [00:10:51]: Yeah. It's kind of B2C and kind of B2B. People are shipping constantly, then they stop. Our activation curve now shows more people activating on weekdays because we have more business users, so it smooths out over time.Agents as the New Interface to DeploymentSwyx [00:11:17]: Was there a point where you started prioritizing AI development or agent development?Jake [00:11:24]: We've prioritized agentic as a top-of-funnel thing. Over the last six months, we've deeply prioritized agentic as a mechanism to build and deploy things because we believe the curve is so steep and that is how people will build and deploy software.Jake [00:11:42]: It almost fundamentally doesn't matter whether this is dot-com or not because we're all on the internet anyway. If agents are going to deploy a bunch of things and we hit an inference wall at some point, we'll fix those problems. The dominant species over the next 10 years is that we've moved from assembly to C to C++ to JavaScript to words. You're going to need to close that loop.Swyx [00:12:13]: When you say this is dot-com, did you mean buying the domain, or the general case?Jake [00:12:17]: I mean the dot-com era, when companies had a huge run-up because people understood the internet was important. Then they hit bottlenecks, fundamental laws of physics, math didn't work, and everybody came back down to earth. But it didn't matter because the internet became so impactful. If you operate on a long enough time horizon, you should build these things anyway because you can see where it's going.Jake [00:12:45]: That's where I think a lot of agent stuff is. You get to a point where you're running thousands of agents in parallel. What is the inference cost? What is the compute cost? How do you make that efficient? How do you coordinate all this? We have issues coordinating humans; we don't even have good tooling for that. Now we have to figure out how to get agents to coordinate, safely version changes, and know when to raise their hand for someone to intervene. Otherwise it becomes an interrupt factory.Railway's Infrastructure Thesis: Network, Compute, Storage, and MetalSwyx [00:13:19]: Let's go right into the technical side. What are the core infrastructure or architectural beliefs of Railway that allow you to do what you do?Jake [00:13:29]: The primitives matter a lot for us. We need network, compute, storage, and orchestration around it. You need control over a lot of those things. We've talked a lot about how we don't really use Kubernetes because we want higher-order control to place workloads in very specific places.Jake [00:13:48]: The reason is that you have to be very efficient with agents: memory reuse and all these other things, or you're going to massively blow up your cost structure. Being able to rack and stack your own servers and build your own metal unlocks performance and cost. Experiences where you're running 1,000 agents in parallel are not massively cost prohibitive.Jake [00:14:13]: Token use and compute use are blowing up. Over time, those things have to get a lot more efficient. You can get a lot of margin to make those experiences solid by building your own metal. That's all in service of offering a differentiated experience to as many people as humanly possible.Swyx [00:14:51]: You have a data center in Singapore.Jake [00:14:53]: Yeah. We have two in every other region now. In Singapore, we're adding a second one in Q3.Swyx [00:14:58]: What's it like? I've never built a data center. Do you go to Equinix and say, “I want some slots?”Jake [00:15:05]: Yeah. Equinix. You basically go and say, “I want power and I want a cage.” They say, “Great, here's what it's going to be.” You rent the cage for a period of time, fill it with racks and servers, and hook up internet to it. That's all the pieces.Swyx [00:15:36]: Then you handle everything else.Jake [00:15:37]: You handle everything else.Swyx [00:15:39]: What's the math versus clouds doing it for you?Jake [00:15:43]: If we rented in the cloud, our payback period when we go to metal is about three months.Swyx [00:15:50]: Which is crazy.Jake [00:15:51]: It's nuts. That's four years of depreciated hardware. You're going to see a lot of this compute crunch because hyperscalers are buying up a lot of stuff. We're working directly with OEMs, resellers, and people building these machines: Supermicro, Dell, and others.Jake [00:16:11]: Upstream, there's a bunch of supply pressure. When we raised our last round, between deploying capital for servers and now, the amount of money we've raised is less than the amount of money we have in the bank plus the value of the servers because the servers have appreciated as RAM has gone up. It's nuts how valuable hardware has become.Jake [00:16:50]: If you look at hyperscalers, they deployed around $80 billion of capital expenditures this year, and next year will be more. That's a massive infrastructure build-out. You look at that and think it's crazy that they're spending way more than the Manhattan Project. But if every person is going to run dozens or hundreds of agents in parallel, you have no conceptual idea how much compute is required to make that experience happen, even if you're deeply efficient and sharing resources. And that doesn't even count inference.Swyx [00:17:22]: How do you plan the build-out? The growth chart is so vertical. Are you usually at 100% utilization as soon as racks are live? How far ahead are you planning?Jake [00:17:33]: We still maintain cloud presence for bursting. We work with AWS, GCP, and a few other clouds. We can rent, and then the moment we get space or power, we compact those workloads off the cloud. We started on the clouds, then built a system to migrate to our own metal. There's nothing that says you can't continually do that again, and that's exactly what we do. We never want to be compute constrained.Jake [00:18:09]: At the start of the year, we actually became compute constrained because one upstream provider wasn't able to give us quota at the rate we needed, and the hardware was slower. I spent a weekend rebuilding our entire network overlay so we could straddle five clouds: Oracle, AWS, ourselves, GCP, and one other one. We can do more than that now.Jake [00:18:38]: We got into a spot where we were trying to pack instances tight because we couldn't get enough compute. That led to a few reliability issues, which are now past us. I made a tweet pointing out that it's becoming harder and harder to acquire compute at the rate these models need to acquire compute. We got bit by it.Swyx [00:19:15]: How do you think about pricing knowing you might not have your own metal available at all times? Are you pricing assuming you need extra margin if you end up going into the cloud?Jake [00:19:26]: Because we've built out our metal data centers, our margins on metal are around 70%. We can deeply subsidize the cloud business if we want to scale at a reasonable rate. We have a few levers: metal, which makes the margins; cloud burst; debt to buy servers; and venture capital. It's an interesting operational problem: how much cash do we have, how much should we raise, how quickly can we deploy it, and can we scale revenue as quickly as we scale compute?Jake [00:20:05]: If we continue making it trivially easy for people to build and deploy, then the faster we close that loop and the more operationally excellent we are with capital, the faster the business can scale. It's almost a straight linear deployment rate.Financing Infrastructure: Hardware Debt, VC, and Operational LeverageSwyx [00:20:20]: I think infra startups raising debt is a tool people don't utilize enough or know enough about. What can you tell us about that? Is it secured against your CPUs?Jake [00:20:32]: It's secured against our hardware.Swyx [00:20:37]: What rates do you get? Who are the lenders?Jake [00:20:39]: We pay prime plus a spread, and we can refinance any of the debt as rates go down. The terms are pretty good. The unfortunate thing is that Twitter has no nuance, so people say, “Venture debt bad.” But as with all things, there are specific tools and areas where you can be deliberate instead of using one tool as a hammer. Venture capital is not the hammer for everything. You have to explore and figure out what works.Swyx [00:21:12]: VC is usually the most expensive financing you can get.Jake [00:21:15]: Yeah. I also think people think about VC incorrectly from a capital-raising perspective. Most people think, “How do I raise as much money as possible from whoever is probably the best I can get at that time?” That's close to right, but what we've tried to do is figure out what unfair advantage we can buy with that equity.Jake [00:21:34]: It's the most expensive equity you're going to give away at that point in time, assuming the company keeps getting better. How do you use it to work with someone stellar who complements you? In the seed stage, I had never started a company. Ray Tonsing had good advice, and I could text him all the time. He was really fast. Awesome.Jake [00:22:01]: Then with John and Erica at Unusual, they said, “You roughly know what you're doing building a product. We'll mostly leave you alone and be available for advice.” Amazing. Then we got to Series A and the business was an operational tire fire because we didn't know how to scale a business. Work with Erica, and Jordan is over at Redpoint, so bonus.Jake [00:22:28]: Now we've raised from TQ and FPV as we're moving into enterprises. Every step of the way, we've asked: who can we partner with at this specific time to unlock the next section of the journey? I don't know enterprise sales. As an engineer, I can eyeball what features we might need, and we have wonderful people internally who can help. But you want boardroom dynamics where everyone is aligned and asking, “How do we win this?” instead of bickering about strategy.Data Centers in Space and the Physics of ComputeSwyx [00:23:31]: You had a tweet about data centers in space. Why no data centers in space?Jake [00:23:37]: It's not “no data centers in space.” My hot take is that I think it is solvable. I've just never seen anybody solve it.Swyx [00:23:49]: You said, “How are you going to dissipate that much heat in a vacuum?” You're making a physics claim.Jake [00:23:55]: I haven't seen anybody prove how you're going to dissipate that much heat in a vacuum. It doesn't mean it's not possible. It just means nobody has brought it up yet.Swyx [00:24:05]: Astrophage.Jake [00:24:06]: I don't know what that is.Swyx [00:24:07]: The Martian thing. Okay, you're very logical.Jake [00:24:09]: It could work. A lot of people are putting the cart before the horse. They say, “We're going to put data centers in space.” Okay, but how? “We have time to figure it out.” It's like in The Martian where they ask how they're going to intercept something and say, “We'll figure it out.”Swyx [00:24:36]: Making a bet on human invention is weird because you blind trust that it can be solved. But with physics, there are first-principles bounds you can put on it. Maybe not. Maybe you're asking to travel time or break a fundamental thermodynamic law.Jake [00:24:57]: I don't know how VCs do this either. How do you know what's not possible and a grift versus what's possible but sounds completely insane? “We're going to put data centers in space.” Coin flip as to which it is, and I guess you'll know in 10 years. That's one cycle.What Agents Need: Versioning, Observability, and 1,000x ScaleSwyx [00:25:23]: Moving back to agents. The branching, fast spin-up, and orchestration you do feels like pre-work that happened to be exactly what agents want. What do agents want differently than humans?Jake [00:25:37]: They want the ability to version things. It's not that different; it materializes slightly differently. Agents want a way to test changes incrementally. Engineers have feature flags. Is there a reason agents can't use feature flags? I don't think so.Jake [00:25:54]: They want version control. Can we use Git or not Git? That one is up in the air. I think something outside Git will emerge for how we version these things over time. They need observability. You need to query what happened, when it happened, which steps failed, traces, logs, metrics, and all the rest. They need network, compute, and storage. They need to write files, save files, iterate on files, and snapshot file systems.Jake [00:26:25]: A lot of what humans needed is in line with what agents need. Branching and forking are not different; we're just moving 1,000 times quicker. It can look like you need something massively different, but what you need is something massively better than what existed. You need orchestration massively better than Kubernetes. You need networking probably better than Envoy. It goes all the way down the stack.Jake [00:26:55]: If the workload profile doesn't change so much as it gets massively compressed because you need thousands of these things, what assumptions change? etcd is going to melt. You need to replace it with something. You can go all the way down the stack and say, “That part has to change, that part has to change, and that part has to change.”Jake [00:27:19]: The interesting thing about the super-exponential curve is that you have to build systems where you can rip out those parts at any time because a new bottleneck might emerge. You get good at parallel agents, and a different part of the system breaks. So it's similar to what humans needed, but at 1,000x scale.Jake [00:27:55]: How do you do code review in the age of agents?Swyx [00:28:00]: You throw more agents at it.Jake [00:28:01]: You don't. But then who reviews for CVEs and all these other things?Swyx [00:28:07]: More agents.Jake [00:28:08]: And that's how we hit the inference wall. You can continually throw agents at the problem, but I think there's a limit to the number of agents you can throw at a problem.CLI, Agent Handles, and Closing the LoopSwyx [00:28:24]: You already had a CLI before it was cool. How is the shape of what you're exposing changing, if at all?Jake [00:28:28]: CLIs have always been cool. The CLI changes because we think about how to give Claude, Codex, ChatGPT, or any model a handhold.Jake [00:28:50]: A CLI is a single command: deploy, get logs, and so on. Things that were prohibitively annoying to humans are not annoying to agents. They're nice. If I handed you a CLI with 40 arguments and 600 flags, you'd think, “I'm never going to use all of this.” But if you hand it to an agent, it says, “This is excellent. I have so many handles to work with.”Jake [00:29:24]: If you're going to expose things to agents that way, you want as many handles as possible where they can get information, query dynamic information, and close the loop quickly. Most problems right now are about how to close the loop as quickly as possible. Where does the agent get stuck, and how can you remove that?Jake [00:29:49]: Telemetry is important. If you can tell where the agent gets stuck from the CLI and say, “12% of people deviate from the happy path because of this, and now I add this argument and drive it down to 2%,” you massively increase the rate of loop closure.Jake [00:30:03]: That's how we think about not just the CLI, but every point in the dashboard. It's a user journey: I hear about Railway. I get something deployed. I get my first green build or aha moment. I see an endpoint, logs, whatever. Then I iterate. The iteration loop is indefinite. The user wants to deploy a new thing, a Postgres instance, change code, and keep iterating.Jake [00:30:36]: If you focus on the iteration loops and what's blocking them from closing quickly, one thing we say internally is: you never want to be waiting on compute anymore. You always want to be waiting on intelligence. If you're waiting on compute, there's a bottleneck that needs to be destroyed because eventually that bottleneck becomes so large that another workflow emerges to change it.Jake [00:31:04]: We've built a product where you push code, build it, and so on. But I fundamentally believe the push-pull loop is going away. We'll get to a point where you make a small change in production, that change is versioned across your infrastructure, you're working alongside copy-on-write versions of your database and infrastructure, and then you merge it in and it's instantaneously live. That's the holy grail of loops. The push-pull-rebuild thing is a point of friction that we're removing entirely.Canvas as Output: Dashboards, Context Anchors, and HyperstructuresSwyx [00:31:43]: It's incredibly fast. If anyone hasn't tried it, that fast feedback is great. My hot take is that Railway was famous for its canvas, which visualizes your infrastructure and lets you manipulate it visually. But that was for humans. For the next phase of growth, Railway CLI is more important than canvas.Jake [00:32:05]: The canvas is funny because it's a mechanism to show changes over time. You're right that previously we used it a lot as an input. Moving forward, its goal is more like an output. You would go to the canvas, make changes, see them, and watch your infrastructure evolve. Now agents have access to the CLI and can make those changes. So the canvas becomes an output: what information does the human need at this moment to make suitable decisions about control requests? Do I approve this or not?Jake [00:32:57]: It also has to be an anchor for your context, a port in the storm. Think of it like layers in a file system. You start with a project, then drill down into services, then into a function or code, because you want to represent the entire thing not just in your head, but in the canvas. Other people can share that representation, think on the same wavelength, and move quickly.Jake [00:33:33]: A lot of organizations get in trouble as they scale because all the context lives in someone's head. “How does this microservice work?” “I have no idea; go ask this person.” Then you have whole categories of products built around context discovery. A lot of that melts away if you have a solid hierarchy and can infinitely nest services, code, context, and everything else all the way down. That's what lets you build these structures over time.Jake [00:34:18]: It's also what lets us build what I've called hyperstructures: things that are way bigger. You look at the Golden Gate Bridge and ask, “How did we build that?” There's a meme that we lost the technology. To some extent, yes, because the coordination that built those things evolved and changed. We lost some of the art of building structure as we jammed everything into Slack.Swyx [00:34:52]: But you jam everything in Discord.Jake [00:34:53]: Same point. It doesn't matter. It's message passing and interrupts, message passing and interrupts.Swyx [00:35:00]: So you're arguing there should be something better and more structured than Slack?Jake [00:35:04]: Yeah. For sure. I think Slack is awful, and Discord is awful too.Central Station: Context Routing, Support, and Incident ClustersSwyx [00:35:09]: This is the equivalent of my mom test. What have you done that has your solution to this?Jake [00:35:15]: Internally, we've built a tool called Central Station that aggregates all the context from our users. Every piece of feedback, every customer support item, everything gets aggregated into clusters. If an incident is brewing, we can determine how many users are affected and break off a discussion based on that.Jake [00:35:40]: That is more helpful than long-running channels where you're trying to decide which channel to put something in. If you can dynamically aggregate information and dynamically route it to the right person based on context, it works better. We know internally that these four people are close to networking. If we see a networking thing, we can drill it down to those four people. If it's with this part, we can look at the commits. This is no longer a manual process internally.Jake [00:36:13]: If you go to station or help.railway.com, that's why we built it. We wanted to scale with a massive amount of leverage by aggregating feedback.Swyx [00:36:27]: This is built in-house?Jake [00:36:28]: Yep.Swyx [00:36:29]: I remember helping out on this one with Angelo in 2023. You scale a lot with a very small team.Jake [00:36:38]: Yeah. We're about 10 times bigger now.Swyx [00:36:40]: You have your full developer code here? Very cool.Jake [00:36:44]: If you go to railway.com/stats, we expose this as a pub-sub-able thing. It's all real-time metrics. There's a way to get it as JSON somewhere if you care.Jake [00:37:01]: We're big on trying to build everything in public and talk about what we're working on. We've had issues in the past, and we'll say, “Here's how we're fixing these things.” We've gotten compliments and flak for incident reports. We're always trying to make them better and talk with people.Incidents, Disclosure, and Progressive RolloutsSwyx [00:37:20]: You had a big one recently. I liked that it was scoped to 3,000. You presumably used Central Station. Talk through what happened and how you address it internally as a team.Jake [00:37:38]: Internally, this one really sucked. It had to do with an upstream provider that didn't do the behavior it said it documented, which is unfortunate given they wrote the RFC for how the behavior should work. We rolled those things out, and Central Station caught it initially when a couple users said caches weren't invalidating. We turned it off immediately.Jake [00:38:03]: When you roll out to a large user base of three million people, you get a lot of disparate behaviors. We tested in staging and had tests, but we hit an edge case. We've hardened those systems, and now we can make that better. But it was a tough one.Swyx [00:38:39]: I always wonder how private disclosure is supposed to work if people find an issue. Are they supposed to contact you first? When you run a platform, these things will happen. What channels should people pursue to quietly resolve it before it becomes a bigger incident?Jake [00:38:59]: There's responsible disclosure. We err on the side of over-disclosing and letting you know something is wrong versus having your provider gaslight you. We've erred on sharing those things more publicly, even if they impact a small subset of users. That's a decision we've made internally. We have four values. One is honor. The honorable thing is to notify people to the widest degree at which they may have been affected or there was an issue, and then confront it head-on: why did it happen, what can we do better?Swyx [00:39:45]: Not the whole user base. That's because of incremental rollouts and other things?Jake [00:39:50]: Yeah. Progressive rollouts.Swyx [00:39:54]: That should be the norm at all large platforms.Jake [00:39:58]: It should. A variety of companies do this. There's the quote that Meta runs 10,000 different versions of Meta. To our earlier point about agents, they need the same thing. They need shadow traffic and all these other things. We've built so much ceremony around production being sacred that we need to make it trivially easy to test different behaviors in a safe environment. Then you can make mistakes in a safe environment.Safe AI SRE: Customer Agents, Forked Environments, and Production ParityAlessio [00:40:30]: Do you see a world where these things get automatically caught, not necessarily by your agent, but by your customer's agent? The cache invalidation issue seems easy to check if you know to look for it.Jake [00:40:44]: It's hard because to determine it, we almost need to hook into your observability infrastructure. That's why we have the template loop on the platform: so you can roll things out progressively. You can roll out to Johnny Vibe Coder initially, or push a shard that someone consumes at their own leisure. Or you can roll it out over weeks: 0.1% of people, 1% of people, early adopters, then all the way up. That's the non-deterministic version control we talked about earlier.Jake [00:41:30]: I believe that's where most things should go, because most companies end up building staged rollout systems in-house. It's the same thing built again and again at every company. There's a massive opportunity to consolidate developer debt.Alessio [00:41:45]: You should have a free tier. Model providers give free tokens if you let them use the data. You could give free compute if someone is the number-one shard that goes out and lets you plug into their observability.Jake [00:41:55]: We do that. That's why we talked about the impact on 3,000 people. We start with lower-impact people. Larger companies on the platform are last to receive those rollouts so they have a version of the platform that's deeply stable.Alessio [00:42:16]: I have three services, so I'm sure I get the first rollout. You can nuke my thing at any time. There are all these SRE agent companies. Observability people also want agents that fix upstream problems. You have your own agent in the canvas now. How do you see that playing out?Jake [00:42:39]: It's the stacking entropy problem. If you don't have primitives to make iteration in production safe, it becomes difficult. If you're an observability provider saying, “Here's the fix to this error,” assume 80% are good and make sense. But in the last 20% long tail of complex issues, if you let somebody stamp it, you create an opportunity for an incident.Jake [00:43:08]: That's why forked environments are important. People have staging, but it always drifts from production. You need primitives, workflows, and experience built first-party on the platform so you can fork any service at any point in time.Jake [00:43:33]: I think of the canvas as a sheet of transparency paper. The agent is a little guy you push up into the canvas. It should say, “I need to copy that service and that service so I can test these two things.” It gets a read-only copy of production. Anything that's PII gets marked as a transform when we clone the database, create a copy-on-write version, or read from it. Then the agent makes changes and asks, “Does this actually work?” as close to production as possible.Jake [00:44:22]: That's how close you have to be, or you get massive drift. The system becomes unstable. You see this with massive systems built on Docker for local, Kubernetes for production, and a specific thing for something else. That complexity slows developers and becomes unstable at scale, making it hard to iterate. We want to compress that way down and say, “As close to prod as possible is where we want to be.”From AISRE Skeptic to Agent BelieverSwyx [00:45:00]: I was texting Erica for questions, and she says you were originally not a believer in AISRE. Have you come around on it?Jake [00:45:10]: I flipped, but I'm still not a believer in AISRE if you don't have the primitives to make it safe. If you unleash AISRE on production infrastructure without safe primitives for copying volumes and making sure things are fine, it's going to nuke your production database. It's not a matter of if, but when. I'm a big believer in making those loops safe.Jake [00:45:33]: I was a deep AI skeptic until 2023. In 2024, I thought, “Maybe I can roughly make this thing do it.” In 2025, I thought, “Now I can hold this.” Over winter break, everybody came back saying, “It's almost impossible to hold this.”Swyx [00:46:01]: Did you see this on the Claude docs? CloudBot? OpenCloud?Jake [00:46:06]: It's gotten to a point where it's harder to hold it wrong than to hold it right. There's a scene in Avengers where Vision picks up Thor's hammer and says it's terribly well-balanced. It self-balances and works well. I'm a deep believer at this point that this will be the dominant species: assembly, C, C++, JavaScript, words.Swyx [00:46:35]: It feels like a big jump.Jake [00:46:37]: It is. But it's not like you abandon CPU-based discrete logic and move straight to fuzzy logic. You need both. Your skills should call code or applications or some static structure. You can use skills to distill what the procedure should be or how the code should act.Jake [00:47:02]: I'm coming to a thesis: you need three points. You need a clear spec defining the system, the code, and the tests. When you say it out loud, if you've been in engineering long enough, you're like, “Of course. That's an RFC, tests, and code.” But they all matter. Having them together lets them reinforce each other: the spec and tests match, but the code doesn't, so reconcile it. Or the tests and code match but the spec doesn't, so reconcile that. That's the iteration loop.Jake [00:47:41]: That's why you're seeing people talk about software factories, docs, and reconciliation. Some of that is architectural astronomy if you don't implement it, but that loop is where most things will end up.Swyx [00:48:07]: For listeners, we've been talking about this on the pod for three years: the holy trinity of specs and tests. Itamar Friedman from Qodo is the reference if people want to look it up.Self-Modifying Infrastructure and the End of Push-Pull-RebuildSwyx [00:48:18]: One thing I want to mention on the OpenCloud idea is self-modification. I don't know how Railway would support it, but I have my OpenClaw, and I just tell it it has the Railway CLI and can do whatever. In theory, whatever capabilities or new infra it needs, it can call the Railway CLI, provision it, and add it to itself. The agent can modify its own infra.Jake [00:48:45]: It's nuts. I have a loop set up where you put the Railway CLI on top of something that runs on Railway. You're authenticated as whatever the current box is, and you can make any changes to it. Then you call Railway deploy, and it deploys itself.Jake [00:49:04]: It's like: “I need to spin up this instance of this environment. I already exist in this environment. Excellent, I have access to a Postgres instance now.” That's where we want to go with agentic, self-replicating infrastructure. That's your loop: iterate in production. You continue making changes. If it works, merge it upstream. If it doesn't, throw it away.Jake [00:49:37]: How do you make throwaway copies trivial to spin up and super cheap? The era of “I have an AWS instance with four vCPU and 16 gigs of RAM” is going to get destroyed. If you do that for agents, you need a thousand of those machines. It's prohibitively expensive compared with what we've spent a ton of time figuring out: the atomic unit of deploy, whether you call it isolates, sandboxes, or something else. Only pay for what you use, spin up instantaneously, and close the loop as quickly as possible.Jake [00:50:15]: If the system can self-replicate safely and say, “This is my environment, I'm making these changes,” it can come back with, “Does this look good? This is a new state of infrastructure given this prompt. I think I've solved it.” Then you go back and say, “Actually, it looks different.” It does the loop again. Then you say, “Cool. Apply.”Swyx [00:50:38]: That's retroactively obvious, which is the most useful kind. Any other comments on agent deployment on Railway?Jake [00:50:51]: It's getting better every day. I'm on X or Twitter. You can always yell at me about the parts not working as well as they should, because plenty of things should work way better.The New Serverless: Stateful, Long-Running, Pay-for-What-You-Use LinuxSwyx [00:51:04]: At this stage, when people want massively or embarrassingly parallel compute, they usually talk serverless. I feel like there's a new serverless compared to the previous five years of serverless. You're in that new bucket. Do you have comparisons or philosophical differences you want to call out?Jake [00:51:31]: It's somewhere in between. It's the ability to run stateful, long-running workflows or executions.Swyx [00:51:42]: Vercel has Fluid Compute, Cloudflare has some container thing, Google has App Runner and others.Jake [00:51:55]: That's where everything is roughly going, and it's why we've been working on this for six years. We believe users need access to a computer: a box that speaks Linux. They need to deploy what they want. Other systems change the surface area of what you can build. For us, users need a computer and need to deploy anything they truly want. That's why we've focused on the primitives: network, compute, storage. If we give you those and expose them so you can run things indefinitely, that's where we believe it's going.Jake [00:52:43]: Twitter has no nuance, so everyone says “servers” or “serverless.” It's always somewhere in the middle: I want to run it for a long time, but I don't want to provision the resource statically or pay for things I'm not using. That's been our thesis from day one: pay only for what you use, run it indefinitely, and it is full Linux.Swyx [00:53:12]: That's why I like the naming of Fluid. It's fluid. Flexible.Heroku, Focus, and Carrying the Torch Without Becoming the PastSwyx [00:53:18]: Another milestone is the Heroku official deprecation. You're one of the presumptive new Herokus. “New Heroku” has been a category for as long as I've been in developer tooling. It's finally happening. What was that like? Any behind-the-scenes of, “This is the moment”?Jake [00:53:42]: You have people where you're like, “You were running stuff on here? You, as this company?” It's crazy that names you would know are running on it and now coming to us saying, “We want to move a lot of this off.”Swyx [00:54:00]: Any behind-the-scenes on why Salesforce let Heroku stagnate?Jake [00:54:05]: I can only guess. It's hard when it's not your business. Salesforce's business is to build a great CRM. That's their focus. Then you acquire a compute business as an offshoot. A lot of early Meta people talk about focus. Boz has a write-up about how in the early days of Meta they had no money, so they were forced to focus. Then they turned on the money tree and had no reason not to split their focus.Jake [00:54:52]: But that dilutes your product. You get offshoots where you ask, “Is this the focus of the business?” If it's not core, it languishes. A lot of companies get in trouble when they split focus because they're fighting a multi-front war, not just externally but internally for alignment. Where are we going? What are we doing? What is our purpose?Jake [00:55:24]: If you're Salesforce-built and mission-driven, you want to work on Salesforce. Heroku is off to the side. It's not core to the business. Getting resources, budget, focus, and alignment internally becomes hard. It was a matter of time.Swyx [00:56:06]: Kudos for them to call it out instead of leaving it unknown.Jake [00:56:12]: Their release was a little odd. They called it out, but they didn't say they were shutting it down. Behind the scenes, I think they issued messages to people saying they should close accounts and that they were going to deprecate and remove things over time.Jake [00:56:30]: It's crazy because some of my first deployment experiences were on Heroku. You start with dragging things into an FTP server, then you try to get a deploy working, and then it's Heroku. It was the on-ramp for us. But the wheel turns. New things emerge. We're happy to carry the torch for a lot of that. But we don't want to be the new Heroku. We want to be the way people build and deploy software, and ultimately the way people monetize software over time.Swyx [00:57:19]: It's still a big crown to be the new Heroku. There are 50 companies that fought for that.Jake [00:57:23]: Everybody is holding some portion of it. We're happy to support people and companies. The platform works differently. The game loop is similar, but we've been dogmatic about where these things are going: primitives, agents, fan-out. Some things fit; some workflows need to change. We have an approximation of Heroku pipelines with the environment system. It's exciting. We've got a ton of people we can support, and it's growing a lot.Temporal, Workflow Engines, and State MachinesSwyx [00:58:12]: I have one more technical question about Temporal. I've sold my shares. You're a power user and one of our earliest customers. I met you through Temporal. You built on Temporal. You have complaints. This may be the most neutral and informed conversation anyone will hear about Temporal without someone working at the company.Jake [00:58:39]: That's fair. I've used Temporal for almost 10 years because of Cadence at Uber.Swyx [00:58:52]: Give people a sense of what Cadence was at Uber.Jake [00:58:57]: Cadence was the precursor to Temporal. It powers trip actions, rides, when you rent a Jump bike or scooter or car. You're running workflows for a period of time and saying, “This ride will run indefinitely until it finishes.” You attach information: you paused in this zone, so add this charge to the bill. When you end the trip, the workflow is done. That experience was powered by Cadence at the time.Swyx [00:59:34]: I used to say it's like programming the entire user journey top-down as one function.Jake [00:59:39]: It's a powerful idea and important. It's also important for the next phase of the agentic journey. You want an agent to do a specific task, be complete or incomplete on that task, and move on to the next thing. You need a way to manage workflows dynamically.Jake [00:59:59]: Temporal was always great in theory, and great when you got it working the way you wanted in production. But it required you to model the entire journey in your head. If you didn't, you could cause issues where replaying the state of the workflow causes non-determinism.Swyx [01:00:25]: Because it works on deterministic workflow history.Jake [01:00:28]: Exactly. I describe it as a jet engine. If you know how to operate it and run it, it's great. But you can't hand it to people trying to build complicated things if they don't have the whole state in their head.Jake [01:00:48]: We run our whole deployment pipeline on top of it. That's a reasonably complicated workflow: pre-commit hooks, signaling, queuing, and all the rest. We ran into the same thing at Uber. As you express a large workflow, it gets more complicated, with more states in the state machine that you have to map back to the workflow.Swyx [01:01:15]: It's a lot of ifs.Jake [01:01:16]: Exactly. At Uber, we built a system for doing the state machine and testing it. We've started to build some of those things here because it's grown heavily. It's not quite love-hate. When it works well, it works super well. But if someone who doesn't have full context puts something into the system that invalidates state or causes non-determinism, or spins off a ton of activities, you have to keep track of underlying SRE knobs like activity slots. Those should scale with memory, vCPU, and so on. It becomes a bear to scale.Swyx [01:02:10]: You need a capable sysadmin running things behind the scenes. If you moved off, what would you do?Jake [01:02:19]: We'd build our own workflow engine. We have a few internally that we've worked on.Swyx [01:02:27]: This is one of those classes of things you typically wouldn't vibe code, but I'm wondering if you can.Jake [01:02:33]: I still don't think you should vibe code it. You still want to run decent tests to make sure it works.Swyx [01:02:39]: Timo didn't invent that from scratch either. There are libraries you can run. On top of that, it's just a state machine that you have to map out. Ultimately, you define the instructions you want and run them through a state machine.Jake [01:03:00]: It's very doable. Workflow stuff is interesting. Restate is doing neat stuff here.Swyx [01:03:10]: You're tied into JavaScript. Are you a JavaScript maxi?Jake [01:03:13]: Internally, we have TypeScript, Rust, and Go. We don't add more languages. Actually, we have a little C because we write BPF code and hooks. But those are the languages.Swyx [01:03:28]: Is this for sidecars?Jake [01:03:32]: No. It's for the networking stack, volumes, and things like that. We use TypeScript a lot because it powers the dashboard, but we're moving a lot of workflow stuff off the dashboard stack and into the infrastructure stack.Railpack, Nixpacks, and Content-Addressable FilesystemsSwyx [01:04:00]: Cool. Any other technical infrastructure stuff? Railpacks?Jake [01:04:07]: We built an engine for determining dependencies based on source code. It's called Railpack. We built the first version, Nixpacks, on top of Nix, and then we moved.Swyx [01:04:17]: People have been trying to get me to adopt Nix and NixOS for four years. Is it ever going to be a thing?Jake [01:04:23]: I don't know. We're excited about it, but it has pain points. Think of it as a stack of versioned binaries at specific slices in time. If you want version X and version Y, you bloat the package space, which blows up image size and makes real-world workloads difficult.Swyx [01:04:53]: But you content-address it and cache it. In theory, there are optimizations.Jake [01:05:00]: In theory, yes. But with a large enough user base and disparate enough machines, you run into a problem Meta described in the XFAAS paper, their internal serverless system. It becomes difficult at scale unless you break out specific runtimes.Jake [01:05:24]: We didn't want to do that because we wanted to truly allow you to deploy anything. That was our initial thing with Nix. But we've moved toward interesting work around content-addressable file systems that can lazy-load anything from any point and page it into memory.Swyx [01:05:48]: Amazing.Jake [01:05:49]: The future is very bright. It's crazy, and it's going to be nuts.Coding Agent Spend, Roadmaps, and Token ROISwyx [01:05:54]: Founder journey stuff?Alessio [01:05:56]: Your cloud usage: you tweeted you're going to spend $300K this month?Jake [01:06:01]: I think we got to $200K.Alessio [01:06:02]: Coding agents?Jake [01:06:03]: Yeah.Swyx [01:06:04]: Across the company?Alessio [01:06:05]: You only have 35 people, so I'm sure they're not all spending $10K a month. What's the distribution?Jake [01:06:10]: I think I'm at about $25K. We have power users all the way down. We came back from winter break, and I basically said, “If you're writing code by hand, you're doing this wrong.” The tools are good enough now that you can move extremely quickly. There are issues and pain points, but you should be reviewing the code you are writing instead of writing it by hand.Jake [01:06:40]: Architectural patterns matter more now than ever, but you shouldn't spend your time generating code you would write. If you know how to write it, ask the agent to write it and reconcile it until it looks like you would have written it yourself.Jake [01:06:58]: People misconstrue my propensity to push people toward agents as connected to our growth and some reliability bumps. They're not necessarily related. The tools are good enough to move extremely quickly and build things way larger than you could before.Jake [01:07:19]: To the earlier point about cooling data centers in space: I don't know. But with software, you can ask, “How would I build block storage from scratch? How would I do these things?” I have ideas because I have history and have read papers. Let me work them out and build massive test benches with thousands of tests, because those are now free to author. If you're not using AI systems to speed-run your roadmap and reconcile your existing system onto the future, you're missing a large point of what's happening.Alessio [01:08:12]: What's the path to spending $3 million a month? Is it bound by ideas and things customers can absorb?Jake [01:08:19]: For most companies, it's bound by deployment at this point. That's why we've seen a massive boom in users and companies, from Fortune 50s down, asking how to get developers to move faster. You'll probably hit your CFO before any technical limits because they'll look at the eye-watering amount of money spent on tokens. Inference costs have to come down, but we're inference constrained now. There will be price discovery around what makes sense for an org to adopt.Jake [01:09:06]: I think you'll end up with the F1 driver concept. If someone is really adept at these things, it makes sense to put them in a $3 million car. If they're not, it probably doesn't make sense. You'll take a few people and say, “You can drive the F1 car. We need to go in this direction. Figure out if it works and prototype it.”Jake [01:09:33]: We've done some of that and vastly accelerated our roadmap. We thought we'd ship something in a few years; now we can probably ship it in a few months because we validated it and don't have to build it incrementally. We can skip steps and move toward our vision.Alessio [01:09:58]: A lot of people are realizing the roadmap doesn't always have a business impact, so they say tokens are too expensive. But if your roadmap were built to make more money by the time you built it, you'd have token pricing for it, the same way you do with sales. You'd spend a billion dollars on sales if you knew you would get $2 billion of revenue.Jake [01:10:19]: Exactly. A naive way to measure this is the percentage of tokens that end up in production. If you can measure impact because those tokens end up in production, that's awesome. But the burden of proof will rise. Internally, we have a growing number of pull requests that haven't merged. The question becomes: how do you get this into production? It's about how quickly you can build and deploy software, which is exciting because that's our whole thing.The SDLC Shift: Prompt Requests, Feature Flags, and Safe RolloutsSwyx [01:10:56]: The SDLC is changing. One thesis is that the pull request is dying. It's going to be the prompt request. Beyond that, code review is also kind of dying if you have all the other systems in place. What else is changing about the SDLC?Jake [01:11:19]: The AISRE and the tools to make it happen. AISRE is pie-in-the-sky aspirational. What does it take to get an AISRE? What tools do you need to build?Swyx [01:11:32]: You should expose your tooling to customers at some point. The Central Station command center.Jake [01:11:39]: We have it for template maintainers. Template maintainers can deploy and maintain templates, and they get feedback. We're going to expose those things incrementally.Swyx [01:11:51]: Clustering around incidents. Everyone has a version of that, but I don't think anyone has solved it.Jake [01:11:56]: I won't say we've solved it internally, but it's gotten so good that we can see incidents forming pretty quickly. At some point, those will be things either someone else builds or we build. We've always built things purpose-built for us. If it makes sense to make it useful for users, monetize it, or turn that loop into a profit center instead of a cost center, we want to do that.Jake [01:12:28]: Pull request is definitely dying.Swyx [01:12:29]: Do you do first-party feature flagging and incremental rollout stuff?Jake [01:12:34]: We have a feature-flagging engine we built internally and will eventually roll out.Swyx [01:12:38]: I don't see it as a user. How come you didn't give us what you have?Jake [01:12:43]: We have to beta test it. We care a lot about the quality of the things. There's plenty we've used internally that doesn't make it all the way through the journey because it fails. It works for one service but not multiple services. We'd have to build it for multiple services and know that if we released it, we'd rebuild it again and again. Some things are worth that, but many inform the roadmap.Jake [01:13:18]: We don't want to dilute the experience by saying, “This works, but only for this service,” unless it's a core initiative. Over the next few months, we'll roll out things that work for a single service, then multiple services, then multiple services across the environment. You have to be deliberate. Otherwise you create broken disparate experiences and support load because people ask how to use the feature.Jake [01:13:52]: It's the earlier expansion and compaction pattern. You expand the company to get features, then compact and smooth them out so the experience is stellar. You told me in the hallway, “It's gotten so much better.” Internally we're saying, “This part really sucks. We need to make it significantly better.”Swyx [01:14:11]: I can attest to that over the last three years watching you build Railway. For listeners, feature flagging is a huge part of Uber culture. So much so that they have too many feature flags and another thing to remove feature flags. Facebook has Gatekeeper. Agents are going to need this. It's fundamental to incremental rollouts. OpenAI acquired Statsig. GPT-5 is routing and flagging through different models.Jake [01:14:56]: It's super important. If the software development lifecycle is going to change because we're doing things 1,000 times faster and 1,000 times more concurrently, what becomes important at scale?Jake [01:15:16]: Before I started Railway, I built a feature-flagging product and tried to sell it. It was an easier version of LaunchDarkly. I ran into a problem: anyone small enough to adopt your technology doesn't care about feature flags, and anyone large enough to need feature flags needs so much scale that you have to build out all the infrastructure. I scrapped it.Jake [01:15:42]: But what is old is new again. Companies are trying to move quickly, but you can't YOLO a vibe-coded thing straight into production. You need to say, “Here's my blast radius, my impact, and I want to shadow it for these users.” Feature flags. You're going to need the tools larger companies built to maintain their structures. Everything gets compressed by 1,000x so everybody can build those structures quickly.Jake [01:16:07]: That's exactly where we are: compressing the software development lifecycle, then expanding it and adding more new things.Cattle, Pets, and Clonable InfrastructureSwyx [01:16:15]: Another term that comes to mind for newer developers is “cattle, not pets.” People treat production like a pet. It has a name. You baby it and keep it alive. With cattle, you can mass farm, roll out, portion parts out, and kill them.Jake [01:16:37]: I think that might change. You can move toward having pets as long as you have a cloning machine for your pets.Swyx [01:16:52]: Yeah.Jake [01:16:52]: If you can snapshot every single thing at every frame, it doesn't matter if something gets obliterated because you have a snapshot of it. The things we've built right now are designed to block changes from the hermetically sealed DevOps line. You have to write a Dockerfile because you nee

#912 Want to land more podcast interviews and pitch like a pro? In this episode, host Kirsten Tyrrel sits down with Parker Olson, co-founder of PodPitch, to explore the intersection of automation, podcasting, and entrepreneurship. Parker shares how his tool helps experts and businesses get booked on the right shows through AI-powered outreach — and reveals the common mistakes people make when trying to pitch themselves. They also dive into why starting with a clear “listener promise” is essential for any new podcast, how to validate your business idea by asking the hard questions early, and why making your first dollar fast can be the best product development strategy of all! (Original Air Date - 9/16/25) What we discuss with Parker: + What makes a great podcast pitch + Common mistakes when pitching shows + Importance of a clear listener promise + How PodPitch automates outreach + Vetting active vs. inactive podcasts + Why value > self-promotion on interviews + ROI of podcast guest appearances + Validating ideas by asking for payment + B2B vs. B2C sales psychology + Building simple tools before scaling Thank you, Parker! Use code MILLIONAIRE for $100 off your first month of ⁠PodPitch⁠. Follow Parker on ⁠LinkedIn⁠. To get access to our FREE Business Training course go to ⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠MillionaireUniversity.com/training⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠. To get exclusive offers mentioned in this episode and to support the show, visit ⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠millionaireuniversity.com/sponsors⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠. Learn more about your ad choices. Visit megaphone.fm/adchoices

Getting clients from podcasts isn't just for B2B business owners like business coaches and service providers. It can be effective for parenting coaches, health coaches, therapists, and others in the B2C space. Today, I'm breaking down how you can get coaching clients from a podcast as a B2C business owner and why a podcast is an effective marketing and sales platform regardless of whether you serve other business owners or consumers.In this episode, I'm giving you all the tea on:Whether you can get coaching clients from a podcast as a B2C businessHow to create a podcast that will bring in leads and clientsStrategies for promoting your offers on your podcastResources Mentioned in Today's Episode:Get on the waitlist for Podcast Like a Business Owner!Simplecast 2025 Podcast StatsRSS 2025 Podcast StatsRelated Episodes and Blog Posts:Episode 287: The Podcast Marketing Strategy That Booked Out Sarah Lovell's 1:1 Coaching Services [Client Case Study] Ways I Can Serve You:Join the Evergreen Marketing Era NewsletterEvergreen Marketing AcceleratorRecommended Podcast + Business Tools:Email Marketing: Flodesk (14-day Free Trial)Podcast Hosting: Captivate (30-Day Free Trial) Recommended Keyword Research Platform: Keysearch.coCRM: Dubsado (Save 20% on your first month or year)Website Builder: Showit (30-Day Free Trial)Some of the above links are affiliate links, meaning I may earn a small commission at no additional cost to you.For show notes and resources mentioned in today's episode, head to www.mamaturnedmompreneur.com/episode304/Connect with Andria:Threads: @evergreenmarketingeraInstagram: @evergreenmarketingeraEmail: hello@mamaturnedmompreneur.comWebsite: www.mamaturnedmompreneur.com

Have you ever seen Schitt's Creek? No? You really need to watch it. That's advocacy. And it's older than marketing itself - somebody took a bite of something and said, “You gotta try this.” Jason Grunberg, CMO of Forter, didn't watch the show until he got sick and had nothing else to do. By the time he was better, he was binge-watching instead of resting. In this episode, he breaks down what Schitt's Creek teaches B2B marketers about pointy characters, ownable positioning, brand as a bank, and why the transformation story is the only story worth telling. Together, we dig into why “safe is not where we make really strong emotional bonds,” what the Rosebud Motel's rebrand can teach any B2B company trying to differentiate, and why AI inflation has already made “AI” a meaningless differentiator. About our guest, Jason Grunberg Jason Grunberg is CMO at Forter, the identity intelligence platform for digital commerce. With a background spanning agency and in-house roles across B2C and B2B, he brings a rare perspective on what it means to treat every buyer as a consumer - because at the end of the day, a wrong decision costs someone their job, and nothing is more personal than that. What B2B Marketers Can Learn From Schitt's Creek Advocacy is the root of every decision. Jason didn't watch Schitt's Creek because of the awards or the marketing. He watched it because people he trusted kept telling him to. His takeaway for B2B: “Advocacy has been a core part of marketing and brand forever for anything. This is coded almost into the human experience - advocacy is the root of like how we end up making decisions and choices.” Before you chase the next channel, ask whether you're creating the conditions for your customers to tell their colleagues, “You really need to try this.” Pointy characters resonate more than representative ones. The safest instinct in B2B marketing is to round off your personas until they feel inclusive. Schitt's Creek did the opposite - and it's why strangers kept telling Jason the show was basically his family. Ian's takeaway: “The more pointy you make it, the more weird, the more absurd, it actually will resonate that much better.” Stop asking whether every CIO will see themselves in your story. Make the character want something specific, and trust the audience to find themselves in it. Brand is a bank - and technology is never the real differentiator. The Rose Apothecary didn't succeed because of its product formulas. It succeeded because of the experience, the distinctiveness, the emotional value. Jason connects it directly to his work at Forter: “Quality is replicable, at least now more so than ever. The brand has to mean something.” On technology positioning, he's blunt: “If there's always the push from your product team to be like, ‘This is the core differentiator,' I'm like, ‘Cool. That is 2,000 lines of code deep. That sounds really replicable. And it doesn't say I'm getting a raise if I buy this.'” “Safe is not where we make really strong emotional bonds. On the edges is where we do that - because on the inside, there's a lot of edge. We've just been conditioned to not show it all the time.” - Jason Grunberg Time Stamps [1:25] Meet Jason Grunberg, CMO of Forter [2:17] Why Schitt's Creek? The Show That Felt Like His Family [4:53] Jason's Role at Forter: Decisions AI and Customer-Centric Marketing [5:56] What Is Schitt's Creek? Character Development as a Foundation [12:11] Marketing Lesson #1: Advocacy Is Coded Into the Human Experience [15:56] Marketing Lesson #2: Pointy Characters Win — Stop Regressing to the Mean [23:14] B2B Is Still Consumer: Everyone Is a Person Making a Personal Decision [26:35] Marketing Lesson #3: Brand Experience — Rose Apothecary and the Bank Analogy [29:11] Marketing Lesson #4: The Rosebud Motel and the Power of Positioning [32:18] The Name, the Pun, and the Juxtaposition of Lowbrow and Highbrow [36:21] The Audacity of the Arc: Why Schitt's Creek Ended on Purpose [39:07] Final Thoughts and Takeaways Links Connect with Jason on LinkedIn Learn more about Forter About Remarkable! Remarkable! is created by the team at Caspian Studios, the premier B2B Podcast-as-a-Service company. Caspian creates both nonfiction and fiction series for B2B companies. If you want a fiction series check out our new offering - The Business Thriller - Hollywood style storytelling for B2B. Learn more at CaspianStudios.com. In today's episode, you heard from Ian Faison (CEO of Caspian Studios) and Meredith Gooderham (Head of Production). Remarkable was produced this week by Meredith Gooderham, edited by Jon Goldberg, and our theme song is “Solomon” by FALAK. Create something remarkable. Rise above the noise. Hosted by Simplecast, an AdsWizz company. See pcm.adswizz.com for information about our collection and use of personal data for advertising.

I sit down with my friend Jonathan Courtney, a.k.a. Jicecream, to dig into the 9 biggest startup opportunities I see right now across B2C, AI, mobile, and IRL. We each pick ideas, trade reactions, and pressure-test them live. The conversation ranges from agent-first "action apps" to elder tech, third spaces, hobby retreats, pet health, AI-native media, and the case for selling AI "junior employees" to small businesses. Listeners walk away with a concrete map of where to build in 2026, plus the framing I use to decide which niche is worth marrying. Timestamps: 00:00 – Intro 01:14 – Idea 1: Unscripted Creator Shows (Twitch model for tech) 07:50 – Idea 2: Action Apps: AI Agent Native Apps 16:39 – Idea 3: Loneliness and IRL Communities 26:47 – Idea 4: Elder Tech: Building for 65+ 33:21 – Idea 5: Adult Hobbies 38:17 – Idea 6: AI Employee and AI Agents 45:33 – Idea 7: Personalized Nutrition/Health 53:08 – Idea 8: Pet Health and AI for Animals 57:34 – Idea 9: AI-Native Media Companies Done Right 01:03:18 – Stacking Ideas: Live + Retreats + Entrepreneurs 01:07:22 – Final Thoughts The #1 tool to find startup ideas/trends - https://www.ideabrowser.com LCA helps Fortune 500s and fast-growing startups build their future - from Warner Music to Fortnite to Dropbox. We turn 'what if' into reality with AI, apps, and next-gen products https://latecheckout.agency/ The Vibe Marketer - Resources for people into vibe marketing/marketing with AI: https://www.thevibemarketer.com/ FIND ME ON SOCIAL X/Twitter: https://twitter.com/gregisenberg Instagram: https://instagram.com/gregisenberg/ LinkedIn: https://www.linkedin.com/in/gisenberg/ FIND JONATHAN ON SOCIAL Unscheduled CEO Podcast: https://www.unscheduledceo.com/ X/Twitter: https://twitter.com/Jicecream LinkedIn: https://www.linkedin.com/in/jonathan-courtney-4510644b/

Favour Obasi-ike, MBA, MS demystifies the Facebook Ads Library and LinkedIn Ads Library, providing a detailed walkthrough on using them to research competitors, understand ad trends, and inspire ad creation. He emphasizes the distinction between B2C (Facebook/Meta) and B2B (LinkedIn) advertising, noting LinkedIn's higher cost and intent focus, while underscoring the importance of organic branding as a foundation for paid marketing. Favour Obasi-ike demonstrates how leading companies deploy these tools, showcases nuanced platform differences, and compares cost-per-click across Meta, LinkedIn, Google, and TikTok. He also shares new insights on LinkedIn's evolving platform—including paid advice sessions—and explores the promises and pitfalls of AI-powered website builders, warning of current technical limits while highlighting practical safeguards. Throughout, he connects performance measurement, ad copy, landing page optimization, and conversion intent, offering actionable advice on research, conversion strategy, and digital asset protection for marketers and SEO professionals alike.Who Is This For?This podcast episode is ideal for:Marketing professionals, digital strategists, and business owners interested in mastering social media advertising.Anyone seeking practical strategies on using Facebook and LinkedIn Ads Libraries for competitor research, inspiration, and campaign optimization.Individuals curious about the evolving role of AI in SEO, website development, and digital marketing.Key Moments & TimestampsIntroduction to Ads Libraries: difference, power, and practical links – 00:00:03How to use Ads Libraries for research and competitive insight – 00:01:43Detailed comparison of search/filter functionalities (LinkedIn vs. Facebook/Meta) – 00:02:41Limitations: lack of public ad performance analytics – 00:06:25Roleplay: live demonstration with Nvidia and King Kong Marketing – 00:09:15Analyzing ad count and demographic distinctions (B2B vs. B2C) – 00:13:29Using ad longevity and impression markers for campaign inference – 00:14:33Brand presence & organic/paid synergy on platforms – 00:15:28Cost comparison: LinkedIn, Facebook, Google, TikTok – 00:36:14, 00:40:52Best practices: building organic presence before paid campaigns – 00:34:32Discussion: AI website building (pros, cons, future-readiness) – 01:00:41Safeguarding your digital assets and monitoring website readiness – 01:03:09Takeaways: action steps for competitive research and campaign improvement – 01:19:40FAQsQ: What's the biggest difference between Facebook and LinkedIn Ads Libraries?A: Facebook excels at B2C and provides wide targeting, while LinkedIn is tailored for B2B audiences and offers granular demographic filters (00:01:43, 00:13:29).Q: Can I see ad performance and conversion data in these libraries?A: No, performance analytics (like conversions or spend) are not publicly available, but ad frequency, longevity, and low-impression markers offer hints (00:06:25, 00:14:33).Q: Does Favour Obasi-ike recommend using AI website builders?A: They're rapidly evolving, but typically restrict customization and future scalability; always check if your site is AI-ready and back up your code (01:00:41, 01:03:09).Q: How does LinkedIn compare on ad costs?A: LinkedIn is typically $2–$6 per click, more expensive than Facebook and Google, recommending high-ticket or B2B campaigns for ROI (00:36:14, 00:40:52).Action StepsResearch Your Competition: Use Facebook and LinkedIn Ads Libraries to analyze competitors' creative, targeting approaches, and landing pages.Prioritize Organic Presence: Build robust, consistent brand profiles before investing in paid ads (00:34:32).Calculate Platform ROI: Factor in cost-per-click, sales cycle, and campaign intent before allocating budget.Test & Optimize Landing Pages: Ensure ad links align with campaign copy and optimize for conversions.Evaluate AI Tools Carefully: Use AI web builders with caution, regularly back up site code, and assess AI-readiness (01:03:09).Leverage Platform Updates: Explore new LinkedIn offerings like advice sessions for enhanced professional monetization (00:26:56).Safeguard Digital Assets: Keep site ownership and editability top-of-mind for future scalability and security.For a complete learning experience, review the episode's full discussion and check out the referenced Ads Libraries at the top of the chat (01:20:03).Ready to Rank? Book Your SEO & Web Dev Services Today

What if everything you believed about sales was wrong? Art Sobczak sits down with Dr. Lorenzo Bizzi, professor at Cal State Fullerton and author of Myths Versus Science of Selling, to challenge the conventional wisdom that has dominated sales training for decades. From "always be closing" to "people buy on emotion" to "extroverts make the best salespeople" — Dr. Bizzi has spent years collecting academic research that tells a very different story. And he's not just here to tear down the myths; he's here to make you think. In this episode, you'll discover: Why emotional influence tactics can actually work against you — and what to lead with instead The surprising truth about extroverts vs. introverts in sales Why competing against your colleagues may be quietly killing your motivation How "selling orientation" can paradoxically lower your long-term results What truly separates B2B selling from B2C — and why most advice ignores this Whether you're new to sales or a seasoned pro, this conversation will challenge your assumptions and sharpen how you think about every customer interaction. Grab Dr. Bizzi's book on Amazon and visit lhttp://lorenzobizzi.com to learn more.

Listen and subscribe to Money Making Conversations on iHeartRadio, Apple Podcasts, Spotify, www.moneymakingconversations.com/subscribe/ or wherever you listen to podcasts. New Money Making Conversations episodes drop daily. I want to alert you, so you don’t miss out on expert analysis and insider perspectives from my guests who provide tips that can help you uplift the community, improve your financial planning, motivation, or advice on how to be a successful entrepreneur. Keep winning! Two-time Emmy and Three-time NAACP Image Award-winning, television Executive Producer Rushion McDonald interviewed Dr. Cameka Smith. Founder of The BOSS Network, from Money Making Conversations Masterclass: Purpose of the Interview The interview aimed to: Highlight The BOSS Network’s mission to empower women of color through entrepreneurship, career development, and community support. Share Dr. Smith’s personal journey from layoff to leadership, inspiring others to embrace entrepreneurship. Discuss strategies for business success, funding opportunities, and mentorship for Black female founders. Key Takeaways Origin of The BOSS Network Founded in 2009 during the recession after Dr. Smith was laid off from Chicago Public Schools. Initially started as local events in Chicago; now a digital community reaching 200,000 women nationwide. Mission: Bringing Out Successful Sisters (BOSS)—promoting small business spirit and career growth. Impact & Achievements Invested in 100 Black female founders through grants. Trained 50,000 women on business strategies. Coached 10,000 women on starting businesses. Created Boss Business University, offering mentorship and digital programs. Pivot During COVID Shifted from 35% event-based revenue to 75% digital. Launched Boss Impact Fund and Invest in Progress Grant: $10,000 grants + 4-year scholarships for recipients. Combined funding, mentorship, and marketing support for sustainability. Challenges & Mindset Entrepreneurship requires planning, resilience, and community support. Dr. Smith saved money before leaving her job and leveraged relationships for growth. Quote: “Entrepreneurs will work 80 hours for themselves but don’t want to work 40 hours for someone else.” Top 3 Mistakes Entrepreneurs Make Lack of research: Understand your industry, competitors, and market. No revenue model: If you’re not making money, it’s a hobby, not a business. Ignoring relationships: Networking and partnerships are key to success. Unique Marketing & Partnerships Dr. Smith built direct relationships with brands, bypassing agencies that offered “pennies on the dollar.” Created a dual revenue model: B2B (corporate partnerships) + B2C (community engagement). Core Philosophy Motto: Believe, Plan, Win. Quote: “Those that show up, go up.” Success is rooted in faith, persistence, and leveraging community. Notable Quotes “I was born to be an entrepreneur. My mother told me, until you become your own boss, you have to follow the rules.” “Less than 1% of Black women get VC funding—so we created our own fund.” “Relationships are your key to success. When social media goes away, your audience remains.” “If you have a business and you don’t have money, you’ve got a hobby.” “God will not birth anything inside of you that He will not give you the tools to deliver.” #SHMS #STRAW #BESTSupport the show: https://www.steveharveyfm.com/See omnystudio.com/listener for privacy information.

Listen and subscribe to Money Making Conversations on iHeartRadio, Apple Podcasts, Spotify, www.moneymakingconversations.com/subscribe/ or wherever you listen to podcasts. New Money Making Conversations episodes drop daily. I want to alert you, so you don’t miss out on expert analysis and insider perspectives from my guests who provide tips that can help you uplift the community, improve your financial planning, motivation, or advice on how to be a successful entrepreneur. Keep winning! Two-time Emmy and Three-time NAACP Image Award-winning, television Executive Producer Rushion McDonald interviewed Dr. Cameka Smith. Founder of The BOSS Network, from Money Making Conversations Masterclass: Purpose of the Interview The interview aimed to: Highlight The BOSS Network’s mission to empower women of color through entrepreneurship, career development, and community support. Share Dr. Smith’s personal journey from layoff to leadership, inspiring others to embrace entrepreneurship. Discuss strategies for business success, funding opportunities, and mentorship for Black female founders. Key Takeaways Origin of The BOSS Network Founded in 2009 during the recession after Dr. Smith was laid off from Chicago Public Schools. Initially started as local events in Chicago; now a digital community reaching 200,000 women nationwide. Mission: Bringing Out Successful Sisters (BOSS)—promoting small business spirit and career growth. Impact & Achievements Invested in 100 Black female founders through grants. Trained 50,000 women on business strategies. Coached 10,000 women on starting businesses. Created Boss Business University, offering mentorship and digital programs. Pivot During COVID Shifted from 35% event-based revenue to 75% digital. Launched Boss Impact Fund and Invest in Progress Grant: $10,000 grants + 4-year scholarships for recipients. Combined funding, mentorship, and marketing support for sustainability. Challenges & Mindset Entrepreneurship requires planning, resilience, and community support. Dr. Smith saved money before leaving her job and leveraged relationships for growth. Quote: “Entrepreneurs will work 80 hours for themselves but don’t want to work 40 hours for someone else.” Top 3 Mistakes Entrepreneurs Make Lack of research: Understand your industry, competitors, and market. No revenue model: If you’re not making money, it’s a hobby, not a business. Ignoring relationships: Networking and partnerships are key to success. Unique Marketing & Partnerships Dr. Smith built direct relationships with brands, bypassing agencies that offered “pennies on the dollar.” Created a dual revenue model: B2B (corporate partnerships) + B2C (community engagement). Core Philosophy Motto: Believe, Plan, Win. Quote: “Those that show up, go up.” Success is rooted in faith, persistence, and leveraging community. Notable Quotes “I was born to be an entrepreneur. My mother told me, until you become your own boss, you have to follow the rules.” “Less than 1% of Black women get VC funding—so we created our own fund.” “Relationships are your key to success. When social media goes away, your audience remains.” “If you have a business and you don’t have money, you’ve got a hobby.” “God will not birth anything inside of you that He will not give you the tools to deliver.” #SHMS #STRAW #BESTSee omnystudio.com/listener for privacy information.