Podcasts about ICP

Getting hung up on by any leader hurts, but it's the grind. Jason Bay flips the script and shows you how to bounce back and book meetings. In this episode you'll learn:

Here's the knot almost every founder hits. Things are working. Money is coming in. And then everyone around you starts chanting the same advice. Niche down. It sounds smart. It feels terrifying. Because the second you try it, it feels like you're about to fire the people funding your life. So I ran the question through The Room. I convened a council session inside Invisible Council AI with cognitive models of four people who have actually built fortunes on this exact decision. Alex Hormozi. Dan Kennedy. Dan Sullivan. Frank Kern. They did not politely agree. They collided. And the collision is where the gold was. Hormozi separated the two decisions everyone blends together. Kennedy reframed a niche as a farm you can dominate, not a smaller crowd to starve in. Sullivan made the call that your current clients are evidence, not your identity. Kern added the filter that changes everything. Pick the client you could win for even if you only got paid after they succeeded. The Third Mind that emerged from all four was simple and sharp. You don't announce a divorce to find a better date. You build a revenue-safe front door for the proven buyer while the old book of business quietly funds the transition. Tighter front door. Same cash register. This one is for any founder sitting on revenue they're scared to risk and a focus they're scared to commit to. Listen all the way through. The open question at the end is the one that decides whether your niche becomes a farm or a trap. What You'll Learn The two separate decisions you're accidentally blending, and why that blend is the source of the fear. Why cash flow is not the thing you protect at all costs. It's the thing that buys you time to get smarter. How to choose your ideal client from evidence instead of preference, using the clients you already have. Why a niche is not a smaller audience. It's a market small enough to dominate and rich enough to matter. The difference between revenue and complexity wearing a fake mustache. How to reposition without sending a single client a dramatic "we've evolved beyond you" announcement. The 90-day narrowing test that turns a scary identity change into a measurable experiment. The exact first move you can run this week with your last 20 clients and a spreadsheet. Chapter Markers (Times are placeholders. Map to your final audio in your host.) 00:00 — The founder's fear: niche down without blowing up revenue 00:00 — Hormozi: the two decisions you keep blending 00:00 — Pick the niche the evidence is pointing at, not the one you like 00:00 — "Your strategy is what you say no to" 00:00 — Kennedy: a niche is a farm, not a smaller crowd 00:00 — The fantasy demographic test 00:00 — Third Mind: the Cash-Flow Airlock 00:00 — Sullivan: your clients are evidence, not your identity 00:00 — The 10x Client Test 00:00 — Third Mind: the Two-Bank Niche Test 00:00 — Kern: pick who you could win for if you got paid last 00:00 — Kennedy vs Kern: ease versus richness 00:00 — Third Mind: the Revenue-Safe Front Door 00:00 — The Council Brief and your first move 00:00 — The open question: farm or elegant trap Lines From The Room (Pulled from the live council session. These are the cognitive models speaking inside Invisible Council AI.) The Hormozi model, on the real lever: "Your strategy is what you say no to. Not what you put in the Google Doc." The Kennedy model, on choosing wrong: "If the answer is no, you don't have an ICP. You have a fantasy demographic." The Sullivan model, on the trap of revenue: "Complexity disguised as cash flow." The Kern model, on the filter that matters: "Don't choose the ICP you can sell. Choose the ICP you can almost guarantee results for." The Third Mind, on the whole move: "You don't announce a divorce to find a better date." The Frameworks Named In This Session The Cash-Flow Airlock — keep serving the messy back room while the new front door only admits the proven buyer inside a conquerable farm. The Two-Bank Niche Test — deposit into the future bank while making zero withdrawals from the current bank. The 10x Client Test — if I had ten times more clients like this one, would the business get simpler, more profitable, and more energizing, or collapse under complexity. The Revenue-Safe Front Door — test the narrow ICP in media the legacy herd doesn't even consume, while the back room keeps proving appreciation to the people paying now. Your Move This Week Take your last 20 clients. Put them in a spreadsheet. Score each one on: Did they get a measurable result How easy were they to sell How profitable were they to serve How easy were they to fulfill Did serving them drain you or energize you Would you take them if you only got paid after they succeeded Would you want ten times more just like them The overlap is your first farm. Then write one sentence. "I help [specific person or company] solve [specific expensive problem] so they can achieve [specific outcome] without [specific pain]." If it doesn't exclude people, it isn't finished. Then point your next 90 days of new marketing at that person only. Back room keeps getting served. Same cash register.

This week, join Peter and Chris as they deep dive into the fifteenth track off of RiddleBox, the almighty third jokers card from ICP, "The Killing Fields'"! Sit back and listen as they dissect the lyrics and content of the track, discuss spooky songs from Bloody Sunday, talk about attractions in the Dark Carnival, and tackle important topics like ICP's HOF bids for both music and wrestling!      The LinkTree is at https://linktr.ee/juggalorwd... Twitter/X: @JuggaloRWD IG: @JuggaloRWD Facebook: @JuggaloRWD TikTok: @JuggaloRWD Threads: @JuggaloRWD BlueSky: @JuggaloRWD The website is www.JuggaloRewind.com. Join us everywhere to talk to other listeners and about ICP, Twiztid and random juggalo nonsense. Email us at juggalorwd@gmail.com or call/text us at (810) 666-1570.        Join our Patreon! You can join for free OR for only FOUR DOLLARS a month, you can join Kilnore's Army and get at least two bonus episodes per month, videos, chats and more! Even without paying, you can still join the Patreon community! Become an official member of the Phat or Wack Pack today! -- Juggalo Rewind Patreon. Additional music provided by the IRTD. Voiceover work provided by Christmas. All music played is owned by the respective publishers and copywrite holders and is reproduced for review purposes only under fair use. #ForTheJuggaloCulture

For twenty years, marketers chased lowest-common-denominator search traffic by repackaging the same information everyone else was publishing. AI just made that playbook worthless. In this episode of Content Amplified, Stacy Shelley, a 20-year B2B cybersecurity marketing veteran who has led marketing at startups that scaled to hundreds of millions in ARR, explains what marketers should be doing instead. Stacy walks through why generic high-volume content is getting swallowed by AI overviews, why your website's job has narrowed to making an unforgettable impression on people who already know who you are, and why the awareness stage of the funnel now happens in Slack groups, Discords, social feeds, and the communities your audience actually trusts. He also reframes how to measure content success, away from raw traffic and toward ICP-account engagement and pipeline influence. If you are trying to figure out what content marketing looks like after SEO stops carrying the weight, this conversation gives you a clear path forward.About StacyStacy Shelley has been marketing in B2B cybersecurity for about 20 years, starting in the early 2000s post-antivirus era before security became its own industry. He has led marketing for multiple startups, including some that scaled into the hundreds of millions in ARR and others that had strong early exits. His entire career has been spent marketing to security buyers, an audience he describes as smart, skeptical, and full of trust issues, which means the playbooks that work everywhere else rarely translate.Show Notes- Connect with Stacy on LinkedIn: https://www.linkedin.com/in/stacyshelley/Text us what you think about this episode!

In this interview, Matt Pierce, co-founder and CEO of Immediate, shares the story behind the company and its mission to give employees early access to wages they've already earned through a simple, flat-fee alternative to payday and title loans. He discusses Immediate's growth since 2019 to nearly 700 employees nationwide, and how the company is staying mission-driven while scaling in a competitive earned wage access market. Matt also talks about how they're building alignment through shared ownership and stock education, shifting toward strategic partnerships and larger clients, and learning from a past hiring mistake in sales. He closes by reflecting on his own leadership growth, especially around delegation, coaching, and developing stronger leaders across the organization. Episode Highlights & Time Stamps 3:10 Immediate's Earned Wage Access 4:38 Fighting Payday Loans 6:40 Growth With Purpose 11:31 Building True Ownership 15:48 Scaling Through Setbacks 20:30 Learning to Let Go Key Takeaways Fast growth only works when the mission is actively reinforced through stories, not just stated in strategy documents. At Immediate, customer impact stories (avoiding late fees, accessing earned wages) keep teams aligned and motivated. Ownership is strengthened by structure giving employees equity changes how they think, decide, and act. Rapid sales expansion without clear ICP or territories created inefficiency and overlap, requiring a strategic reset. The company shifted toward strategic partnerships to scale more efficiently and improve enterprise reach. Founder leadership must evolve from "doing the work" to "coaching the team" to avoid becoming a bottleneck. Trusting the team and stepping back is essential for sustainable scale. This episode is a must-listen for CEOs and executives looking to lead innovation with purpose, scale responsibly with AI, and build cultures where people feel empowered to think boldly and grow. About the Guest Matt Pierce is the co-founder of Immediate, an earned wage access company helping employees access wages they've already earned, offering a responsible alternative to payday lending. Under his leadership, Immediate has scaled rapidly while focusing on mission-driven growth and financial wellness for workers across the U.S. How to Connect with Matt Pierce: LinkedIn: Matt Pierce https://www.linkedin.com/in/piercmb/ Company Website: https://www.joinimmediate.com/ – to learn more about his work and platform Get In Touch with Matt: https://www.joinimmediate.com/contact-us Resources & Next Steps Ready to take your leadership energy to the next level? Explore free training and resources at https://training.coreelevation.com/ to help you identify energy leaks, strengthen your leadership presence, and elevate your team's performance.

If your ICP (Ideal Customer Profile) is still built on broad categories, instinct, and a little wishful thinking, it may be more aspirational than operational.  An ICP like that leaves too much room for interpretation. Marketing, sales, and ops start working from different definitions of the right account, and the business keeps chasing customers that look right on paper but don't behave like winners.  In this episode, Drew talks with Drake Lenhan, Sitecore's Sr. Director, Global Market Intelligence & Portfolio Strategy, about what it takes to turn ICP into a source of focus that the whole business can work from.  Drake walks through the progression from validating where you actually win to building a scoring model, securing cross-functional buy-in, and creating a system that stays steady as the market shifts.  What You'll Learn:  How to spot gaps between assumed fit and actual fit  How to turn raw account traits into a practical ranking system  Why use case fit matters as much as segment fit  How to keep ICP from going stale after launch  If you're a B2B CMO ready to revisit your ICP with win data, sharper focus, and stronger cross-functional alignment, this episode gives you the blueprint.  For full show notes and transcripts, visit https://renegademarketing.com/podcasts/ To learn more about CMO Huddles, visit https://cmohuddles.com/

This week, join Peter and Chris as they deep dive into the fourteenth track off of RiddleBox, the almighty third jokers card from ICP, "12'"! Sit back and listen as they dissect the lyrics and content of the track, discuss capital punishment, talk about the ABK Tour, and tackle important topics like ICP's history with judges!      The LinkTree is at https://linktr.ee/juggalorwd... Twitter/X: @JuggaloRWD IG: @JuggaloRWD Facebook: @JuggaloRWD TikTok: @JuggaloRWD Threads: @JuggaloRWD BlueSky: @JuggaloRWD The website is www.JuggaloRewind.com. Join us everywhere to talk to other listeners and about ICP, Twiztid and random juggalo nonsense. Email us at juggalorwd@gmail.com or call/text us at (810) 666-1570.        Join our Patreon! You can join for free OR for only FOUR DOLLARS a month, you can join Kilnore's Army and get at least two bonus episodes per month, videos, chats and more! Even without paying, you can still join the Patreon community! Become an official member of the Phat or Wack Pack today! -- Juggalo Rewind Patreon. Additional music provided by the IRTD. Voiceover work provided by Christmas. All music played is owned by the respective publishers and copywrite holders and is reproduced for review purposes only under fair use. #ForTheJuggaloCulture

Does everyone on your revenue team actually agree on who your ideal customer is? Daniel sits down with Hailey McDonald, the new VP of Revenue Marketing at Sprout Social, on day one of her new role. They get into one of the most expensive mistakes in B2B Marketing: building campaigns before your ICP is truly locked in across every team. Hailey breaks down why most companies are doing ABM in name only, how to tell within five minutes that a team's ICP is broken, and why getting Marketing, sales, CS, and rev ops aligned on a single definition is the foundation everything else is built on. She also explains the difference between ICP and total addressable market, and how pipeline hitting while revenue misses is one of the clearest signals something is off with your targeting. Daniel makes the case that personalization at scale is really just personality at scale, and why the brands that stay consistent with their messaging even under pressure are the ones that win long term. Plus, Hailey's marketing hill she would die on: you can't have demand without brand. If you're looking to actually understand and identify who your audience is, this episode is for you.  Wrike brings structure, visibility, and accountability to work, so companies can make better business decisions, improve efficiency, and reduce risk. Learn more at https://wrike.com/tmm Follow Hailey: LinkedIn: https://www.linkedin.com/in/haymcdee/ Follow Daniel: YouTube: https://www.youtube.com/@themarketingmillennials/featured Twitter: https://www.twitter.com/Dmurr68 LinkedIn: https://www.linkedin.com/in/daniel-murray-marketing Sign up for The Marketing Millennials newsletter: www.workweek.com/brand/the-marketing-millennials Daniel is a Workweek friend, working to produce amazing podcasts. To find out more, visit: www.workweek.com

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

We just launched our new book! You can grab The Power of Your Personal Brand: A Playbook for Struggling Middle Managers Who Want to Do Big Things on Amazon or at ForthRight-People.com It seems like everyone is talking about the role AI should play in just about everything. You guessed it! Strategic action planning is no exception. You can prompt your favorite large language model aka LLM - ours is ChatGPT - to do some incredibly helpful things for your strategic action planning. Things like asking it to run a competitive analysis for your business, asking it to run industry trends, and asking it to give an ideal customer profile aka ICP. As with anything, there are some watchouts. Enjoy this special look at Anne's Tint World franchise in Cincinnati-Newtown on Round Bottom Rd. For more about ForthRight Business by ForthRight People or for 1:1 consultation, check us out at ForthRight-Business.com And as always, if you need Strategic Counsel, don't hesitate to reach out to us at: ForthRight-People.com FACEBOOK https://www.facebook.com/forthrightpeople.marketingagency INSTAGRAM https://www.instagram.com/forthrightpeople/ LINKEDIN https://www.linkedin.com/company/forthright-people/ RESOURCES https://www.forthright-people.com/resources VIRTUAL CONSULTANCY https://www.forthright-people.com/shop

In this episode of Fullerton Unfiltered, Brian and Adam break down how branding directly impacts the type of customers your business attracts. From websites and social media to trucks, uniforms, and messaging, they unpack why some companies attract premium clients while others constantly battle price shoppers. This conversation dives into positioning, trust, perceived value, and how to build a brand that attracts the right ICP and helps your business stand out in a crowded market.

This episode is the final installment in a three-part miniseries on ABM and go-to-market strategy, and it is extremely practical. My guest is Rehan Mirza, Chief Growth Officer at Verifiable, a credentialing automation platform that has lived through every stage of the ABM journey, from cold outbound blasting to sophisticated, intent-driven orchestration across a complex enterprise sales motion.Rehan tells the story of how Verifiable evolved its ICP from fast-moving digital health startups to regional health plans with hundreds of thousands of providers, and why that shift forced a complete rethink of how marketing, BDR, and alliances teams operate together. He talks candidly about the early lesson that volume-based outbound erodes trust, especially in healthcare, and how that shaped a completely different philosophy built around delivering value before making an ask.If you are a healthcare technology marketer working through how to make ABM actually function inside your organization, this episode gives you a clear, honest view of what it takes. Rehan has the scars to prove it.Key Topics: "(00:00:00)" Introduction and the Sway Health Podcast of the Year Award"(00:03:00)" Bridging the gap between AI activity and revenue results"(00:05:00)" Defining credentialing and Verifiable's origin story"(00:07:00)" Transitioning from a free proof of concept to a Salesforce-integrated platform"(00:09:00)" Shifting from cold outbound to intent-based lead orchestration"(00:10:00)" Ideal Customer Profile (ICP) evolution: From digital health to major payers"(00:14:00)" Moving up-market and the role of hyper-focus in ABM"(00:15:00)" Rethinking attribution: Why 70 to 80 percent overlap is the goal"(00:18:00)" Moving from pipeline generation to pipeline acceleration"(00:22:00)" The CORE framework: Conversion, Orchestration, Resonance, and Ecosystems"(00:23:00)" Using AI SDRs as a channel rather than a replacement for humans"(00:25:00)" Lessons learned: Why volume-based "spamming" erodes trust in healthcare"(00:28:00)" Closing summary and key takeaways for ABM successIf you are interested in discussing this or any other topic, let's have a chat.  Reach out to me directly to schedule a no-obligation discussion. This isn't a sales call, but rather an opportunity to talk through your questions and challenges.Follow me on LinkedIn.Subscribe to The Healthtech Marketing Show on Spotify or watch us on YouTube for more insights into marketing, AI, ABM, buyer journeys, and beyond!Thank you to our presenting sponsor, HealthcareNOW, 24/7 expert shows, interviews, and podcasts, powering healthcare leaders with innovation, policy, and strategy insights.

This week, former Forrester Research Director, Jeff Clark, is back in the studio with our host Ian Truscott to discuss an article from Anthony McPartlin, Principal Analyst at Forrester, Agentic Prospecting: Seven Reasons The Hype Falls Short. Demand generation and prospecting have changed, with sales teams now armed with tools that allow them to run lead generation campaigns across LinkedIn and email, which was traditionally the role of marketing, but now this role is being handed to the robots, with agentic prospecting handling everything from deciding the ICP, buyer personas, to executing the campaign.  Picking 5 f'in' things from the article, as is the editorial policy of the podcast, Ian and Jeff discuss: Agentic Prospecting Assumes Signal Quality That Doesn't Exist The Assumption that Sales is a Numbers Game Accuracy is Fragile Due to Heavy Reliance On LLMs & External Data The Fallacy of End-To-End Autonomy Claims The Spam Problem Ian then joins Robert Rose in the virtual bar, The Rose & Rockstar, to discuss Robert's recent article from The Content Marketing Institute - Content-Led Marketing: The Essential Strategy for the AI Era. They discusses the evolution of marketing strategies from campaigns to content-led marketing, and the impact of AI and community building on brand storytelling. Enjoy! — The Links The people: Ian Truscott on LinkedIn  Jeff Clark on LinkedIn Robert Rose on LinkedIn Mentioned this week: Agentic Prospecting: Seven Reasons The Hype Falls Short Tuesday 2¢ - The Cost of the Easy Button Content-Led Marketing: The Essential Strategy for the AI Era Robert's podcast: This Old Marketing  Robert's newsletter: Lens, his websites, robertrose.net and seventhbear.com Rockstar CMO: The Beat Newsletter that we send every Monday Rockstar CMO on the web and LinkedIn Previous episodes and all the show notes: Rockstar CMO FM. Track List: We'll be right back by Stienski & Mass Media on YouTube Piano Music is by Johnny Easton, shared under a Creative Commons license The Miracles - Love Machine You can listen to this on all good podcast platforms, like Apple, Amazon, and Spotify. Learn more about your ad choices. Visit megaphone.fm/adchoices

This week, join Peter and Chris as they deep dive into the thirteenth track off of RiddleBox, the almighty third jokers card from ICP , "Ol' Evil Eye'" and all of the versions and interpolations! Sit back and listen as they dissect the lyrics and content of the track, discuss Edgar Allen Poe and the Telltale Heart, talk about Plaxico Burress, and tackle important topics like inflation affecting the price of cookies!      The LinkTree is at https://linktr.ee/juggalorwd... Twitter/X: @JuggaloRWD IG: @JuggaloRWD Facebook: @JuggaloRWD TikTok: @JuggaloRWD Threads: @JuggaloRWD BlueSky: @JuggaloRWD The website is www.JuggaloRewind.com. Join us everywhere to talk to other listeners and about ICP, Twiztid and random juggalo nonsense. Email us at juggalorwd@gmail.com or call/text us at (810) 666-1570.        Join our Patreon! You can join for free OR for only FOUR DOLLARS a month, you can join Kilnore's Army and get at least two bonus episodes per month, videos, chats and more! Even without paying, you can still join the Patreon community! Become an official member of the Phat or Wack Pack today! -- Juggalo Rewind Patreon. Additional music provided by the IRTD. Voiceover work provided by Christmas. All music played is owned by the respective publishers and copywrite holders and is reproduced for review purposes only under fair use. #ForTheJuggaloCulture

Jason Druss spent 15 years being the customer — a film colorist at Warner Bros, NFL Films, and his own Philly boutique — before Adobe pulled him into product marketing for Premier Pro and After Effects. In this episode, Jason (Principal Product Marketing Manager, Adobe) drops his takes: why workflow isn't a buzzword when you've actually lived it, how his team runs a private WhatsApp group with hundreds of users, and why being your own ICP is both a superpower and a trap. If you've ever felt like a fraud talking about users you've never met, this one's for you.More from this episodeWhy "customer" gives Jason the ick (and what word he uses instead)The PMM job is 50% talking to users — not Slack, not slides, not strategy decksHow Adobe's PMM team gets buy-in before a feature exists, not afterThe Tarantino move: why Jason starts every story at the endBeing your own ICP is a cheat code… until it makes you look like a fanboy at annual planningThe exact reason Frame.io's Camera to Cloud killed an industry workflow that hadn't changed since 1920Why every PMM should buy a pillow with their product's logo on it (yes, really)The unsexy truth about "creative freedom" — you have to earn it with data firstHow Jason found his PMM job: he wasn't looking, his mentor was watching his LinkedIn postsWhy "make it pretty" and "make it beautiful" are two completely different briefsTime Stamps 00:00 Cold open — the misfit intros00:45 Why this episode is different: a PMM pulled IN to PMM, not chasing it01:30 Jason Druss intro — from colorist to Adobe PMM02:15 THE QUESTION: Are product marketers marketers?03:30 "We're storytellers before we're marketers"04:30 Should the product or the user be the main character?05:30 The trap of feature-led storytelling vs. workflow thinking07:00 What "workflow" actually means (and why it's not jargon)09:00 The Frame.io / Camera to Cloud story12:30 How Frame.io rewrote a 100-year-old industry workflow14:00 Jason's spicy take: PMMs must eat, live, breathe the product16:00 How user needs have shifted dramatically in 5–10 years18:00 The Premier Pro pillow story (and why every PMM should have one)19:00 Where most companies fail at user research20:30 The private WhatsApp group with hundreds of users21:30 Weekly webinars, betas, and the questions you're NOT asking users24:00 Scrappy is a state of mind, not a company size25:00 Jason's career timeline: Blackmagic → NFL Films → Warner Bros → Frame.io → Adobe28:00 The crisis of faith — leaving "colorist" behind30:00 Why Jason's passion is impossible to fake31:30 The dark side of being your own ICP33:00 Mixing intuition with data — the PMM credibility unlock35:00 Advice for aspiring PMMs: become a subject matter expert first38:00 The creativity rant — your differentiator vs. AI41:30 ROI, business metrics, and earning the seat at the table44:00 The "beautiful circle" of product marketing (and who's outside it)46:00 Where to find Jason + Adobe Max teaser48:00 OutroHosted on Ausha. See ausha.co/privacy-policy for more information.

The Bougie Executive Podcast | Episode 2: The Identity Shift That Took Me From $650 to $12,500 Per MonthFor years, I was the bottleneck in my own business. Waking up at 5 AM, working through lunch, answering client emails at midnight, over-delivering on $650 retainers, and making less than my old corporate salary. I kept telling myself it was a hustle problem. It wasn't. It was an identity problem.In this episode of The Bougie Executive Podcast, I'm walking you through the exact mindset shift that took my luxury digital marketing agency from $650 monthly clients to $12,500 monthly retainers in less than 18 months, and I'm being honest about how scared I was the whole time.This is the conversation about money your favorite business coach probably isn't having with you. It's not about marketing. It's not about closing. It's not even about pricing strategy. It's about who you believe you are when you walk into a sales call.In this episode you will learn:Why "service provider energy" is keeping you broke and how to recognize it in your contracts, proposals, and sales callsThe Sunday night client text that broke me and forced me to raise my prices 4X overnightThe one question to ask yourself this week that will change how you price every offer going forwardThe 3 identity shifts every female entrepreneur needs to make to scale from low-ticket to luxury pricingWhy luxury clients aren't paying for deliverables, strategy, or even results, they're paying for decisivenessHow to identify the client on your roster the future version of you would not takeWhy undercharging is a trauma response, not a pricing strategyThe 3 identity shifts covered in this episode:From service provider to strategist, service providers get paid to do the thing, strategists get paid to think about the thingFrom strategist to authority, strategists compete on quality, authorities eliminate competition entirelyFrom authority to decisive leader, the shift that unlocks $10K+ monthly retainersTopics covered:How to raise your prices as a service-based business owner, identity-based pricing, mindset shifts for women entrepreneurs, scaling a marketing agency, fractional CMO pricing, luxury client acquisition, how to charge more as a woman in business, Black women entrepreneurs raising rates, social media management pricing, agency pricing strategy, six figure entrepreneur mindset, seven figure entrepreneur mindset, scope creep, ideal client profile, ICP, premium positioning.About The Bougie Executive Podcast:The Bougie Executive is a weekly podcast for ambitious women building wealth, leadership, and legacy. Hosted by Kareesha Carter, the founder and CEO of The Bougie Executive Agency, a luxury digital marketing firm serving six and seven-figure brands. This show is for the CEO mom, the faith-driven entrepreneur, and the woman who refuses to choose between her family and her ambition because she knows she was built for both.New episodes drop every Monday, Wednesday, and Friday at 9 AM PT.Mondays: business strategy, pricing, sales, scaling, and systems for women entrepreneursWednesdays: motherhood, burnout recovery, work life integration, and the real life of a CEO momFridays: faith, mindset, manifestation, and the spiritual side of building wealthConnect with Kareesha Carter:Instagram: @therealk.carterThreads: @therealk.carterLinkedIn: Kareesha CarterWebsite: thebougieexecutiveagency.coSubscribe, rate, and review The Bougie Executive Podcast on Spotify, Apple Podcasts, and wherever you listen. Tag the host on Instagram or Threads with your favorite quote from this episode for a chance to be featured in a Friday episode shoutout.If you have ever wondered why you keep undercharging even though you know you're worth more , this is your sign. You are not underpriced because the market is hard. You are underpriced because you have not yet decided you are the woman who charges more.

In this exciting episode: It's all Aaron, all the time!First, we finally find out what Aaron thinks about the Super Famous Fun Time Guys playlist we made for him in the last episode. Haven't heard it yet? Give it a listen HERESecond, Aaron went to see ICP live in Dallas, and he'll share a recap of the entire show experience!If you want to interact with us, send us messages, follow us, support us, or join our community, check out the links on our WEBSITE.If you want EVEN MORE underground goodness, check out Robbie's underground rap and horrorcore focused news show on YouTube, DO IT FOR THE UNDERGROUND (DIFTUG) HERESend us Fan Mail

In "Scaling with Intent: Removing the Constraints to Growth" Joe Lynch and Holly LaBoda, Founder and Chief Growth Officer of Formula L, discuss how logistics leaders can bridge the gap between high-level strategy and field execution by building a sustainable, system-led sales infrastructure. About Holly LaBoda Holly LaBoda is the Founder and Chief Growth Officer of Formula L, a sales operating system built for logistics, supply chain, distribution, and complex B2B service organizations. She has spent 18 years working inside these industries — including a decade at C.H. Robinson leading enterprise sales system design and go-to-market strategy — before building Formula L from the patterns she saw break organizations of every size. Holly holds an M.S. in Performance Improvement and certifications in change management and strategy — which means she doesn't just teach what worked once; she builds the system that makes it work consistently. She has worked alongside hundreds of sales leaders and thousands of sellers across logistics, freight, and distribution. Holly serves on the TMSA Board of Directors and is based in Minneapolis, Minnesota. About Formula L Formula L is a sales operating system built for logistics, supply chain, distribution, and professional services organizations that have outgrown how they operate. Most growth leaders hit a ceiling that isn't about strategy — it's about the system underneath it. Formula L builds the infrastructure that closes the gap between the strategy leadership decides and what actually shows up in the field: a proprietary diagnostic and competency model, the LIFT Method development process, and a full partnership model that delivers the operating system alongside the team. The result is sales growth that doesn't depend on heroics — just a system built to handle it. Formula L works primarily with founder-led and PE-backed organizations in logistics and complex B2B services. Key Takeaways: Scaling with Intent: Removing the Constraints to Growth In "Scaling with Intent: Removing the Constraints to Growth" Joe Lynch and Holly LaBoda, Founder and Chief Growth Officer of Formula L, discuss how logistics leaders can bridge the gap between high-level strategy and field execution by building a sustainable, system-led sales infrastructure. Move Beyond "Heroics-Based" Sales: Many logistics companies rely on a few "hero" sellers or the founder's personal book of business. Holly emphasizes that sustainable scaling requires a system-led growth model where results are driven by a repeatable infrastructure rather than individual talent alone. Identify the "Growth Leap" Constraints: Organizations often hit a ceiling when their current processes can no longer support their size. Common constraints include capacity (the leader becoming a bottleneck) and coordination (complex solutions requiring too much internal sign-off), both of which must be diagnosed to restart growth. Close the Strategy-to-Execution Gap: A major growth killer is the disconnect between leadership's strategy and the field's execution. Formula L focuses on operationalizing strategy into daily sales behaviors so that the vision actually shows up in the field. Avoid the "Feel-Good" Training Trap: Sales training is often a "feel-good intervention" that fails because the underlying system is broken. Before implementing training, leaders must ensure the sales process, compensation, and ideal customer profiles (ICP) are aligned, or the training won't stick. Focus on Business Trigger Events over Raw Intent: While "intent data" (tracking website visits) is popular, the real value lies in understanding the trigger event—what changed in the prospect's business that made them look for a solution? This context allows for a more strategic, less "stalker-like" sales approach. The Importance of Leadership Alignment: Growth requires that all leaders are "rowing in the same direction." This often means making hard choices about role clarity, such as ensuring a sales leader isn't also burdened with customer support or operations, which creates a "split-focus" failure. Practice through Behavioral Coaching: High-level growth requires behavioral change, not just knowledge. Effective development involves learning labs and AI-driven practice to allow sellers to get "reps" in a low-stakes environment, similar to how elite athletes or military personnel train for high-pressure situations. Learn More About Scaling with Intent: Removing the Constraints to Growth Holly LaBoda | Linkedin Formula L | Linkedin Formula L The Logistics of Logistics Podcast If you enjoy the podcast, please leave a positive review, subscribe, and share it with your friends and colleagues. The Logistics of Logistics Podcast: Google, Apple, Castbox, Spotify, Stitcher, PlayerFM, Tunein, Podbean, Owltail, Libsyn, Overcast Check out The Logistics of Logistics on Youtube

In this high-yield, no-fluff episode, Dennis is joined by Dr. Michael Falk, a pediatric emergency medicine physician, former academic, and combat-experienced relief worker who has run airways in Haiti post-earthquake, Mosul during the ISIS fight, Ukraine, and Gaza. They break down exactly why pediatric airways are a completely different beast in prolonged field care and give you field-proven tactics that actually work when you're the only one there with a BVM and a prayer.Key Takeaways You Can Use TomorrowPositioning is everything: One to two inches under the shoulders (or whole body) prevents automatic obstruction from the massive occiput.Adjuncts > early tube: NPA or OPA + side-lying (gravity is your friend) can keep you from tubing in the field.Tube sizing rule: Child's pinky ≈ ET tube diameter. Depth = 3× tube size. Always go smaller — you can ventilate, you can't un-damage a ripped airway.Intubation mindset: Kid airway is more anterior and cephalad. Slow down, work your way in, or you'll be in the esophagus.GCS decision:

Neste episódio do Vamos de Vendas, Gustavo Pagotto recebe Helio Azevedo, especialista em vendas B2B, ex-executivo de IBM, Microsoft e SAP, para uma conversa sobre como simplificar processos comerciais e aplicar as melhores práticas de multinacionais em empresas brasileiras.Ao longo do episódio, Helio mostra que grandes empresas não crescem por serem mais complexas, mas justamente por conseguirem simplificar processos, cultura e gestão. Ele explica como padronização, clareza de métricas e foco no essencial aceleram a escala de operações comerciais, desde onboarding e CRM até remuneração variável e gestão de performance.A conversa também explora os principais erros de empresas em crescimento, como automatizar processos desnecessários, criar excesso de burocracia no CRM e copiar práticas de multinacionais sem ter a base estruturada. Helio compartilha exemplos práticos de transformação em empresas de tecnologia, fala sobre cultura organizacional, liderança e mostra como inteligência artificial pode acelerar produtividade, enablement e desenvolvimento comercial.

I'm joined again by Imran Muthuvappa to walk through how to build your own AI Chief of Staff using a tool called Nebula. Imran shows me how to spin up specialized agents that handle the work a real chief of staff would do — surfacing team blockers, tracking project status, holding people accountable to offsite vision goals, running daily agenda briefings, and prospecting ICP leads. We also get into mini apps, model selection for cost efficiency, and why personal software is becoming a real category. By the end, the takeaway is clear: every role now has a "work on the job" component where you supervise yourself and offload tasks to agents. Links Mentioned: Try Nebula: https://startup-ideas-pod.link/nebula Precall Agent: https://startup-ideas-pod.link/precall-agent Project Status Agent: https://startup-ideas-pod.link/project-status-agent Lead Gen Agent: https://startup-ideas-pod.link/lead-gen-agent Timestamps: 00:00 – Intro 02:13 – What is Nebula 02:54 – What an AI Chief of Staff Actually Does 4:26 – Nebula vs OpenClaw vs Hermes 06:09 – Building the Blockage Radar Agent 09:47 – Agent Features 12:04 – Choosing Cheaper Models for Simple Tasks 13:15 – Building Project Status Agent 13:53 – Connecting Tools to Agents 17:38 – Building Vision Tracker Agent 22:07 – Mini Apps and Personal Software as a New Paradigm 25:13 – Building a Daily Agenda Agent and Second Brain Integration 30:25 – Hours Saved vs. Anxiety Reduced for Founders 33:02 – Building the Lead Gen Prospector Agent 39:19 – Final Thoughts: Automate Three to Five Things Key Points An AI Chief of Staff handles the boring executive support work — calendar, email, LinkedIn, project status — so a human can focus on decisions. Nebula lets you build, deploy, and share custom agents through a Slack-like interface, where each agent has its own goals, tools, and system prompt. Voice input via SuperWhisper or WhisperFlow gets you to roughly 150 words per minute, which Imran calls the biggest productivity lift available right now. Cheaper models like the Nebula model handle most chief-of-staff tasks well — reserve frontier models like Opus or Sonnet for deep coding or reasoning work. Mini apps inside Nebula are spinnable web dashboards that connect back to your agents — a glimpse of personal software replacing off-the-shelf tools. The new skill is judgment: picking which three to five things to automate out of your week. 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 IMRAN ON SOCIAL X/Twitter: https://x.com/imranye Alif: https://alif.build/

This week, join Peter and Chris as they deep dive into the twelfth track off of RiddleBox, the almighty third jokers card from ICP , "Lil Somethin' Somethin'" and all of the remixes and uh, samples! Sit back and listen as they dissect the lyrics and content of the track, discuss the Hulk Hogan doc, talk about Twiztid 420 shows and Jamacia trips, and tackle important topics like students working at Dairy Queen!      The LinkTree is at https://linktr.ee/juggalorwd... Twitter/X: @JuggaloRWD IG: @JuggaloRWD Facebook: @JuggaloRWD TikTok: @JuggaloRWD Threads: @JuggaloRWD BlueSky: @JuggaloRWD The website is www.JuggaloRewind.com. Join us everywhere to talk to other listeners and about ICP, Twiztid and random juggalo nonsense. Email us at juggalorwd@gmail.com or call/text us at (810) 666-1570.        Join our Patreon! You can join for free OR for only FOUR DOLLARS a month, you can join Kilnore's Army and get at least two bonus episodes per month, videos, chats and more! Even without paying, you can still join the Patreon community! Become an official member of the Phat or Wack Pack today! -- Juggalo Rewind Patreon. Additional music provided by the IRTD. Voiceover work provided by Christmas. All music played is owned by the respective publishers and copywrite holders and is reproduced for review purposes only under fair use. #ForTheJuggaloCulture

Send us Fan MailOn this episode of the ABM Done Right Podcast, Sloan Newman (North American ABM Leader at NTT Data and author of "The Relationship Revolution) joins Eric Gruber (CEO of Personal ABM) to discuss:1. The strategic ICP - Why it's important, how it's different from the traditional ICP,  how Sloan built the strategic ICP for NTT Data, what he looked at to build it,  and how the strategic ICP should inform the ICP?  2. How compensation needs to change  3. Why senior-level marketers need to drive the ABM program?  4. The role that Challenger should play in ABM. 

Superhuman Mail users respond to 72% more emails per hour and save an average of four hours every week — numbers backed by a case study from one of the Big Three strategy consulting firms. Rahul Vohra, CEO at Superhuman Mail, built the world's fastest email engine over three years without launching, held the line until the product was ready, and then productized product-market fit into a repeatable, measurable science. Following Superhuman's acquisition by Grammarly in 2025, Rahul is now steering the company toward a unified AI-native productivity suite spanning email, calendar, tasks, and agents.What you'll learn:The 5-step PMF Engine: how to survey, segment, analyze, implement, and track your way to product-market fit with a numerical scoreWhy you should ignore the not disappointed and most somewhat disappointed users — and which signals actually tell you who to build forHow to use the High Expectation Customer (HXC) framework to narrow your market without changing your productWhy PMF is a moving target and how to defend it against commoditization and copy-cat competitionHow Rahul operates as the editor of the product — using 20 verbatim quotes to push PMs and designers to sharper decisionsKey takeaways:If more than 40% of your users would be very disappointed without your product, you have an initial PMF — and you can measure your way thereChanging your market is faster than changing your product — segmentation alone can jump your PMF score 10 points overnightBuilding for your highest-expectation customer is not the same as building for your ICP — confuse the two, and you'll optimize for the wrong signalCredits:Host: Carlos Gonzalez de VillaumbrosiaGuest: Rahul VohraSocial Links:Find out more about Product School hereFollow our Podcast on TikTok hereFollow Product School on LinkedIn here

Figure out what you need to use for your AI tech stack:https://value.8figureagency.co/topaiJordan sits down with Noah Friedberg, founder of Maverick Creative, to break down how marketing agencies and ecom brands are using Arc Ads and AI UGC creators to drive viral content at scale. Noah walks through a live demo of Arc Ads, shares the framework his clients use to hit eight figures on TikTok Shop, and explains where AI replaces human influencers — and where it doesn't. If you run an agency or ecom brand and want to understand the AI UGC opportunity, this one's for you.Timestamps(00:00) Intro: Why AI UGC is the fastest path to going viral(00:54) Noah's background — Maverick Creative, TikTok Shop, working with 7-8 figure ecom brands(03:14) The mindset shift: volume, shots on net, and why one $25K influencer video is a billboard, not a sales channel(04:00) The 12,000 videos = $3M framework from TikTok Shop(05:38) Case study: Launching an 8-figure Amazon brand on TikTok Shop in under 3 months(06:48) Why Arc Ads vs. other AI video platforms ("the Apple of its category")(08:51) Live Arc Ads demo: Going from nothing to a finished AI UGC video(10:25) Script strategy: Using authority figures (e.g., AI doctor) to build trust and call out your ICP(13:21) The most complex AI UGC formats: cartoons, green screens, B-roll + talking head combos(14:40) Does AI UGC work for service businesses and agencies? (Yes — credit repair, info, low-ticket offers)(15:36) Building an AI influencer for an agency from scratch (warmed-up pages, US-hosted iPhones, full funnel)(19:15) When you outgrow Arc Ads: custom workflows with Claude Code, multi-tool stacks, B-roll generation(22:44) Why workflow automation matters — content running 24/7 without human touch(23:42) Scale numbers: 50-60 accounts per brand, 10 videos per page per day, up to 550 videos/day(25:00) The biggest mistake brands make: confusing one viral video with a real system(26:21) How Noah measures data at scale (Kalodata, social one, competitor analysis)(28:20) Why "set it and forget it" AI is a myth — the human strategy layer still winsKey TakeawaysVolume beats prestige. A single $20–25K influencer video is essentially a billboard. A few thousand AI UGC videos at a few dollars each gives you orders of magnitude more shots on net.Quality at volume is the unlock. The 12K videos = $3M framework only works when each video meets a real quality bar — trash content at scale doesn't move revenue.Arc Ads is the entry point. Easy, fast, cheap, realistic talking-head videos. But for B-roll, cartoons, and custom stitched workflows, you need agentic tools like Claude Code on top.Systematize, don't celebrate. Most brands hit one viral video and assume that's the new normal. Without a system, 80% of revenue keeps coming from one creator or one format.AI doesn't replace strategy. Brands that try to "set and forget" AI workflows fail. The human guiding hand — script direction, competitor analysis, taste — is still where the edge lives.Resources & Tools MentionedArc Ads — arcads.aiWhisper Flow — for dictating scriptsClaude Code — for custom AI UGC workflowsn8n — automationKalodata, Social One — data and trend analysis toolsConnect with NoahWebsite: maverickcreative.netDMs: @NoahFriedberg on all platforms

This week, join Peter and Chris as they deep dive into the eleventh track off of RiddleBox, the almighty third jokers card from ICP , "Dead Body Man" and all of the remixes and samples! Sit back and listen as they dissect the lyrics and content of the track, discuss local news anchors, talk about killing radio stations, and tackle important topics like Bob Dole and Columbo!      The LinkTree is at https://linktr.ee/juggalorwd... Twitter/X: @JuggaloRWD IG: @JuggaloRWD Facebook: @JuggaloRWD TikTok: @JuggaloRWD Threads: @JuggaloRWD BlueSky: @JuggaloRWD The website is www.JuggaloRewind.com. Join us everywhere to talk to other listeners and about ICP, Twiztid and random juggalo nonsense. Email us at juggalorwd@gmail.com or call/text us at (810) 666-1570.        Join our Patreon! You can join for free OR for only FOUR DOLLARS a month, you can join Kilnore's Army and get at least two bonus episodes per month, videos, chats and more! Even without paying, you can still join the Patreon community! Become an official member of the Phat or Wack Pack today! -- Juggalo Rewind Patreon. Additional music provided by the IRTD. Voiceover work provided by Christmas. All music played is owned by the respective publishers and copywrite holders and is reproduced for review purposes only under fair use. #ForTheJuggaloCulture

AI is shifting from model development to real-world usage, exposing a new bottleneck that most sales teams are not prepared to understand or sell against. As inference speed, memory bandwidth, and infrastructure become the true differentiators, traditional software playbooks begin to break down. Alex Varel joins John Kaplan and John McMahon to unpack what it takes to sell in this new environment, where technical depth, curiosity, and adaptability are no longer optional. The conversation explores how AI is reshaping productivity, why ICPs must evolve weekly, and how elite sellers distinguish themselves by orchestrating value across increasingly complex buying groups. Alex Varel is EVP of Worldwide Sales at Cerebras Systems, where he leads global go-to-market efforts at the forefront of AI infrastructure. He has built and scaled high-performing teams across MongoDB, Zscaler, and Multiverse, driving growth through IPO, hyper-scale expansion, and emerging technology shifts. Connect with Alex: LinkedIn Resources mentioned: "The Power of Myth" by Joseph Campbell "AI Superpowers" by Kai-Fu Lee “Leonardo da Vinci” by Walter Isaacson "No Country for Old Men" by Cormac McCarthy "The Road" by Cormac McCarthy “The Founders: The Story of Paypal and the Entrepreneurs Who Shaped Silicon Valley” by Jimmy Soni Key takeaways from this episode: 00:00 – A look inside what it really takes to rethink computing architecture when speed, not scale, becomes the constraint 13:09 – Why many leaders underestimate how the shift from training to inference is redefining where competitive advantage actually lives 25:27 – The mistake many CROs make when applying legacy software playbooks to markets that require constant recalibration 21:33 – What it really takes to turn AI from a concept into a daily productivity multiplier inside a revenue organization 31:34 – Why most sales organizations quietly accept a broken productivity model and what changes when that assumption is challenged 34:26 – A look inside the evolving role of the AE as a multi-dimensional operator across technical, business, and interpersonal domains 49:41 – Why treating ICP as a static exercise leads to missed growth opportunities in markets that are shifting in real time Hosted by five-time CRO John McMahon and Force Management Co-Founder John Kaplan, the Revenue Builders podcast goes behind the scenes with the sales leaders who have been there, done that, and seen the results. This show is brought to you by Force Management. We help companies improve sales performance, executing their growth strategy at the point of sale. Connect with Us: LinkedInYouTubeForce Management

In this episode of "Voices of Self-Funding," host Ramesh Kumar sits down with Trey Hinson, Founder of Goliath Sales Strategies and a seasoned marketing and sales leader with over 24 years in the healthcare benefits space. Trey unpacks what authentic, research-driven sales and marketing look like in today's self-funded ecosystem. You'll learn: - Why modern brokers are demanding measurable outcomes, value-aligned proof, and a disciplined ICP strategy—and how carriers and TPAs can better meet those expectations. - The shift from feature-centric pitching to case-study-backed storytelling. - The importance of rep enablement for building a sales system that scales sustainably. This is a must-listen conversation for anyone looking to strengthen broker relationships, improve retention, and build sales systems that last. Tune in now! This episode is sponsored by zakipoint Health. At zakipoint Health, we are transforming the healthcare experience by delivering transparency, direction, and personalized support to members of self-insured plans. Our powerful platform unifies all benefit services, data, insights, and tools into one intelligent ecosystem empowering members to make informed decisions and take proactive steps toward better health outcomes. With AI at its core, zakipoint Health functions as the “Intel Inside” of healthcare navigation driving engagement, reducing risk, and delivering measurable cost savings. Employers and partners benefit from robust reporting, actionable insights, and tools that not only identify healthcare risks but also guide members toward high-value care. By bridging the gap between complexity and clarity in the U.S. healthcare system, we help organizations lower costs, improve outcomes, and support healthier, more engaged populations making healthcare less stressful and more effective for millions. Find all of our network podcasts on your favorite podcast platforms and be sure to subscribe and like us. Learn more at www.healthcarenowradio.com/listen/

Certified nurse midwife Roxanne explains common skin changes in pregnancy caused by hormonal shifts, increased blood volume, and a growing belly, including hyperpigmentation (melasma, linea nigra), vascular changes (spider veins, varicose veins), and stretch marks. She shares practical tips like daily SPF and sun protection for darkening, and compression socks, avoiding prolonged standing/crossing legs, walking, and massage to support circulation. For stretch marks, she notes there's no evidence that creams prevent them during pregnancy and retinoids aren't recommended until postpartum; causes are multifactorial (genetics, collagen, hydration, baby size/weight gain). Roxanne also reviews pregnancy itching and rashes: PUPPP (third trimester, spares belly button), atopic eruption (first/second trimester, widespread), and more concerning conditions needing evaluation—ICP (itching palms/soles), pemphigoid gestationis (starts at belly button; risks for baby), and rare pustular psoriasis with systemic symptoms—advising viewers to contact their provider for assessment and treatment options.Watch our video about ICP here: https://youtu.be/uzZz2KuZDAU00:00 Welcome and Introductions01:01 Why Skin Changes Happen01:44 Hyperpigmentation and Melasma02:40 Spider and Varicose Veins03:48 Stretch Marks Truths06:18 Common Changes Recap07:15 Itching and PUPPP Rash08:57 Atopic Eruption Explained09:53 Red Flags and Serious Rashes13:45 Final Recap and Next Steps————

Does AI really break B2B positioning, or is it exposing deeper product problems? In this roundtable, Refine Labs' VP of Innovation Matt Sciannella sits down with Fletch PMM founders Anthony Pierri and Rob Kaminski to unpack what's actually happening when companies try to position themselves for the AI era.They cover why AI mandates from VCs create confusion (not clarity), how Intercom, Palantir, Salesforce, and Owner.com handle multi-product positioning, and why delegating positioning to LLMs is a race to mediocrity.What is product positioning in B2B SaaS?Product positioning defines who your product is for, what problem it solves, and why it's different from alternatives. It's the upstream decision that drives homepage messaging, paid media, and GTM clarity.How does AI affect B2B positioning strategy?AI doesn't break positioning fundamentals — it adds market uncertainty and product pressure. Companies still must answer: what problem do you solve, for whom, and better than what?Can AI write your positioning for you?No. LLMs can accelerate research and fill in details, but they can't generate non-obvious strategy from scratch. They're best used when humans provide 80% of the thinking first.Why do multi-product companies struggle with positioning?Most markets are fragmented. Customers think narrowly — they're not shopping for "everything." Leading with one clear use case (like Apple with iPhone, Owner.com with restaurant grading) outperforms breadth.What is a go-to-market positioning framework?A GTM positioning framework defines your category, ideal customer profile (ICP), competitive alternatives, differentiated value, and homepage message — in that order, before messaging or campaigns.#b2bmarketing #ProductPositioning #GTMStrategy #B2BSaaS #DemandGeneration #ProductMarketing #AIMarketing #ContentMarketing #SaaSMarketing #RefineLabsRoundtable #FletchPMM #MarketingStrategy #ICPMessaging #HomepageCopywriting #GoToMarket

⁠⁠⁠⁠Subscribe to the Outbound Kitchen newsletter⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠---This episode was originally recorded in French for Cognism's Prospect podcast with Laetitia Fall. The English audio you're hearing is an AI-translated dub generated with ElevenLabs. Original French version: https://youtu.be/DMRO_GGp-1A--If you're new here, I'm Elric Legloire, founder of Outbound Kitchen. I help B2B SaaS companies between $2M and $50M ARR boost their outbound results. My view: in 2026, productivity is the multiplier, not headcount. --We discuss:- Why outbound isn't dead, but pipeline got roughly 10x more expensive (1% conversion in 2015 to needing 1,000 emails per opportunity in 2023, source: Winning By Design)- Why global SDR headcount grew over 20% in a year while public layoffs dominated the LinkedIn feed- The Owner.com benchmark: 40 appointments per BDR per month, 25% close rate, $70-80K sourced revenue per BDR per month- When to hire experienced SDRs vs juniors, and the 12-meetings-per-month threshold that signals your playbook is ready- Why ICP work beats tool selection (Tier 1 closes at 25%, Tier 2 at 5%, you need 5x the volume to compensate)- Snowflake's 140 ICP data points and why 10-15 is the realistic target for most teams- Multichannel orchestration when only 30% of your prospects are reachable on LinkedIn- The data-quality test most teams skip: coverage rate per persona, per market- AI in outbound (January 2026): what actually works, why most LinkedIn AI messages fail, and the foundation AI needs (market, CRM, message principles, signals)Referenced:Outbound Kitchen newsletter: https://newsletter.outbound.kitchenElric Legloire on LinkedIn: https://www.linkedin.com/in/elriclegloire/Cognism's original French episode: https://youtu.be/DMRO_GGp-1AHost: Laetitia Fall Sources cited in episode: Winning By Design, Insight Partners (Jeremy Donovan's portfolio data), Owner.com BDR benchmarks, Snowflake ICP methodology----When you're ready⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠Want to work with me? Send me a DM⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠---Connect with me⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠

In this episode of The Ross Simmonds Show, Ross breaks down why OpenAI and HubSpot's media acquisitions this quarter aren't about content quality. They're about owning distribution. He connects the dots on what this land grab means for every B2B marketer and how to apply the same strategy without a billion-dollar balance sheet. Key Takeaways and Insights: 1. Media Acquisition Is the New Moat - OpenAI and HubSpot made bold media acquisitions in the same quarter. This isn't about content quality. It's about owning the rooms where buying decisions happen. - Distribution is leverage. And leverage compounds. The brands that win will own the audience, not just the message. 2. The Land Grab Has Already Started - Penn bought Barstool. HubSpot acquired The Hustle and Starter Story. Robinhood built a media empire. Plaid acquired fintech media to own operator attention. - The cadence of these deals is accelerating. This is not a trend. It's a land grab and most B2B teams haven't noticed. 3. Super Bowl Ads vs. Owned Attention - $27M buys six Super Bowl ads that disappear in 30 seconds. The same capital can buy a media asset with daily access to your exact ICP. - Most teams rent attention. The best operators own it. Predictable pipeline starts with predictable distribution. 4. Google's AI Shift Changes the Game - AI Overviews are reducing clicks to traditional search results while Google embeds YouTube directly into the SERP. - Media value is no longer just blog rankings. It's multimedia presence. Visibility now requires platform-native authority. 5. You Cannot Game LLM Visibility - Traditional SEO could be manipulated with backlinks and paid boosts. AI visibility requires real brand equity and positive sentiment. - LLMs train on authority signals across media properties. If you want to show up in AI answers, you must be worth citing. 6. Brand Equity Beats Editorial Independence - Acquired media serves stakeholders. Narrative shapes culture and buying media shapes narrative. - Read content with context. Ownership matters. Content influence increasingly flows through owned channels. 7. The 4 Distribution Questions Every Marketer Should Ask - Which newsletter has the audience you wish you had? Which creator has your buyers' trust? What shows does your ICP consume weekly? What niche media opportunity is still wide open? - Use LLMs and audience intelligence tools to find answers faster. The operators asking these questions now are building moats everyone else will pay to access later. 8. How to Build a Media Engine Without Buying One - Start one channel and let patience compound. Sponsor niche newsletters instead of chasing giants. Partner with trusted creators via revenue share, salary, or equity. - In the AI era, content is cheap. Reputation and distribution are scarce. Build accordingly. 9. Three Predictions for the Next Decade - By 2035, every unicorn B2B company will own a media property. Newsletter and YouTube network valuations will triple as LLM visibility becomes priced in. - Agencies will survive by brokering, building, or optimizing media ecosystems, not just producing content. 10. Distribution Is the Last Moat Standing - AI commoditized content creation. The advantage shifts to those who control reach. A true content moat goes beyond your domain. - Visibility is engineered, not hoped for. The window to build that moat cheaply is closing fast. Resources & Tools:

Nicole Phelps shares her experience being pregnant while her partner, Michael Phelps, was training for the Olympics. She hired a doula and prepared to possibly give birth without Michael there. A few weeks before her due date, Nicole started experiencing extreme itchiness, especially on the palms of her hands, and was tested for Intrahepatic Cholestasis of Pregnancy (ICP). However, she went into labor before the results came back. Michael made it just in time, and her son, Boomer, was born healthy. The test result came back positive and she knew she'd have to be on the lookout for another ICP diagnosis with future pregnancies. On this episode, she also shares her second pregnancy and birth story and how her doctor monitored her for ICP leading up to her son Beckett's birth. Nicole wanted to share her story to raise awareness about ICP so other women can be on the lookout for the symptoms. Links: Airdoctorpro.com code BIRTHHOUR for up to $300 off! Know Your Options Online Childbirth Course - use code 100OFF for $100 off. Beyond the First Latch Course (comes free with KYO course)  Support The Birth Hour via Patreon! You can now gift memberships to Patreon here! 

This week, join Peter and Chris as they deep dive into the tenth track off of RiddleBox, the almighty third jokers card from ICP , "The Joker's Wild"! Sit back and listen as they dissect the lyrics and content of the track, discuss game shows of years gone by, talk about other game show/talk show songs, and tackle important topics like Nickelodeon shows of the 90s!      The LinkTree is at https://linktr.ee/juggalorwd... Twitter/X: @JuggaloRWD IG: @JuggaloRWD Facebook: @JuggaloRWD TikTok: @JuggaloRWD Threads: @JuggaloRWD BlueSky: @JuggaloRWD The website is www.JuggaloRewind.com. Join us everywhere to talk to other listeners and about ICP, Twiztid and random juggalo nonsense. Email us at juggalorwd@gmail.com or call/text us at (810) 666-1570.        Join our Patreon! You can join for free OR for only FOUR DOLLARS a month, you can join Kilnore's Army and get at least two bonus episodes per month, videos, chats and more! Even without paying, you can still join the Patreon community! Become an official member of the Phat or Wack Pack today! -- Juggalo Rewind Patreon. Additional music provided by the IRTD. Voiceover work provided by Christmas. All music played is owned by the respective publishers and copywrite holders and is reproduced for review purposes only under fair use. #ForTheJuggaloCulture

Most B2B sales teams are fishing in the same pond with the same tools as every competitor. The difference between winning and losing isn't the tech — it's the system.In this mini series wrap-up, Dave, Regan, and Luigi reunite in the room to break down the complete client acquisition system they're building inside Coach Pilot — and what it actually takes to go from knowing your ICP to building repeatable, scalable revenue.This isn't theory. It's the real work: ride-alongs with customers, deep ICP research, pipeline infrastructure, and the system that connects it all.What you'll hear in this episode:— Why leaders misread their CRM — and why going into the field changes everything— How deep ICP research (not just a nice playbook page) drives faster sales velocity— Why a wide target audience creates a top-heavy, broken pipeline— What triggers really mean for both inbound and outbound — and why most reps ignore them— The real problem with noisy, unpersonalized LinkedIn outreach (and what not to do)— Why only 57% of sellers are actually compliant to their own sales process— The fishing analogy that explains why your competitors close deals faster— How to go from founder-led sales to a scalable GTM system without it breaking— When to pressure test, systemize, and then automate your acquisition processThis episode is for: B2B founders, revenue leaders, account executives, sales managers, and anyone building or fixing a client acquisition system from the ground up.

In this episode of In Depth, First Round Partner Josh Kopelman sits down with Shachar Hirshberg and Dan Shiebler, co-founders of Artemis, the AI-native security platform that just emerged from stealth with $70M in combined seed and Series A funding. Shachar and Dan unpack how they built a 30-person team in seven months, why AI-native companies are outperforming their AI-enabled counterparts, and why they plan to stay on a texting basis with every customer, even at scale. In today's episode, we discuss: How to interview for AI fluency when building an AI-native startup Why founder-market fit is a critical early signal for startup success The surprising lesson Dan learned from founder-led sales How Dan and Shachar are instilling customer-obsession into Artemis' culture How the two co-founders approach conflict and decision-making References: Abnormal: https://abnormal.ai Amazon Web Services (AWS): https://aws.amazon.com Anthropic: https://www.anthropic.com Artemis: https://artemissecurity.com CrowdStrike: https://www.crowdstrike.com Demisto (now Cortex XSOAR): https://www.paloaltonetworks.com/cortex/cortex-xsoar OpenAI: https://openai.com Palo Alto Networks: https://www.paloaltonetworks.com Todd Jackson: https://www.linkedin.com/in/toddj0/ Where to find Shachar Hirshberg: LinkedIn: https://www.linkedin.com/in/shachar-hirshberg/ Where to find Dan Shiebler: LinkedIn: https://www.linkedin.com/in/dan-shiebler-10219b42/ Where to find Josh: LinkedIn: https://www.linkedin.com/in/jkopelman/ Twitter/X: https://x.com/joshk Where to find First Round Capital: Website: https://firstround.com/ First Round Review: https://review.firstround.com/ Twitter/X: https://twitter.com/firstround YouTube: https://www.youtube.com/@FirstRoundCapital This podcast on all platforms: https://review.firstround.com/podcast Timestamps: 00:00 Introduction 00:06 What Artemis does and why now 02:51 Shachar's AWS and Palo Alto playbook 05:15 Dan's founder journey: From Twitter to Abnormal 08:51 Why founder-market fit is critical for startups 11:38 Finding the right moment to take the leap and build 13:52 The hiring process that powers a startup in stealth 16:58 Building a team centered on AI capabilities 21:48 How AI implementation changes dashboard metrics 23:22 The ICP they chased and the one they ignored 26:44 The magic of closing the first customers 27:49 The surprising signals of early product-market fit 32:06 Critical lessons from founder-led sales 33:51 Why the first product should make founders uncomfortable 36:03 Hiring 30 people while still in stealth 42:08 “Should we be arguing more?” 43:37 How the AI security market is evolving 49:03 Why AI-native beats AI-enabled company structure 51:09 The most surprising moments as a first-time founder

Most marketers glance at their click data and move on. But Jay Schwedelson and Daniel Murray think that's a massive missed opportunity hiding in plain sight. This Bathroom Break gets into the underrated power of click-through segmentation, bot inflation you probably don't know you have, and why your unsubscribe link might be quietly wrecking your metrics. Oh, and Jay gave up caffeine seven weeks ago. Chamomile tea era, officially.ㅤFollow Daniel on LinkedIn and check out The Marketing Millennials podcast for sharp, no-fluff marketing insights. Subscribe to Ari Murray's newsletter at gotomillions.co for sharp, actionable marketing insights.ㅤBest Moments:(03:00) Why your click data is worth way more than you're treating it(04:00) How to build retargeting audiences from email clicks for almost nothing(06:45) The two or three in the morning trick that reveals your real click-through rate(07:40) Using an invisible link above the fold to catch bot clicks before they skew your data(08:26) The surprisingly common mistake of counting unsubscribe clicks in your CTR(08:45) Why filtering clicks by ICP before retargeting makes everything sharperㅤCheck out Jay's YOUTUBE Channel: https://www.youtube.com/@schwedelsonCheck out Jay's TIKTOK: https://www.tiktok.com/@schwedelsonCheck Out Jay's INSTAGRAM: https://www.instagram.com/jayschwedelson/ㅤPre-order Jay Schwedelson's new book, Stupider People Have Done It (out June 9, 2026). All net proceeds are donated to The V Foundation for Cancer Research—let's kick cancer's butt: https://www.amazon.com/Stupider-People-Have-Done-Marketing/dp/1637635206

Most CEOs think more pipeline is the answer, but chasing volume without alignment will wreck your revenue engine. In this episode, Janice B Gordon and Lindsay Rios unpack the pipeline myth, share hard-won lessons from scaling high-growth organizations, and reveal why aligning teams on ICP is the secret to scalable, predictable growth. What you'll learn: a) Why most revenue problems aren't sales issues, they're ICP misalignment issues b) How to spot (and fix) the costly "kids are fighting" dynamic across go-to-market teams c) The real downside of prioritizing pipeline volume over quality Janice B Gordon welcomes Lindsay Rios, a fractional CRO and GTM strategist who helps scaling startups and SMBs rebuild revenue foundations for intentional, accelerated growth. Timestamps: 04:00 Discussing gender assumptions and biases 09:30 Discussing gender disparity in careers 12:44 Misleading pipeline growth signals 15:27 Reflecting on company culture fit 18:06 Focusing on meaningful sales metrics 24:03 Challenges with hiring outbound agencies 26:54 Defining the ideal customer 29:40 Evaluating customer acquisition costs 34:29 Creating strong team values Connect with Lindsay LinkedIn: https://www.linkedin.com/in/lindsayrios/   Connect with Janice Book Janice to speak at your next sales or leadership event: https://janicebgordon.com LinkedIn: https://www.linkedin.com/janice-b-gordon/ Instagram: https://www.instagram.com/janicebgordon Scale Your Sales Podcast: https://scaleyoursales.co.uk/podcast Enjoy the episode? Share your takeaway in the comments and leave a review on Apple Podcasts to help more leaders discover the show.

HEARD IN THIS EPISODE ◼ Why the four-year decline in staffing revenue isn't a market problem — it's a sales behavior problem that leaders are actively making worse by obsessing over the wrong metrics ◼ How COVID didn't just change where salespeople work — it quietly made them lazy, and why most sales leaders haven't noticed yet ◼ What the best staffing firms are doing differently right now that almost nobody else is: pulling recruiters into the sales process before the deal is even close ◼ Why your ICP is probably wrong — and how getting more specific with a smaller target list will generate more revenue than casting a wider net ever could ◼ How one simple mental shift — from account management to pre-client acquisition — could completely rewire the way your sales team operates EXPECT TO LEARN This episode will fundamentally challenge how you think about sales activity and what it's actually worth. You'll walk away with a sharper framework for diagnosing what's broken in your sales organization, whether it's your people, your process, or the pressure you're putting on both, and a clear-eyed view of why doing less, more deliberately, consistently beats doing more with less intention. If you lead a staffing firm or a sales team, this conversation will make you uncomfortable in exactly the right way.   KEY MOMENTS [00:01] – The #1 mistake holding firms back [01:08] – Chasing shiny objects kills revenue [02:21] – What to do when business is down [04:08] – How to prioritize your fix-it list [05:28] – Did COVID break the staffing industry? [07:02] – How COVID made staffing sales reps lazy [08:21] – Outputs vs. outcomes in sales [09:18] – Rewarding the wrong KPIs [10:48] – What consultative selling looks like [12:49] – Where firms get their ICP wrong [14:45] – Messaging by ICP level [16:38] – The Under Armour sales analogy [18:58] – Research has never been easier [23:00] – What top firms do differently [24:45] – Speed closes deals, not relationships [27:52] – Fixing staffing's reputation problem [31:42] – Sales reps as pre-client managers [33:26] – Optimistic or pessimistic on 2026? [35:41] – Coach in the moment, not end of month [37:17] – About AFM Strategic Partners [42:20] – Rapid fire: book that changed her life [43:24] – Advice for new staffing professionals ABOUT THE GUEST Anna Frazzetto is the Founder and CEO of AFM Strategic Partners and one of the most recognized voices in staffing and sales leadership — named to Staffing Industry Analysts' Global Power 150 Women in Staffing for seven consecutive years. She built her career scaling businesses from the ground up, including growing a solutions practice from $3M to $100M, and has led global sales transformations across some of the most complex corners of the industry. Her perspective is rare because it spans both sides of the table: the strategic and the deeply human, shaped in part by her experience as a cancer survivor who chose to bet on herself and start something new. Her new book, *Sales Leadership in Action*, distills over 100 field-tested tips for sales leaders who want to stop firefighting and start building teams that close. ABOUT THE HOST Brad Bialy is a trusted voice and highly sought-after speaker in the staffing and recruiting industry, known for helping firms grow through integrated marketing, sales, and recruiting strategies. With over 13 years at Haley Marketing and a proven track record guiding hundreds of firms, Brad brings deep expertise and a fresh, actionable perspective to every engagement. He's the host of Take the Stage and InSights, two of the staffing industry's leading podcasts with more than 225,000 downloads. SPONSORS AND OFFERS Book a 30-minute marketing consultation with host Brad Bialy: https://bit.ly/Bialy30 Benefits in a Card helps staffing firms offer meaningful benefits to their entire workforce through flexible, unbundled plans designed for high-turnover environments—making it easier to control costs, improve retention, and stay competitive. https://www.BenefitsInACard.com TRICOM partners with staffing firms as an asset-based lender and full-service back-office provider, helping owners scale confidently by reducing risk and easing the operational strain of payroll, cash flow, and administration. https://www.tricom.com  

Solo Jim: I have nothing left, except Spider-man and Jim. That's right no Mike or Jeff this week but Jim is your savior on this fine Adam Scott Nickelback Birthday Bash.Stand By Me In Theaters: Corey Feldman snuck into a screening of Stand By Me and couldn't stop filming the screen for his social media. Fine this dude for piracy.Crowd Controversy: EROK has launched an investigation into the crowd photos from Goonies and Stand By Me screenings that have been posted by Corey. He has an expert on hand and everything! Is this a thing?COREY FELDMAN!, SHOW STOPPER!, LET'S JUST TALK!, DON CHEADLE!, BOOGIE NIGHTS!, JIM AND THEM IS POP CULTURE!, CHRIS HANSEN!, HAVE A SEAT!, DATELINE!, TO CATCH A PREDATOR!, REAL ONES!, LVL UP EXPO!, HACKAMANIA!, LIVE!, SOLO SHOW!, NO JEFF!, NO MIKE!, ONLY JIM!, JUST JIM!, FAKE FRIENDS!, WHO'S LEFT!?, FRIDAY NIGHT!, 22 NECKLACE!, REAL ONES!, KISS EM IF YOU GOT EM!, AUDITIONS!, NICKELBACK BIRTHDAY BASH!, ADAM SCOTT!, NO MAS!, SIPPING ON SHOTS!, PO BOX!, HOOK!, TEXAS CHAINSAW MASSACRE!, CHRIS HANSEN CAMEO!, FIRST THING IN THE MORNING!, GOBLIN GHOUL!, APRIL FOOLS!, ADAN GONZALEZ!, STAUNCH TV!, DRAFTED!, IRAN!, WAR!, PROTECT ME!, ICP!, MIRACLES!, THE BOY BLUE!, COREY FELDMAN!, STAND BY ME!, SNEAK INTO THEATER!, WEDNESDAY!, WATCHED STAND BY ME TOGETHER!, THEATRICAL RELEASE!, MILES APART!, CHOPPER SIC BALLS!, JIM AND THEM FINALE SPECIAL!, INTERVIEW!, PLAYING WITH YOUR FRIENDS!, AWKWARD!, ANNOYED!, RUDE!, YAWNING!, AARP!, WIL WHEATON!, ANNOYING!, PERFORMATIVE!, SUMMERTIME!, JERRY O'CONNELL!, BORED!, SHALLOW!, RIVER PHOENIX!, VEGETARIAN!, INTO MUSIC!, COPIED!, BREAKING BAD!, STOLE DEAD PEOPLE'S HABITS!, FENIX TX!, KRISTIN!, DENISE RICHARDS!, BRAVE BROWSER!, FAKE CROWD!, PHOTOSHOP!, AI!, EROK!, SATURATION!, CONTRAST!, DOCTORED PHOTOS!, INVESTIGATION!, FIVERR!,

Solo Jim: I have nothing left, except Spider-man and Jim. That's right no Mike or Jeff this week but Jim is your savior on this fine Adam Scott Nickelback Birthday Bash.Stand By Me In Theaters: Corey Feldman snuck into a screening of Stand By Me and couldn't stop filming the screen for his social media. Fine this dude for piracy.Crowd Controversy: EROK has launched an investigation into the crowd photos from Goonies and Stand By Me screenings that have been posted by Corey. He has an expert on hand and everything! Is this a thing?COREY FELDMAN!, SHOW STOPPER!, LET'S JUST TALK!, DON CHEADLE!, BOOGIE NIGHTS!, JIM AND THEM IS POP CULTURE!, CHRIS HANSEN!, HAVE A SEAT!, DATELINE!, TO CATCH A PREDATOR!, REAL ONES!, LVL UP EXPO!, HACKAMANIA!, LIVE!, SOLO SHOW!, NO JEFF!, NO MIKE!, ONLY JIM!, JUST JIM!, FAKE FRIENDS!, WHO'S LEFT!?, FRIDAY NIGHT!, 22 NECKLACE!, REAL ONES!, KISS EM IF YOU GOT EM!, AUDITIONS!, NICKELBACK BIRTHDAY BASH!, ADAM SCOTT!, NO MAS!, SIPPING ON SHOTS!, PO BOX!, HOOK!, TEXAS CHAINSAW MASSACRE!, CHRIS HANSEN CAMEO!, FIRST THING IN THE MORNING!, GOBLIN GHOUL!, APRIL FOOLS!, ADAN GONZALEZ!, STAUNCH TV!, DRAFTED!, IRAN!, WAR!, PROTECT ME!, ICP!, MIRACLES!, THE BOY BLUE!, COREY FELDMAN!, STAND BY ME!, SNEAK INTO THEATER!, WEDNESDAY!, WATCHED STAND BY ME TOGETHER!, THEATRICAL RELEASE!, MILES APART!, CHOPPER SIC BALLS!, JIM AND THEM FINALE SPECIAL!, INTERVIEW!, PLAYING WITH YOUR FRIENDS!, AWKWARD!, ANNOYED!, RUDE!, YAWNING!, AARP!, WIL WHEATON!, ANNOYING!, PERFORMATIVE!, SUMMERTIME!, JERRY O'CONNELL!, BORED!, SHALLOW!, RIVER PHOENIX!, VEGETARIAN!, INTO MUSIC!, COPIED!, BREAKING BAD!, STOLE DEAD PEOPLE'S HABITS!, FENIX TX!, KRISTIN!, DENISE RICHARDS!, BRAVE BROWSER!, FAKE CROWD!, PHOTOSHOP!, AI!, EROK!, SATURATION!, CONTRAST!, DOCTORED PHOTOS!, INVESTIGATION!, FIVERR!,

This week, join Peter and Chris as they deep dive into the ninth track off of RiddleBox, the almighty third jokers card from ICP , "Headless Boogie"! Sit back and listen as they dissect the lyrics and content of the track, discuss tour statistics, talk about Wolfman Jack, and tackle important topics like booking a pirate-themed Gathering of the Juggalos!      The LinkTree is at https://linktr.ee/juggalorwd... Twitter/X: @JuggaloRWD IG: @JuggaloRWD Facebook: @JuggaloRWD TikTok: @JuggaloRWD Threads: @JuggaloRWD BlueSky: @JuggaloRWD The website is www.JuggaloRewind.com. Join us everywhere to talk to other listeners and about ICP, Twiztid and random juggalo nonsense. Email us at juggalorwd@gmail.com or call/text us at (810) 666-1570.        Join our Patreon! For only FOUR DOLLARS a month, you can join Kilnore's Army and get at least two bonus episodes per month, videos, chats and more! Even without paying, you can join the Patreon community! Become an official member of the Phat or Wack Pack today! -- Juggalo Rewind Patreon. Additional music provided by the IRTD. Voiceover work provided by Christmas. All music played is owned by the respective publishers and copywrite holders and is reproduced for review purposes only under fair use. #ForTheJuggaloCulture

Most companies don't fail because of product, they fail because they never build a clear, repeatable sales system around a problem that actually matters. That shows up early when founders delegate sales too soon, chase broad markets without focus, and struggle to translate technical insight into customer urgency. In this conversation, Lou Shipley brings a career spanning door-to-door selling to leading and teaching at Harvard to break down what separates companies that scale from those that stall. He introduces frameworks like the “problem with the problem” and the “murder board,” while reinforcing a consistent theme: sales is not a downstream function, it is the organizing discipline of the business. For leaders trying to build a high-performance culture or evaluate their next move, this conversation clarifies what to look for and what to avoid. Lou Shipley is a three-time CEO, Harvard Business School professor, and author of Unlikely Entrepreneurs. He has led multiple startups and previously taught sales at MIT. Connect with Lou:  LinkedIn Website Resources mentioned: Unlikely Entrepreneurs: Wins, Losses, and Crucial Lessons on Building Great Companies by N. Louis Shipley and Patricia Favreau Key takeaways from this episode: 00:00 – How Lou Shipley built his sales foundation on 100% commission 06:00 – The 30-second mistake sellers keep making and how it kills deals early 10:33 – Why Lou Shipley believes emotional connection to the problem changes everything 25:55 – Why founders who delegate sales too early almost always get it wrong 33:33 – A behind-the-scenes look at how great teams pressure-test their strategy before the market does 40:22 – The three questions that instantly expose whether a company is worth joining 44:25 – Why narrowing your ICP is the fastest path to real revenue growth, not a limitation 58:33 – The real reason most companies fail before they ever scale Hosted by five-time CRO John McMahon and Force Management Co-Founder John Kaplan, the Revenue Builders podcast goes behind the scenes with the sales leaders who have been there, done that, and seen the results. This show is brought to you by Force Management. We help companies improve sales performance, executing their growth strategy at the point of sale. Connect with Us: LinkedInYouTubeForce Management

Most sales teams don't lose deals because they lack talent.They lose because there's no real system connecting ICP, outreach, discovery, and close.In this special mini series recap, we pulled the best moments from all five episodes of our client acquisition series — giving you the complete playbook in one place.From defining who you actually sell to, all the way through to closing with confidence and delivering on the promise.You'll hear from five experts on what actually moves the needle in modern B2B sales — and what's quietly killing pipelines everywhere.Inside this episode:why knowing your ICP changes everything downstreamhow to build a warm pipeline before you ever reach outwhy 68% of prospects see zero difference between sellersthe data → insight → question framework for outreach that gets repliesthe biggest mistake salespeople make on discovery callswhy chasing kills deals and what to do insteadred flags and green flags in qualificationwhy disqualifying is not losing — it's winning smarter⭐ Unlock free resources (templates, frameworks & prompts): ⁠https://coachpilot.beehiiv.com/⁠Join the community & access 157+ templates, frameworks and mega AI prompts used by top revenue teams.Watch Full Episode on YouTube: ⁠https://www.youtube.com/@revenueleaders⁠Follow us: ⁠https://www.instagram.com/davidfastuca/⁠

Roxanne breaks down Intrahepatic Cholestasis of Pregnancy (ICP) —a pregnancy-specific liver condition (about 2–3% of pregnancies) where bile acids build up in the bloodstream, often causing intense itching on palms/soles with no rash. She reviews other possible symptoms (jaundice, dark urine, light stools, fatigue, right upper quadrant pain), how diagnosis is made with symptoms plus bile acid labs (and sometimes liver enzymes), and how treatment depends on bile acid levels. Roxanne discusses options such as meds to lower bile acids and improve itching, fetal monitoring (NSTs/BPPs), and sometimes induction as early as 36 weeks—especially if bile acids are over 100. She explains baby risks (preterm birth, respiratory distress, stillbirth), including stillbirth rates. ICP usually resolves after birth but can recur (40–60%).Links for non stress test and biophysical profile breakdowns:NST: https://youtu.be/Bl-Q-GBHGLEBPP: https://youtu.be/r-holR0V4u000:00 Welcome and Overview00:16 Meet the Hosts01:04 ICP Symptoms and Why It Matters01:29 What ICP Is in the Liver02:15 Risks for Mom and Baby03:32 Other Signs and Diagnosis04:22 Treatment and Monitoring Plan05:24 Bile Acid Levels and Induction Timing06:49 Stillbirth Risk Numbers Explained09:08 Quick ICP Recap11:20 After Birth and Future Pregnancies11:59 Questions, Course, and Wrap-Up————Get Your Copy of Training for Two on Amazon: https://amzn.to/3VOTdwH

Today, I'm getting real about the harsh truths of entrepreneurship as I hit my six-year milestone of being self-employed and the importance of building a consistent system of productivity! We'll break down why not all revenue is created equal and how targeting the right ideal customer profile (ICP) is the secret to scaling your freight brokerage without burning out. From mastering time management and shortening fluff-filled meetings to protecting your self-worth from the volatility of the P&L, our discussion today will be your straightforward guide to navigate the "wasteland" between a big idea and true execution!  

Episode SummaryIn this episode of Million Dollar Flip Flops, Rodric sits down with Colin Herdman — lifelong entrepreneur, co-founder of Monkey Island Ventures, and founder of Rainmaker, a company helping business owners grow their network, leads, and sales using LinkedIn.Colin shares how he went from launching his first business a week after college to building multiple companies across digital marketing, software development, and LinkedIn growth strategy. Along the way, he's learned that real business growth still comes down to the same fundamentals: understanding your audience, teaching what you know, and building genuine relationships.Rodric and Colin also dig into AI, the future of marketing, community building, and why LinkedIn live streams may be one of the most underrated tools available for founders, coaches, and sales leaders today.This is a conversation about growth, yes — but even more, it's about authenticity, education, thought leadership, and how to stand out online without becoming just more noise.In this episode, you'll hear:Colin's journey from college graduate to lifelong entrepreneurThe story behind Monkey Island VenturesWhat his three companies are focused on todayWhy AI is changing marketing — and what it cannot replaceWhy community may become even more valuable in an AI-heavy worldColin's philosophy for using LinkedIn the right wayThe difference between creating noise and creating trustWhy educational content beats salesy content on LinkedInHow Colin uses LinkedIn live streams to generate leads and referralsA step-by-step breakdown of his LinkedIn live stream strategyWhy repetition and thought leadership matter more than constant content churnHighlights & Timestamps[00:00] Colin's core LinkedIn philosophy Colin explains the big idea behind his approach to LinkedIn: authenticity, education, experimentation, and understanding what your audience can learn from you.[01:00] Meet Colin Herdman Colin introduces himself as a lifelong entrepreneur who launched his first business one week after college.[01:00] From criminal justice degree to entrepreneurship He shares how he never used his degree and instead learned business through experience and the school of hard knocks.[02:00] The businesses Colin is building today Colin breaks down the three companies under Monkey Island Ventures: Aurion, Cloudburst, and Rainmaker.[03:00] What's changing fastest in marketing right now Rodric asks Colin about the biggest shifts in marketing, and Colin points straight to AI, automation, and the need for authenticity.[04:00] Why community matters more than ever Rodric and Colin talk about how AI may make entrepreneurship even lonelier — and why real community will become even more valuable.[05:00] What's next for Colin Colin shares why he is focused on growing the current businesses while staying open to future opportunities.[05:00] What Rainmaker actually does Colin explains how Rainmaker helps founders, coaches, and sales leaders use LinkedIn to grow relationships, leads, and sales.[06:00] Colin's philosophy for LinkedIn growth He outlines the three layers of his strategy: authenticity, educational mindset, and understanding what your audience wants to learn from you.[08:00] How he identifies the right audience Colin explains how he uses Sales Navigator and ICP-based targeting to define who to connect with.[09:00] Why first connections matter He shares why his team reaches out to around 100 people a week and why growing a first-degree network is foundational.[10:00] The three campaign types he uses Colin walks through the main campaign formats he uses: drip messaging, LinkedIn polls, and live streams.[11:00] Why LinkedIn live streams are the biggest opportunity He explains why live streams are powerful, why LinkedIn is leaning into them, and why they cut through AI-driven sameness.[12:00] How Colin structures live streams Colin shares how he chooses a specific audience and a repeatable 101-level topic that can be taught over and over again.[14:00] Why repetition works better than constant reinvention He explains why repeating great content to the right audience is smarter than always creating something new.[14:00] How LinkedIn event invites do the heavy lifting Colin shares how LinkedIn's event system helps drive awareness, reminders, and attendance without feeling spammy.[16:00] The real power of the follow-up After each live stream, Colin follows up with attendees in a thoughtful way that opens the door for natural next-step conversations.[18:00] How live streams build long-term trust Colin explains how repeated educational live streams create awareness, thought leadership, and referral momentum over time.[20:00] Where to find Colin He shares where people can connect with him, download his live stream resource, and learn more.[21:00] Colin's question for the next guest Colin asks the next guest what book most helped them implement growth and strategy in their business.[21:00] The question Colin was asked Colin reflects on the importance of turning inward and trying to stay true to who he is.Notable Quotes“Nobody wants to be sold on LinkedIn.” – Colin Herdman“What is it that they can learn from me? What can I teach?” – Colin Herdman“The real opportunity is on LinkedIn when you know what your audience can learn from you.” – Colin Herdman“It's all about authenticity. It's all about education. It's all about you.” – Colin Herdman“You don't have to keep creating new content all the time.” – Colin Herdman“What happens over time is you become top of mind for whatever topics you continually present on.” – Colin Herdman“It's all about sending the elevator back down.” – Rodric LenhartConnect with Colin

Photographer and artist Ed Templeton joins PhotoWork with Sasha Wolf to reflect on his evolution from professional skateboarder to photographer and painter, and how early influences like Nan Goldin and Larry Clark shaped his approach to documenting his own life. Templeton discusses his photobook Wires Crossed (Aperture), an intimate look at skate culture from an insider's perspective, and his collaborative process with editor Lesley A. Martin. The conversation looks into Templeton's hybrid analog and digital workflow and concludes with the development of Contemporary Suburbium (Nazraeli Press), an accordion style book, made in collaboration with his wife, photographer Deana Templeton, highlighting his ongoing engagement with the photobook and everyday subject matter. https://ed-templeton.com Ed Templeton (b.1972) is an American painter and photographer whose work reflects human behavior with emphasis on youth subcultures, religious affectation, and suburban conventions using a cinéma vérité approach embracing chance encounters. Templeton is a respected cult figure in the subculture of skateboarding, a two-time world-champion, and Skateboarding Hall of Fame inductee. He is best known for his photographic books and multimedia exhibitions. His work has been exhibited in museums worldwide including MOCA, Los Angeles, ICP, NYC, Palais de Tokyo, Paris, Kunsthalle, Vienna, Pier 24 Photography, San Francisco. His work is held in the collections of the Museum of Modern Art in New York, SMAK Museum Belgium, Orange County Museum of Art, Bonnefanten Museum, Maastricht.