Podcasts about product development

Ramya Shastri: When Sprint Goals Are Missing, The Consequences of a Task-Driven Product Owner Read the full Show Notes and search through the world's largest audio library on Scrum directly on the Scrum Master Toolbox Podcast website: http://bit.ly/SMTP_ShowNotes. The Great Product Owner: The Goal Oriented PO Ramya describes a great Product Owner as one who is protective of the team, ensures sprint goals are clearly defined, and consults the team before accepting customer demands. This PO fosters a collaborative environment where the team can thrive and deliver results. The Bad Product Owner: When Sprint Goals Are Missing, The Consequences of a Task-Driven Product Owner A bad Product Owner neglects the importance of sprint goals, focusing only on tasks and requirements. This creates an unmanageable workload for the team, leading to low productivity and confusion. Ramya highlights the value of using analogies, like fitness goals, to help reluctant POs understand the importance of sprint goals. [The Scrum Master Toolbox Podcast Recommends]

How do you make your OKRs truly customer-centric? Our guest today is Jeff Gothelf, a coach, trainer, speaker, and author of five books. You'll learn how to identify and drive results, why cross-functional collaboration is important in determining OKRs, how to get started with OKRs, and more.Podcast feed: subscribe to https://feeds.simplecast.com/4MvgQ73R in your favorite podcast app, and follow us on iTunes, Stitcher, or Google Podcasts.Show NotesWho Does What By How Much – Jeff's latest bookEpisode 137: Lean, Agile & Design Thinking with Jeff GothelfEpisode 273: Publishing Options for Design Books with Louis RosenfeldMeasure What Matters – a book by John Doerr2022 Cleveland Clinic OKRsGet a copy of Jeff's latest bookFollow Jeff of LinkedInVisit Jeff's websiteThis episode is brought to you by Wix Studio — the new web platform for agencies and enterprises. The magic of Wix Studio is its advanced design capabilities which makes website creation efficient and intuitive. Here are a few things you can do:Work in sync with your team on one canvasReuse templates, widgets and sections across sitesCreate a client kit for seamless handoversAnd leverage best-in-class SEO defaults across all your Wix sitesStep into Wix Studio to see more at wix.com/studioInterested in sponsoring an episode? Learn more here.Leave a ReviewReviews are hugely important because they help new people discover this podcast. If you enjoyed listening to this episode, please leave a review on iTunes. Here's how.

Two-time Emmy and Three-time NAACP Image Award-winning, television Executive Producer Rushion McDonald interviewed Joi Mebane She is a trailblazing entrepreneur and beauty educator with over 21 years in the industry. As the visionary behind The Look by Joi, she's crafted signature brow techniques and an innovative beauty line, featuring the popular 60 Second Brow Kit and signature lipsticks.   The Look by Joi is a leading beauty brand founded by acclaimed makeup artist Joi Mebane. Known for its innovative brow and beauty products, The Look by Joi empowers individuals to define their unique look with ease and confidence. Rooted in Joi's artistry and extensive industry experience, the brand offers a curated selection of high-quality, user-friendly tools and cosmetics, from brow kits to vibrant lip colors. At The Look by Joi, we believe in effortless beauty that's accessible to all, with each product designed to enhance natural features. From the runway to everyday, The Look by Joi is transforming beauty routines with expert innovation and a personalized touch.  1. Building The Look by Joi Brand    - Joi's journey from makeup artist to entrepreneur, founding The Look by Joi to empower beauty professionals.    - The creation and success of her 60 Second Brow Kit and signature lipsticks as staple products.   2. Beauty Education and Mentorship    - Joi's role as a beauty educator, with a community of over 10,000 professionals.    - Her mission to teach strategic business and self-care practices that help professionals succeed in beauty and business.   3. Global Inspiration and Product Development    - Joi's travels abroad to source materials and gain inspiration for her beauty line.    - How her global perspective influences product design and enhances the brand's self-care mission.   4. High-Profile Media Features and Bravo Appearance    - Joi's media exposure on NBC, Fox News, and Bravo's *Below Deck Mediterranean*.    - The impact of these appearances on brand visibility and credibility in the beauty industry.   5. Atlanta Fashion Week Partnership    - The Look by Joi's exclusive makeup partnership with Atlanta Fashion Week, providing beauty services and brand exposure.    - Joi's approach to leveraging high-profile events like Atlanta Fashion Week to strengthen brand awareness and influence.   6.Balancing Leisure, Business, and Self-Care    - Joi's dedication to incorporating leisure and self-care into business, balancing work with wellness and travel.    - Tips on how other entrepreneurs can achieve similar balance in their careers.   7. Future Growth and Goals for The Look by Joi    - Joi's vision for the brand's growth, upcoming product lines, and new initiatives.    - Long-term goals for expanding her influence in beauty education and product innovation. #SHMS #BEST #STRAWSupport the show: https://www.steveharveyfm.com/See omnystudio.com/listener for privacy information.

Next in Creator Media spoke with Ashley Rudder, Chief Creator Officer, DNY, about how brands need to not just let go of their creative control when working with creators on YouTube and TikTok, but may need to bring this talent in much earlier in the development process to best take advantage of their cultural connections.Takeaways:• The Evolution of Creative Leadership: Ashley Rudder's role as Chief Creator Officer highlights a modern, multidisciplinary approach to creative leadership, integrating brand marketing, social adaptability, and production expertise.• Importance of Authentic Partnerships: Successful creator collaborations move beyond transactional relationships. • Platform-Specific Expertise: Each social platform requires tailored strategies. Brands benefit from working with creators adept at navigating platform nuances to deliver culturally relevant content.• Metrics Beyond Vanity: Meaningful success metrics include post shares, bookmarks, and community engagement, rather than superficial vanity metrics like impressions or EMVs.• Integration into Product Development: Creators' real-time audience insights make them invaluable contributors to product development and go-to-market strategies. • Sustained Creator Relationships: Long-term partnerships with creators foster authenticity and loyalty among their audiences, enhancing the brand's credibility and influence.Guest: Ashley RudderHost: Mike ShieldsSponsor: VuePlannerProducer: FEL Creative

In this episode of Sick Health with Kevin Ban, MD, we explore how military brainwave tech can help you unlock peak performance, focus, and optimal mental health (all from the comfort of home)! Join us, and neuro-tech pioneer Jamie Alders, VP of Product at Neurable shares how this “Fitbit for your brain” can unlock untold benefits in your life. This brand new solution can keep you away from the clinic, wires, gooey glues and more!  Imagine a brain booster that you can use just like everyday headphones!From improving focus and productivity to preventing burnout, we uncover how this technology is transforming our understanding of mental performance. Jamie shares insights into how their device helps users optimize their work periods, identify peak focus times, and take scientifically-timed breaks based on actual brain activity - highly personalized to the user. But this scientific breakthrough isn't just about productivity. We dive into the potentially life-changing medical applications of this technology, from detecting traumatic brain injuries in military personnel to establishing baselines for sports-related concussions. As Jamie explains, "We have a device that can collect orders of magnitude more data than you could get before... having data about your brain for eight to 10 hours a day, every day."This podcast episode reveals:How brain wave measurement technology actually worksThe difference between focus and meditation in your brainWhy timing your breaks matters more than you thinkThe future of neurological health monitoringGroundbreaking applications in brain injury detectionWhether you're interested in optimizing your performance, preventing burnout, or understanding the future of brain health monitoring, this episode offers fascinating insights into how technology is revolutionizing our understanding of the brain.Don't forget to like, subscribe, and share with someone who might benefit from understanding this breakthrough in neural technology.About Jamie Alders:As Vice President of Product at Neurable, Jamie leads Neurable's Product Development, where he is revolutionizing  access to data about your brain and opening up new ways to interact with technology. Jamie graduated from Duke University with a degree in Mechanical Engineering. He designed and launched consumer electronics products at Bose like iPodFollow us on YouTube and leave your comments at: https://www.youtube.com/@SickHealthwithKevinBanMD Connect with Kevin on Facebook: https://www.facebook.com/profile.php?id=61558197731269 Instagram: https://www.instagram.com/sickhealthigsh=MXQ5Y3Q1ZjE0bnZmdQ%3D%3D Threads: https://www.threads.net/@sickhealth Linkedin: https://www.linkedin.com/company/sick-health-with-kevin-ban-md/ Tik Tok: https://shorturl.at/oORXY Contact email: team@sickhealthshow.com Executive Producer: Kevin Ban, MD Production Director, Editor and Producer: Bat-Sheva Guez Graphic designer: Leah VanWhy YouTube SEO: Lighthouse-Digitalmarketing.com Social media: Rebekah Pajak Intern: Nicole Berritto This show's content represents the personal opinions of Kevin Ban, MD. It is not intended to be a substitute for professional medical advice, diagnosis, or treatment, and does not create a physician-patient relationship with Kevin Ban, MD. Always seek the advice of your physician or other health car...

“Big budget energy is about getting more value…” Welcome back to The Marketing Hustle, the podcast that brings you unfiltered stories from start-up Founders of bold brands. This week, your host Lottie chats to the Co-Founder of NICE wine, Jeremy May.  NICE began when two freelancers joined forces to take over the world of canned wine. They went on to become known as the start-up with bold ideas, standing out on the shelves and also in aeroplane magazines. They are a masterclass of big budget energy. Tune in to hear Jeremy chat about their Travis Kelce hoax, what the traits are of the best marketers, and how entrepreneurial spirits form part of their hiring strategy… along with some great facts about wine, of course. Finally… if you enjoy the episode, please leave us a review, it helps more than you know. Now let's get stuck in! Chapters: [02:52] The Importance of Marketing and Distribution [06:07] Building a Strong Marketing Team [08:58] Understanding Marketing Beyond Campaigns [12:08] Product Development and Market Positioning [14:57] Innovations in Wine Packaging [17:49] Consumer Behavior and Market Trends [21:05] Expanding Product Range and Consumer Choices [24:01] Navigating the On-Trade Market [32:19] Brand Identity and Product Innovation [34:15] The Role of Marketing in Product Launches [36:36] Big Budget Energy: Maximizing Impact with Limited Resources [40:43] Adapting Marketing Strategies in Uncertain Times [48:12] The Traits of Successful Marketers [51:01] Collaborative Brainstorming for Creative Ideas [54:43] Learning from Failures in Marketing Campaigns [58:48] The Future of AI in Marketing *This episode is brought to you by Be A Bear, find out how you can grow your audience here: https://www.beabear.co.uk/  Connect with Jeremy: https://www.linkedin.com/in/jeremy-may-0a645614/ Explore NICE: https://nice-drinks.co.uk/ Follow your host, Lottie Unwin: https://www.linkedin.com/in/lottie-unwin-she-her-7b577742/ Discover Up World + Brand Hackers: https://up-world.co/

All Aboard the AI Hype Train!!!Product management is DEAD! It died facing a high-noon showdown with AI, and the rumors of it's demise are spreading faster than a locomotive through the boom-town of Silicon Valley.In this episode of Arguing Agile, Product Manager Brian Orlando and Enterprise Business Agility Coach Om Patel try a daring uncoupling of the the AI hype train as they examine Claire Vo's take on whether product management is about to derail.Listen as we navigate treacherous mountain passes following this shiny new engine, exploring: The runaway train of AI expectations vs. realityWhy the "lone ranger" product manager is a dangerous mythNavigating the switchyard of cross-functional collaborationBreaking out of the Silicon Valley echo chamberWhy technical skills are just one car in the product management trainWhat's your ticket to the future of product management say? Drop your perspective in the comments, partner!#AI #ProductManagement #Innovation #TeamTopologies #TechLeadership #ProductDevelopment #AgileCoaching= = = = = = = = = = = =Watch on YouTube= = = = = = = = = = = =Subscribe on YouTube:https://www.youtube.com/channel/UC8XUSoJPxGPI8EtuUAHOb6g?sub_confirmation=1Apple:https://podcasts.apple.com/us/podcast/agile-podcast/id1568557596Spotify:https://open.spotify.com/show/362QvYORmtZRKAeTAE57v3= = = = = = = = = = = =Toronto Is My Beat (Music Sample)By Whitewolf (Source: https://ccmixter.org/files/whitewolf225/60181)CC BY 4.0 DEED (https://creativecommons.org/licenses/by/4.0/deed.en)

In this episode, Bill Kennedy interviews Tanmai Gopal, co-founder and CEO of Hasura, discussing the evolution of San Francisco post-pandemic, the innovative approach of Hasura, and the importance of data security and access. Tanmai shares insights from his academic journey, including his experiences with internships and his master's degree in computer vision, culminating in a fascinating project involving drones. In this conversation, Tanmai Gopal discusses his journey from academia to entrepreneurship, focusing on his experiences in building a consulting business and transitioning to product development. He shares insights on the evolution of GraphQL, the challenges of navigating business decisions, and the future of data access in the context of AI and emerging technologies. The discussion highlights the importance of understanding data modeling and the need for innovative solutions in the software industry.00:00 Introduction03:15 What is Tanmai Doing Today05:45 Understanding Hasura's Approach to APIs14:40 Pre-Hosted Solutions in Hasura22:26 First Memories of a Computer35:40 Favorite Classes During University49:25 From Consulting to Product1:01:35 Extending GraphQL 1:10:30 Competitors of Hasura1:18:40 Data Privacy1:22:10 Contact InfoConnect with Tanmai: Linkedin: https://www.linkedin.com/in/tanmaig/X: https://x.com/tanmaigo?lang=enMentioned in today's episode:Hasura: https://hasura.io/GraphQL: https://graphql.org/Want more from Ardan Labs? You can learn Go, Kubernetes, Docker & more through our video training, live events, or through our blog!Online Courses : https://ardanlabs.com/education/ Live Events : https://www.ardanlabs.com/live-training-events/ Blog : https://www.ardanlabs.com/blog Github : https://github.com/ardanlabs

1/

In this episode of Wheelchair Nerds, we dive deep into the world of product development with Dan Debrah, Vice President of Research and Development at Permobil. Join us as we explore the journey from concept to creation, uncovering how Dan and his team generate ideas, gather invaluable market research, and navigate the challenges of bringing products to life. 

How to validate ideas faster?How to get an MVP right – best practices.Proven strategies for faster MVP development Speakers:– Todd Yates, Chief Technology Officer at Transact– Erika Rice Scherpelz, Head of Engineering at Sourcegraph– Mahmoud Galal, Software Engineering Manager at KitopiHost: Dominika Szelkenbach, Consulting Practice Lead at NetguruThis session was a part of Disruption Forum Engineering Horizons.

In this What's Next with Aki Anastasiou interview, Ryan Switala discusses the technologies Liberty is using to improve its life insurance products. Switala is the Head of Simple Life Solutions at Liberty and has worked at the company for 18 years — beginning as an Actuarial Specialist in 2006. He then held several notable positions at Liberty before being appointed to his current role — including Head of Risk for Product Development, Actuarial Consultant for Group Reinsurance, and Chief Specialist for Partner Integration. In this What's Next interview, Switala discusses how Liberty's digital transformation strategy is helping make life insurance more accessible to its clients. He unpacks the powerful technologies that are being used to streamline the customer journey and make life insurance easier to understand for the average South African. Switala then expands on Liberty's use of AI and machine learning to deliver ever-evolving, highly personalised client experiences. He concludes the interview by sharing the most exciting digital innovations that Liberty plans to incorporate into its life insurance offerings.

Scott MacKenzie interviews Justin Sirotin from OCTO, a company that designs complete customer experiences across various industries. OCTO, named after the octopus's adaptability, has been in operation for 15 years. Justin, with nearly 30 years in industrial design, emphasizes the importance of usability in technology. They discuss the challenges of integrating edge technology with utility grids to improve efficiency and user experience. Justin highlights the need for seamless, user-friendly designs to avoid user frustration. They also touch on the rapid prototyping and testing approach of companies like SpaceX and Formula One, which emphasize real-world testing and continuous improvement. Action Items [ ] Reach out to Justin on LinkedIn or through the Octo website to discuss further. Outline Introduction and Purpose of Industrial Talk Scott MacKenzie introduces the Industrial Talk podcast, emphasizing its focus on industry professionals and their innovations. Scott highlights the platform's mission to amplify messages and support industry professionals worldwide. He expresses his admiration for industry professionals who solve problems and make the world a better place. Scott mentions the ease of getting involved with Industrial Talk for those interested in amplifying their message or technology. Introduction of Justin and OCTO Scott introduces Justin and his company, OCTO, and explains the company's name and its origin. Justin shares the story behind the name OCTO, which was inspired by the adaptability of an octopus. Justin explains that the name OCTO is a shortened version of octopus, as the full name was unavailable. Scott and Justin engage in a light-hearted discussion about the name and its superhero-like connotations. Justin's Background and OCTO's Services Justin provides a brief overview of his background in industrial design and his nearly 30 years of experience in the field. He explains that OCTO designs complete customer experiences, including pre-product, product, and post-product services. Justin mentions that he has started several companies and also teaches manufacturing techniques at the Rhode Island School of Design. He emphasizes the importance of embracing constraints and building market-validated creative solutions. Challenges and Insights from Teaching Industrial Design Justin discusses the challenges of staying current in the industry and the impact of his students on his learning. He shares his experiences visiting factories in Vietnam and China to stay informed about production processes. Justin highlights the generational differences in attitudes towards consumption and the environment. He emphasizes the importance of efficiency and zero waste in the manufacturing sector. The Role of Design in Technology and User Experience Scott and Justin discuss the importance of designing technology that is user-friendly and meets the needs of end-users. Justin explains that OCTO's role is to connect technology with user needs, ensuring seamless integration and usability. They discuss the evolution of the design field from being seen as just making things pretty to being integral to functionality. Justin shares an anecdote about a client who believed that complex software should be hard to use, illustrating the shift in thinking. Designing for the Utility Grid and User Experience Scott and Justin delve into the complexities of designing for the utility grid and the challenges of integrating new technologies. Justin explains the role of OCTO in...

In episode 52, Breanna Selsor, a Marketing and Communications Intern at Iowa State University is joined by Alana Corwin and Jamal Beavers Jr. as part of the Young Innovators Series. Alana and Jamal dive into their journey in creating Apricity and their goals for the future of their company. Thank you for listening!

Global Product Management Talk is pleased to bring you the next episode of... Product Mastery Now with host Chad McAllister, PhD. The podcast is all about helping people involved in innovation and managing products become more successful, grow their careers, and STANDOUT from their peers. About the Episode:  In this episode, I interview Mike Hyzy, Senior Principal Consultant at Daugherty Business Solutions. He explains how to conduct an AI-powered design sprint that transforms product concepts into clickable prototypes in just hours instead of weeks. Using a custom ChatGPT model combined with collaborative team workshops, product teams can rapidly move from initial customer insights to validated prototypes while incorporating strategic foresight and market analysis. Key Topics: Strategic foresight approach to product development, focusing on customer needs 2-5 years aheadTriple diamond decision framework for analyzing problems, customers, and marketsIntegration of team collaboration, AI assistance, and external validationRapid wireframe and UI design generation using ChatGPT and DALL-ECreation of interactive prototypes using CodePen for immediate testingCustom AI model prompts and best practices for design sprint facilitationEarly go-to-market strategy integration in the product development processPractical implementation of AI tools to accelerate product innovation

At Mondoro, we believe design goes beyond borders, crafting products that speak to a global audience. As a company creating home decor and furnishings for international markets, we embrace trends that resonate across cultures and continents. In this episode of #GlobalTradeGal, Anita explores how interconnectedness and rapid communication have transformed design into a global language.

SummaryIn this episode of BizNinja Entrepreneur Radio, host Tyler Jorgenson sits down with Jonny Locarni, founder of Magic Cactus, a unique brand creating alcohol alternatives infused with hemp and functional ingredients. Jonny shares his entrepreneurial journey, starting with hustling as a young adult, to creating a product that fills a distinct market gap. He discusses the challenges of developing a commercially viable drink that provides the social experience of alcohol minus its negative effects. Tyler and Jonny dive deep into navigating regulations, consumer insights, and how Magic Cactus offers a mindful and inclusive drinking alternative to alcohol.Jonny explains the evolution of Magic Cactus from early formulation hurdles, like using coconut water, to finding the perfect balance with cactus water, which aligns with their brand's Arizona roots and offers health benefits without excess sugar. The two also explore the complexities of creating a brand that appeals to a broader audience, focusing not just on sobriety but on mindful consumption, showing how Magic Cactus is changing the way people approach social drinking. They also discuss the brand's vision for the future, regulatory hopes, and how they aim to expand their footprint.The episode closes with a reflection on building a brand that goes beyond selling a product by creating a community and reshaping perceptions around alcohol alternatives. Jonny's story highlights how branding, purpose, and market timing are pivotal to success. Listeners are encouraged to check out Magic Cactus and join their mission of creating a non-toxic and socially engaging drink alternative. Visit magiccactus.com to learn more. TakeawaysEntrepreneurial Spark & Innovation: Jonny Locarni's journey demonstrates how early business ventures can ignite a lifelong passion for entrepreneurship, leading to innovative solutions such as Magic Cactus, which offers a unique, healthier alternative to traditional alcoholic beverages.Formulation Challenges & Branding: Developing a commercially viable product requires overcoming multiple hurdles, including consumer taste preferences and nutritional balance. Magic Cactus's pivot from coconut water to cactus water shows how adapting to feedback can lead to better product alignment and brand storytelling.Mindful Drinking & Market Positioning: Magic Cactus isn't solely about promoting sobriety but encouraging mindful consumption. The brand's inclusive approach aims to cater to a broad spectrum of consumers, offering an alternative that bridges the gap between traditional drinking and healthier choices, while donating 10% of profits to support substance abuse treatment initiatives.

Mariah Parsons hosts Rebecca 'Becca' Mijares, Founder of Romp Stomp, a brand that creates easy-to-wear shoes for toddlers. Becca shares her entrepreneurial journey, starting with a crappy website and Facebook ads during the early COVID-19 days. She discusses the rebranding from Memoir Kids to Romp Stomp, emphasizing bold colors and fun designs. Becca highlights the importance of customer feedback, especially via Instagram DMs, and the role of email and SMS marketing in retention. She also mentions the challenge of expanding their product line to serve customers longer. Becca recommends resources like Twitter and in-person networking for founders. Episode Timestamps: 2:16 Becca Mijares's Background and Romp Stomp Brand Introduction Becca Mijares introduces herself and her brand, Romp Stomp, which makes shoes for toddlers that are easy to wear and protect their feet. She shares her entrepreneurial journey, mentioning her father's influence as a violin maker and entrepreneur. Becca explains the inspiration behind Romp Stomp, stemming from her sister's dislike for wearing shoes as a child. She describes the initial stages of her brand, including creating a crappy website and running Facebook ads to test the market. 3:46 Challenges and Learning in Product Development Becca discusses the importance of starting with a minimum viable product and iterating based on customer feedback. She emphasizes the value of customer feedback in improving the product and making it more appealing to parents. Becca shares her experience with rebranding from Memoir Kids to Romp Stomp to better reflect the fun and bold personalities of toddlers. She talks about the process of choosing colors, names, and brand kits, and the importance of standing out in the market. 4:02 Product Development and Trends Becca explains the balance between being on-trend and meeting customer needs, using the example of checkered shoes. She mentions the importance of small launches to test new designs and gather feedback. Becca discusses her approach to trend prediction, including looking at trending colors and trusting her gut. She highlights the role of social media and Pinterest in finding inspiration for new designs and activities. 4:18 Social Media Strategy and Community Building Becca talks about using Instagram for community building rather than direct customer acquisition. She explains the importance of responding to negative comments and using messaging for detailed feedback. Becca shares her strategy for creating valuable content, focusing on quality over quantity. She mentions using tools like Ask the Public to find popular search terms and create relevant content. 30:17 Advertising and Retention Strategies Becca shares her early experience with Facebook ads and the importance of demonstrating the product in ads. She emphasizes the value of showing the problem the product solves and using user-generated content. Becca discusses the importance of testing new ads regularly to maintain performance. She highlights the role of email and SMS marketing in retaining customers and providing personalized service. 37:40 Future Plans and Resources for Founders Becca talks about the challenge of serving customers for only a few years due to the rapid growth of toddlers' feet. She mentions the goal of expanding the product line to serve customers longer. Becca shares her approach to consuming content and making decisions based on what's best for her business. She emphasizes the value of in-person events and networking for problem-solving and finding solutions. 43:08 Final Thoughts and Promotions Becca mentions upcoming Black Friday sales and encourages listeners to sign up for email updates. Mariah thanks Becca for sharing her insights and experiences. The episode concludes with Mariah expressing her excitement for the audience to hear the conversation.

The full schedule for Latent Space LIVE! at NeurIPS has been announced, featuring Best of 2024 overview talks for the AI Startup Landscape, Computer Vision, Open Models, Transformers Killers, Synthetic Data, Agents, and Scaling, and speakers from Sarah Guo of Conviction, Roboflow, AI2/Meta, Recursal/Together, HuggingFace, OpenHands and SemiAnalysis. Join us for the IRL event/Livestream! Alessio will also be holding a meetup at AWS Re:Invent in Las Vegas this Wednesday. See our new Events page for dates of AI Engineer Summit, Singapore, and World's Fair in 2025. LAST CALL for questions for our big 2024 recap episode! Submit questions and messages on Speakpipe here for a chance to appear on the show!When we first observed that GPT Wrappers are Good, Actually, we did not even have Bolt on our radar. Since we recorded our Anthropic episode discussing building Agents with the new Claude 3.5 Sonnet, Bolt.new (by Stackblitz) has easily cleared the $8m ARR bar, repeating and accelerating its initial $4m feat.There are very many AI code generators and VS Code forks out there, but Bolt probably broke through initially because of its incredible zero shot low effort app generation:But as we explain in the pod, Bolt also emphasized deploy (Netlify)/ backend (Supabase)/ fullstack capabilities on top of Stackblitz's existing WebContainer full-WASM-powered-developer-environment-in-the-browser tech. Since then, the team has been shipping like mad (with weekly office hours), with bugfixing, full screen, multi-device, long context, diff based edits (using speculative decoding like we covered in Inference, Fast and Slow).All of this has captured the imagination of low/no code builders like Greg Isenberg and many others on YouTube/TikTok/Reddit/X/Linkedin etc:Just as with Fireworks, our relationship with Bolt/Stackblitz goes a bit deeper than normal - swyx advised the launch and got a front row seat to this epic journey, as well as demoed it with Realtime Voice at the recent OpenAI Dev Day. So we are very proud to be the first/closest to tell the full open story of Bolt/Stackblitz!Flow Engineering + Qodo/AlphaCodium UpdateIn year 2 of the pod we have been on a roll getting former guests to return as guest cohosts (Harrison Chase, Aman Sanger, Jon Frankle), and it was a pleasure to catch Itamar Friedman back on the pod, giving us an update on all things Qodo and Testing Agents from our last catchup a year and a half ago:Qodo (they renamed in September) went viral in early January this year with AlphaCodium (paper here, code here) beating DeepMind's AlphaCode with high efficiency:With a simple problem solving code agent:* The first step is to have the model reason about the problem. They describe it using bullet points and focus on the goal, inputs, outputs, rules, constraints, and any other relevant details.* Then, they make the model reason about the public tests and come up with an explanation of why the input leads to that particular output. * The model generates two to three potential solutions in text and ranks them in terms of correctness, simplicity, and robustness. * Then, it generates more diverse tests for the problem, covering cases not part of the original public tests. * Iteratively, pick a solution, generate the code, and run it on a few test cases. * If the tests fail, improve the code and repeat the process until the code passes every test.swyx has previously written similar thoughts on types vs tests for putting bounds on program behavior, but AlphaCodium extends this to AI generated tests and code.More recently, Itamar has also shown that AlphaCodium's techniques also extend well to the o1 models:Making Flow Engineering a useful technique to improve code model performance on every model. This is something we see AI Engineers uniquely well positioned to do compared to ML Engineers/Researchers.Full Video PodcastLike and subscribe!Show Notes* Itamar* Qodo* First episode* Eric* Bolt* StackBlitz* Thinkster* AlphaCodium* WebContainersChapters* 00:00:00 Introductions & Updates* 00:06:01 Generic vs. Specific AI Agents* 00:07:40 Maintaining vs Creating with AI* 00:17:46 Human vs Agent Computer Interfaces* 00:20:15 Why Docker doesn't work for Bolt* 00:24:23 Creating Testing and Code Review Loops* 00:28:07 Bolt's Task Breakdown Flow* 00:31:04 AI in Complex Enterprise Environments* 00:41:43 AlphaCodium* 00:44:39 Strategies for Breaking Down Complex Tasks* 00:45:22 Building in Open Source* 00:50:35 Choosing a product as a founder* 00:59:03 Reflections on Bolt Success* 01:06:07 Building a B2C GTM* 01:18:11 AI Capabilities and Pricing Tiers* 01:20:28 What makes Bolt unique* 01:23:07 Future Growth and Product Development* 01:29:06 Competitive Landscape in AI Engineering* 01:30:01 Advice to Founders and Embracing AI* 01:32:20 Having a baby and completing an Iron ManTranscriptAlessio [00:00:00]: Hey everyone, welcome to the Latent Space Podcast. This is Alessio, partner and CTO at Decibel Partners, and I'm joined by my co-host Swyx, founder of Smol.ai.Swyx [00:00:12]: Hey, and today we're still in our sort of makeshift in-between studio, but we're very delighted to have a former returning guest host, Itamar. Welcome back.Itamar [00:00:21]: Great to be here after a year or more. Yeah, a year and a half.Swyx [00:00:24]: You're one of our earliest guests on Agents. Now you're CEO co-founder of Kodo. Right. Which has just been renamed. You also raised a $40 million Series A, and we can get caught up on everything, but we're also delighted to have our new guest, Eric. Welcome.Eric [00:00:42]: Thank you. Excited to be here. Should I say Bolt or StackBlitz?Swyx [00:00:45]: Like, is it like its own company now or?Eric [00:00:47]: Yeah. Bolt's definitely bolt.new. That's the thing that we're probably the most known for, I imagine, at this point.Swyx [00:00:54]: Which is ridiculous to say because you were working at StackBlitz for so long.Eric [00:00:57]: Yeah. I mean, within a week, we were doing like double the amount of traffic. And StackBlitz had been online for seven years, and we were like, what? But anyways, yeah. So we're StackBlitz, the company behind bolt.new. If you've heard of bolt.new, that's our stuff. Yeah.Swyx [00:01:12]: Yeah.Itamar [00:01:13]: Excellent. I see, by the way, that the founder mode, you need to know to capture opportunities. So kudos on doing that, right? You're working on some technology, and then suddenly you can exploit that to a new world. Yeah.Eric [00:01:24]: Totally. And I think, well, not to jump, but 100%, I mean, a couple of months ago, we had the idea for Bolt earlier this year, but we haven't really shared this too much publicly. But we actually had tried to build it with some of those state-of-the-art models back in January, February, you can kind of imagine which, and they just weren't good enough to actually do the code generation where the code was accurate and it was fast and whatever have you without a ton of like rag, but then there was like issues with that. So we put it on the shelf and then we got kind of a sneak peek of some of the new models that have come out in the past couple of months now. And so once we saw that, once we actually saw the code gen from it, we were like, oh my God, like, okay, we can build a product around this. And so that was really the impetus of us building the thing. But with that, it was StackBlitz, the core StackBlitz product the past seven years has been an IDE for developers. So the entire user experience flow we've built up just didn't make sense. And so when we kind of went out to build Bolt, we just thought, you know, if we were inventing our product today, what would the interface look like given what is now possible with the AI code gen? And so there's definitely a lot of conversations we had internally, but you know, just kind of when we logically laid it out, we were like, yeah, I think it makes sense to just greenfield a new thing and let's see what happens. If it works great, then we'll figure it out. If it doesn't work great, then it'll get deleted at some point. So that's kind of how it actually came to be.Swyx [00:02:49]: I'll mention your background a little bit. You were also founder of Thinkster before you started StackBlitz. So both of you are second time founders. Both of you have sort of re-founded your company recently. Yours was more of a rename. I think a slightly different direction as well. And then we can talk about both. Maybe just chronologically, should we get caught up on where Kodo is first and then you know, just like what people should know since the last pod? Sure.Itamar [00:03:12]: The last pod was two months after we launched and we basically had the vision that we talked about. The idea that software development is about specification, test and code, etc. We are more on the testing part as in essence, we think that if you solve testing, you solve software development. The beautiful chart that we'll put up on screen. And testing is a really big field, like there are many dimensions, unit testing, the level of the component, how big it is, how large it is. And then there is like different type of testing, is it regression or smoke or whatever. So back then we only had like one ID extension with unit tests as in focus. One and a half year later, first ID extension supports more type of testing as context aware. We index local, local repos, but also 10,000s of repos for Fortune 500 companies. We have another agent, another tool that is called, the pure agent is the open source and the commercial one is CodoMerge. And then we have another open source called CoverAgent, which is not yet a commercial product coming very soon. It's very impressive. It could be that already people are approving automated pull requests that they don't even aware in really big open sources. So once we have enough of these, we will also launch another agent. So for the first one and a half year, what we did is grew in our offering and mostly on the side of, does this code actually works, testing, code review, et cetera. And we believe that's the critical milestone that needs to be achieved to actually have the AI engineer for enterprise software. And then like for the first year was everything bottom up, getting to 1 million installation. 2024, that was 2023, 2024 was starting to monetize, to feel like how it is to make the first buck. So we did the teams offering, it went well with a thousand of teams, et cetera. And then we started like just a few months ago to do enterprise with everything you need, which is a lot of things that discussed in the last post that was just released by Codelm. So that's how we call it at Codelm. Just opening the brackets, our company name was Codelm AI, and we renamed to Codo and we call our models Codelm. So back to my point, so we started Enterprise Motion and already have multiple Fortune 100 companies. And then with that, we raised a series of $40 million. And what's exciting about it is that enables us to develop more agents. That's our focus. I think it's very different. We're not coming very soon with an ID or something like that.Swyx [00:06:01]: You don't want to fork this code?Itamar [00:06:03]: Maybe we'll fork JetBrains or something just to be different.Swyx [00:06:08]: I noticed that, you know, I think the promise of general purpose agents has kind of died. Like everyone is doing kind of what you're doing. There's Codogen, Codomerge, and then there's a third one. What's the name of it?Itamar [00:06:17]: Yeah. Codocover. Cover. Which is like a commercial version of a cover agent. It's coming soon.Swyx [00:06:23]: Yeah. It's very similar with factory AI, also doing like droids. They all have special purpose doing things, but people don't really want general purpose agents. Right. The last time you were here, we talked about AutoGBT, the biggest thing of 2023. This year, not really relevant anymore. And I think it's mostly just because when you give me a general purpose agent, I don't know what to do with it.Eric [00:06:42]: Yeah.Itamar [00:06:43]: I totally agree with that. We're seeing it for a while and I think it will stay like that despite the computer use, et cetera, that supposedly can just replace us. You can just like prompt it to be, hey, now be a QA or be a QA person or a developer. I still think that there's a few reasons why you see like a dedicated agent. Again, I'm a bit more focused, like my head is more on complex software for big teams and enterprise, et cetera. And even think about permissions and what are the data sources and just the same way you manage permissions for users. Developers, you probably want to have dedicated guardrails and dedicated approvals for agents. I intentionally like touched a point on not many people think about. And of course, then what you can think of, like maybe there's different tools, tool use, et cetera. But just the first point by itself is a good reason why you want to have different agents.Alessio [00:07:40]: Just to compare that with Bot.new, you're almost focused on like the application is very complex and now you need better tools to kind of manage it and build on top of it. On Bot.new, it's almost like I was using it the other day. There's basically like, hey, look, I'm just trying to get started. You know, I'm not very opinionated on like how you're going to implement this. Like this is what I want to do. And you build a beautiful app with it. What people ask as the next step, you know, going back to like the general versus like specific, have you had people say, hey, you know, this is great to start, but then I want a specific Bot.new dot whatever else to do a more vertical integration and kind of like development or what's the, what do people say?Eric [00:08:18]: Yeah. I think, I think you kind of hit the, hit it head on, which is, you know, kind of the way that we've, we've kind of talked about internally is it's like people are using Bolt to go from like 0.0 to 1.0, like that's like kind of the biggest unlock that Bolt has versus most other things out there. I mean, I think that's kind of what's, what's very unique about Bolt. I think the, you know, the working on like existing enterprise applications is, I mean, it's crazy important because, you know, there's a, you look, when you look at the fortune 500, I mean, these code bases, some of these have been around for 20, 30 plus years. And so it's important to be going from, you know, 101.3 to 101.4, et cetera. I think for us, so what's been actually pretty interesting is we see there's kind of two different users for us that are coming in and it's very distinct. It's like people that are developers already. And then there's people that have never really written software and more if they have, it's been very, very minimal. And so in the first camp, what these developers are doing, like to go from zero to one, they're coming to Bolt and then they're ejecting the thing to get up or just downloading it and, you know, opening cursor, like whatever to, to, you know, keep iterating on the thing. And sometimes they'll bring it back to Bolt to like add in a huge piece of functionality or something. Right. But for the people that don't know how to code, they're actually just, they, they live in this thing. And that was one of the weird things when we launched is, you know, within a day of us being online, one of the most popular YouTube videos, and there's been a ton since, which was, you know, there's like, oh, Bolt is the cursor killer. And I originally saw the headlines and I was like, thanks for the views. I mean, I don't know. This doesn't make sense to me. That's not, that's not what we kind of thought.Swyx [00:09:44]: It's how YouTubers talk to each other. Well, everything kills everything else.Eric [00:09:47]: Totally. But what blew my mind was that there was any comparison because it's like cursor is a, is a local IDE product. But when, when we actually kind of dug into it and we, and we have people that are using our product saying this, I'm not using cursor. And I was like, what? And it turns out there are hundreds of thousands of people that we have seen that we're using cursor and we're trying to build apps with that where they're not traditional software does, but we're heavily leaning on the AI. And as you can imagine, it is very complicated, right? To do that with cursor. So when Bolt came out, they're like, wow, this thing's amazing because it kind of inverts the complexity where it's like, you know, it's not an IDE, it's, it's a, it's a chat-based sort of interface that we have. So that's kind of the split, which is rather interesting. We've had like the first startups now launch off of Bolt entirely where this, you know, tomorrow I'm doing a live stream with this guy named Paul, who he's built an entire CRM using this thing and you know, with backend, et cetera. And people have made their first money on the internet period, you know, launching this with Stripe or whatever have you. So that's, that's kind of the two main, the two main categories of folks that we see using Bolt though.Itamar [00:10:51]: I agree that I don't understand the comparison. It doesn't make sense to me. I think like we have like two type of families of tools. One is like we re-imagine the software development. I think Bolt is there and I think like a cursor is more like a evolution of what we already have. It's like taking the IDE and it's, it's amazing and it's okay, let's, let's adapt the IDE to an era where LLMs can do a lot for us. And Bolt is more like, okay, let's rethink everything totally. And I think we see a few tools there, like maybe Vercel, Veo and maybe Repl.it in that area. And then in the area of let's expedite, let's change, let's, let's progress with what we already have. You can see Cursor and Kodo, but we're different between ourselves, Cursor and Kodo, but definitely I think that comparison doesn't make sense.Alessio [00:11:42]: And just to set the context, this is not a Twitter demo. You've made 4 million of revenue in four weeks. So this is, this is actually working, you know, it's not a, what, what do you think that is? Like, there's been so many people demoing coding agents on Twitter and then it doesn't really work. And then you guys were just like, here you go, it's live, go use it, pay us for it. You know, is there anything in the development that was like interesting and maybe how that compares to building your own agents?Eric [00:12:08]: We had no idea, honestly, like we, we, we've been pretty blown away and, and things have just kind of continued to grow faster since then. We're like, oh, today is week six. So I, I kind of came back to the point you just made, right, where it's, you, you kind of outlined, it's like, there's kind of this new market of like kind of rethinking the software development and then there's heavily augmenting existing developers. I think that, you know, both of which are, you know, AI code gen being extremely good, it's allowed existing developers, it's allowing existing developers to camera out software far faster than they could have ever before, right? It's like the ultimate power tool for an existing developer. But this code gen stuff is now so good. And then, and we saw this over the past, you know, from the beginning of the year when we tried to first build, it's actually lowered the barrier to people that, that aren't traditionally software engineers. But the kind of the key thing is if you kind of think about it from, imagine you've never written software before, right? My co-founder and I, he and I grew up down the street from each other in Chicago. We learned how to code when we were 13 together and we've been building stuff ever since. And this is back in like the mid 2000s or whatever, you know, there was nothing for free to learn from online on the internet and how to code. For our 13th birthdays, we asked our parents for, you know, O'Reilly books cause you couldn't get this at the library, right? And so instead of like an Xbox, we got, you know, programming books. But the hardest part for everyone learning to code is getting an environment set up locally, you know? And so when we built StackBlitz, like kind of the key thesis, like seven years ago, the insight we had was that, Hey, it seems like the browser has a lot of new APIs like WebAssembly and service workers, et cetera, where you could actually write an operating system that ran inside the browser that could boot in milliseconds. And you, you know, basically there's this missing capability of the web. Like the web should be able to build apps for the web, right? You should be able to build the web on the web. Every other platform has that, Visual Studio for Windows, Xcode for Mac. The web has no built in primitive for this. And so just like our built in kind of like nerd instinct on this was like, that seems like a huge hole and it's, you know, it will be very valuable or like, you know, very valuable problem to solve. So if you want to set up that environments, you know, this is what we spent the past seven years doing. And the reality is existing developers have running locally. They already know how to set up that environment. So the problem isn't as acute for them. When we put Bolt online, we took that technology called WebContainer and married it with these, you know, state of the art frontier models. And the people that have the most pain with getting stuff set up locally is people that don't code. I think that's been, you know, really the big explosive reason is no one else has been trying to make dev environments work inside of a browser tab, you know, for the past if since ever, other than basically our company, largely because there wasn't an immediate demand or need. So I think we kind of find ourselves at the right place at the right time. And again, for this market of people that don't know how to write software, you would kind of expect that you should be able to do this without downloading something to your computer in the same way that, hey, I don't have to download Photoshop now to make designs because there's Figma. I don't have to download Word because there's, you know, Google Docs. They're kind of looking at this as that sort of thing, right? Which was kind of the, you know, our impetus and kind of vision from the get-go. But you know, the code gen, the AI code gen stuff that's come out has just been, you know, an order of magnitude multiplier on how magic that is, right? So that's kind of my best distillation of like, what is going on here, you know?Alessio [00:15:21]: And you can deploy too, right?Eric [00:15:22]: Yeah.Alessio [00:15:23]: Yeah.Eric [00:15:24]: And so that's, what's really cool is it's, you know, we have deployment built in with Netlify and this is actually, I think, Sean, you actually built this at Netlify when you were there. Yeah. It's one of the most brilliant integrations actually, because, you know, effectively the API that Sean built, maybe you can speak to it, but like as a provider, we can just effectively give files to Netlify without the user even logging in and they have a live website. And if they want to keep, hold onto it, they can click a link and claim it to their Netlify account. But it basically is just this really magic experience because when you come to Bolt, you say, I want a website. Like my mom, 70, 71 years old, made her first website, you know, on the internet two weeks ago, right? It was about her nursing days.Swyx [00:16:03]: Oh, that's fantastic though. It wouldn't have been made.Eric [00:16:06]: A hundred percent. Cause even in, you know, when we've had a lot of people building personal, like deeply personal stuff, like in the first week we launched this, the sales guy from the East Coast, you know, replied to a tweet of mine and he said, thank you so much for building this to your team. His daughter has a medical condition and so for her to travel, she has to like line up donors or something, you know, so ahead of time. And so he actually used Bolt to make a website to do that, to actually go and send it to folks in the region she was going to travel to ahead of time. I was really touched by it, but I also thought like, why, you know, why didn't he use like Wix or Squarespace? Right? I mean, this is, this is a solved problem, quote unquote, right? And then when I thought, I actually use Squarespace for my, for my, uh, the wedding website for my wife and I, like back in 2021, so I'm familiar, you know, it was, it was faster. I know how to code. I was like, this is faster. Right. And I thought back and I was like, there's a whole interface you have to learn how to use. And it's actually not that simple. There's like a million things you can configure in that thing. When you come to Bolt, there's a, there's a text box. You just say, I need a, I need a wedding website. Here's the date. Here's where it is. And here's a photo of me and my wife, put it somewhere relevant. It's actually the simplest way. And that's what my, when my mom came, she said, uh, I'm Pat Simons. I was a nurse in the seventies, you know, and like, here's the things I did and a website came out. So coming back to why is this such a, I think, why are we seeing this sort of growth? It's, this is the simplest interface I think maybe ever created to actually build it, a deploy a website. And then that website, my mom made, she's like, okay, this looks great. And there's, there's one button, you just click it, deploy, and it's live and you can buy a domain name, attach it to it. And you know, it's as simple as it gets, it's getting even simpler with some of the stuff we're working on. But anyways, so that's, it's, it's, uh, it's been really interesting to see some of the usage like that.Swyx [00:17:46]: I can offer my perspective. So I, you know, I probably should have disclosed a little bit that, uh, I'm a, uh, stack list investor.Alessio [00:17:53]: Canceled the episode. I know, I know. Don't play it now. Pause.Eric actually reached out to ShowMeBolt before the launch. And we, you know, we talked a lot about, like, the framing of, of what we're going to talk about how we marketed the thing, but also, like, what we're So that's what Bolt was going to need, like a whole sort of infrastructure.swyx: Netlify, I was a maintainer but I won't take claim for the anonymous upload. That's actually the origin story of Netlify. We can have Matt Billman talk about it, but that was [00:18:00] how Netlify started. You could drag and drop your zip file or folder from your desktop onto a website, it would have a live URL with no sign in.swyx: And so that was the origin story of Netlify. And it just persists to today. And it's just like it's really nice, interesting that both Bolt and CognitionDevIn and a bunch of other sort of agent type startups, they all use Netlify to deploy because of this one feature. They don't really care about the other features.swyx: But, but just because it's easy for computers to use and talk to it, like if you build an interface for computers specifically, that it's easy for them to Navigate, then they will be used in agents. And I think that's a learning that a lot of developer tools companies are having. That's my bolt launch story and now if I say all that stuff.swyx: And I just wanted to come back to, like, the Webcontainers things, right? Like, I think you put a lot of weight on the technical modes. I think you also are just like, very good at product. So you've, you've like, built a better agent than a lot of people, the rest of us, including myself, who have tried to build these things, and we didn't get as far as you did.swyx: Don't shortchange yourself on products. But I think specifically [00:19:00] on, on infra, on like the sandboxing, like this is a thing that people really want. Alessio has Bax E2B, which we'll have on at some point, talking about like the sort of the server full side. But yours is, you know, inside of the browser, serverless.swyx: It doesn't cost you anything to serve one person versus a million people. It doesn't, doesn't cost you anything. I think that's interesting. I think in theory, we should be able to like run tests because you can run the full backend. Like, you can run Git, you can run Node, you can run maybe Python someday.swyx: We talked about this. But ideally, you should be able to have a fully gentic loop, running code, seeing the errors, correcting code, and just kind of self healing, right? Like, I mean, isn't that the dream?Eric: Totally.swyx: Yeah,Eric: totally. At least in bold, we've got, we've got a good amount of that today. I mean, there's a lot more for us to do, but one of the nice things, because like in web container, you know, there's a lot of kind of stuff you go Google like, you know, turn docker container into wasm.Eric: You'll find a lot of stuff out there that will do that. The problem is it's very big, it's slow, and that ruins the experience. And so what we ended up doing is just writing an operating system from [00:20:00] scratch that was just purpose built to, you know, run in a browser tab. And the reason being is, you know, Docker 2 awesome things will give you an image that's like out 60 to 100 megabits, you know, maybe more, you know, and our, our OS, you know, kind of clocks in, I think, I think we're in like a, maybe, maybe a megabyte or less or something like that.Eric: I mean, it's, it's, you know, really, really, you know, stripped down.swyx: This is basically the task involved is I understand that it's. Mapping every single, single Linux call to some kind of web, web assembly implementation,Eric: but more or less, and, and then there's a lot of things actually, like when you're looking at a dev environment, there's a lot of things that you don't need that a traditional OS is gonna have, right?Eric: Like, you know audio drivers or you like, there's just like, there's just tons of things. Oh, yeah. Right. Yeah. That goes . Yeah. You can just kind, you can, you can kind of tos them. Or alternatively, what you can do is you can actually be the nice thing. And this is, this kind of comes back to the origins of browsers, which is, you know, they're, they're at the beginning of the web and, you know, the late nineties, there was two very different kind of visions for the web where Alan Kay vehemently [00:21:00] disagree with the idea that should be document based, which is, you know, Tim Berners Lee, you know, that, and that's kind of what ended up winning, winning was this document based kind of browsing documents on the web thing.Eric: Alan Kay, he's got this like very famous quote where he said, you know, you want web browsers to be mini operating systems. They should download little mini binaries and execute with like a little mini virtualized operating system in there. And what's kind of interesting about the history, not to geek out on this aspect, what's kind of interesting about the history is both of those folks ended up being right.Eric: Documents were actually the pragmatic way that the web worked. Was, you know, became the most ubiquitous platform in the world to the degree now that this is why WebAssembly has been invented is that we're doing, we need to do more low level things in a browser, same thing with WebGPU, et cetera. And so all these APIs, you know, to build an operating system came to the browser.Eric: And that was actually the realization we had in 2017 was, holy heck, like you can actually, you know, service workers, which were designed for allowing your app to work offline. That was the kind of the key one where it was like, wait a second, you can actually now run. Web servers within a [00:22:00] browser, like you can run a server that you open up.Eric: That's wild. Like full Node. js. Full Node. js. Like that capability. Like, I can have a URL that's programmatically controlled. By a web application itself, boom. Like the web can build the web. The primitive is there. Everyone at the time, like we talked to people that like worked on, you know Chrome and V8 and they were like, uhhhh.Eric: You know, like I don't know. But it's one of those things you just kind of have to go do it to find out. So we spent a couple of years, you know, working on it and yeah. And, and, and got to work in back in 2021 is when we kind of put the first like data of web container online. Butswyx: in partnership with Google, right?swyx: Like Google actually had to help you get over the finish line with stuff.Eric: A hundred percent, because well, you know, over the years of when we were doing the R and D on the thing. Kind of the biggest challenge, the two ways that you can kind of test how powerful and capable a platform are, the two types of applications are one, video games, right, because they're just very compute intensive, a lot of calculations that have to happen, right?Eric: The second one are IDEs, because you're talking about actually virtualizing the actual [00:23:00] runtime environment you are in to actually build apps on top of it, which requires sophisticated capabilities, a lot of access to data. You know, a good amount of compute power, right, to effectively, you know, building app in app sort of thing.Eric: So those, those are the stress tests. So if your platform is missing stuff, those are the things where you find out. Those are, those are the people building games and IDEs. They're the ones filing bugs on operating system level stuff. And for us, browser level stuff.Eric [00:23:47]: yeah, what ended up happening is we were just hammering, you know, the Chromium bug tracker, and they're like, who are these guys? Yeah. And, and they were amazing because I mean, just making Chrome DevTools be able to debug, I mean, it's, it's not, it wasn't originally built right for debugging an operating system, right? They've been phenomenal working with us and just kind of really pushing the limits, but that it's a rising tide that's kind of lifted all boats because now there's a lot of different types of applications that you can debug with Chrome Dev Tools that are running a browser that runs more reliably because just the stress testing that, that we and, you know, games that are coming to the web are kind of pushing as well, but.Itamar [00:24:23]: That's awesome. About the testing, I think like most, let's say coding assistant from different kinds will need this loop of testing. And even I would add code review to some, to some extent that you mentioned. How is testing different from code review? Code review could be, for example, PR review, like a code review that is done at the point of when you want to merge branches. But I would say that code review, for example, checks best practices, maintainability, and so on. It's not just like CI, but more than CI. And testing is like a more like checking functionality, et cetera. So it's different. We call, by the way, all of these together code integrity, but that's a different story. Just to go back to the, to the testing and specifically. Yeah. It's, it's, it's since the first slide. Yeah. We're consistent. So if we go back to the testing, I think like, it's not surprising that for us testing is important and for Bolt it's testing important, but I want to shed some light on a different perspective of it. Like let's think about autonomous driving. Those startups that are doing autonomous driving for highway and autonomous driving for the city. And I think like we saw the autonomous of the highway much faster and reaching to a level, I don't know, four or so much faster than those in the city. Now, in both cases, you need testing and quote unquote testing, you know, verifying validation that you're doing the right thing on the road and you're reading and et cetera. But it's probably like so different in the city that it could be like actually different technology. And I claim that we're seeing something similar here. So when you're building the next Wix, and if I was them, I was like looking at you and being a bit scared. That's what you're disrupting, what you just said. Then basically, I would say that, for example, the UX UI is freaking important. And because you're you're more aiming for the end user. In this case, maybe it's an end user that doesn't know how to develop for developers. It's also important. But let alone those that do not know to develop, they need a slick UI UX. And I think like that's one reason, for example, I think Cursor have like really good technology. I don't know the underlying what's under the hood, but at least what they're saying. But I think also their UX UI is great. It's a lot because they did their own ID. While if you're aiming for the city AI, suddenly like there's a lot of testing and code review technology that it's not necessarily like that important. For example, let's talk about integration tests. Probably like a lot of what you're building involved at the moment is isolated applications. Maybe the vision or the end game is maybe like having one solution for everything. It could be that eventually the highway companies will go into the city and the other way around. But at the beginning, there is a difference. And integration tests are a good example. I guess they're a bit less important. And when you think about enterprise software, they're really important. So to recap, like I think like the idea of looping and verifying your test and verifying your code in different ways, testing or code review, et cetera, seems to be important in the highway AI and the city AI, but in different ways and different like critical for the city, even more and more variety. Actually, I was looking to ask you like what kind of loops you guys are doing. For example, when I'm using Bolt and I'm enjoying it a lot, then I do see like sometimes you're trying to catch the errors and fix them. And also, I noticed that you're breaking down tasks into smaller ones and then et cetera, which is already a common notion for a year ago. But it seems like you're doing it really well. So if you're willing to share anything about it.Eric [00:28:07]: Yeah, yeah. I realized I never actually hit the punchline of what I was saying before. I mentioned the point about us kind of writing an operating system from scratch because what ended up being important about that is that to your point, it's actually a very, like compared to like a, you know, if you're like running cursor on anyone's machine, you kind of don't know what you're dealing with, with the OS you're running on. There could be an error happens. It could be like a million different things, right? There could be some config. There could be, it could be God knows what, right? The thing with WebConnect is because we wrote the entire thing from scratch. It's actually a unified image basically. And we can instrument it at any level that we think is going to be useful, which is exactly what we did when we started building Bolt is we instrumented stuff at like the process level, at the runtime level, you know, et cetera, et cetera, et cetera. Stuff that would just be not impossible to do on local, but to do that in a way that works across any operating system, whatever is, I mean, would just be insanely, you know, insanely difficult to do right and reliably. And that's what you saw when you've used Bolt is that when an error actually will occur, whether it's in the build process or the actual web application itself is failing or anything kind of in between, you can actually capture those errors. And today it's a very primitive way of how we've implemented it largely because the product just didn't exist 90 days ago. So we're like, we got some work ahead of us and we got to hire some more a little bit, but basically we present and we say, Hey, this is, here's kind of the things that went wrong. There's a fix it button and then a ignore button, and then you can just hit fix it. And then we take all that telemetry through our agent, you run it through our agent and say, kind of, here's the state of the application. Here's kind of the errors that we got from Node.js or the browser or whatever, and like dah, dah, dah, dah. And it can take a crack at actually solving it. And it's actually pretty darn good at being able to do that. That's kind of been a, you know, closing the loop and having it be a reliable kind of base has seemed to be a pretty big upgrade over doing stuff locally, just because I think that's a pretty key ingredient of it. And yeah, I think breaking things down into smaller tasks, like that's, that's kind of a key part of our agent. I think like Claude did a really good job with artifacts. I think, you know, us and kind of everyone else has, has kind of taken their approach of like actually breaking out certain tasks in a certain order into, you know, kind of a concrete way. And, and so actually the core of Bolt, I know we actually made open source. So you can actually go and check out like the system prompts and et cetera, and you can run it locally and whatever have you. So anyone that's interested in this stuff, I'd highly recommend taking a look at. There's not a lot of like stuff that's like open source in this realm. It's, that was one of the fun things that we've we thought would be cool to do. And people, people seem to like it. I mean, there's a lot of forks and people adding different models and stuff. So it's been cool to see.Swyx [00:30:41]: Yeah. I'm happy to add, I added real-time voice for my opening day demo and it was really fun to hack with. So thank you for doing that. Yeah. Thank you. I'm going to steal your code.Eric [00:30:52]: Because I want that.Swyx [00:30:52]: It's funny because I built on top of the fork of Bolt.new that already has the multi LLM thing. And so you just told me you're going to merge that in. So then you're going to merge two layers of forks down into this thing. So it'll be fun.Eric [00:31:03]: Heck yeah.Alessio [00:31:04]: Just to touch on like the environment, Itamar, you maybe go into the most complicated environments that even the people that work there don't know how to run. How much of an impact does that have on your performance? Like, you know, it's most of the work you're doing actually figuring out environment and like the libraries, because I'm sure they're using outdated version of languages, they're using outdated libraries, they're using forks that have not been on the public internet before. How much of the work that you're doing is like there versus like at the LLM level?Itamar [00:31:32]: One of the reasons I was asking about, you know, what are the steps to break things down, because it really matters. Like, what's the tech stack? How complicated the software is? It's hard to figure it out when you're dealing with the real world, any environment of enterprise as a city, when I'm like, while maybe sometimes like, I think you do enable like in Bolt, like to install stuff, but it's quite a like controlled environment. And that's a good thing to do, because then you narrow down and it's easier to make things work. So definitely, there are two dimensions, I think, actually spaces. One is the fact just like installing our software without yet like doing anything, making it work, just installing it because we work with enterprise and Fortune 500, etc. Many of them want on prem solution.Swyx [00:32:22]: So you have how many deployment options?Itamar [00:32:24]: Basically, we had, we did a metric metrics, say 96 options, because, you know, they're different dimensions. Like, for example, one dimension, we connect to your code management system to your Git. So are you having like GitHub, GitLab? Subversion? Is it like on cloud or deployed on prem? Just an example. Which model agree to use its APIs or ours? Like we have our Is it TestGPT? Yeah, when we started with TestGPT, it was a huge mistake name. It was cool back then, but I don't think it's a good idea to name a model after someone else's model. Anyway, that's my opinion. So we gotSwyx [00:33:02]: I'm interested in these learnings, like things that you change your mind on.Itamar [00:33:06]: Eventually, when you're building a company, you're building a brand and you want to create your own brand. By the way, when I thought about Bolt.new, I also thought about if it's not a problem, because when I think about Bolt, I do think about like a couple of companies that are already called this way.Swyx [00:33:19]: Curse companies. You could call it Codium just to...Itamar [00:33:24]: Okay, thank you. Touche. Touche.Eric [00:33:27]: Yeah, you got to imagine the board meeting before we launched Bolt, one of our investors, you can imagine they're like, are you sure? Because from the investment side, it's kind of a famous, very notorious Bolt. And they're like, are you sure you want to go with that name? Oh, yeah. Yeah, absolutely.Itamar [00:33:43]: At this point, we have actually four models. There is a model for autocomplete. There's a model for the chat. There is a model dedicated for more for code review. And there is a model that is for code embedding. Actually, you might notice that there isn't a good code embedding model out there. Can you name one? Like dedicated for code?Swyx [00:34:04]: There's code indexing, and then you can do sort of like the hide for code. And then you can embed the descriptions of the code.Itamar [00:34:12]: Yeah, but you do see a lot of type of models that are dedicated for embedding and for different spaces, different fields, etc. And I'm not aware. And I know that if you go to the bedrock, try to find like there's a few code embedding models, but none of them are specialized for code.Swyx [00:34:31]: Is there a benchmark that you would tell us to pay attention to?Itamar [00:34:34]: Yeah, so it's coming. Wait for that. Anyway, we have our models. And just to go back to the 96 option of deployment. So I'm closing the brackets for us. So one is like dimensional, like what Git deployment you have, like what models do you agree to use? Dotter could be like if it's air-gapped completely, or you want VPC, and then you have Azure, GCP, and AWS, which is different. Do you use Kubernetes or do not? Because we want to exploit that. There are companies that do not do that, etc. I guess you know what I mean. So that's one thing. And considering that we are dealing with one of all four enterprises, we needed to deal with that. So you asked me about how complicated it is to solve that complex code. I said, it's just a deployment part. And then now to the software, we see a lot of different challenges. For example, some companies, they did actually a good job to build a lot of microservices. Let's not get to if it's good or not, but let's first assume that it is a good thing. A lot of microservices, each one of them has their own repo. And now you have tens of thousands of repos. And you as a developer want to develop something. And I remember me coming to a corporate for the first time. I don't know where to look at, like where to find things. So just doing a good indexing for that is like a challenge. And moreover, the regular indexing, the one that you can find, we wrote a few blogs on that. By the way, we also have some open source, different than yours, but actually three and growing. Then it doesn't work. You need to let the tech leads and the companies influence your indexing. For example, Mark with different repos with different colors. This is a high quality repo. This is a lower quality repo. This is a repo that we want to deprecate. This is a repo we want to grow, etc. And let that be part of your indexing. And only then things actually work for enterprise and they don't get to a fatigue of, oh, this is awesome. Oh, but I'm starting, it's annoying me. I think Copilot is an amazing tool, but I'm quoting others, meaning GitHub Copilot, that they see not so good retention of GitHub Copilot and enterprise. Ooh, spicy. Yeah. I saw snapshots of people and we have customers that are Copilot users as well. And also I saw research, some of them is public by the way, between 38 to 50% retention for users using Copilot and enterprise. So it's not so good. By the way, I don't think it's that bad, but it's not so good. So I think that's a reason because, yeah, it helps you auto-complete, but then, and especially if you're working on your repo alone, but if it's need that context of remote repos that you're code-based, that's hard. So to make things work, there's a lot of work on that, like giving the controllability for the tech leads, for the developer platform or developer experience department in the organization to influence how things are working. A short example, because if you have like really old legacy code, probably some of it is not so good anymore. If you just fine tune on these code base, then there is a bias to repeat those mistakes or old practices, etc. So you need, for example, as I mentioned, to influence that. For example, in Coda, you can have a markdown of best practices by the tech leads and Coda will include that and relate to that and will not offer suggestions that are not according to the best practices, just as an example. So that's just a short list of things that you need to do in order to deal with, like you mentioned, the 100.1 to 100.2 version of software. I just want to say what you're doing is extremelyEric [00:38:32]: impressive because it's very difficult. I mean, the business of Stackplus, kind of before bulk came online, we sold a version of our IDE that went on-prem. So I understand what you're saying about the difficulty of getting stuff just working on-prem. Holy heck. I mean, that is extremely hard. I guess the question I have for you is, I mean, we were just doing that with kind of Kubernetes-based stuff, but the spread of Fortune 500 companies that you're working with, how are they doing the inference for this? Are you kind of plugging into Azure's OpenAI stuff and AWS's Bedrock, you know, Cloud stuff? Or are they just like running stuff on GPUs? Like, what is that? How are these folks approaching that? Because, man, what we saw on the enterprise side, I mean, I got to imagine that that's a huge challenge. Everything you said and more, like,Itamar [00:39:15]: for example, like someone could be, and I don't think any of these is bad. Like, they made their decision. Like, for example, some people, they're, I want only AWS and VPC on AWS, no matter what. And then they, some of them, like there is a subset, I will say, I'm willing to take models only for from Bedrock and not ours. And we have a problem because there is no good code embedding model on Bedrock. And that's part of what we're doing now with AWS to solve that. We solve it in a different way. But if you are willing to run on AWS VPC, but run your run models on GPUs or inferentia, like the new version of the more coming out, then our models can run on that. But everything you said is right. Like, we see like on-prem deployment where they have their own GPUs. We see Azure where you're using OpenAI Azure. We see cases where you're running on GCP and they want OpenAI. Like this cross, like a case, although there is Gemini or even Sonnet, I think is available on GCP, just an example. So all the options, that's part of the challenge. I admit that we thought about it, but it was even more complicated. And it took us a few months to actually, that metrics that I mentioned, to start clicking each one of the blocks there. A few months is impressive. I mean,Eric [00:40:35]: honestly, just that's okay. Every one of these enterprises is, their networking is different. Just everything's different. Every single one is different. I see you understand. Yeah. So that just cannot be understated. That it is, that's extremely impressive. Hats off.Itamar [00:40:50]: It could be, by the way, like, for example, oh, we're only AWS, but our GitHub enterprise is on-prem. Oh, we forgot. So we need like a private link or whatever, like every time like that. It's not, and you do need to think about it if you want to work with an enterprise. And it's important. Like I understand like their, I respect their point of view.Swyx [00:41:10]: And this primarily impacts your architecture, your tech choices. Like you have to, you can't choose some vendors because...Itamar [00:41:15]: Yeah, definitely. To be frank, it makes us hard for a startup because it means that we want, we want everyone to enjoy all the variety of models. By the way, it was hard for us with our technology. I want to open a bracket, like a window. I guess you're familiar with our Alpha Codium, which is an open source.Eric [00:41:33]: We got to go over that. Yeah. So I'll do that quickly.Itamar [00:41:36]: Yeah. A pin in that. Yeah. Actually, we didn't have it in the last episode. So, so, okay.Swyx [00:41:41]: Okay. We'll come back to that later, but let's talk about...Itamar [00:41:43]: Yeah. So, so just like shortly, and then we can double click on Alpha Codium. But Alpha Codium is a open source tool. You can go and try it and lets you compete on CodeForce. This is a website and a competition and actually reach a master level level, like 95% with a click of a button. You don't need to do anything. And part of what we did there is taking a problem and breaking it to different, like smaller blocks. And then the models are doing a much better job. Like we all know it by now that taking small tasks and solving them, by the way, even O1, which is supposed to be able to do system two thinking like Greg from OpenAI like hinted, is doing better on these kinds of problems. But still, it's very useful to break it down for O1, despite O1 being able to think by itself. And that's what we presented like just a month ago, OpenAI released that now they are doing 93 percentile with O1 IOI left and International Olympiad of Formation. Sorry, I forgot. Exactly. I told you I forgot. And we took their O1 preview with Alpha Codium and did better. Like it just shows like, and there is a big difference between the preview and the IOI. It shows like that these models are not still system two thinkers, and there is a big difference. So maybe they're not complete system two. Yeah, they need some guidance. I call them system 1.5. We can, we can have it. I thought about it. Like, you know, I care about this philosophy stuff. And I think like we didn't see it even close to a system two thinking. I can elaborate later. But closing the brackets, like we take Alpha Codium and as our principle of thinking, we take tasks and break them down to smaller tasks. And then we want to exploit the best model to solve them. So I want to enable anyone to enjoy O1 and SONET and Gemini 1.5, etc. But at the same time, I need to develop my own models as well, because some of the Fortune 500 want to have all air gapped or whatever. So that's a challenge. Now you need to support so many models. And to some extent, I would say that the flow engineering, the breaking down to two different blocks is a necessity for us. Why? Because when you take a big block, a big problem, you need a very different prompt for each one of the models to actually work. But when you take a big problem and break it into small tasks, we can talk how we do that, then the prompt matters less. What I want to say, like all this, like as a startup trying to do different deployment, getting all the juice that you can get from models, etc. is a big problem. And one need to think about it. And one of our mitigation is that process of taking tasks and breaking them down. That's why I'm really interested to know how you guys are doing it. And part of what we do is also open source. So you can see.Swyx [00:44:39]: There's a lot in there. But yeah, flow over prompt. I do believe that that does make sense. I feel like there's a lot that both of you can sort of exchange notes on breaking down problems. And I just want you guys to just go for it. This is fun to watch.Eric [00:44:55]: Yeah. I mean, what's super interesting is the context you're working in is, because for us too with Bolt, we've started thinking because our kind of existing business line was going behind the firewall, right? We were like, how do we do this? Adding the inference aspect on, we're like, okay, how does... Because I mean, there's not a lot of prior art, right? I mean, this is all new. This is all new. So I definitely am going to have a lot of questions for you.Itamar [00:45:17]: I'm here. We're very open, by the way. We have a paper on a blog or like whatever.Swyx [00:45:22]: The Alphacodeum, GitHub, and we'll put all this in the show notes.Itamar [00:45:25]: Yeah. And even the new results of O1, we published it.Eric [00:45:29]: I love that. And I also just, I think spiritually, I like your approach of being transparent. Because I think there's a lot of hype-ium around AI stuff. And a lot of it is, it's just like, you have these companies that are just kind of keep their stuff closed source and then just max hype it, but then it's kind of nothing. And I think it kind of gives a bad rep to the incredible stuff that's actually happening here. And so I think it's stuff like what you're doing where, I mean, true merit and you're cracking open actual code for others to learn from and use. That strikes me as the right approach. And it's great to hear that you're making such incredible progress.Itamar [00:46:02]: I have something to share about the open source. Most of our tools are, we have an open source version and then a premium pro version. But it's not an easy decision to do that. I actually wanted to ask you about your strategy, but I think in your case, there is, in my opinion, relatively a good strategy where a lot of parts of open source, but then you have the deployment and the environment, which is not right if I get it correctly. And then there's a clear, almost hugging face model. Yeah, you can do that, but why should you try to deploy it yourself, deploy it with us? But in our case, and I'm not sure you're not going to hit also some competitors, and I guess you are. I wanted to ask you, for example, on some of them. In our case, one day we looked on one of our competitors that is doing code review. We're a platform. We have the code review, the testing, et cetera, spread over the ID to get. And in each agent, we have a few startups or a big incumbents that are doing only that. So we noticed one of our competitors having not only a very similar UI of our open source, but actually even our typo. And you sit there and you're kind of like, yeah, we're not that good. We don't use enough Grammarly or whatever. And we had a couple of these and we saw it there. And then it's a challenge. And I want to ask you, Bald is doing so well, and then you open source it. So I think I know what my answer was. I gave it before, but still interestingEric [00:47:29]: to hear what you think. GeoHot said back, I don't know who he was up to at this exact moment, but I think on comma AI, all that stuff's open source. And someone had asked him, why is this open source? And he's like, if you're not actually confident that you can go and crush it and build the best thing, then yeah, you should probably keep your stuff closed source. He said something akin to that. I'm probably kind of butchering it, but I thought it was kind of a really good point. And that's not to say that you should just open source everything, because for obvious reasons, there's kind of strategic things you have to kind of take in mind. But I actually think a pretty liberal approach, as liberal as you kind of can be, it can really make a lot of sense. Because that is so validating that one of your competitors is taking your stuff and they're like, yeah, let's just kind of tweak the styles. I mean, clearly, right? I think it's kind of healthy because it keeps, I'm sure back at HQ that day when you saw that, you're like, oh, all right, well, we have to grind even harder to make sure we stay ahead. And so I think it's actually a very useful, motivating thing for the teams. Because you might feel this period of comfort. I think a lot of companies will have this period of comfort where they're not feeling the competition and one day they get disrupted. So kind of putting stuff out there and letting people push it forces you to face reality soon, right? And actually feel that incrementally so you can kind of adjust course. And that's for us, the open source version of Bolt has had a lot of features people have been begging us for, like persisting chat messages and checkpoints and stuff. Within the first week, that stuff was landed in the open source versions. And they're like, why can't you ship this? It's in the open, so people have forked it. And we're like, we're trying to keep our servers and GPUs online. But it's been great because the folks in the community did a great job, kept us on our toes. And we've got to know most of these folks too at this point that have been building these things. And so it actually was very instructive. Like, okay, well, if we're going to go kind of land this, there's some UX patterns we can kind of look at and the code is open source to this stuff. What's great about these, what's not. So anyways, NetNet, I think it's awesome. I think from a competitive point of view for us, I think in particular, what's interesting is the core technology of WebContainer going. And I think that right now, there's really nothing that's kind of on par with that. And we also, we have a business of, because WebContainer runs in your browser, but to make it work, you have to install stuff from NPM. You have to make cores bypass requests, like connected databases, which all require server-side proxying or acceleration. And so we actually sell WebContainer as a service. One of the core reasons we open-sourced kind of the core components of Bolt when we launched was that we think that there's going to be a lot more of these AI, in-your-browser AI co-gen experiences, kind of like what Anthropic did with Artifacts and Clod. By the way, Artifacts uses WebContainers. Not yet. No, yeah. Should I strike that? I think that they've got their own thing at the moment, but there's been a lot of interest in WebContainers from folks doing things in that sort of realm and in the AI labs and startups and everything in between. So I think there'll be, I imagine, over the coming months, there'll be lots of things being announced to folks kind of adopting it. But yeah, I think effectively...Swyx [00:50:35]: Okay, I'll say this. If you're a large model lab and you want to build sandbox environments inside of your chat app, you should call Eric.Itamar [00:50:43]: But wait, wait, wait, wait, wait, wait. I have a question about that. I think OpenAI, they felt that people are not using their model as they would want to. So they built ChatGPT. But I would say that ChatGPT now defines OpenAI. I know they're doing a lot of business from their APIs, but still, is this how you think? Isn't Bolt.new your business now? Why don't you focus on that instead of the...Swyx [00:51:16]: What's your advice as a founder?Eric [00:51:18]: You're right. And so going into it, we, candidly, we were like, Bolt.new, this thing is super cool. We think people are stoked. We think people will be stoked. But we were like, maybe that's allowed. Best case scenario, after month one, we'd be mind blown if we added a couple hundred K of error or something. And we were like, but we think there's probably going to be an immediate huge business. Because there was some early poll on folks wanting to put WebContainer into their product offerings, kind of similar to what Bolt is doing or whatever. We were actually prepared for the inverse outcome here. But I mean, well, I guess we've seen poll on both. But I mean, what's happened with Bolt, and you're right, it's actually the same strategy as like OpenAI or Anthropic, where we have our ChatGPT to OpenAI's APIs is Bolt to WebContainer. And so we've kind of taken that same approach. And we're seeing, I guess, some of the similar results, except right now, the revenue side is extremely lopsided to Bolt.Itamar [00:52:16]: I think if you ask me what's my advice, I think you have three options. One is to focus on Bolt. The other is to focus on the WebContainer. The third is to raise one billion dollars and do them both. I'm serious. I think otherwise, you need to choose. And if you raise enough money, and I think it's big bucks, because you're going to be chased by competitors. And I think it will be challenging to do both. And maybe you can. I don't know. We do see these numbers right now, raising above $100 million, even without havingEric [00:52:49]: a product. You can see these. It's excellent advice. And I think what's been amazing, but also kind of challenging is we're trying to forecast, okay, well, where are these things going? I mean, in the initial weeks, I think us and all the investors in the company that we're sharing this with, it was like, this is cool. Okay, we added 500k. Wow, that's crazy. Wow, we're at a million now. Most things, you have this kind of the tech crunch launch of initiation and then the thing of sorrow. And if there's going to be a downtrend, it's just not coming yet. Now that we're kind of looking ahead, we're six weeks in. So now we're getting enough confidence in our convictions to go, okay, this se

Technology is reshaping the food industry, enabling faster innovation, improved efficiency, and more personalised product offerings. But how are businesses navigating the balance between cutting-edge tools and consumer expectations, especially when it comes to new product development (NPD)? In this episode of the Food Matters Live podcast, recorded live at our Food Matters Live event in Ascot in October 2024, our expert panel discusses the role of technology in driving product development, from recipe management systems to the impact of artificial intelligence on the innovation process. Technology can help us streamline NPD workflows and analyse vast amounts of consumer data, so how will that help companies, both large and small, innovate more effectively? Our panel delves into the pros and cons of emerging technologies, the importance of balancing data-driven insights with the human touch, and how businesses are leveraging tech to scale quickly without compromising on quality. Guests: Michael Adams, Head of Product Innovation, Campden BRI Andrew Godley, Professor of Entrepreneurship and Innovation, University of Sussex Michaela Neame, Head of Product, Merchant Gourmet Amir Mousavi, Founder, Good Food Studio

Aliona Zapanovici: Helping Agile Teams Be Passionate About Their Products, A Product Owner Superpower Read the full Show Notes and search through the world's largest audio library on Scrum directly on the Scrum Master Toolbox Podcast website: http://bit.ly/SMTP_ShowNotes. The Great Product Owner: Helping Agile Teams Be Passionate About Their Products, A PO Superpower A standout Product Owner embodies a blend of deep product knowledge, market insight, and trust in the development team. Aliona highlights how such a PO remains accountable while empowering the team to excel, ensuring they see their value reflected in the product. This dynamic builds passion and commitment within the team. Self-reflection Question: How do you work with the Product Owner to ensure that your team feels trusted and valued while maintaining accountability? The Bad Product Owner: The Challenges of a Proxy PO Aliona shares an experience with a proxy PO lacking real decision-making power. This situation led to confusion, delays, and rework, ultimately ending in the PO's departure and a demotivated team. This story underscores the necessity for Product Owners to possess both authority and clear accountability to effectively guide the team. Self-reflection Question: Does your PO have the necessary authority and trust to lead effectively? [The Scrum Master Toolbox Podcast Recommends]

Ankur Goyal is the founder of ​Braintrust​, a year old LLM eval platform that is already used by Figma, Vercel and Stripe and just raised $36m from a16z. It's a rocketship.This episode is brought to you by WorkOS. If you're thinking about selling to enterprise customers, WorkOS can help you add enterprise features like Single Sign On and audit logs. Key Success Factors- Started with a targeted list of ~50 companies already working with AI- Focused on early adopters and innovators in the space- Strategy: If they could make the frontrunners happy, others would followLinks:- Braintrust - Ankur Goyal - Alana Goyal - Basecase  - Elad Gil  - Martin Casado Chapters:* 00:00  Introduction to BrainTrust and Its Success* 02:52  The Importance of User Research in Product Development* 06:11  Building Relationships with Key Customers* 09:05  The Role of Feedback in Product Improvement* 11:54  The Impact of Mentorship on Entrepreneurial Success* 15:11  Identifying Market Opportunities in AI Development* 18:00  Effective User Interviews and Problem Validation* 20:59  The Evolution of BrainTrust's Product Features* 23:55  Advice for Aspiring DevTool Founders* 26:48  Exciting Developments in the DevTool Space

Sometimes, you need to go the extra mile to make a point—like buying every medicine at CVS to show regulators that medicine can, and often does, have flavor. Sensible regulations should be rooted in logic, not outdated prohibition fears or baseless stigmas. If cannabis is legalized, it should be treated like any other industry, not one plagued by fear of being a shadowy boogeyman.This week, we sit down with Wendy Bronfein to dive into:Key Differences Between Maryland and Missouri's Cannabis MarketsEmerging Marketing Trends and Customer-Focused StrategiesInnovative Crohn's Disease Research and Product Development...and so much more. Chapters:Introduction and Background (00:00:00) - Brian and Kellen introduce their guest Wendy Bronfein, co-founder of Cura Wellness. Wendy shares her background in the television industry and how she transitioned into the cannabis space.Early Days of Maryland Cannabis (00:01:15) - Wendy discusses how her family became involved in the Maryland medical cannabis market, including their trip to Colorado and the process of applying for a license in 2015.Launching Curio Wellness (00:02:47) - The company won a license, built their facility, and became operational in 2017, shipping to licensed dispensaries in December of that year.Transition to Adult Use (00:03:07) - Maryland transitioned from medical to adult-use cannabis in July, with Wendy explaining the regulatory changes and market dynamics.Product Innovation and Research (00:33:59) - Curio Wellness discusses their approach to product development, including specialized products for sleep, mood, and potential medical treatments like a Crohn's disease tablet.Marketing Challenges and Regulations (00:25:16) - Wendy explains the marketing restrictions in Maryland compared to Missouri, highlighting the challenges of advertising in the cannabis industry.Personal Insights and Closing (00:42:33) - The interview concludes with personal questions about Wendy's dream smoking session, her views on branding, and her favorite ice cream. Guest Linkshttps://curiowellness.com/https://x.com/curiowellnesshttps://www.instagram.com/curiowellnessbrand/https://www.linkedin.com/company/curio-wellness/https://www.youtube.com/channel/UCeT6Sut8Wsi4Xr_o9uq0edQhttps://www.linkedin.com/in/wbronfein/Our LinksBryan Fields on Twitter Kellan Finney on Twitter The Dime on Twitter At Eighth Revolution (8th Rev), we provide services from capital to cannabinoid and everything in between in the cannabinoid industry.8th Revolution Cannabinoid Playbook is an Industry-leading report covering the entire cannabis supply chain The Dime is a top 5% most shared  global podcast The Dime has a New Website. Shhhh its not finished. The Dime is a top 50 Cannabis Podcast Sign up for our playbook here:

Founder Richard Lee originally started a company that hosted table tennis competitions, but he took an opportunity to acquire Joola, a German table tennis equipment brand, and expanded its product assortment into pickleball equipment. He shares advice for other entrepreneurs looking to maximize their opportunity in new categories.To learn more about Joola and show notes: https://www.shopify.com/blog/joola-pickleballSubscribe to the Shopify Masters YouTube channel: https://www.youtube.com/channel/UCLicUpeWYLe0zSCiIdZKv_g

In this episode, Carlos Gonzalez de Villaumbrosia interviews Drew Lesicko, Vice President of Product and Technology at SoulCycle.SoulCycle, founded in 2006, is a pioneer in boutique fitness known for its passionate customer community. The company has successfully blended physical and digital experiences, particularly during the COVID-19 pandemic when it launched its At-Home Bike.Drew oversees the full digital journey of SoulCycle customers and all technology platforms for the company. He joined SoulCycle in 2018 and played a crucial role in launching the At-Home Bike at the beginning of the pandemic, which helped sustain the business when physical studios had to close. What you'll learn:Drew's approach to balancing physical and digital experiences in fitness.SoulCycle's adaptation during the pandemic, the strategy for blending physical and digital experiences, and the future of connected fitness technology. How SoulCycle has built such a strong customer community and how they're using data and AI to personalize each rider's fitness journey.The future of connected fitness technology and SoulCycle's positioning in this evolving landscape.Key Takeaways

Success as a platform PM requires both technical depth and exceptional emotional intelligence to navigate complex organizational dynamics...That goes double if you work in banking or finance!In this episode of Arguing Agile, Enterprise Business Agility Coach Om Patel and Product Manager Brian Orlando read and respond to a question from a listener who is a platform product managers at a Bank.Getting into the nitty-gritty of platform how-to's, this episode is perfect for product managers, agile coaches, and technology leaders working in traditional industries looking to modernize their approach to platform management!As industries embrace digital transformation (err... product operating model), platform product managers face unique challenges, including: How to effectively manage cross-functional relationships in siloed environmentsStrategies for prioritizing platform features that deliver organization-wide valueTips for reducing cognitive load across teamsWays to build trust and showcase value as a platform teamCreate value through standardization without weaponizing itBuild effective cross-functional relationships#ProductManagement #TeamTopologies #PlatformTeam #AgileLeadership #Banking #TechLeadership #ProductDevelopment #AgileCoaching= = = = = = = = = = = =Watch it on YouTube= = = = = = = = = = = =Subscribe to our YouTube Channel:https://www.youtube.com/channel/UC8XUSoJPxGPI8EtuUAHOb6g?sub_confirmation=1Apple Podcasts:https://podcasts.apple.com/us/podcast/agile-podcast/id1568557596Spotify:https://open.spotify.com/show/362QvYORmtZRKAeTAE57v3Amazon Music:https://music.amazon.com/podcasts/ee3506fc-38f2-46d1-a301-79681c55ed82/Agile-Podcast= = = = = = = = = = = =Toronto Is My Beat (Music Sample)By Whitewolf (Source: https://ccmixter.org/files/whitewolf225/60181)CC BY 4.0 DEED (https://creativecommons.org/licenses/by/4.0/deed.en)

Links Emily's IG: Fringe Sport Get HGC Tix Outline (0:00) Introduction to Emily Samuel and Her Journey (2:18) The Birth of the Booty Box (3:26) Challenges in Product Development (6:16) Collaboration with Fringe Sport (9:23) Product Features and Versatility (12:19) Market Reception and Launch Excitement (15:06) Final Thoughts and Future Aspirations Description In this conversation, Emily Samuel shares her journey from being a trainer at a celebrity-favorite gym to inventing the Booty Box, a versatile piece of fitness equipment designed for home gyms. She discusses the challenges she faced in product development, her collaboration with Fringe Sport, and her excitement for the upcoming launch. Emily emphasizes the importance of creating solutions for common fitness needs, particularly for women, and reflects on her unique position as a female entrepreneur in the fitness industry. --- Support this podcast: https://podcasters.spotify.com/pod/show/garage-gym-experiment/support

OSF HealthCare, Providence, UMass Memorial Medical Center, and TytoCare share actionable strategies and best practices to transform hybrid care and offer patients personalized, flexible and accessible care.  Our expert panel also explores how virtual care reduces costs and addresses healthcare challenges like staff shortages.   Key topics include:  Maximizing Hybrid Care Models: Panelists explore how hybrid and home-based care models – supported by technology, are revolutionizing how providers deliver care – making it more accessible, efficient, and impactful. Home-Based Healthcare Innovations: Real-world success stories highlighted how providers make healthcare accessible from the comfort of home, schools, and community centers. Technology-Driven Solutions: Technical tools enable immersive primary care experiences remotely, enhancing connectivity and care delivery for families. Highlights: Providence: Kate Baars shared how remote patient monitoring helps achieve compelling clinical and financial outcomes OSF OnCall: Jennie Van Antwerp walked us through innovations in acute and digital care delivery at OSF. UMass Memorial Medical Center: Dr. John Broach discussed how the medical center utilizes technology to drive efficient responses and care, eliminating ED visits. TytoCare: Tina Nelson highlighted strategic partnerships that enable healthcare access for underserved communities through remote technology. Panelists: Kate Baars, Executive Director, Product Development, Virtual Care & Digital Health, Providence Jennie Van Antwerp, MSN, RN, Director, Digital Acute Care/ Digital Care Division, OSF OnCall (Colleen Reynolds) John Broach, MD, Division Direction for EMS and DIsaters Medicine, UMASS Medical Center Christina (Tina) Nelson, Strategic Partnership Manager, TytoCare   https://www.brightspotsinhealthcare.com/events/how-providers-are-maximizing-hybrid-care-and-home-based-interventions   This episode is sponsored by TytoCare   TytoCare is a virtual healthcare company that enables leading health plans and providers to deliver remote healthcare to the whole family through its Home Smart Clinic. Combining a cutting-edge, easy-to-use, FDA-cleared device with AI-powered guidance and diagnostic support, the Home Smart Clinic enables the whole family to conduct remote physical exams with a doctor, replicating in-clinic exams for immediate answers from home. TytoCare drives utilization rates that are six times higher than traditional telehealth services; reduces the total cost of care by an average of five percent; diverts ED visits by an average of 10.8%; and has a high average NPS of 83. The Home Smart Clinic includes Tyto Engagement Labs™, a proven framework of engagement journeys designed for the successful deployment and adoption of the solution. To complete its offering, TytoCare also provides the Pro Smart Clinic, for professional settings outside the home to serve rural clinics, schools, workplaces, and more. TytoCare serves over 250 major health systems and health plans in the U.S., Europe, Asia, Latin America, and the Middle East. For more information, visit us at tytocare.com.

Global Product Management Talk is pleased to bring you the next episode of... Product Mastery Now with host Chad McAllister, PhD. The podcast is all about helping people involved in innovation and managing products become more successful, grow their careers, and STANDOUT from their peers. About the Episode:  In this episode, I speak with Atif Rafiq about how senior product leaders approach strategy development and execution. Atif brings valuable insights from a recent PDMA executive workshop where leaders discussed their real-world challenges with strategic decision making and innovation strategy. Key topics from our discussion: Main challenges product leaders face when developing strategyA practical framework for exploring product opportunitiesHow AI tools can help with strategic decision makingThe importance of early-stage product workWays to improve alignment across organizationsReal-world example using a subscription service concept

Angela presents the second of a two part conversation with Dr Gregory Kelly, in which they discuss the intriguing topic of senescent cells, often referred to as "zombie cells." These cells accumulate with age, resist apoptosis, and contribute to inflammation, negatively impacting overall health and vitality. Dr. Kelly explains the mechanisms behind cellular senescence and introduces the concept of senolytics—compounds designed to help clear these dysfunctional cells from the body KEY TAKEAWAYS Senescent cells, often referred to as "zombie cells," resist apoptosis (cell death) and accumulate with aging. They do not contribute to bodily functions and instead release inflammatory compounds that can lead to various age-related health issues. Senolytic compounds are designed to help clear out senescent cells from the body. By periodically taking these compounds, individuals can promote cellular health and potentially improve energy levels, joint comfort, and overall vitality. The process of using senolytics can be likened to pruning yellow leaves from a plant. Just as removing unhealthy leaves allows for new growth, clearing out senescent cells can help rejuvenate tissues and promote healthier cellular function. It is suggested that individuals start considering senolytics around the age of 40, especially if they have experienced significant stress or health issues. Younger individuals may not need to use them as frequently, while older adults may benefit more from regular use. BEST MOMENTS "Senescent cells resist cell death, are unrepairable, and secrete inflammatory compounds, contributing to aging and various health issues."  "If exercise was a pill, everyone would take it because it stimulates autophagy and helps slow the accumulation of senescent cells."  "Senolytics are compounds that can finally get a senescent cell to change its mind and go through this falling off process."  "If we want a different result than our parents or grandparents, we have to start doing more and start doing it younger." VALUABLE RESOURCES Get a free snapshot of your health and personalised report at www.yourtotalhealthcheck.com Join The High Performance Health Community Save 15% on Qualia Mind with Code ANGELA15 at http://www.qualialife.com/angela Check out Leela Quantum Technology and save 10% with code ANGELA at www.leelaq.com ABOUT THE GUEST Dr. Gregory Kelly is a naturopathic physician (N.D.). He is Vice President of Product Development at Qualia Life Sciences and author of the book Shape Shift. He was an editor of the journal Alternative Medicine Review and has been an instructor at the University of Bridgeport in the College of Naturopathic Medicine, where he taught classes in Nutrition and Counseling Skills. Dr. Kelly has published numerous articles on various aspects of natural medicine and nutrition, contributed three chapters to the Textbook of Natural Medicine, and has more than 30 journal articles indexed on Pubmed. His areas of special interest and expertise include nootropics, anti-aging and regenerative medicine, weight management, and the chronobiology of performance and health. ABOUT THE HOST Angela Foster is an award winning Nutritionist, Health & Performance Coach, Speaker and Host of the High Performance Health podcast. A former Corporate lawyer turned industry leader in biohacking and health optimisation for women, Angela has been featured in various media including Huff Post, Runners world, The Health Optimisation Summit, BrainTap, The Women's Biohacking Conference, Livestrong & Natural Health Magazine. Angela is the creator of BioSyncing®️ a blueprint for ambitious entrepreneurial women to biohack their health so they can 10X how they show up in their business and their family without burning out. Angela's BioSyncing®️ Blueprint is currently closed. Click here to get on the waitlist. The High Performance Health Podcast is a top rated global podcast. Each week, Angela brings you a new insight, biohack or high performance habit to help you unlock optimal health, longevity and higher performance. Hit the follow button to make sure you get notified each time Angela releases a new episode. CONTACT DETAILS Instagram Facebook LinkedIn Affiliate Disclaimer: Note this description contains affiliate links that allow you to find the items mentioned in this video and support the channel at no cost to you. While this channel may earn minimal sums when the viewer uses the links, the viewer is under no obligation to use these links. Thank you for supporting the show! Disclaimer: The High Performance Health Podcast is for general information purposes only and do not constitute the practice of professional or coaching advice and no client relationship is formed. The use of information on this podcast, or materials linked from this podcast is at the user's own risk. The content of this podcast is not intended to be a substitute for medical or other professional advice, diagnosis, or treatment. Users should seek the assistance of their medical doctor or other health care professional for before taking any steps to implement any of the items discussed in this podcast.

In Episode 157 of the PricePlow Podcast, Mike and Ben sit down with Kyle Thomas, Chief Commercial Officer of Nutrabolt, to discuss the company's groundbreaking partnership with The Hershey Company. Kyle, who joined Nutrabolt in 2021 after years in the Coca-Cola system, provides unique insights into how this collaboration came to be and what it means for both C4 and the broader supplement industry. The conversation covers not only the recent launch of C4 Whey protein featuring real Reese's and C4 Original pre-workout with Bubble Yum flavor, but also dives deep into Kyle's strategic vision for the brand, the evolution of C4's demographics, and how the company is positioning itself in the ever-growing energy drink market. This podcast was recorded shortly after Team PricePlow's visit to Nutrabolt HQ in Austin, Texas, making for some timely discussion of upcoming innovations. Subscribe to the PricePlow Podcast on your favorite platform and watch on YouTube to stay updated on the supplement industry's biggest moves! https://blog.priceplow.com/podcast/kyle-thomas-nutrabolt-c4-hershey-157 Video: C4's Kyle Thomas Talks Hershey Partnership & Brand Strategy https://www.youtube.com/watch?v=0yzsJca0cNA Detailed Show Notes with Kyle Thomas (0:00) – Introductions & Kyle's Background: A Wild Ride to Nutrabolt (4:00) – The Evolution of Sports Nutrition on Coca-Cola's Radar (9:00) – The Hershey Partnership (16:30) – Brand Strategy & Demographics (27:00) – Product Development & Testing (35:00) – Master Branding Strategy (42:00) – Keurig Dr Pepper Partnership Where to Follow Kyle, Nutrabolt, and C4 Kyle Thomas on LinkedIn @C4Energy on Instagram @Cellucor on Instagram Cellucor News on PricePlow Thank you to Kyle Thomas and the entire Nutrabolt team for hosting us at their headquarters and sharing insights into their exciting partnership with The Hershey Company. We're looking forward to trying more innovative collaborations in the future! Stay up to date with Cellucor/C4's latest releases by signing up for PricePlow's news alerts, and don't forget to subscribe to the PricePlow Podcast and leave us a great review!

Indie Hacker Special! I speak to Piyush Patel, the founder of AmplifyX Labs and a prominent voice in the micro-SaaS and indie hacking space. From bootstrapping projects to building in public and exploring AI-powered tools, Piyush shares invaluable insights into his personal journey, product development strategies, getting your first customers and the future of micro-SaaS. This episode is packed with actionable advice for aspiring indie hackers, developers, and entrepreneurs who want to build and scale meaningful projects without funding. He also shares how numerology and astrology influence both his personal and business decisions, and reveals the surprising story of how he used Bumble to gain new customers!in this conversation we talk:Why most people don't know what indie hacking is, and how the small but vibrant community in India is shaping the space.Piyush's step-by-step ideation process for identifying and validating product ideas.Building Minimum Viable Products (MVPs) and finding your first customers without breaking the bank.Common mistakes to avoid when developing and scaling a micro-SaaS product.The key strategies Piyush uses to scale his projects while staying bootstrapped.Why he prioritizes “selling before building” and “distribution before product” as the foundation for success.Navigating tough calls, feature prioritization, and knowing when to pivot or shut down a project.His thoughts on the rise of "AI for X" products and how indie developers can leverage AI to innovate.Opportunities and threats AI presents for the indie hacking community.Learning from failure and building emotional resilience as a bootstrapped founder.Tips for indie developers to build their personal brand on YouTube and social media.How to prioritize marketing efforts across channels like SEO, Meta, TikTok, and email marketing.Why networking is crucial for indie developers and Piyush's advice for making meaningful connections.How public speaking has helped him grow personally and professionally, with tips for beginners.Where Piyush sees the micro-SaaS industry heading in the next 5–10 years.Advice for aspiring indie hackers: Qualities you need, mistakes to avoid, and how to stay motivated.What he would do differently if he had to start over from scratch.and much more!Links https://www.linkedin.com/in/whatsuppiyush/https://bento.me/whatsuppiyushhttps://x.com/WhatsUpPiyush  Hosted And Produced by Neil Patel https://www.linkedin.com/today/author/neilpatel2 Enjoyed this episode? Don't forget to subscribe and leave us a review! Share this episode with your friends. Listen and Subscribe to More Episodeshttps://www.indianstartupshow.com/ Music by Punch Deck.https://open.spotify.com/artist/7kdduxAVaFnbHJyNxl7FWV

saas.unbound is a podcast for and about founders who are working on scaling inspiring products that people love, brought to you by https://saas.group/, a serial acquirer of B2B SaaS companies. In episode #23, Anna Nadeina talks with Rory, founder and CEO at trumpet, auto-personalised & interactive digital sales rooms. ----------Episode's Chapters-------------- 00:00 - Introduction to Rory Sadler and trumpet 05:01 - Identifying the Problem trumpet Solves 12:23 - Leveraging Communities for Growth 18:17 - Adding Services to the Product 24:25 - Balancing Customer Feedback and Product Development 31:33 - Fostering a Growth Mindset in Team Members 37:55 - Biggest Wins and Learning Moments Rory - https://www.linkedin.com/in/rory-sadler-trumpet/ trumpet - https://www.sendtrumpet.com/ Subscribe to our channel to be the first to see the interviews that we publish twice a week - https://www.youtube.com/@saas-group Stay up to date: Twitter: https://twitter.com/SaaS_group LinkedIn: https://www.linkedin.com/company/14790796