Podcasts about Gatekeeper

If your contact rate is struggling, this is the fix. Join Michael Weaver LIVE on June 11th at noon CST - Increase Your Contact to Quote Ratio: Converting Dials to Dollars.

Rupprecht Podszun und Justus Haucap blicken auf die SCiDA-Konferenz in Düsseldorf und eine bemerkenswerte Diagnose von Bundeskartellamtspräsident Andreas Mundt: Das Kartellrecht könne gegen die großen Plattformen zu wenig ausrichten.Die Diagnose wirft eine grundsätzliche Frage auf: Reicht Kartellrechtsdurchsetzung gegen Big Tech überhaupt noch aus – oder braucht es inzwischen Regulierung? Doch selbst damit ist die Debatte nicht beendet. Auch der Digital Markets Act (DMA) gilt vielen nicht als Patentlösung. Hilft die private Rechtsdurchsetzung? Die Diskussion führt schnell über das Recht hinaus in Richtung Industriepolitik. Braucht Europa weniger Verfahren und mehr eigene Champions? Dazu passt das zweite Thema der Folge: das neue Tech-Paket der EU. Die Idee dahinter ist einfach: Europa soll seine Nachfrage strategischer einsetzen. Rechenzentren, Cloud-Dienste, Chips - die ganze digitale Infrastruktur "made in Europe"? Der "Staat als Ankerkunde" ist ein Konzept dafür. Für Wettbewerbsfans ist das zunächst ein ungewohnter Gedanke.„Buy European“ klingt schließlich nicht nach klassischemLeistungswettbewerb. Gleichzeitig stellt sich die Frage, ob europäische Wettbewerber ohne solche Impulse überhaupt eine Chance haben, sich gegen die etablierten Tech-Giganten zu entfalten.Die Debatte berührt damit eine Grundsatzfrage: Soll Wettbewerbspolitik Märkte nur offenhalten – oder auch aktiv dazu beitragen, neue Wettbewerber entstehen zu lassen? Außerdem in der Folge: Auf welchen Gatekeeper würde Justus Haucap seine Altersvorsorge setzen? Und in welchem Bereich die Deutsche Bahn tatsächlich erstaunlich erfolgreichist.Weitere HinweiseFranck, J. U., M. Peitz (2026), Stille Triebkraft wirtschaftlichen Erfolgs, Konrad-Adenauer-Stiftung (Hrsg.) Blog-Reports von derKonferenz zu "Shaping Competition in the Digital Age (SCiDA)"Tag 1Tag 2Europäische Kommission (2026), Kommission schlägt Paket zur technologischen Souveränität zur Stärkung der digitalen Autonomie und Resilienz Europas vor

Drop us a text message to say hi and let us know what you think of the show. (Include your email if you'd like us to reply)In which John and David discover that Jesus does not replace one gatekeeper with another. Instead, he becomes the gate himself. Along the way we connect John 10 with Psalm 118, Nicodemus, the healing of the blind man, and the challenge of resisting the gatekeeper that lives within each of us. Episode 245 of the Two Texts Podcast | Jesus and God's "Name" 9If you want to get in touch about something in the podcast you can reach out on podcast@twotexts.com or by liking and following the Two Texts podcast on Facebook, Instagram and Twitter. If you enjoy the podcast, we'd love it if you left a review or comment where you're listening from – and if you really enjoyed it, why not share it with a friend?Music by Woodford Music (c) 2021________Help us keep Two Texts free for everyone by becoming a supporter of the show John and David want to ensure that Two Texts always remains free content for everyone. We don't want to create a paywall or have premium content that would exclude others. However, Two Texts costs us around £60 per month (US$75; CAD$100) to make. If you'd like to support the show with even just a small monthly donation it would help ensure we can continue to produce the content that you love. Thank you so much.Support the show

RoseMarie Terenzio spent five years as the Chief of Staff to John F. Kennedy Jr. at George Magazine, operating at the center of one of the most highly scrutinized media and celebrity relationships of the 1990s. Working alongside both John F. Kennedy Jr. and Carolyn Bessette Kennedy during the height of public fascination surrounding the couple, RoseMarie managed the constant demands, pressure, and visibility that came with supporting an American icon.   Today, RoseMarie is a two-time New York Times bestselling author, co-author of JFK Jr: An Intimate Oral Biography, Executive Producer of I Am JFK Jr., and Vice President at Avoq where she specializes in strategic communications and crisis management work for high-profile leaders and organizations. In this episode of REACH, RoseMarie shares what it was really like to support JFK Jr. behind the scenes, navigate the evolving relationship between celebrity and media, and balance the mythology surrounding one of America's most famous couples with the private realities of the people behind the headlines. To explore more of RoseMarie's work, click the links below: Fairy Tale Interrupted: https://www.amazon.com/dp/1439187681?ref_=cm_sw_r_ffobk_cp_ud_dp_6GQPE6YGD35C4986D1ZG_1&bestFormat=true  JFK Jr: An Intimate Oral Biography: https://www.amazon.com/dp/1668018527?_encoding=UTF8&psc=1&ref_=cm_sw_r_ffobk_cp_ud_dp_VJXGGNAFD1F5YPTPY2XD_1&bestFormat=true  Avoq: https://teamavoq.com/people/rosemarie-terenzio/ 

The excitement is building for the outcome from this Core Update that started on May 21, 2026. And the data of the site performance in logs tells me everything I need to know.This week a little more about the newest VizzEx tool - Symmetry Gate™ Check Tool. You can find it at:https://symmetrygate.aiLast week's episode: ⁠https://www.confessionsofanseo.com/podcast/passing-the-symmetry-gate-for-ai-visibility-confessions-s6-episode-20/Mentioned in the show:https://status.search.google.com/VizzEx - ⁠⁠⁠⁠⁠⁠⁠https://vizzex.ai/vizzex-pro/⁠⁠Subscribe to Confessions of an SEO™ wherever you get your podcasts. Your subscribing and download sends the message that you appreciate what is being shared and helping others find Confessions of an SEO™An easy place to leave a review ⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠https://www.podchaser.com/podcasts/confessions-of-an-seo-1973881⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠You can find me on⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠Carolyn Holzman⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠ - Linkedin⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠American Way Media⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠ ⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠ Google Directly⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠AmericanWayMedia.com⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠ Consulting AgencyNeed Help With an Issue? - reach out Text me here - 512-222-3132Music from Uppbeathttps://uppbeat.io/t/doug-organ/fugue-stateLicense code: HESHAZ4ZOAUMWTUA

Dies ist nur er erste Teil der Mitglieder-Folge. Alles Laubar-Mitglieder können die ganze Folge hören. Werde hier Mitglied von Alles-laufbar.de, der Onlineplattform für die deutschsprachige Trailcommunity und erhalte Zugriff auf exklusive Inhalte. Ab 3,90 Euro/Monat bist du dabei! Willkommen zur Mai-Folge des Alles Laufbar Mitglieder-Podcasts! Für diesen Mitgliederpodcast haben ein volles Programm für euch vorbereitet.Wir besprechen den ereignisreichen zurückliegenden Monat. Denn es ist einiges passiert, inklusive einiger mutmaßlicher „Aufregerthemen“. Zunächst berichten wir von unseren beiden Rennen. Benni war beim Mountainman Nesselwang am Start und ist, obwohl er aus seiner Sicht keinen guten Tag erwischt hat, noch Deutscher Meister in der Mannschaftswertung geworden. Christian findet: Titel ist Titel. Letzterer war beim Rennsteig und konnte trotz viel Trainingsausfall eine für ihn überraschend gute Zeit laufen. Wir waren beim Sales-Meeting von La Sportiva am Gardasee und haben den im nächsten Jahr erscheinenden Prodigio Pro 2 gesehen. Vom Gardasee selbst haben wir dann weniger gesehen, denn das Wetter war miserabel.Außerdem berichtet Christian von seinen Erfahrungen beim Zuschauen des Zegama-Livestreams, für den er extra Geld bezahlt hat. Soviel sei gesagt: Christian hat das Abo des Senders wieder gekündigt. Im Hauptteil besprechen wir die drei großen Themen des Monats: Rachel Entrekins sensationellen Overall-Sieg beim Cocodona 250; fast zeitgleich läuft der Influencer Arda Saatçi einen selbstorganisierten Ultra und erhält ein Vielfaches an Aufmerksamkeit. Was hat das eine mit dem anderen zu tun? Wie hängt beides zusammen? Nicht zuletzt sprechen wir über den „Circle Pit“, eine Marketing-Aktion von Satisfy zusammen mit Adidas, die für viel Kritik innerhalb der Trailrunningszene gesorgt hat. Werden hier die Werte des Sports verkauft? Wie kann man solche Aktionen kritisieren, ohne als „Gatekeeper“ zu agieren? Uns findest du hier:Website: Alles-laufbar.deInstagram: @alleslaufbarYouTube: @alleslaufbarStrava Club: @Alles laufbar.de

Your conscious mind is only 5% of your brain, but it's the GATEKEEPER controlling access to everything. Most peoiple are trying to manifest whilst completely bypassing this critical step, and then wonder why nothing's working. Today, I'm revealing the magic word that unlocks the cosmic Costco (spoiler: it's VISION), teaching you how to use your imagination the RIGHT way, and showing you how to get your rational mind working FOR you instead of against you. Plus, we're doing the "What Am I Done With?" list that's going to change everything. This is where manifestation stops being woo-woo and starts becoming strategic. Today's Challenge: Make your 'I'm done with this' list, then write the opposite of that on the other side of the paper. This will give you a really good indication of what you want to begin calling in and manifesting into your life. To secure your spot for the LIVE workshop, happening on May 28th at 5pm UK time, register for free below: >>> SAVE YOUR SPOT FOR THE WORKSHOP PLUS, I've also created a free bonus pack to help you maximise your experience throughout the challenge, with a Morning Manifestation Meditation to rewire your subconscious, as well as a workbook to guide you through the 7-days of the challenge. It's not mandatory but it is juicy - get access below: >>> Manifest In May Bonus Pack: Workbook & Manifestation Meditation And if you're ready to master manifestation once and for all, I''ll be sharing a secret offer to come and join me inside of my Just F*cking Manifest It Academy on Day 7 of the challenge. Check out the academy below and keep your eyes & ears opened for the secret offer! www.jfmiacademy.com Loved this episode? I'd love to hear your thoughts! Reach out to me on Instagram @noor_hibbert and let me know your biggest takeaways and breakthroughs from this episode - I respond to all DMs personally!

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

Proton-Drive Angebot

► Hier gehts zur nächsten Episode (Meine Geschichte): ⁠https://linkly.link/2WkUE⁠  ► kostenloses Startgespräch buchen: ⁠https://linkly.link/24kPi⁠ ► Kickscale Extended Free Version: ⁠https://2ly.link/1zdl4Cold Calling Blueprint: SDR Veljko Vukovic erklärt, wie er im ersten Quartal 220% seiner SDR-Ziele erreichte und Woche für Woche 10+ Termine durch Cold Calling bucht, ohne jahrelange Erfahrung und trotz Akzent. In dieser Episode zeigt Veljko, warum das so ist und wie es anders geht: mit Reflexion, echter Recherche über die Person und einem simplen Cold-Call-Blueprint, der wirklich funktioniert. So kann ich dir im Sales helfen:zur Software Sales Formula: https://www.softwaresalesformula.comzum Sales Gym: https://www.sales-gym.ioKickscale:Extended Free Version: https://2ly.link/1zdl4Timestamps:Infos:jiri@softwaresalesformula.com https://www.softwaresalesformula.com  https://www.sales.gym.io (0:00) Warum 83% aller SDRs ihre Ziele verfehlen(2:00) Veljkos Weg: Vom Eisverkäufer zum Top SDR(6:00) Erster Tag als SDR: 120 Calls, null Termine(8:00) Reflexion nach Tag 1: Was wirklich schiefgelaufen ist(11:00) Input vs. Output – Das Gym-Prinzip im Sales(13:00) Mentaler State: Wie du deine PS auf die Straße bringst(17:00) Rechercheroutine: Person statt Unternehmen recherchieren(24:00) Cold Calling vs. E-Mail vs. LinkedIn(30:00) Cold Calling Blueprint Schritt für Schritt(40:00) Gatekeeper richtig ansprechen(43:00) Tagesstruktur und Focus Blocks(48:00) Lernen aus eigenen Calls(54:00) Top Erfolgsprinzipien nach 4 Monaten(57:00) Das SDR-Gesetz: Wöchentlicher Reflexionsblock

Cristina Gomez reviews the latest UFO / UAP news and covers a newly named Pentagon UFO gatekeeper, blocked Congressional access, obstruction at the top of the intelligence community, Jeremy Corbell on the 46 UFO videos, and Burlison demanding the release of a 1952 UFO film from MIT Lincoln Lab.To see the VIDEO of this episode, click or copy link - https://youtu.be/PClQE2NO8kYVisit my website with International UFO News, Articles, Videos, and Podcast direct links -www.ufonews.co00:00 - The UFO Gatekeeper01:00 - Burchett UFO Blockade02:30 - The Name In The Open04:30 - UFO Files Obstructed05:30 - Corbell On UFO Secrecy07:30 - Burlison Names UFO LabBecome a supporter of this podcast: https://www.spreaker.com/podcast/strange-and-unexplained--5235662/support.

Wie entstehen öffentliche Meinungen? Woraus setzt sich Öffentlichkeit zusammen? Und wie hat sich diese Sphäre über die Jahrhunderte verändert? In „Strukturwandel der Öffentlichkeit“ (1962) analysiert Jürgen Habermas den Aufstieg und Niedergang der sogenannten bürgerlichen Öffentlichkeit. Ihre Entstehung verortet er im Europa des 18. und 19. Jahrhunderts: In Salons und Kaffeehäusern treten Privatpersonen erstmals zu einem „räsonierenden“ Publikum zusammen, um über Politik, Gesellschaft und Kultur zu diskutieren. Doch mit dem Aufkommen der Massenmedien im 20. Jahrhundert – Radio, Fernsehen, Internet – erodiert diese bürgerliche Öffentlichkeit, die Habermas noch vom rationalen Prinzip des „besseren Arguments“ geleitet sah. Zunehmend bestimmen ökonomische Interessen gigantischer Medienkonzerne, wie Öffentlichkeit organisiert ist. Das räsonierende Publikum, so Habermas, wird zum konsumierenden Publikum. Unter den Bedingungen des digitalen Kapitalismus und der Plattformisierung stellt sich erneut die Frage, wie sich die Struktur der Öffentlichkeit verändert. Soziale Medien verschieben dabei die Grenze zwischen ‚privat' und ‚öffentlich‘ grundlegend: Inhalte können nun unmittelbar veröffentlicht und verbreitet werden, ohne zuvor die klassischen Filterinstanzen oder „Gatekeeper“ wie Zeitungsredaktionen und Medienhäuser zu durchlaufen. Sind die Sozialen Medien von heute die Salons und Kaffeehäuser des 18. Jahrhunderts – neue Orte demokratischer Verständigung? Oder markieren sie vielmehr einen historischen Bruch, indem Öffentlichkeit nicht mehr primär die Funktion der Verständigung, sondern der Unterhaltung und zunehmend auch der Überwachung einnimmt? In der neuen Folge unseres Theorie-Podcasts führt Alex Demirović in Habermas' Strukturwandel der Öffentlichkeit ein und spricht mit dem Soziologen und Kommunikationswissenschaftler Sebastian Sevignani über die Aktualität des Werks. Kontakt, Kritik, Feedback: theoriepodcast@rosalux.org

► Hier gehts zur nächsten Episode (Meine Geschichte): https://linkly.link/2WkUE  ► kostenloses Startgespräch buchen: https://linkly.link/24kPi ► Kickscale Extended Free Version: https://2ly.link/1zdl4 Cold Calling Blueprint: SDR Veljko Vukovic erklärt, wie er im ersten Quartal 220% seiner SDR-Ziele erreichte und Woche für Woche 10+ Termine durch Cold Calling bucht, ohne jahrelange Erfahrung und trotz Akzent. In dieser Episode zeigt Veljko, warum das so ist und wie es anders geht: mit Reflexion, echter Recherche über die Person und einem simplen Cold-Call-Blueprint, der wirklich funktioniert.  So kann ich dir im Sales helfen: zur Software Sales Formula: https://www.softwaresalesformula.com zum Sales Gym: https://www.sales-gym.io Kickscale: Extended Free Version: https://2ly.link/1zdl4 Timestamps: (0:00) Warum 83% aller SDRs ihre Ziele verfehlen (2:00) Veljkos Weg: Vom Eisverkäufer zum Top SDR (6:00) Erster Tag als SDR: 120 Calls, null Termine (8:00) Reflexion nach Tag 1: Was wirklich schiefgelaufen ist (11:00) Input vs. Output – Das Gym-Prinzip im Sales (13:00) Mentaler State: Wie du deine PS auf die Straße bringst (17:00) Rechercheroutine: Person statt Unternehmen recherchieren (24:00) Cold Calling vs. E-Mail vs. LinkedIn (30:00) Cold Calling Blueprint Schritt für Schritt (40:00) Gatekeeper richtig ansprechen (43:00) Tagesstruktur und Focus Blocks (48:00) Lernen aus eigenen Calls (54:00) Top Erfolgsprinzipien nach 4 Monaten (57:00) Das SDR-Gesetz: Wöchentlicher Reflexionsblock Infos: jiri@softwaresalesformula.com https://www.softwaresalesformula.com  https://www.sales.gym.io 

Is AI reinforcing or diluting your brand? Which brands do LLMs choose to surface and why? LLMs are actively shaping how brands are discovered, compared and chosen. They are becoming the new gatekeepers of growth. In this expert roundtable, Kantar leaders, from across disciplines and markets, discuss how LLMs are reshaping brand discovery.You'll leave with clarity on:1. New opportunities for growth in the AI era2. Practical guidance to support confident, informed next steps for your brand3. Data-led perspectives to shape what to focus on Win the LLMs' choice using signal intelligenceVisibility is not enough. Brands need signal intelligence to understand how AI assistants are reshaping consumer decisions. Win the LLMs' choice by strengthening the brand signals AI relies on. BrandDigital AI signals goes beyond short-term discoverability to show how LLMs shape long-term brand equity, grounded in Kantar's Meaningful, Different and Salient (MDS) framework.From visibility metrics to MDS-aligned signals, itreveals how brand predisposition is built or erodedacross AI assistants.Find out more: Kantar BrandDigital AI signals Hosted on Acast. See acast.com/privacy for more information.

Bro. Matthew Robbins , president Basileia Ministries Living water Worship Centre  https://www.basileiaministries.com/livingwater   In this powerful message, “Our Gate Keeper,” we explore the battle between the soul, spirit, and flesh and discover why Jesus must become the overseer of our thoughts, emotions, and decisions. Through scriptures like Hebrews 4:12, John 10, Philippians 4:8, and Peter walking on water, this sermon reveals how the Holy Spirit works to guide believers into victorious living. Learn how to guard your mind, cast down destructive thoughts, overcome fear and doubt, and stop allowing harmful influences to “park” in your soul. This message will challenge you to surrender fully to God's Word and let the Great Shepherd become the true Gate Keeper of your life.

Recent biographies and investigative accounts reframe Ghislaine Maxwell not merely as Jeffrey Epstein's accomplice, but as a critical gatekeeper who facilitated his entrée into elite circles—including the British royal family. According to author Andrew Lownie's new book Entitled, Maxwell leveraged her longstanding friendship with Prince Andrew (which began during his Oxford-era years) to introduce Epstein into royal social settings. Maxwell reportedly used Andrew as social bait to lure prominent individuals, enhancing Epstein's access to power and influence—passing as much more than a mere sidekick in Epstein's networks. These revelations depict Maxwell as a central enabler whose social maneuvering had profound consequences for the monarchy's reputation.These accounts align with what Prince Andrew himself acknowledged in a 2019 Newsnight interview—that he met Epstein through Maxwell. He confirmed that Epstein and Maxwell attended a shooting weekend at Sandringham in 2000 at his invitation, though he portrayed the weekend as innocuous. Nonetheless, archival emails, photographs, and court filings have illustrated the depth of their association, underscoring how Maxwell's social influence and ties to Andrew played a pivotal role in Epstein's infiltration of high-society networks.to contact me:bobbycapucci@protonmail.comsource:‘Entitled' Reveals Ghislaine Maxwell's Grip on Prince AndrewBecome a supporter of this podcast: https://www.spreaker.com/podcast/the-moscow-murders-and-more--5852883/support.

Recent biographies and investigative accounts reframe Ghislaine Maxwell not merely as Jeffrey Epstein's accomplice, but as a critical gatekeeper who facilitated his entrée into elite circles—including the British royal family. According to author Andrew Lownie's new book Entitled, Maxwell leveraged her longstanding friendship with Prince Andrew (which began during his Oxford-era years) to introduce Epstein into royal social settings. Maxwell reportedly used Andrew as social bait to lure prominent individuals, enhancing Epstein's access to power and influence—passing as much more than a mere sidekick in Epstein's networks. These revelations depict Maxwell as a central enabler whose social maneuvering had profound consequences for the monarchy's reputation.These accounts align with what Prince Andrew himself acknowledged in a 2019 Newsnight interview—that he met Epstein through Maxwell. He confirmed that Epstein and Maxwell attended a shooting weekend at Sandringham in 2000 at his invitation, though he portrayed the weekend as innocuous. Nonetheless, archival emails, photographs, and court filings have illustrated the depth of their association, underscoring how Maxwell's social influence and ties to Andrew played a pivotal role in Epstein's infiltration of high-society networks.to contact me:bobbycapucci@protonmail.comsource:‘Entitled' Reveals Ghislaine Maxwell's Grip on Prince Andrew

Smrithi Mohan is General Counsel at Awesome, the parent company of SmugMug and Flickr, where she oversees all legal, IP, privacy, and compliance matters for two of the world's most recognized photo-sharing platforms. She previously spent a decade at Dun & Bradstreet, where she built the company's first global IP and innovation practice. An elected Board of Education member and recognized Top Woman Leader, she speaks and writes on legal operations, IP strategy, leadership, and building legal functions from the ground up. In this episode… When a new AI feature ships or a new product is designed, general counsel may not be looped in until after key decisions are made. This creates risk because most product decisions have legal implications, especially around data use, user rights, and consent. That changes when legal teams are brought into the product development cycle at the outset, helping design outcomes that align with legal obligations and business goals. How can general counsel and legal teams move from being seen as gatekeepers to business drivers? Shifting how general counsel and legal teams are viewed starts with building strong relationships across business teams. When legal leaders understand how product, engineering, and other teams operate, they are more likely to be included as ideas take shape. Early involvement enables general counsel to explain regulatory requirements and legal frameworks across different jurisdictions, thereby improving products and making them more defensible. It also creates space to ask fundamental questions in AI development upfront, including what data is being used, whether the company has the right to use it, who owns the outputs, and whether user information is collected with proper consent flows. Vendor relationships require the same level of attention, as older contracts may not address AI and often need audits, addendums, and updated terms.  In this episode of She Said Privacy/He Said Security, Jodi and Justin Daniels talk with Smrithi Mohan, General Counsel at Awesome, about how legal teams can integrate into AI and product development. Smrithi explains why general counsel needs to act as business architects and not just legal advisors, and what it takes to make that shift. She outlines the core legal questions teams should address when developing AI tools and other products, how to manage third-party vendor contract risks, and the evolving legal gray areas surrounding AI-generated content and platform liability. Smrithi also offers practical advice on building genuine, collaborative relationships across teams. 

Schickt uns euer Feedback zur EpisodeDas Internet fühlt sich plötzlich fremd an: zu glatt, zu voll, zu laut und manchmal so künstlich, dass wir selbst echten Menschen nicht mehr trauen. Wir nehmen die Dead Internet Theory ernst, ohne in Verschwörung abzurutschen, und schauen stattdessen auf die Resultate: KI-Slop, Content-Farmen, Bots, Propaganda und eine Aufmerksamkeitsökonomie, die Masse belohnt statt Sinn. Wenn Kommunikation ohne echte Intention entsteht, kippt der Diskursraum und es wird immer schwerer, „gute“ Informationen zwischen den Klatschblättern zu finden.Gleichzeitig verlagert sich Vertrauen ausgerechnet zu LLMs wie ChatGPT, Claude oder Perplexity, weil sie den Informationsdschungel scheinbar filtern. Wir sprechen darüber, warum das LLM damit zum Gatekeeper wird, wie sich SEO Richtung GEO verschiebt, und weshalb der Wettbewerb der KI-Firmen strukturell zu Monopolen drängt. Dual-Use, Government-Contracts und „too big to fail“ sind nicht nur Schlagworte, sondern echte Pfade, über die KI-Infrastruktur staatstragend werden kann. Hinter dem Hype liegt zudem viel menschliche Arbeit: RLHF, Clickworker und eine „polierte“ Oberfläche, die Desinformation genauso glattziehen kann wie hilfreiches Wissen.Wir bleiben nicht im Doom hängen, sondern suchen konkrete Gegenentwürfe: Transparenz, Open Source, Datensouveränität sowie EU-Regeln wie Digital Services Act und Digital Markets Act. Und wir zeigen, wie KI auch anders wirken kann, etwa als Moderations- und Auswertungswerkzeug für bessere Diskussionen, inklusive unserer kleinen Habermas-Maschine im Unternehmensalltag. Zum Schluss wird es praktisch: Welche neuen Kompetenzen brauchen wir, um Blackbox-Autorität zu widerstehen, Outputs einzuordnen und Ziele sauber zu setzen, ohne Lernarbeit und Urteilskraft zu verlieren?

Recent biographies and investigative accounts reframe Ghislaine Maxwell not merely as Jeffrey Epstein's accomplice, but as a critical gatekeeper who facilitated his entrée into elite circles—including the British royal family. According to author Andrew Lownie's new book Entitled, Maxwell leveraged her longstanding friendship with Prince Andrew (which began during his Oxford-era years) to introduce Epstein into royal social settings. Maxwell reportedly used Andrew as social bait to lure prominent individuals, enhancing Epstein's access to power and influence—passing as much more than a mere sidekick in Epstein's networks. These revelations depict Maxwell as a central enabler whose social maneuvering had profound consequences for the monarchy's reputation.These accounts align with what Prince Andrew himself acknowledged in a 2019 Newsnight interview—that he met Epstein through Maxwell. He confirmed that Epstein and Maxwell attended a shooting weekend at Sandringham in 2000 at his invitation, though he portrayed the weekend as innocuous. Nonetheless, archival emails, photographs, and court filings have illustrated the depth of their association, underscoring how Maxwell's social influence and ties to Andrew played a pivotal role in Epstein's infiltration of high-society networks.to contact me:bobbycapucci@protonmail.comsource:‘Entitled' Reveals Ghislaine Maxwell's Grip on Prince AndrewBecome a supporter of this podcast: https://www.spreaker.com/podcast/the-epstein-chronicles--5003294/support.

 Hey there, Welcome to Living Word! We're so glad you're here with us. If you find this message inspiring, don't forget to hit that like button and subscribe for more amazing content. We've got a lineup of guest speakers, pastors, and engaging discussions with our awesome community members coming your way. Let's dive in together! Our Links–• Join The Prayer Movement!: https://theprayermovement.com• Instagram: https://www.instagram.com/livingwordmn• Facebook: https://www.facebook.com/livingwordmn• Stay up to date with all things LWCC at https://www.LWCC.org• Join our Online Church community here: https://www.lwcc.org/onlinechurch• Give online: https://www.lwcc.org/give/• If you recently committed your life to God, we'd like to give you a free eBook to help you in your spiritual journey. Click here to download: https://www.lwcc.org/nextsteps/#LivingWord #ChurchSermon #Worship 

Hey there, Welcome to Living Word! We're so glad you're here with us. If you find this message inspiring, don't forget to hit that like button and subscribe for more amazing content. We've got a lineup of guest speakers, pastors, and engaging discussions with our awesome community members coming your way. Let's dive in together! Our Links–• Join The Prayer Movement!: https://theprayermovement.com• Instagram: https://www.instagram.com/livingwordmn• Facebook: https://www.facebook.com/livingwordmn• Stay up to date with all things LWCC at https://www.LWCC.org• Join our Online Church community here: https://www.lwcc.org/onlinechurch• Give online: https://www.lwcc.org/give/• If you recently committed your life to God, we'd like to give you a free eBook to help you in your spiritual journey. Click here to download: https://www.lwcc.org/nextsteps/#LivingWord #ChurchSermon #Worship

This is from our video on Gatekeeper Tips and Tactics That Actually Work. You can watch the video here https://youtu.be/CqeDVGKYYcY?si=QF9IMUAuK0beQoYU

11. HEADLINE: Historical Precedents for Modern Maritime Chokepoints GUEST: Ziyi (Emily) WangSUMMARY: Emily Wang explains how the 1936 Montreux Convention established Turkey as a durable gatekeeper for the Turkish Straits, offering lessons for modern conflicts. The treaty balanced the shared tacit interests of opposing powers like Britain and Russia. Its success highlights the importance of legally binding frameworks in managing strategic waterways.1912

SCREEN QUEENS: "Trust Me: The False Prophet," "Hulk Hogan: Real American," and "Imperfect Women," a morning show sea shanty, what happened to Colin Jost and Pete Davidson's ferry, and Cat Gatekeeper browser extension is genius See Privacy Policy at https://art19.com/privacy and California Privacy Notice at https://art19.com/privacy#do-not-sell-my-info.

A flawless packet and a clean slide deck still weren't enough to win $100,000, and that sting leads to a bigger lesson about how groups actually decide. When six people with different biases sit in judgment, logic alone rarely creates agreement. What moves the room is alignment: they understand it fast, they feel why it matters, and they arrive at the same “oh, I see” moment together. That's the hidden work behind successful grant pitches, sales presentations, board presentations, and any high-stakes group conversation. We dig into a simple framework for stakeholder buy-in: cognitive clarity, emotional engagement, and a shared aha experience. Then we take a surprising detour through the Hebrew alphabet and its pictogram roots to show why the brain craves visuals and why a picture can carry meaning instantly across age, language, and expertise. If your message is trapped in dense text, the audience's attention slips because their brain is trying to conserve energy and avoid risk. From there, we jump into NotebookLM as a practical AI communication tool you can use right now. We talk about grounding outputs in your own data sources, why source quality determines outcome, and how citations create trust. Most importantly, we show how to turn messy information into visual storytelling assets like infographics, slide support, audio overviews, and quick video explainers you can send after a meeting to reinforce retention and keep the group aligned. If you want an unfair advantage in executive communication, hit play, then subscribe, share with a teammate, and leave a review with your biggest presentation challenge.Support the show

Geschätzte Lesedauer: 12 Minuten Du willst komplexe B2B Deals gewinnen und fragst dich, warum so viele Angebote im Nirvana verschwinden? Was glaubst du, ist eigentlich der häufigste Grund, warum du Aufträge verlierst? Der Wettbewerb? Der Preis? Dein Produkt? Falsch. Denn der häufigste Grund ist, dass dein Kunde sich gar nicht entscheidet. Er sagt also nicht „Nein, wir nehmen den anderen". Stattdessen sagt er: „Wir warten erst mal ab." Genau hier liegt das Problem, das deine Pipeline aufbläht und außerdem deine Marge frisst. 40 bis 60 Prozent aller qualifizierten B2B-Pipelines enden in „No Decision". Das ist also zwei- bis dreimal so viel, wie du an den Wettbewerb verlierst. Folglich zeige ich dir in dieser Folge, warum das so ist und wie du als Verkäufer im Mittelstand vom ahnungslosen Hoffnungsverkäufer zum gefragten Entscheidungsarchitekten wirst. Wir reden über Buying Center, über die drei Phasen jeder Kaufentscheidung und außerdem über die eine Frage, die du stellen musst, bevor du jemals wieder ein Angebot rausschickst. Warum 60 % deiner Pipeline im komplexen B2B Vertrieb in „No Decision" enden Lass uns ehrlich sein. Du steckst Tage, manchmal sogar Wochen in ein Angebot. Dein Team ist beschäftigt. Die Kalkulation steht. Außerdem hat dein Vertrieb das Ding gefühlt schon im Sack. Und dann? Funkstille. Kein Auftrag, keine Absage, einfach nichts. Das ist kein Einzelfall, sondern die Regel. Studien zeigen seit Jahren das gleiche Bild: Der größte Wettbewerber im B2B ist nicht der Anbieter um die Ecke. Vielmehr ist es die Nicht-Entscheidung. Der Kunde verschiebt, vertagt oder vergisst. Manchmal hat er auch intern einfach keinen Konsens erreicht, was er überhaupt will. Gartner hat 2025 untersucht, wie B2B-Buying-Committees ticken. Das Ergebnis: 74 Prozent dieser Buying-Teams zeigen einen ungesunden Konflikt während des Entscheidungsprozesses. Das ist also keine produktive Meinungsverschiedenheit, sondern lähmender Stillstand. Forrester legt sogar noch nach: 86 Prozent aller B2B-Käufe kommen in den frühen Phasen ins Stocken, bevor überhaupt ein Lieferant ausgewählt wird. Wenn du also brav wartest, bis der Kunde mit einer Anfrage auf dich zukommt, bist du nicht im Spiel. Im Gegenteil: Du bist Teil des Problems. Tote Pferde reiten – das große Pipeline-Märchen Viele Verkäufer im Mittelstand reiten tote Pferde. Sie haben Pipelines, die voll aussehen, aber zu 80 Prozent aus Angeboten bestehen, die niemals einen Auftrag werden. Das frisst Zeit, Geld und außerdem deine Brainpower. Folglich lenkt es dich von den wenigen, wirklich relevanten Deals ab. Eine Not-to-do-Liste ist hier oft wirksamer als jede Akquise-Kampagne. Welche Angebote schreibst du nicht? Wo investierst du keine Stunde mehr? Im transaktionalen Geschäft („Schick mir mal eine Kiste Schrauben") magst du mit Masse arbeiten. Aber im komplexen B2B Vertrieb, in dem dein Kunde mit der Entscheidung ein echtes Risiko eingeht, gilt das Gegenteil. Die drei Phasen jeder B2B-Kaufentscheidung Damit du komplexe B2B Deals gewinnen kannst, musst du zuerst verstehen, wie eine Kaufentscheidung beim Kunden überhaupt entsteht. Es sind drei Phasen, und in keiner davon stehst du als Verkäufer automatisch im Mittelpunkt. Phase 1: Das Problem erkennen und priorisieren Bevor irgendetwas passiert, muss intern jemand sagen: „So kann es nicht weitergehen." Ein Beispiel: Der Vertriebsleiter merkt, dass die Daten über seinen Vertriebsprozess nicht reichen. Folglich kann er sein Team nicht steuern. Erst wenn dieses Problem benannt und priorisiert ist, entsteht überhaupt Handlungsdruck. Ohne diesen Druck passiert gar nichts. Null. Nada. Phase 2: Den Lösungsweg wählen Jetzt wird es spannend. Der Kunde überlegt nämlich, wie er das Problem lösen kann. Stellt er jemanden ein? Nimmt er ein neues CRM-System? Oder beauftragt er eine Beratung? Hier sitzt plötzlich nicht mehr nur der Vertriebsleiter am Tisch. Stattdessen kommen IT, Controlling, Marketing und Geschäftsführung dazu. Genau hier entsteht das Buying Center B2B – das Einkaufsgremium, das gemeinsam entscheidet. Und genau hier scheitern die meisten Projekte. Nicht etwa, weil die Leute böse sind, sondern weil sie sich intern nicht einig werden, was die beste Lösung ist. Phase 3: Den Lieferanten auswählen Das ist die einfachste Phase – aber nur für den Kunden. Er hat sich entschieden, was er will. Jetzt googelt er, vergleicht und holt drei Angebote ein. Genau hier kommen die meisten Verkäufer ins Spiel. Allerdings zu spät. Wenn du erst in Phase 3 auftauchst, sind die Kriterien schon definiert. Folglich bist du austauschbar. Es geht nur noch um Preis und Spezifikation. Damit bist du einer von vielen, der eine Ausschreibung beantwortet. Willkommen also in der Margenhölle. Buying Center B2B: Mit wem du wirklich sprechen musst Verkaufst du komplexe Lösungen, verkaufst du nie an „den Entscheider". Vielmehr verkaufst du an ein Gremium. Forrester hat in einer Studie aus 2025 nachgewiesen: An einer typischen B2B-Kaufentscheidung sind 13 interne Stakeholder und 9 externe Beteiligte involviert. Das ist also kein Meeting mehr, sondern eine Konferenz. Jeder dieser Stakeholder hat andere Prioritäten: Der Einkauf denkt an Kosten und Compliance. Der Fachbereich will Funktionalität und außerdem einen einfachen Alltag. Die IT denkt an Integration, Sicherheit und ihren ohnehin schon vollen Schreibtisch. Die Geschäftsführung will den strategischen Wert sehen. Legal will Verträge prüfen, die nicht zur Falle werden. Diese Leute reden oft gar nicht miteinander. Außerdem haben sie unterschiedliche Risikoprofile, Budgetverantwortungen und manchmal sogar unterschiedliche Zeitzonen. Das Ergebnis ist meistens nicht „Wir machen es nicht", sondern „Wir warten ab". Und genau das ist No Decision. Die gute Nachricht im Chaos des Buying Center B2B Wenn ein Buying Center es schafft, einen Konsens zu erreichen, ist die Wahrscheinlichkeit, dass der Deal auch wirklich durchgezogen wird, 2,5 Mal so hoch. Das heißt: Wenn du es schaffst, dem Gremium beim Konsens zu helfen, hast du einen riesigen Hebel. Genau das ist heute deine Aufgabe als Verkäufer im Mittelstand. Nicht charmant lächeln. Sondern moderieren, strukturieren und vor allem führen. Komplexe B2B Deals gewinnen: Vom Hoffnungsverkäufer zum Entscheidungsarchitekten Hier kommt der entscheidende Mindset-Shift, den du im Kopf machen musst. Ein Angebot ist nämlich kein Akquise-Tool. Vielmehr ist ein Angebot die Bestätigung eines gemeinsam erarbeiteten Lösungswegs. Es gehört auf Stufe 3. Wenn Stufe 1 und 2 nicht abgeschlossen sind, macht ein Angebot überhaupt keinen Sinn. Der Hoffnungsverkäufer schreibt 50 Angebote pro Quartal und betet, dass eines davon zurückkommt. Der Entscheidungsarchitekt dagegen schreibt 10 Angebote, von denen 7 gewonnen werden – weil er vorher gemeinsam mit dem Kunden den Boden bereitet hat. Welcher von beiden willst du sein? Früh rein, statt spät reagieren: Der Challenger-Ansatz für komplexen B2B Vertrieb Die wirklich starken Verkäufer im Mittelstand sind nicht die, die schnell Angebote rausballern. Im Gegenteil: Es sind die, die früh beim Kunden auf der Matte stehen. Idealerweise, bevor der Kunde das Problem überhaupt erkannt hat. Stell dir vor, du gehst zu einem potenziellen Kunden und sagst: „Bei euch läuft im Vertrieb scheinbar alles super. Aber wusstet ihr, dass euer Wettbewerb längst Datenmodelle nutzt, mit denen er eure besten Kunden gezielt abfischen kann? Wenn ihr da nicht in den nächsten zwölf Monaten nachzieht, habt ihr ein massives Problem." Das ist die Idee hinter dem Challenger Sale. Du provozierst, du bringst neue Perspektiven und außerdem schaffst du den Handlungsdruck, der intern noch fehlt. Und – by the way – du bist der Anbieter, der das Problem lösen kann. So bist du nicht mehr Teilnehmer einer Ausschreibung, sondern Architekt der Entscheidung. Bevor du das nächste Angebot schreibst: Diese Fragen MUSST du stellen Wenn ein Kunde sagt „Schicken Sie uns mal ein Angebot", ist das der Moment, in dem 80 Prozent der Verkäufer den größten Fehler ihrer Woche machen. Sie sagen nämlich begeistert „Ja, mache ich!" und verschwinden zwei Wochen in der Angebotsstube. Mach das bitte nicht. Stell stattdessen Fragen. Diese hier: Gibt es ein definiertes Budget oder zumindest einen Investitionsrahmen? Gibt es einen konkreten Zeitdruck oder ein Critical Event (z. B. auslaufende Lizenzen, neue Mitarbeiter, regulatorische Frist)? Wer ist am Entscheidungsprozess beteiligt? Wie läuft so eine Entscheidung typischerweise bei euch ab? Wer wird das am Ende unterschreiben – und was ist für diese Person besonders wichtig? Was passiert, wenn ihr nichts tut? Welche Konsequenz hat die Nicht-Entscheidung? Wenn dein Ansprechpartner diese Fragen nicht beantworten kann oder will, ist das ein Signal. Entweder bist du beim falschen Menschen. Oder du bist zum falschen Zeitpunkt da. Beides ist also wichtig zu wissen, bevor du Tage in ein Angebot investierst, das nie kommen wird. Übrigens: Manchmal steckt hinter „Schick uns ein Angebot" schlicht die Botschaft: „Geh mir nicht auf den Sack und verpiss dich." Auch das musst du herausfinden. Mit Fragen. Die Stakeholder-Map: Dein wichtigstes Werkzeug im B2B Entscheidungsgremium Um das B2B Entscheidungsgremium wirklich zu verstehen, brauchst du eine Stakeholder-Map. Das ist eine Karte, auf der du gemeinsam mit deinem Ansprechpartner aufzeichnest, wer in welcher Rolle an der Entscheidung beteiligt ist. Wer ist Promoter, wer ist Blocker, wer ist Mobilizer und wer ist Gatekeeper? Amerikanische Studien zeigen: Unternehmen, die systematisch eine Stakeholder-Influencer-Map aufstellen, haben fast 40 Prozent höhere Gewinnchancen in ihrer Pipeline. Logisch. Wenn nämlich irgendwo im Unternehmen jemand sitzt, der dich blockiert, wird dein Angebot nicht gewinnen, egal wie schön es ist. Die richtigen Fragen für deine Stakeholder-Map Stell deinem Ansprechpartner diese Fragen, um die Map gemeinsam zu bauen: Mit diesen Fragen baust du eine belastbare Stakeholder-Map und kannst komplexe B2B Deals gewinnen. Wer muss bei einer Investition in dieser Größenordnung mit am Tisch sitzen? Damit findest du Einkauf, IT, Legal, Fachbereich und außerdem die Geschäftsführung. Gab es in der Vergangenheit ähnliche Projekte, die intern gescheitert sind? Woran lag das? Damit erkennst du Haken und Ösen, bevor du reintappst. Wer könnte interne Bedenken haben – und welche? Damit identifizierst du Blocker, bevor sie aktiv werden. Wer hat zuletzt eine ähnliche Entscheidung erfolgreich intern durchgebracht? Wie hat er das gemacht? Damit findest du den Mobilizer – die Person, die intern verkaufen kann. Was passiert, wenn ihr nichts tut? Damit machst du den Schmerz der Nicht-Entscheidung greifbar. Wenn du diese Map gemeinsam mit deinem Ansprechpartner erstellst, passiert etwas Magisches. Erstens: Du siehst sofort, wie tief er selbst im Thema drin ist. Zweitens: Er commitet sich automatisch stärker, weil er aktiv mitgearbeitet hat. Und drittens: Du kannst plötzlich viel besser einschätzen, ob und wann das Angebot kommt – und außerdem, woran es vielleicht hängt. Mobilizer finden – die Geheimwaffe, um komplexe B2B Deals zu gewinnen Im Buch The Challenger Customer beschreiben Brent Adamson und Matthew Dixon eine Rolle, die im Buying Center alles entscheidet: den Mobilizer. Das ist nämlich die Person, die intern andere überzeugen kann. Die Veränderung treiben will. Die nicht nur nett zuhört, sondern das Projekt aktiv durchdrückt. Talker und Blocker gibt es genug. Mobilizer dagegen sind selten. Aber wenn du einen findest und ihn richtig ausstattest – mit Argumenten, mit Daten und außerdem mit einer klaren Story – wird er für dich intern arbeiten. Das ist also der einzige Hebel, der „Unhealthy Conflict" in einem Buying Committee aufbrechen kann. Quick Takeaways: Was du sofort umsetzen kannst 40 bis 60 Prozent aller B2B-Angebote enden in No Decision – das ist also dein größter Wettbewerber, nicht der Mitbewerber. Eine Kaufentscheidung läuft in drei Phasen ab: Problem erkennen, Lösungsweg wählen und außerdem Lieferant auswählen. Sei früh dabei, nicht erst in Phase 3. 13 interne und 9 externe Stakeholder sind im Schnitt an einer komplexen B2B-Entscheidung beteiligt – verkaufe also nie an „den einen Entscheider". 74 % der Buying-Teams erleben ungesunden Konflikt – folglich ist es deine Aufgabe, Konsens zu moderieren. Ein Angebot ist kein Akquise-Tool, sondern die Bestätigung eines gemeinsam erarbeiteten Lösungswegs. Stelle die fünf Killer-Fragen (Budget, Critical Event, Buying Center, Unterzeichner, Konsequenz der Nicht-Entscheidung), bevor du auch nur eine Excel-Zeile für ein Angebot tippst. Bau eine Stakeholder-Map mit deinem Ansprechpartner – das erhöht deine Win-Rate um bis zu 40 %. Pragmatismus zum Schluss Musst du das bei jedem Angebot durchziehen? Nein. Wenn du einen Bestandskunden hast, der seit Jahren zuverlässig kauft und dir Aufträge zuschiebt – dann mach es einfach. Aber selbst dann lohnt es sich, regelmäßig zu hinterfragen: Habe ich wirklich alles erfasst? Verkaufe ich nur an meinen einen Ansprechpartner – oder gibt es da intern noch jemanden, an den ich verkaufen könnte? Sehr viele Verkäufer lassen genau hier viel Geld liegen. Die Regel: Bei jedem komplexen Deal, bei dem es um Risiko, Investition und Veränderung geht, stell die Fragen. Bau die Map. Werde zum Architekten. Sonst bleibst du Hoffnungsverkäufer. Fazit: Komplexe B2B Deals gewinnen ist eine Frage der Methode Wenn du im Mittelstand komplexe B2B Deals gewinnen willst, hilft dir kein neues CRM-System und auch keine geschliffene Verkaufsphrase. Was dir wirklich hilft, ist ein anderes Selbstverständnis. Du bist nicht mehr der Anbieter, der ein Angebot abgibt. Vielmehr bist du der Architekt, der einem Buying Center hilft, eine Entscheidung zu treffen, die alle tragen. Das ist Arbeit. Außerdem ist es mehr Zeit pro Deal. Aber es ist die einzige Methode, mit der du raus aus dem No-Decision-Sumpf kommst und endlich wieder planbar gewinnst. Folglich steigt deine Win-Rate, deine Marge auch – und nebenbei hörst du auf, tote Pferde zu reiten. Frag dich heute Abend: An welchen drei Deals in meiner Pipeline arbeite ich gerade, ohne wirklich zu wissen, wie der Kunde entscheidet? Dann ruf morgen früh dort an. Stell die Fragen. Bau die Map. Und falls du dabei Unterstützung brauchst – mein Team und ich helfen Vertriebsleitern und Unternehmern im Mittelstand genau dabei. Buch dir hier dein kostenloses Strategiegespräch und wir schauen uns deine Pipeline gemeinsam an: Termin mit Chris vereinbaren. FAQ – Komplexe B2B Deals gewinnen Was bedeutet „No Decision" im komplexen B2B Vertrieb? „No Decision" heißt, dass ein Kunde sich am Ende eines Verkaufsprozesses gar nicht entscheidet – weder für dich noch gegen dich. Statt eines Auftrags oder einer Absage passiert: nichts. Studien zeigen, dass 40 bis 60 % aller qualifizierten B2B-Pipelines so enden. Folglich ist das im komplexen B2B Vertrieb der größte Verlustgrund – größer als jeder Wettbewerber. Was ist ein Buying Center B2B? Ein Buying Center B2B (auch Einkaufsgremium oder B2B Entscheidungsgremium) ist die Gruppe von Personen, die im Unternehmen eines Kunden gemeinsam über einen Kauf entscheidet. Im Schnitt sind das 13 interne und außerdem 9 externe Stakeholder. Dazu gehören Fachbereich, Einkauf, IT, Legal und Geschäftsführung – jede Rolle mit eigenen Prioritäten. Wie viele Personen sind an einer B2B-Kaufentscheidung beteiligt? Forrester hat 2025 ermittelt, dass an einer typischen komplexen B2B-Kaufentscheidung im Schnitt 13 interne und 9 externe Stakeholder beteiligt sind. Frühere Studien sprachen dagegen von 5,4 Personen – die Zahl ist in den letzten Jahren also massiv gestiegen, weil Risiken, Compliance und Digitalisierung mehr Abteilungen einbinden. Welche Fragen muss ich stellen, um komplexe B2B Deals gewinnen zu können? Mindestens fünf: Gibt es ein konkretes Budget? Gibt es einen Critical Event mit Zeitdruck? Wer ist im Buying Center? Wer unterschreibt am Ende und was ist diesem Menschen wichtig? Und außerdem: Was passiert, wenn der Kunde nichts tut? Wer diese Fragen nicht beantwortet bekommt, schreibt das Angebot oft umsonst. Was ist ein Mobilizer im komplexen B2B Vertrieb? Ein Mobilizer ist eine Person im Buying Center, die intern Veränderung treiben kann und auch will. Er überzeugt Kollegen, räumt Widerstände aus und treibt das Projekt zum Abschluss. Im Buch „The Challenger Customer" wird er als entscheidender Hebel beschrieben, um komplexe B2B Deals gewinnen zu können – weil ohne ihn der interne Konsens kaum entsteht. Was nimmst du mit? Welche Frage aus dieser Folge wirst du beim nächsten komplexen Angebot zuerst stellen? Schreib es gerne in die Kommentare auf YouTube oder schick mir eine Nachricht auf LinkedIn. Und wenn dir die Folge geholfen hat: Teile sie mit einem Vertriebskollegen, der gerade mal wieder ein Angebot in den Wind schreibt. Das ist nämlich die beste Hilfe, die du ihm heute geben kannst.

The views of my guest do not reflect that if my own. That being said, this is on of our attempts to bring levity to conspiracy world. Try not to get offended, Eric is a comedian after all.Eric's website https://www.erichollerbach.com/Forbidden Knowledge Network https://forbiddenknowledge.news/ FKN Link Treehttps://linktr.ee/FKNlinksMake a Donation to Forbidden Knowledge News https://www.paypal.me/forbiddenknowledgenehttps://buymeacoffee.com/forbiddenWe are back on YouTube! https://youtube.com/@forbiddenknowledgenews?si=XQhXCjteMKYNUJSjBackup channelhttps://youtube.com/@fknshow1?si=tIoIjpUGeSoRNaEsDoors of Perception is available now on Amazon Prime!https://watch.amazon.com/detail?gti=amzn1.dv.gti.8a60e6c7-678d-4502-b335-adfbb30697b8&ref_=atv_lp_share_mv&r=webDoors of Perception official trailerhttps://youtu.be/F-VJ01kMSII?si=Ee6xwtUONA18HNLZListen to Forbidden Knowledge News on clearair.fm every Tuesday, Thursday, and Saturday 12:15pm CSThttps://clearair.fm/Pick up Independent Media Token herehttps://www.independentmediatoken.com/Be prepared for any emergency with Prep Starts Now!https://prepstartsnow.com/discount/FKNStart your microdosing journey with BrainsupremeGet 15% off your order here!!https://brainsupreme.co/FKN15Book a free consultation with Jennifer Halcame Emailjenniferhalcame@gmail.comFacebook pagehttps://www.facebook.com/profile.php?id=61561665957079&mibextid=ZbWKwLWatch The Forbidden Documentary: Occult Louisiana on Tubi: https://link.tubi.tv/pGXW6chxCJbC60 PurplePowerhttps://go.shopc60.com/FORBIDDEN10/or use coupon code knowledge10Johnny Larson's artworkhttps://www.patreon.com/JohnnyLarsonSign up on Rokfin!https://rokfin.com/fknplusPodcastshttps://www.spreaker.com/show/forbiddenAvailable on all platforms Support FKN on Spreaker https://spreaker.page.link/KoPgfbEq8kcsR5oj9FKN ON Rumblehttps://rumble.com/c/FKNpGet Cory Hughes books!Lee Harvey Oswald In Black and White https://www.amazon.com/dp/B0FJ2PQJRMA Warning From History Audio bookhttps://buymeacoffee.com/jfkbook/e/392579https://www.buymeacoffee.com/jfkbookhttps://www.amazon.com/Warning-History-Cory-Hughes/dp/B0CL14VQY6/ref=mp_s_a_1_1?crid=72HEFZQA7TAP&keywords=a+warning+from+history+cory+hughes&qid=1698861279&sprefix=a+warning+fro%2Caps%2C121&sr=8-1https://coryhughes.org/Our Facebook pageshttps://www.facebook.com/forbiddenknowledgenewsconspiracy/https://www.facebook.com/FKNNetwork/Instagram @forbiddenknowledgenews1@forbiddenknowledgenetworkXhttps://x.com/ForbiddenKnow10?t=uO5AqEtDuHdF9fXYtCUtfw&s=09Email Forbidden Knowledge News forbiddenknowledgenews@gmail.comsome music thanks to:https://www.bensound.com/ULFAPO3OJSCGN8LDDGLBEYNSIXA6EMZJ5FUXWYNC6WJNJKRS8DH27IXE3D73E97DC6JMAFZLSZDGTWFIBecome a supporter of this podcast: https://www.spreaker.com/podcast/forbidden-knowledge-news--3589233/support.

John 1:19-21You might like to get some copies of The Lightning-Fast Field Guide to the Bible for yourself and for others - here's a link that gets TMBH a little kickback: https://amzn.to/4pEYSS9Thanks to everyone who supports TMBH at patreon.com/thetmbhpodcastYou're the reason we can all do this together!Discuss the episode hereMusic by Jeff Foote

SPC, the fruit and veg processor, has been a major beneficiary as Aussies are stocking up on baked beans and canned goods. Uniqlo is heading for another record year, with global expansion driving a surprise surge in profits. Anthropic is holding back its most powerful AI mode… and only giving it to Big Tech… to stop hackers winning the AI arms race. _ Download the free app (App Store): http://bit.ly/FluxAppStore Download the free app (Google Play): http://bit.ly/FluxappGooglePlay Daily newsletter: https://bit.ly/fluxnewsletter Flux on Instagram: http://bit.ly/fluxinsta Flux on TikTok: https://www.tiktok.com/@flux.finance —- The content in this podcast reflects the views and opinions of the hosts, and is intended for personal and not commercial use. We do not represent or endorse the accuracy or reliability of any opinion, statement or other information provided or distributed in these episodes. —- Important Information: This material has been created with the co-operation of BlackRock Investment Management (Australia) Limited (BIMAL) ABN 13006 165 975, AFSL 230 523 on 1 April 2026. Comments made by BIMAL employees here represent BIMAL’s views only. This material provides general advice only and does not take into account your individual objectives, financial situation, needs or circumstances. Before making any investment decision, you should obtain financial advice tailored to you having regard to your individual objectives, financial situation, needs and circumstances. Refer to BIMAL’s Financial Services Guide on its website for more information. This material is not a financial product recommendation or an offer or solicitation with respect to the purchase or sale of any financial product in any jurisdiction. ------- S&P Dow Jones Indices does not sponsor, endorse, sell, or promote any product based onan S&P Dow Jones index nor does it make any representation regarding the advisability ofinvesting in the products. Before making any investment decisions, you should assesswhether the product or service is appropriate for you and read the PDS and TMD availableat blackrock.com.au.See omnystudio.com/listener for privacy information.

Imagine your mindset is behind gates and you are stood infront of them with your armour on as the gatekeeper. How important is that role?Very.... It's very important to you and for you to make sure that you are taking responsibility and accountibility of your own mindset and what positive and negative things you're allowing to affect it.Don't underestimate the power of your own mindset and what you need to do to stack up and uplevel it and the reasons why. It is literally lifechanging - of which I walk the talk and I'm living proof it works - that's why I master in it.Enjoy this episode.Show up to your life & Keep Going Always ™ Rebecca.xMy website is here > ⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠https://www.rebeccaadamsbiz.com⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠My powerful EXPANSION program is here to transform your life > ⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠https://racourses.thinkific.com/courses/expansion⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠My amazing guided journals & planners are here > ⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠https://www.rebeccaadamsbiz.com/books⁠⁠⁠⁠⁠⁠⁠

Veteran CCM radio promoter Chris Hauser shares a fascinating behind-the-scenes look at how songs actually make it onto the air, revealing the intense competition and industry strategy it takes to break a song. We'll also explore the tension between art and audience, and how a great song always finds its way in the end.

Author, Columnest and podcaster Drew Allen joined Caleb for a conversation about the current state of the country and the conservative camp. https://drewallen.substack.com/Church and State is brought to you by,  YOU!  Visit us at: https://churchandstate.media where you can support us by donating directly and find links to shop with our affiliates.Get our merch at https://standupnowapparel.com/partner-church-and-state/   Learn how to Protect Your Wealth against inflation at: www.BH-PM.com and tell them Church and State sent you.Support Church and State today by shopping at www.MyPillow.com using our coupon code: “CHURCHANDSTATE”.Our links are on link tree: https://linktr.ee/churchandstate                    Subscribe to our Locals Community (churchandstate1.locals.com)   Follow us on Rumble (@ChurchandState1776) https://rumble.com/user/ChurchandState1776    X(twitter) (@1churchandstate) https://x.com/1churchandstatefacebook (churchandstate1776) https://www.facebook.com/ChurchandState1776   SubStack (churchandstate.substack.com) https://churchandstate.substack.com/     *Help fund our fight against tyranny: Buy from our affiliates and tell them Church and State sent you. *Tune in on NRBTV Tue-Fri 1:30 PM Pacific! Become a supporter of this podcast: https://www.spreaker.com/podcast/prepper-broadcasting-network--3295097/support.BECOME A SUPPORTER FOR AD FREE PODCASTS, EARLY ACCESS & TONS OF MEMBERS ONLY CONTENT!Red Beacon Ready OUR PREPAREDNESS SHOPThe Prepper's Medical Handbook Build Your Medical Cache – Welcome PBN FamilySupport PBN with a Donation Join the Prepper Broadcasting Network for expert insights on #Survival, #Prepping, #SelfReliance, #OffGridLiving, #Homesteading, #Homestead building, #SelfSufficiency, #Permaculture, #OffGrid solutions, and #SHTF preparedness. With diverse hosts and shows, get practical tips to thrive independently – subscribe now!Newsletter – Welcome PBN FamilyGet Your Free Copy of 50 MUST READ BOOKS TO SURVIVE DOOMSDAY

Head to https://betterhelp.com/vetted to get 10% off your first month with our sponsor, BetterHelp. Therapy can be a meaningful space to reflect, grow, and create positive change in your life.CALL FREE ‪(469) 324-9929‬ and leave Vetted ONE message with your UFO/ET experience and we might play it on the show. (We do NOT return calls.)

Ein herbstlicher Abend im Frühling in Berlin Mitte. Das erste Mal seit Wochen wieder gemeinsam in einem Hotelzimmer. Beide leicht angemüdet.Über deutsche Feldwebel als Gatekeeper am Flughafen, darüber wie lange man eigentlich auf einer öffentlichen Toilette verweilen darf und dann noch ohne abzuschließen, den Rita Süssmuth Castrop Look, Übergewichtsgebühren für Menschen beim Check in, die Kaulitzbrüder in LA, Anderson Paak in einer Corvette und über zu viele Michaels in der Lobby.Werbepartner fraenkEgal ob Bindungsangst, Geizhals oder Handysucht, bei deinem Handyvertrag brauchst du kein Drama.Lade dir die fraenk App herunter, nutze den Freundecode „FRIENDLY4“ und starte direkt mit extra Datenvolumen.Mehr Infos unter: fraenk.de/Friendlyfire.Executive Producer: Ruben Schulze-FröhlichProducer: Kai SteinmetzProjektleitung: Annabell RühlemannSounddesign & Produktion: Carl von Gaisberg„Beisenherz und Polak – Friendly Fire“ ist ein Podcast aus den Wake Word Studios. Hosted on Acast. See acast.com/privacy for more information.

- iOS 26.4 & Co.: Ohne Siri, aber trotzdem gut? - All-in-one: Apple startet neue Business-Plattform - Alarmstufe Rot: Schwere iOS-Sicherheitslücke und jeder kann sie nutzen - Apple TV geht Rundfunkanstalten auf den Sender: Droht mehr Regulierung? - WWDC voraus: Apple kündigt Termin an - Umfrage der Woche - Zuschriften unserer Hörer === Anzeige / Sponsorenhinweis === Diese Folge wird präsentiert von Incogni. Nutze den Code APFELFUNK unter dem unten aufgeführten Link, um einen exklusiven Rabatt in Höhe von 60% auf dein Incogni-Abo zu erhalten: https://incogni.com/apfelfunk === Anzeige / Sponsorenhinweis Ende === Links zur Sendung: - Apfelfunk News: iOS 264 und iPadOS 264 mit KI-Playlist-Generator und neuen Emoji - https://apfelfunk.com/apple-veroeffentlicht-ios-26-4-und-ipados-26-4-mit-ki-playlist-generator-und-neuen-emoji/ - Apfelfunk News: Neue Firmware 8B39 für AirPods Pro und AirPods 4 - https://apfelfunk.com/apple-veroeffentlicht-neue-firmware-8b39-fuer-airpods-pro-und-airpods-4/ - Apfelfunk News: watchOS-Updates für ältere Modelle zur Zertifikatsverlängerung - https://apfelfunk.com/apple-veroeffentlicht-watchos-updates-fuer-aeltere-modelle-zur-zertifikatsverlaengerung/ - Apfelfunk News: Sicherheitsupdates für ältere iOS- und macOS-Versionen - https://apfelfunk.com/apple-veroeffentlicht-sicherheitsupdates-fuer-aeltere-ios-und-macos-versionen/ - Apfelfunk News: Geschäftstools in kostenloser Apple Business Plattform vereint - https://apfelfunk.com/apple-vereint-geschaeftstools-in-kostenloser-apple-business-plattform/ - Apfelfunk News: Schwere iOS-Sicherheitslücke mit öffentlichem Exploit-Code - https://apfelfunk.com/schwere-ios-sicherheitsluecke-exploit-code-oeffentlich-veroeffentlicht/ - Apfelfunk News: EU-Sender fordern Regulierung von Apple TV und Siri als Gatekeeper - https://apfelfunk.com/eu-sender-fordern-regulierung-von-apple-tv-und-siri-als-gatekeeper/ - Mac & i: WWDC 2026 am 8. Juni mit erstem Blick auf iOS 27 und macOS 27 - https://www.heise.de/news/WWDC-2026-am-8-Juni-Apple-gewaehrt-ersten-Blick-auf-iOS-27-und-macOS-27-11221912.html Kapitelmarken: (00:00:00) Begrüßung (00:22:40) Werbung (00:26:03) Begrüßung (00:32:44) Themen (00:33:45) iOS 26.4 & Co.: Ohne Siri, aber trotzdem gut? (01:09:26) All-in-one: Apple startet neue Business-Plattform (01:16:29) Alarmstufe Rot: Schwere iOS-Sicherheitslücke und jeder kann sie nutzen (01:21:08) Apple TV geht Rundfunkanstalten auf den Sender: Droht mehr Regulierung? (01:27:34) WWDC voraus: Apple kündigt Termin an (01:31:25) Umfrage der Woche (01:35:50) Zuschriften unserer Hörer

Kiera joins Dr. Paul Etchison on the Dental Practice Heroes podcast to talk about the infamous front desk and how to finally figure out what levers should be pulled and which should be pushed to get the department in ship-shape. The best part about this episode is that Kiera and Dr. Etchison make the steps to success easy to understand and implement. Episode resources: Subscribe to The Dental A-Team podcast Schedule a Practice Assessment Leave us a review Transcript: The Dental A Team (00:00) Hello, Dental A Team listeners, this is Kiera. And today we are sharing a guest interview I did on another podcast. And it was too valuable not to bring you guys here.   this episode, you're gonna hear this host lead the conversation and then I'll wrap us up at the end. I cannot wait. It was truly one of my most incredible episodes and I truly hope you enjoy.   speaker-0 (00:19) Kiera, so glad to have you back on the podcast. It's always a joy having you on here. And I'll tell the listeners, I've worked personally with Kiera a number of occasions, someone I very much trust, someone I respect entirely in the industry and just knows her stuff and always a great guest to have you on. And today we're going to be talking about, you know, front desk stuff where   I work with a lot of clients. Do you work with a lot of clients? I don't know if you share the same regard. I would love to hear your opinion on this, but I would say most of the clients that I work with, the front desk tends to be their most chaotic and unorganized department. I mean, do you feel that you share the same sentiment?   speaker-1 (00:59) Yeah, Paul super excited to be on the podcast with you. Always enjoy a good chat and I mean, think proof's in the pudding. Do you remember the number one reason you called me to work with you the first time? Oh yeah, I was front office.   speaker-0 (01:12) I think it was the second time and the third time.   speaker-1 (01:14) It really all those times were and the answer is yes and this is why I created Dental A Team is because like Working in the dental college and seeing so many dental students like you guys learn how to Drop your box on an MO and like how do I have a perfect crown prep? You don't learn how do I do the billing and how do I do the insurance and how do I schedule patients like you learn how to have patient etiquette and great dentistry and so that's why I created Dental A Team like it's dentists and teams like hey dentist let's get you to rock your space and then let's work on the team side because   because even myself as a team member, there was no learning. It was like, just do it. And I'm like, well, what do I just do? And so I think the front office just feels so elusive. It feels so scary. And like, Paul, you're in someone's mouth. You're not like, ⁓ how do I do an insurance claim? And so I think there's so many nuances, but also for dentists, the front office is the gatekeeper of your money. Like they're the ones who schedule for you. They're the ones who present your cases for you. They're the ones who collect the money for you. They're the ones who bill for you. So so much of your financial freedom and like,   your paycheck is also directed by a department you don't even understand. So I think that that's why there's so much just like, it's not conflict, it's just almost like unknown and it feels daunting. And so you don't even know what levers to push or pull because you don't even understand how the how the engine works. It'd be like, hey, Kiera, my car is making a sound and I'm like, good, I don't know what to do. Like, that's not even my realm. And I think that that's how a lot of dentists feel about the front office. So, yeah, that's why that's why I exist and why I love to   be on the podcast and share because it doesn't need to feel daunting or scary, nor do you need to do it all. I think just being aware and knowing what things to look for, what things you can expect and having a hopefully a trusted voice in the industry where like, hey, I'm here, no judgment. Like just ask all the questions and let's help you guys get your team up to par. And also for team members, cause they, lot of times don't even know what they should do either.   speaker-0 (03:05) Yeah, absolutely. They're just thrown in there and said, here, figure it out. Do it. Just answer the phone and do all this fun stuff. I mean, like, I think what struggles for dentists as practice owners is we just don't understand, like you mentioned. We don't understand, like, how to send a claim, how to look at an insurance breakdown. But whereas every other element of the practice, we have a deeper understanding on it. Do you think, I mean, I'm sure it would be beneficial, but is it necessary for a dentist to learn everything about claim submission and all these things?   front desk related? Or can we get by with some more higher level organizations such as you provide?   speaker-1 (03:41) I think, Paul, it depends on who you are. think Paul Etchison, I would say you probably can get by with some high level. You got it, you got it figured out, you can sift through. For some other doctors, they want to at least know. But I would say it's a blanket statement across the board. I think at least having a slight awareness, go up to the front office and just sit there and be like, hey, walk me through how you submit a claim. ⁓ I think you even knowing some of the jargon, the language of   what's going on up there. Like, can I see an EOB? ⁓ That's like, and I think it's kind of like, go back Paul, being a business owner, I equate front office to like a PNL and CPA and bookkeeping. We have all learned how to run a business without being a CPA or a bookkeeper, but it's because we're in the language of the PNL. And I think, how can you get into the language of the front office? You know yourself, but.   I think abdication and just like delegation, like hands off is probably a dangerous space to be, think for any business owner. Like I don't want to be in sales, but if I don't understand the sales process, that's not going to work. Marketing, like, okay, great. But I need to at least understand the nuances of it. And I think that's the same for front office. So I would say as a simple blip, why not just go up and listen to how your front office schedules? Why not go up and just see how they submit claims or verify insurance?   And then, yes, I would talk to and listen to podcasts by the Dental A Team or other trusted individuals in the field. ⁓ We have online courses that we've created for all of these. Not so dentists learn it, but just to like, what's kind of my, I don't know, like front office for dummies, like go back to those books that they had, like, what's my quick overview to where I'm not going to get screwed over, I'm not going to get embezzled from, I'm going to know what to expect of my team. And I'm even happy to share even simple job descriptions of what those roles   can and should be doing. I think even that knowledge alone helps doctors just feel more confident and competent of like, ⁓ my office manager should be acting like a COO. My billers should be acting like a CFO or an accountant. Like they should at least know this and be able to bring things in. And my over 90 should be know more than 5 % of my collections. Like knowing just those little pieces, I think ⁓ that's just going to give people more confidence. But again,   equated to how you work with your CPA and your bookkeeper. You didn't know that, but you were immersed in the language of it. And I think the more you can just look, know, learn without doing. And I'm talking like this is like a week or a month. Like it's not like years and years. Like you could just quickly get affiliated with it. But I think audits and spot audits once a quarter would really be beneficial. And if you're a hands-on person like myself, literally have your front office have you like submit one claim and submit and   put in one payment onto the software, ⁓ do one insurance verification, do one scheduling. It might feel weird, but just like you have your front office come back and watch a crown so they can explain it in a treatment plan, just doing it one time also gives you a lot of familiarity that I think you can catch a lot of things just because you almost know what does A plus B equals C, how does that equation actually work.   speaker-0 (06:54) Yeah, and I love that CPA analogy because that makes a lot of sense. Like we don't get deep into the bookkeeping and deep into the profit and loss, but we do know enough that we can use it. You know, and I see with like the front office is that a lot of dental practice owners, just don't see the value and they just don't see like why to provide the training out there. And it's such a large part of the practice. I mean, just like, like if you could like pick just a few, what are some downstream things that happen that us as owners see that is more visual to us?   evidence of lack of training upfront.   speaker-1 (07:27) Yeah. ⁓   Paul, I don't disagree and I think it's something crazy because it's like hygiene is so important and so we like focus a lot on hygiene and make sure it's there. But your front office is the, I call it like the bookends of the practice. They're the initial ⁓ information for the practice and the first impression and then they're also the last impression. And I can't tell you how many doctors I'm like, Paul, you're amazing, but your front office is actually destroying your business and you don't even know it. So things that you might not catch or see are sometimes like your front office with billing, like look at your review.   because if your billing is having problems, it will pop up in reviews and they'll say like, they charged me wrong or they didn't quote me right. Like that's gonna do some red flag alerts for you just to be able to quickly see. Usually the billing issues downstream are gonna show up in the reviews and patients leaving the practice that you might not even know about. ⁓ Other things that I think you can catch are like, if you have any type of recording of phone calls or have a family member that you trust, just be a random new patient with air quotes on it.   and give feedback of how they were treated on the phone. I think that's a really good way to find out because if your front office puts them on hold or they don't have like genuine care and customer service centric, patients are going to leave that you don't even get the opportunity and you're spending all this money on marketing. But then our front office is like, could you please hold? And it's like, great, super happy to be put on hold or I can't get you scheduled in or even like, I think sometimes dentists, you.   Kind of like myself, when I go into a practice, I'm like a creepy little hangout behind the scenes. Like, doctors, if you have a little bit of downtime, just go like hang on the wall and listen to how your front office team is answering the phones, how they're presenting treatment plans. You probably like, areas that I see a lot of opportunities that are missed are, how are we converting our phone calls and getting patients on the schedule? How are we scheduling? Like, are my patients saying, I cringe when I go in. I cringe when I hear phone calls.   I cringe when I hear another scheduling. I cringe when we're presenting treatment. If a patient's like, I'll just wait. They're like, OK. I'm like, OK. No, like, we should go past this two times. There's ways to do it. Or if a patient calls about a balance and they're like, it's OK. We'll just write it off. And I'm like, we're writing that off? ⁓ You can look at audit trails to see what is being written off on your accounts in billing. ⁓ You also can look at your AR. You could quickly just run the AR report. You don't even have to know.   A good benchmark is less than 1 % of your collection, or like one month's worth of collections should be all that's in your AR. So if you're producing 100 grand, we should have no more than 100 grand in total AR. So those are just some downstream of, think, like really making sure our schedule's full and we're treating patients amazing so they're not leaving before we even get that opportunity. Are cases being closed? And like we've got great verbiage to close cases.   And then honestly, like there was a practice and I walked in and there was a huge stack of checks and I was like, what are these doing? They're like, I just don't have time to enter those. And I'm like, well, we don't have time to like pay you either. So get those checks in like really truly. I'm not trying to be a jerk, but like you've got to get these in. ⁓ And then looking at the claims and how much AR sitting in there just to see, and then doing a quick audit trail to see I had a practice. had about, gosh, about a million dollars worth of AR.   And I was like, is high. And they're like, yeah. Like if we can't get in touch with the patient, we just write it off. And I was like, I'm sorry, what? Like you just write? They're like, yeah, we try. But like, if they don't answer, we just write it off. And I was like, so that's like not allowed. And we need to have the doctor approve those. So I think some of those little pieces, and those can be set up with audit trails or permissions within the software. And I think even just some of those safeguards can really help a practice.   Like these are, think, a lot of red hot fires that could be worse than you realize. Dr. Paul, you could be doing amazing dentistry, but if your front office team is not great on the phone, not great with case acceptance, not great with billing, you might accidentally be losing a lot of, like there's just a lot of open holes and you're trying to put in more by diagnosing more and doing more dentistry at the top. But our buckets got quite a few little leaky holes that even if we put like patched a couple, you'd see your practice grow a lot more with minimal effort.   speaker-0 (11:47) Yeah, I always like to think of the idea that if we've got like a $1 million practice and typically we see case acceptance in like the one third, like 33 % ish, you know, when we're looking at a fee. So you would think that we're diagnosing $3 million. So most doctors will focus on the things such as like, well, let's work on the way I talk to the patient. Let's work on this. Whereas completely missing the fact that, I mean, just even getting a 5 % increase in case acceptance that would come from training on the front desk end versus   stuff that you would do on the back. So it's like, it's a valuable part of the office. But, you know, I'd love to ask you, we've got this part of the office that is a lot of competing demands, a lot of different things to do at once. And what I see is doctors often getting upset at their front desk when they're not filling the schedule because the doctor has a cancellation and now the doctor has time to like say what is going on and they go to the front, they say, well, who's filling the schedule? And everyone's like, well, we're doing this, this, this, and this. How do you, as an owner, like,   help a department see these competing demands and have the right sort of priorities.   speaker-1 (12:53) Yeah, Paul, there's a great book ⁓ that I am obsessed with this year. We sent it out to a bunch of people and let's see. Hold on. I'm looking it up.   You know, I really love it. Clearly. I think it's called Begin with We. Let me just double check myself on it. I'm pretty confident looking it up real quick. ⁓ It's We. Yes, Begin with We and it's by Kyle McDowell. And it was something that I really got obsessed with this year because there was a one of his 10 rules is outcomes over activity.   And I realized that I think that that is one of the greatest hiccups in the dental practice is we're so obsessed with activity, but not outcomes. And so in a dental practice, I'm really big on what is the outcome that this position needs to get.   I don't want them and I used to do this. Like I used to have end of day checklists that were like front office team needs to make 25 re-care calls. And then I was like, why am I saying that? What I really want from those 25 re-care calls is I want a full schedule and I don't want my team to be perfect, but I do need to make sure that the main outcome. So like one main outcome or KPI or metric per position and they know and like some people are like, Carol, how do get your team to do this? And I'm like, my team knew that if our schedule was not full, they were not going home.   like period, like you're gonna, I don't care, you're gonna stay until eight o'clock at night, but like that schedule is expected to be full. And it's not that I'm like driving hard lines. It was, this is the most important thing. So my scheduler, their goal is that they need to have my doctor scheduled to goal 90 % of the time, like we are scheduled to go or it's front office team knows that my hygiene schedule needs to be completely full with all confirmed patients because don't worry, they play games and it's like, well, my schedule is full. And I'm like, yeah, well, half of these weren't confirmed. They're gonna be no shows. So it's a...   My schedule is full or we're allowed one hygiene opening with all of our hygienists per day. But like by end of day, this needs to be done in every day that that's our goal. And our goal is to make sure that hygiene is up to goal 90 % of the time. We track it daily. We track it weekly. We make sure they're there. My treatment coordinator, my doctors need to be up to goal, like to their scheduled daily production goal. That's the expectation every day is that they're scheduled to goal. And when I look at the course of a week or a month, my expectation is that 90 % of my days, Paul, you're hitting your daily goal.   Well, now that and that's like, that's their main focus. I think so often we're like, we want the schedule full, we want the patient experience, we want this and we want that. But I'm like, if I can simplify it for my team, just like my AR, my AR needs to be less than one month's worth of collections and I need less than these amounts per category. Great. There's so many other things they can do that they can get busy and like, I got to answer the phone. But if I know before I leave, like the way I win and the way I check my day off is.   I've got my doctor scheduled to goal, I've got my hygiene schedule full and we've got our months collections done. Those are three of your biggest areas. Of course there's a thousand things, but when we lock and load on that and my doctor needs to diagnose X amount, ⁓ it does also then impact our case acceptance because guess what? Now that treatment coordinator is like, shoot, I have to get Dr. Paul up to, I don't know, 5,000, 8,000, whatever your daily goal is. And I know that that's my expectation and I'm going to be reporting every single week on this.   And what happens if I don't hit goal? So some people incentivize with bonuses. Some people, this is just part of your job description. Some people are meeting on weekly one-on-ones and like helping them through it. Some people like treatment coordinators work with their doctors and they review treatment cases every single week. But if you can laser focus each one of them, but it's not a would like to have, it's a must have as a culture. And we are a culture of we hit our outcomes consistently and we don't miss those. We don't have to be perfect, but that's what we track and measure by.   That's how you improve at practice. And then all the other noise goes away because me as a team member, I'm not trying to compete for what I think is most important. You've helped me know and we've aligned and we've agreed. And I know what's going to be the outcome if I choose not to. And then everything else kind of falls into place. As a front office team member, there's a lot to do. But I think just giving one or two really helps streamline that.   speaker-0 (16:56) So like what I hear you saying is that if it's important to you as the owner, you've got to.   make it important to the team as well. And that's by discussing, making it a focus. Yet, I find that a lot of practice owners are very scared, and I don't know if scared is the right word. Maybe fearful of ⁓ pressing too many buttons up there. know, like upsetting people, over-asking, asking too many things. I mean, do you think that practice owners need to have a mindset shift around the leadership that comes with the front office?   speaker-1 (17:29) I think it's a...   I don't know, like it's almost like a family motto and it's a team motto. Like we all work and contribute and each of us is part of this bigger whole. And so like if Dr. Etch does not diagnose enough dentistry for us, like that's a broken part in our whole like wheel. And I need to be as a team member able to count on Dr. Etch to be on time for our patients and to diagnose enough treatment for us. Like that's his part of our puzzle. And if he doesn't do that, I need to hold him accountable. And so it's not a Dr. Etch's   like top dog supervisor, we're all part of this to make a hole and we all need to be able to have like go to five dysfunctions of a team. Like how can we have more healthy debate and call each other out? ⁓ I love thinking of sports analogies where like they want to win. We all know what like win on the scoreboard looks like and I can only imagine like, could you imagine like we'll just use the Chiefs. I like everybody knows the Chiefs like right now. So like could you imagine Patrick Mahomes?   Like someone doesn't block for him and he gets completely smashed and he's like, Hey coach Reed, could you please tell the team to tell them to block? It would be ludicrous. Like Paul, you even laugh about it because it's so ridiculous. Instead in the moment he's like dudes block for me. Like I'm not, we're not going to win if you don't do your job. But yet in the dental office, we don't see ourselves in that way of being able to call each other out when we're not, we're not doing our part of the puzzle to win on the team. And so I think doctors, I think that's the mindset.   mindset shift of you should be able to hold them accountable just like they should be able to hold you accountable and if we see it, a lot of times I like these KPIs to be up on a board where it's visible and it's either green or red and my name's on it and I know that I've got to contribute and we look at this whole family aka your practice every week and are we green or are we red? Did Dr. Etch hold up his end of the deal? Did I hold up my end of the deal? Did our other person hold up their end of the deal? And when you start to see that,   It's like a sports team and we say we have this scoreboard to know if we're getting the W at the end of the day or if we're getting the L and we have to call each other out when we're not. Yes, we're here to help, but we also are a team of outcomes over activity and a team of ownership mindset where I own that and I make sure that I'm blocking for you so you can like go and win the touchdown. But all of us are winning collectively together. We don't just have a superstar all star. It's a collective effort. So I think.   Yes, you can be concerned, I think doctors, you push buttons when you come up and you're like, who's filling my schedule? Rather than maybe you hang out and just listen for a minute and hear how things are going, that you could then take that into coaching in the future. ⁓ You are always praising good behavior, but you have a clear scoreboard. It's like you don't have to go up there. But if we're missing the scoreboard, then we have conversations more consistently, so it doesn't feel out of the blue. We're able to coach and counsel more often, and that's just part of it. We call each other out in the moment rather than like,   talking around each other, we call each other in the moment.   speaker-0 (20:26) I love like just the idea of that it's a culture piece and you make a part of your culture and it's more like macro level. It's like we're looking like, like you mentioned, the outcomes over the activity. ⁓ if, if I'm a doctor and I'm listening to this podcast right now and I'm like, yeah, that sounds great in theory, but that would never work in my office, not with my personnel and not with my team. They wouldn't take that sort of constructivism or that, that feedback and they wouldn't have that, that team attitude. And I deal with this a lot with coaching clients and I'm sure you do as well.   It's a culture change that's required, but it could make the owner's life so much easier if we just only had to focus on the outcomes and not so much micro things. How would you suggest a doctor maybe have this conversation with their front office team to say, like, I want it to be more like this. This is what my vision is for this. Help me get to this point. Like, what do you think that would sound like?   speaker-1 (21:22) Yeah, and I do love this. This is why we coach like doctors and teams. This is why we come in because sometimes an outside voice is easier than an inside voice, right? Like I get it. It's scary for me. This is why like know yourself and be free. And if you're not the one that's like I'm good at setting a vision, but like holding lines like this is not my jam rock on like you need a good pair to you. That's a great office manager who's really good at communicating this and getting a team on board. So I think like sometimes doctors show they've got to be   the producer, the diagnoser, the sales, marketing, all the pieces plus the accountability. I'm like, know what you're really good at. Paul, I look at you, you're an amazing visionary, you're really talented at dentistry, you're great at culture, and your office manager was kick a next to you. She did so good at holding pieces together and you would bring in training to give her support so they could grow to the next level.   You are like you're like I'll kind of do it, but like that's not who I am. I'm the same way I've got an operations person next to me and can I do it? Yes, but is that my zone of genius? No, and that doesn't mean we abdicate and we're like, well just because I don't like it don't do it, but I think like if you're really good at this then rock on and do it.   But doctors, we need a vision of where you're going. And that's your main thing that we need from you of like, what does this look like? Where are we headed and why? Like what's the lighthouse on the hill that we can all rally behind? And then we need a really good like leadership team or office manager next to us. And every time I talk to doctors about joining us in consulting, my first question is like, great, what are your issues, problems? Like tell me about your practice and who's your implementer next to you. And if they don't have a strong OM next to them, I know that that's 90 % of their problems. So we need to fill that seat next to them because   a good yin and yang, Paul you know this just like I do, they need to be that accountability person. You're drilling and filling, but then that becomes part of our culture and I think if you've never been this way, a good way to take this into action is like let's have a team like state of the company or like next vision or whatever you want to call it, but like this is how we've been operating.   And this is where we're moving to and this is why and this is how it's going to make all of our lives easier. And I understand that it's going to be a little jostly and hey, so maybe you hire a coach or consultant that's going to help with that. Maybe you and your office manager rally. But I have found and I have seen that a lot of times having somebody outside can help. Like Paul, that's why you hired us is because like we needed an outside voice even though we were saying the same thing.   to come and I love all of our consultants, we've been team members, we've been in the front office, like we've been there, done that, done it successfully to really empathize and understand. But I think it's gotta be a, is where we've been, this is where we're going, this is why. And if a doctor were to say, that's not my team, they won't relate to that, I would say, look at you first and say, like, choose your heart. If your team's that way, like, do you really wanna move into this next layer? Like, how bad is that pain?   Because if you're not willing to do this, your team's not going to follow you either. But you are the culture setter of your practice. So what you tolerate, it's not what you say, it's what you tolerate. And so that is truly your standards of the practice. So I would say it's also a, you got to have like a little like conversation with you in the mirror of, I really willing to change my culture? Am I really willing to go through the like, there is a chasm you've got to cross.   But the other side is truly beauty and it does work and teams do actually thrive if they know how do I get my win? What does my doctor truly want from me? And teams genuinely do want their doctor to thrive. Like that's why they're there. So I think you have to be committed to holding that line, to driving that vision, to having the uncomfortable conversations and making them comfortable and having a really good person next to you. It can be a DA, it can be an OM, it can be a hygienist.   But I think a lot of times having two voices that move it forward oftentimes are easier. But doctors, you've got to be a really strong lighthouse on the hill. And you've got to be committed. And you're willing to go through the effort to change a culture. ⁓ Culture doesn't happen overnight. Culture is a slow burn that takes a while to turn. ⁓ But I think it's like the Titanic. You don't think it's moving. But then when you look up, it has made progress, even though it didn't feel like it. And I think that that's the same with culture.   speaker-0 (25:35) Do you feel that, I mean, it's almost like, and I see this with my clients, is that they're focusing on the wrong area. Like, we're looking at, someone might reach out to you and say, hey, my front desk, I want them to do this, they're not doing this. I want them to do this other thing. They dig their feet in, they say no. I mean, can you tell the story of a recent client that you worked with that maybe came in and was pointing a lot of fingers, but really, it just needed to look in the mirror?   speaker-1 (26:01) Yes, this happens often. And I think it's like a whack-a-mole. And I think that that's why people do reach out for coaching. I think that they recognize that I'm spinning all these tops and I just don't know where I need to go. And it's like, great. So a recent client that I would say they were so obsessed about their hygiene department and they were trying to run around. They're like, we need to fix this, we need to fix that.   And I was like, actually what you're saying with all these words that you don't realize is you just want more profitability. You're stressed out of your mind. So you're going after all these different things when we just need to get your profitability dialed in. We need to figure out like where are we cash bleeding and fix that issue because your hygiene department probably only needs like a small uptick, but you're after that. You're after this person, you're after this, but your real main problem is your cashflow low. Like that's it. And that's a you thing. That's a you not knowing business. That's a we need to fix that.   And then we look at which systems do we need to implement or which department do we need to go attack that's going to actually fix that problem for you. And so I think so many times people want to, like we hear podcasts, right? So it's like, okay, I'm taking notes today. I'm going to go check in on all these KPIs. But sometimes like something I love about how we consult is a lot of consulting companies like ABCD, you got to do that. And for me, I look at, all right, what are we already doing really well?   what is the true pain point of the practice and what's the one, two or three things that are very easy changes that are going to exponentially get you out of the problem you're in and move you forward. I might have a set way that I want you to say a phone script. I might have a set way that I want your case acceptance to go but those might not be the root issue and the root issue might be you as a leader need to get us a vision. I will tell you Paul, we had a mastermind in person and people were like complaining like my team's not bought in, my team's not bought in and I was like all right guys, I just have a quick question.   If I were to walk into your practice today, how many of you like talk to your team, you're not allowed to give them influence. How many of them could tell me where we're going and like where we're headed in the next five to 10 years? They did not raise their hands. And I was like, that's your problem right there. You have not given this team where we're going, why we're going. And so they're just rowing their own little boats over here thinking they're doing the most important thing versus I'm headed towards this. This is my number. This is how I win. And you gave them that clarity.   and you looked in the mirror first and got the vision. So I say, this is twofold. There was one of, you need to give the vision to your team. You need to have the clarity of where you're going. And second, instead of playing whack-a-mole and like trying to fix every little thing, what's our true root problem that we need to solve? And if things are going good or like mostly good, let's go after the fastest, easiest levers. Like people are like, I need more profit or production. I'm like, okay, what are the easiest, fastest ways? Increase our production, increase our collections, decrease our spending. Production.   diagnose more, close more cases, look at our block scheduling and look at our hygiene. Like those are like your simplest easiest ways and make sure like our schedules fill to goal. Like that's really there's not a lot that we have to do that I think we sometimes over complicate when we could simplify and make it a lot easier. And I think that that's probably the whole message of this of there. I think it's actually a lot easier to get to where you're trying to go. I just think like go all the way back to the beginning.   It's like my car is making this sound and I don't know how to fix it. So I'm going to try the spark plugs. I'm going to try the brakes. I'm going to try the da da da. When really all you needed to do was just like fill it up with gas. So just finding that simple piece I think is where people, it's hard because they don't know. So they're going to play whack-a-mole rather than give me the vision, get the numbers dialed in and let your team thrive in those departments.   speaker-0 (29:39) I couldn't agree more. I love that you said that. I think that's going to be so useful for so many people to hear. Talk about what the Dental A Team is up to this spring and how people can reach out to you if they want to learn more.   speaker-1 (29:51) Yeah, we are always like, we're just here to help. So we do doctor and team training, we do virtual and in-person. We have in-person masterminds, which are super fun for doctors to get connected. And I didn't like to be the owner that like, I go get rallied and then my team doesn't. So I'm really big on like, let's rally you and your team so you don't have to try this. Like, got super pumped on the podcast, but like, hey, OM, could you go listen to this podcast and do your job better?   So we do a good job of blending for people. so, yeah, in February we're in person and then in April we're doing our master, our summit. So we always do a summit. And if you guys tell us that you heard about it ⁓ on Pulse, definitely you will get ⁓ a VIP ticket, but that's going to be on April 24th. It's a four hour CE. It's our amazing summit. Head on over to TheDentalATeam.com or you can email us Hello@TheDentalATeam.com I'd love to have you there.   But yeah, if you're like, gosh, I just need help. We do like a full practice like autopsy with you and like, hey, let me just give you some free advice. Let us help you out. But yeah, anyway, we can help you and your team streamline. So doctors can be amazing doctors and CEOs. Teams can level up to their highest potential and we do it together. Conjecture like Paul, Paul's an amazing doctor. Like talk to him about like doctor mindset. I don't know how to tell you how to do a fill. Like that's Paul's world, but how to get your team on board and how to rally with you and support you in the life you deserve. That's what deadly teams about. And   I would say doctors, be selfish. You're CEOs. You should be the dentist. You should be the CEO. You don't need to be the everything. You don't need to know all the front office. are people that can help you and support you. ⁓ But learning that and getting your team the tools, that is your job to do. And I would encourage you to reach out if we can help in any way. And always, always a huge fan of Paul and his group. And listen to Paul. He's got brilliant ideas. He's one of my favorite dentists that I've ever coached. And he's an amazing person at culture and.   of being able to drive people to results. And I think I'm just a good jelly to his peanut butter. We do the team side. do the helping your doctors get to the life they want through team execution.   speaker-0 (31:50) Awesome, Kiera. Thank you so much for coming on the podcast. I always enjoy having you on, love connecting with you and listeners. Go check out Kiera's stuff. She's brilliant. She is a brilliant person and she knows how to get your team on board and to do the things that you want them to do. So thank you so much, Kiera.   speaker-1 (32:06) Thank you. I appreciate it so much, Paul. Thank you so much.   The Dental A Team (32:09) All right, Dental A Team listeners, that was the guest interview that I absolutely loved. And I hope that if there was one idea that stood out to you, don't just agree with it, but actually go implement it this week. And if you need help setting this up in your practice or you need help just navigating or need a friend, head on over to TheDentalATeam.com and I'll be able to help you guys out. Click on the book of call or any way that we can support and serve you. That's what we're here for. That's what we're obsessed with. And as always, thanks for listening and I'll catch you next time on the Dental A Team podcast.

Are you the gatekeeper?When I first started my degree in journalism  and PR, we often talked about the gatekeepers in traditional media… the publisher, the producer, the journalist, the editor. Other people were in charge of deciding if your voice would be heard on television, in print media, or on the radio. The gatekeepers controlled the access.Podcasting allows you to share your story in the most real, deep, authentic way...simply as you. You don't have to wait until someone gives you permission or grants you access.Take this episode as your permission slip to open the gates! Stop being your own gatekeeper. Share your story. More women need to be sharing so we can dream into the possibilities and examples we hear. It matters more than you know.Now, you can watch guest podcast episodes on YouTube HERE!! Contact Info:Julie Berman - Hostwww.womenwithcooljobs.com@womencooljobs (Instagram)Julie Berman's LinkedIn Profile Send Julie a text!!------------------------------------------------------------------------------------------I absolutely LOVE being the host and producer of "Women with Cool Jobs", where I interview women who have unique, trailblazing, and innovative careers. It has been such a blessing to share stories of incredible, inspiring women since I started in 2020.If you have benefitted from this work, or simply appreciate that I do it, please consider buying me a  $5 coffee. ☕️ https://www.buymeacoffee.com/julieberman Thank you so much for supporting me -- whether by sharing an episode with a friend, attending a LIVE WWCJ event in Phoenix, connecting with me on Instagram @womencooljobs or LinkedIn, sending me a note on my website (www.womenwithcooljobs.com), or by buying me a coffee! It all means so much.

This is part 2 of a conversation with Chirag Patel. Chirag is based in London where consults on the ethical and science-based practice of behavior management and training for animals housed in domestic, zoo, and laboratory environments. Chirag earned his BSc (Hons) in Veterinary Sciences from the Royal Veterinary College in London and a Postgraduate Certificate in Clinical Animal Behavior from the University of Lincoln, UK. He is also a certified parrot behavior consultant (CPBC) with the International Association of Animal Behavior Consultants (IAABC). Currently, Chirag is studying for a MSc in Applied Behavior Analysis. In Part 1 we ended with a discussion of marker signals. In many of the demos I've watched of Chirag's training he uses with food without a marker signal. Chirag explained his thinking behind this strategy. In Part 2 we begin with my reasons for the choices I make related to the use of marker signals. The click in clicker training has been referred to in many ways. It is a bridge, a marker signal, a snap shot that captures a precise moment. It is very much a cue. I add yet another metaphor for the role the click plays. It is a gatekeeper. I explain what I mean by that in this episode.

This week we watch Jesus confront the Pharisees who prided themselves on protecting God's law, but in doing so, they kept people from God's love. In their desire for control they acted as gatekeepers for who deserved love and who didn't deserve love. Jesus tears down the barriers that religion builds and throws open the doors of grace. This week we allow Jesus to challenge us by asking who might feel shut out because of how I speak, act or believe and instead of being a gatekeeper what if I became a gateway to mercy instead?  

Having finally perfected the art of fight picking, Phil is now the main host of Heavy Hands.  Don't miss the first Heavy Henka of the year! Join us as we break down the conclusion of this month's outrageous grand sumo tournament: https://www.patreon.com/heavyhands  Predatory instinct: how Max Holloway attacks: https://open.substack.com/pub/facepunching/p/predatory-instinct-how-max-holloway?r=evbq&utm_campaign=post&utm_medium=web&showWelcomeOnShare=false  Heavy Hands merch: https://www.redbubble.com/shop/ap/64577943?asc=u  CONTENTS: 00:00 Intro 00:30 Strickland vs Hernandez 27:31 Neal vs Medic 36:50 Ige vs Costa 52:45 Moreno vs Kavanagh 1:17:40 Vera vs Martinez  

Estrangement. How did you get here? Things used to be good between you and your adult child. But after they got married, communication changed. The tone felt different. Access narrowed. Texts started using wording that felt out of character for your son or daughter. And slowly, it began to feel like you were no longer relating directly to them. You know it's ultimately their choice… and still, something doesn't quite add up. In this episode, we talk about gatekeepers — a dynamic many estranged mothers sense but don't know how to navigate. Come in and listen. Is your family estrangement being driven by a gatekeeper? Let's talk about it. . Next Steps: 1) Apply for your FREE consultation to talk to Jenny 1:1. Find out the exact path forward to feeling better and greatly increasing your chances of getting your son or daughter back in your life. And learn how estrangement coaching can get you there: www.theestrangedmomcoach.com/schedule    ⬇️ 2) Access your audio meditation to help you cast your anxieties and worries about estrangement at the feet of Jesus: https://www.theestrangedmomcoach.com/meditation   ⬇️ 3) Join the free Facebook support community for Christian estranged mothers: https://www.facebook.com/groups/christianestrangedmothers    ⬇️ 4) Download Your Free Guide Of What To Do When Your Adult Child Estranges: https://www.theestrangedmomcoach.com/child-estrangement-next-steps  . Client Reviews… ⭐⭐⭐⭐⭐  Jenny's teachings have produced results reconnecting me with my estranged daughter I cannot express enough gratitude for the incredible support and guidance received in the most tragic time of my life from coach Jenny Good. Her faith, compassion, understanding, dedication and display of radical love has truly been life-changing for me. I was so overwhelmed with feelings of confusion, guilt, and sadness. I felt lost and didn't know how to navigate through the emotional turmoil I was experiencing. However, from the very first call, Jenny created a safe and non-judgmental space for me to share my details. Her ability to listen attentively and empathize while helping me understand a different way of thinking is truly remarkable. She understood my feelings and offered tools each session in ways I have not experienced even from therapy. I am forever thankful for the medicine she has poured into me to be the very best version of myself! This has rippled into all areas of life for me. Jenny's teachings have produced results reconnecting me with my estranged daughter! Thank you for being the vessel of unwavering faith & love that so many of us could benefit from, estranged or not. A true Godsend.  - Melinda Wyman . ⭐⭐⭐⭐⭐ I am living a truly happy life, and I reconciled with my son  Having a coach and mentor who is rooted in Christ is very important. I've experienced so much inner healing with Jenny as my Coach. I am living a truly happy life, and I reconciled with my son! I feel empowered to continue stepping into my full power as a mother and to live a life where my children matter, but they don't determine my worth. I am me again. - Carol Adams

Hey Voices from the Bench community! Jessica Love here, sending a shoutout from Utah! If you're passionate about creating natural, beautiful smiles—but want to simplify your workflow without sacrificing aesthetics—this is for you. I'm honored to be part of Ivoclar's development team introducing a powerful new stain and glaze system featuring Structure Paste, IPS e.max Ceram Art. Create stunning depth and lifelike color in as little as one firing. Let's continue to innovate, simplify, and create meaningful change—one smile at a time. Elvis actually made it down to the exhibition halls this year — and hyperDENT from FOLLOW-ME! Technology was everywhere. Booth after booth, people were talking milling strategies, templates, and workflows. It felt like a full-on CAM takeover. Their Milling Roadmap scavenger hunt had attendees bouncing between Axsys, Imagine, D.O.F., and Roland collecting stamps like responsible adults… Responsible adults chasing a bright orange folding electric hyperDENT scooter. That's what we love about the FOLLOW-ME! team — world-class CAM engineers talking microns and validation protocols one minute, then ripping around Lab Day the next. Serious about precision. Not too serious about themselves. Big shoutout for bringing the brains — and the electric horsepower. Come see and talk to Elvis and Barb at all these amazing shows in 2026* Dental Lab Association of Texas Meeting in Dallas Apr 9-11 https://members.dlat.org/ exocad Insights in Mallorca, Spain Apr 30 - May 1 https://exocad.com/insights-2026 This week we finally get Jay Collins to stop dodging Elvis long enough to sit down and share one of the wildest journeys in dental lab history. From a family split between union steamfitters and dental technicians in Philadelphia to surviving “The Great Brotherly Lab War,” Jay's story is packed with grit, loyalty, and a whole lot of Irish Catholic chaos. What started with an uncle drafted into dental technology during Vietnam eventually turned into a multi-generation lab legacy—and Jay swearing he'd never get into teeth… only to build a powerhouse anyway. After the 2008 crash wiped out his construction business, Jay bet everything on selling outsourced restorations door-to-door, sleeping in his car, showering at the gym, and cold-calling hundreds of offices a week. What followed was the development of his unapologetically bold, psychologically savvy sales approach—what he calls being “aggressively calm.” From pushing doctors to “no,” to matching their energy toe-to-toe, to walking into offices as “the lab” and walking out with cases in hand, Jay breaks down the mindset shift most lab owners desperately need: sales isn't optional, and it definitely isn't accidental. Now leading multiple lab locations under the brilliantly simple name thedentallab.net, Jay shares hard truths about growth, mergers, firing abusive clients, and why cutting your sales department in tough times is the worst move you can make. If you've ever struggled with prospecting, scaling, or standing your ground with doctors, this episode is packed with practical strategies, hilarious role-playing, and a reminder that confidence—backed by accountability—wins every time. At Canadian Dental Labs, Icortica has become a cornerstone of how we operate—giving us at-a-glance visibility into performance, helping us focus our efforts, spot opportunities early, and solve problems before they grow. It takes the guesswork out of decision-making and shows us what to do next. Plus, the Icortica team is incredibly responsive and feels like a true partner in our success. If you're serious about growing your business and understanding your customers better, Icortica can get you there. Learn more at icortica.com/voices — Icortica, helping dental labs grow. Join us at exocad Insights 2026, happening April 30–May 1, 2026, on the stunning island of Mallorca, Spain. This two-day event features powerhouse keynotes, hands-on workshops, live software demos, and top-tier industry showcases—all in one unforgettable setting. Barb and Elvis will be on site bringing you exclusive interviews, plus don't miss the Women in Dentistry Lunch, celebrating career growth, wellbeing, and the real stories shaping our profession. And of course, cap it all off with the legendary exoGlam Night under the stars. Tickets are limited. Visit exocad.com/insights-2026 and use code VFTBPalma15 for 15% off.Special Guest: Jay Collins.

Masterpiece Podcasts: Collection of Chinese Classic Novels

Margo is joined by award-winning PR strategist, community builder, and host of the Small Business PR Podcast, Gloria Chou. Known for disrupting traditional PR by helping creatives, founders, and small business owners land top-tier media using AI tools instead of big budgets or insider connections. In this episode, Gloria joins Margo to unpack how PR now fuels AI search visibility, why press and podcasts act as modern trust signals, and how artists, makers, and small brands can use accessible tools like ChatGPT and Perplexity to pitch with clarity, credibility, and relevance. Margo and Gloria discuss: Why visibility—not talent—is often the biggest hurdle for creatives Reframing PR as relevance-driven storytelling (not self-promotion) Gloria's CPR Method: Credibility, Point of View, Relevance How cold pitching works—even without contacts or PR experience Using AI tools to research angles and draft pitches in minutes Press & podcasts as critical trust signals in AI-driven search The shift from traditional SEO to AI shopping and discovery Mindset shifts to overcome imposter syndrome and "not newsworthy" thinking Connect with Gloria: Website: www.gloriachoupr.com Instagram: @gloriachoupr YouTube: @smallbusinesspr LinkedIn: in/gloriaychou Connect with Margo: Website: www.windowsillchats.com Instagram: @windowsillchats www.patreon.com/inthewindowsill https://www.yourtantaustudio.com/thefoundry

Kennst du das? Du lieferst ab, übernimmst Verantwortung, arbeitest hart, bist loyal. Und dann bekommt jemand anderes die Beförderung. Karriere ist nicht nur Kompetenz. Karriere ist auch Sichtbarkeit, Timing, Macht, Netzwerke – und manchmal schlicht Glück.In dieser Folge #437 spreche mich mit Saruul Krause-Jentsch. Saruul ist Head of Podcast Central Europe bei Spotify, Speakerin und ist nach ihrer Zeit als Gründerin seit Jahren selbst in einer anspruchsvollen Führungsrolle.Saruul hat als Speakerin auf unserem Female Leadership Summit in Hamburg einen Satz gesagt, der im Raum hängen blieb: Es gibt ungeschriebene Regeln – und wenn du sie nicht kennst, kannst du sie auch nicht navigieren.Wir sprechen darüber, warum Frauen häufig glauben, sie müssten nur „alles richtig machen“, um belohnt zu werden – und warum dieses Narrativ uns im Weg steht. Denn in vielen Organisationen gilt: Gute Arbeit reicht nicht. Du musst auch darüber sprechen. Du musst sichtbar sein. Und du musst strategisch verstehen, wann Chancen verteilt werden – und wie du „top of mind“ wirst.Saruul teilt außerdem einen Karriere-Satz, der unbequem ist, aber oft stimmt:„Be nice to your boss or leave.“Denn Führungskräfte sind Gatekeeper. Sie können dich fördern – oder verhindern. Und wenn du merkst, dass du an einem Ort nicht wachsen kannst, ist Loyalität keine Tugend, sondern eine Bremse.Ein weiteres zentrales Thema: der Likeability Bias. Saruul spricht darüber, dass Frauen ehrgeizig sein dürfen – aber gesellschaftlich immer noch stärker dafür bestraft werden. In vielen Systemen müssen Frauen gleichzeitig driven UND sympathisch bleiben, um nicht als „zu viel“ abgestempelt zu werden.Und wir sprechen über Mutterschaft: Warum Frauen oft schon Jahre vor einem möglichen Kind anfangen, ihre Karriere zu verkleinern – und warum Sheryl Sandbergs Satz „Don't leave before you leave“ immer noch ein wichtiger Reality Check ist.Diese Episode ist ein ehrlicher Blick auf Karriere, Macht und Strukturen – und gleichzeitig ein Aufruf, die Regeln zu verstehen, um sie später verändern zu können.In dieser Folge sprechen wir über:Karriere-Mythen und ungeschriebene Regeln in Unternehmenwarum Karriere auch Glück, Timing und Marktbedingungen istSichtbarkeit im Job: „Mach Gutes – und rede darüber“strategische Allianzen und Networking ohne BullshitCorporate Politics und der Einfluss von Führungskräften„Be nice to your boss or leave“: toxische Dynamiken erkennenLikeability Bias: warum Frauen doppelt performen müssenPrivilegien reflektieren und trotzdem ambitioniert bleibenMutterschaft als Karriere-Hürde – und als unterschätzte Ressourcewarum eine Firma dich nicht zurücklieben kannKarriere ist nicht fair. Aber du kannst lernen, das Spielfeld zu verstehen – und deinen Einfluss klüger zu nutzen.+++Alle Links und Details findest du hier.Du willst noch mehr? Dann melde dich jetzt bei der Female Leadership Academy 2026 an und gestalte deine Leadership Karriere mit uns.Du brauchst mehr Infos? Melde dich hier zum Newsletter an.+++Keywords: Karriere Tipps Frauen, Karriere Wahrheit, Karriere im Konzern, Female Leadership, Sichtbarkeit im Job, Beförderung, Karriereplanung, Networking Frauen, Unwritten rules career, Likeability Bias, Karriere als Mutter, Mutterschaft Karriere, Boss Beziehung, Karriere Strategie, Power Skills, Soft Power, Corporate Politics, Frauen und Macht Hosted on Acast. See acast.com/privacy for more information.

The Body (Part 1): Where Faith Faces the PhysicalLearning to lead the physical with the power of the Spirit.Over the last few weeks, we've unpacked the Soul—our mind, will, and emotions. We discussed the mind as the Gatekeeper and the will as the Decision Center. Today, I want to turn our attention to the part of us that often gets misunderstood, neglected, or overspiritualized: the body.The body is not separate from our faith. It's not something we simply “put up with” until heaven, and it's definitely not meant to lead our lives either. It is the training ground where we learn to lead the physical with the power of the Spirit.When the Body Becomes LoudFor many believers, faith feels easiest when it stays theoretical—when it lives in thoughts, prayers, or convictions. But the moment faith faces the physical reality of pain, symptoms, or limitations, things change.Suddenly, belief has to move from what we say to what we actually stand on. I was reminded of this in a deeply personal way this past week. As many of you know, I've been recovering from knee surgery for the last eight weeks. It's been a process of learning to "suffer well" and choosing to depend on God's strength when my own physical frame felt weak.I also saw this play out with my mom. She has been walking through a physical challenge—an abnormal lump that brought up a lot of "what if" questions from the enemy. She didn't ignore the situation, but she refused to let a medical report become the final authority over her life.A Testimony: "Only God Could Do This"We attended a healing conference together last weekend. My mom went forward for prayer, expecting a general moment of intercession. Instead, my friend Chad Gonzalez—who had no prior knowledge of her situation—stopped and spoke specifically to her.Read the rest at:https://open.substack.com/pub/litwithprayer/p/the-body-part-1-where-faith-faces?r=5sajy&utm_campaign=post&utm_medium=web&showWelcomeOnShare=true 

Some notes from ALIS 2026

Find out if EDI is still the backbone of scalable freight operations and what happens when you stop penalizing brokers for growth in this episode with our returning guest, Brad Perling of Bitfreighter! Brad shares why their EDI-first freight technology strategy is quietly reshaping shipper integration, automated quoting, and brokerage scalability. Brad and I talk through why EDI remains the most reliable foundation for freight data integrity, how unlimited EDI messaging pricing removes one of the biggest cost barriers for growing brokerages, seamless integration through APIs and RPA across TMS platforms and load boards, and how real-time quoting analytics are driving millions in new revenue for customers. If you're a freight broker or shipper looking to scale without breaking your tech stack or your budget, this conversation lays out exactly why EDI (if done right) is still a competitive advantage in modern freight tech!   About Brad Perling Brad Perling is the CEO and co-founder of Bitfreighter. With over 15 years of experience in the industry and growing 2 successful brokerages, Brad's deep understanding of logistics challenges has fueled his passion for finding better software solutions. He knew there was a need for a disruptive new model in the EDI space and was determined to create it. He has a passion for aviation and enjoys playing hockey and golf while spending time with his wife and 2 kids.   Connect with Brad Website: https://www.bitfreighter.com/  LinkedIn: https://www.linkedin.com/in/brad-perling-5a101655/  

(00:00-6:13) Put em on the glass. The Hyzer House Hooligan isn't happy for a second straight day. What a great mouth horn, Tim. The Gatekeeper of Humor.(6:21-11:54) Some slower Zeppelin. Doug still needs new headphones. Ross Dellenger with an article on topics of CFB that will possibility be tended to after the season wraps up. Week Zero, playing dates for the CFP, date of transfer portal, and spring and summer access periods.(12:04-18:55) The boy is trying. Following through on the deep tease of a gold mine for Doug. 10 STL Dining Trends to watch in 2026. Announcing the winner of day 2 of the Design Aire Heating & Cooling E-Mail of the DaySee Privacy Policy at https://art19.com/privacy and California Privacy Notice at https://art19.com/privacy#do-not-sell-my-info.