Ask HN: Are people vibe coding internal tools at your companies?
Is replacing SaaS with vibe coding a thing? Are there measurable gains? How much work is it to support/maintain these? We took a different approach. Instead of vibe coding separate tools, we built the tool generation directly into the document editor. Type /ai, describe what you need, and the component appears inline in your note. The idea was that the tool and the context that explains it should live in the same place. Works well for internal tooling in our experience. I used to have a single dashboard of all the users in my admin page of my site/startup. Now I've vibe coded a bunch of charts, and actionable tasks I can take from the admin dashboard. It's become my command center for my site/startup. I heard design team is building sites to help better visualize what they want to do. Don't think it's worth the effort vs just Figma, but that's just me. I used it to make an internal service to replace three external api calls. Err five now. yep. SaaS is a dying sector. It just doesn't know it yet