
🚀 Scaling an engineering team without traditional managers ⚙️ How we've done it at @alanengineering ⬇️ medium.com/alan/scaling-engi…

@avec_alan, previously: @Intercom

🚀 Scaling an engineering team without traditional managers ⚙️ How we've done it at @alanengineering ⬇️ medium.com/alan/scaling-engi…

We wrote about Hopper, the agent we built at Alan. It started as a coding agent for builders. Today 80% of Alaners use it, and 25% of our merged PRs come from it. More technical posts to follow in the coming weeks/months! medium.com/alan/hopper-we-bu…

Ever wondered how Alan reimburses health claims so fast? Spoiler: we automated 70% of document processing. We just dropped the first article of our doc processing series — stay tuned for more on how we're scaling this across other countries and use cases. buff.ly/2Lu7aWD

📣 We’re doing something a bit different at @alan: an on-site Engineering Recruitment Day 📍 Paris (Alan HQ) 🗓️ Tue, March 17 ⏳ Apply by Wed, March 11 👉 jobs.ashbyhq.com/alan/a8b3fe…

We wrote about how we built this momentum, the systems behind it, and what's next: alan.com/en/blog/discover-al…

Everyone Can Build is now real: * Faster iteration. Broader ownership. * Teams unblocked. * Code became our shared interface. #everyonecanbuild

We started with foundations: * Running the product locally * Standardizing on @cursor_ai * Dedicated crew for setup & AI workflows

283 PRs later from designers, PMs, and Ops at Alan. Small text edits → layout tweaks → full features. #everyonecanbuild

A button color took weeks to ship. Not because it was hard—but because the designer who spotted it couldn't fix it themselves. So we asked: what if everyone could build? #everyonecanbuild

"Claude did it almost on its own while I was boiling water for my tea" That's how our engineers now fix flaky tests at Alan. Read more about our journey from manual debugging to AI-powered investigation in our latest article 👇 medium.com/alan/from-gut-fee…

💬 Instead of waiting for “vibe-coding” tools to scale… What if we made existing engineering tools and workflows more accessible?

So, when should you use it? ✅ Rapid experiments: landing pages, waitlists, MVPs ✅ Small teams: can handle an app with a few engineers ❌ Large teams or large codebases: not ready yet

⚠️ The rough edges - No branches → every save goes straight to main (no workflow/CI) - Tests & linters exist, but don’t run on Lovable - File sprawl: creates new files instead of editing → dead code risk - Tagger conflicts (e.g. breaks map rendering)

✨ The good - Instant feedback loop: prompt → preview → revert if needed - Custom domain deployment, effortless updates - Supabase integration (auth, edge functions, env vars) worked seamlessly - Proactive nudges: refactoring + security alerts keep code healthy

In theory, this is exactly where vibe-coding tends to break down. And yet—Lovable delivered. Here’s what stood out 👇

💡 Should you use @lovable? Over the past few months, I’ve had the privilege of watching yamas.tech/ come to life built with Lovable. It’s not “just a landing page.” It’s a full-fledged product: frontend with complex states + AI multi-agent backend.