Yassine Hinnach

Your engineering team's AI adoption rate is now your most important competitive metric. No it's not DORA, velocity or even revenue per engineer. Because in 2025, the gap between AI-native and AI-resistant engineering teams isn't linear. It's exponential !! At Lightdash, we made a controversial decision and gave our engineers 30 days to become AI-native. If they couldn't ship production features every day with AI then there was no longer a place for them on the team. Everyone stepped up! The engineers that adapted best? They're not writing code anymore. They're architecting systems, reviewing AI output, and shipping 5x more features that customers actually pay for. The engineers resisting this are at our competitors, still debating whether GitHub Copilot counts as "real programming." It should feel uncomfortable but if your engineering team isn't shipping at least 50% of their code through AI tools today, you're already 12 months behind. By next year, you'll be competing against teams where humans haven't written a line of boilerplate in months. Yes, quality matters. Yes, understanding matters. But the teams obsessing over "AI readiness frameworks" while their competitors ship? They're writing beautiful documentation for products that will never see market fit. Stop measuring how well you're adopting AI. Start measuring how much faster you're beating competitors because of it. The future belongs to teams who ship, not teams who study.

90

55 Comments

I caught up with a friend who works at a mid-size Swedish tech company. Over the last 4 months, their shipping velocity has almost doubled – not because they hired more engineers, adopted some new agile framework, or worked late nights. It came down to a single change in how they build products: they started using Lovable to prototype features instead of writing traditional spec docs. Before Lovable, it usually went like this: PMs drafted long PRDs, trying to anticipate every detail. Multiple stakeholders reviewed these documents, leaving comments and raising concerns. The document grew with each iteration. Alignment meetings were frequent but often resulting in ambiguity. Engineers often began implementation while details were still debated. Inevitably, confusion emerged about trade-offs, timelines got pushed, and features shipped incomplete or scaled back. Now, PMs build interactive prototypes directly in Lovable. These aren’t wireframes or rough mockups – they’re fully clickable, end-to-end experiences that feel like the real product. Engineers don’t have to guess what the flow should be. Designers don’t have to explain interactions. Everyone sees the same thing, from day one. The end result is fewer meetings, fewer misunderstandings, fewer rewrites. What used to take weeks of coordination now happens in a single day. This is what has provided the most value for enterprises using Lovable so far. Over time, the increase of clarity and velocity saves the companies millions of $ in wasted effort.

2,480

175 Comments

YC has two distinct phases that most people don’t realize. For the first two months, you’re in “PMF mode.” Building product, talking to customers, iterating rapidly, finding product-market fit. The focus is entirely internal. Then something dramatic happens in the final 3-4 weeks. YC shifts into “fundraising mode.” Suddenly your group partner meetings are about valuation, dilution scenarios, investor introductions, and demo day preparation. The shift can feel overwhelming. One week you’re debugging voice AI latency issues. The next week you’re modeling how much runway different funding amounts will give you. The genius of this approach is the timing. Right when you’re gaining real momentum with your product, YC creates an environment where investors feel FOMO about getting in. There are thousands of investors but only 100-150 companies per batch. When every investor knows this is their one shot at the best new startups, they move fast. The transition from building to fundraising felt like switching from practicing in your garage to performing at Madison Square Garden. Same songs, completely different energy. Most founders think about fundraising as a distraction from building. YC makes it feel like the natural evolution of what you’ve been building toward. Good luck to all the S25 batch founders as they start fundraising. Hit me up if you have any questions or need investor intros!

139

16 Comments

Big news. We've launched Thena + Anthropic integration 🎉 Claude can now see what your support team sees with real-time access to customer support data via Thena’s Model Context Protocol (MCP). - Identify product issues, patterns and opportunities - Understand risk signals and build out account management plans - Get real insights from real time conversations for product development and Engineering cycles - Connect with peer MCP servers to unify and monitor the overall business state This means Claude can: - Answer support queries with full context Flag bugs, churn risks, and feature gaps. - Create and update tickets contextually - Summarize and surface insights for product, eng, success, and beyond Support data is no longer siloed. It’s now active fuel for every part of your business.

60

5 Comments