Original Summary

I’m curious how other SaaS founders are handling this now. AI has made the first version ridiculously fast to build. But I’ve also seen the opposite problem: You can get pretty far into implementation before realizing you never really decided what version of the product you were building. Not “did we write a 40-page PRD.” More basic stuff: -what’s actually in v1 -what isn’t -assumptions we’re making -where the risky parts are -what the architecture needs to support later -what the business expects vs. what engineering is implementing I’m a software engineer and I kept running into that translation problem, so I built a free tool that takes a product idea and creates two versions of the plan: an executive blueprint and a technical blueprint. I built it, so obvious disclosure there. It’s free and part of Pilot Spring, not a separate SaaS I’m trying to sell. What I’m more interested in is how people here handle this themselves. If you’re using Cursor, Claude Code, Lovable, Replit, etc., what do you give it before you start building? A PRD? Architecture notes? A giant prompt? Or do you just start and work it out as you go?   submitted by   /u/Bandbyneckbeard [link]   [comments]

  • 情报分类：开源项目与落地
  • 分类依据：内容涉及项目实践、创业、副业或变现
  • 信息来源：Reddit · SaaS
  • 发布时间：2026/9/25 05:46:06