Original Summary

I’ve built QuoVeo, a quotation/proposal SaaS for small service businesses. One product decision we spent a lot of time on was what should happen when a client asks for changes after a proposal is already sent. The obvious approach is to create V2, V3, V4, etc. But that quickly creates confusion around: - which version is current - which signature belongs to which version - whether payments/invoices stay connected - whether a revised proposal is still the same deal Our approach is: - allow a limited number of in-place revisions - keep the same proposal link, invoice, payment history and context - if the change becomes a genuinely new deal, fork it into a new proposal I’m curious how other SaaS builders would handle this. Would you prefer every revision to become a new record, or keep revisions attached until the deal meaningfully changes? Product for context: https://quoveo.vektrascalesolutions.com   submitted by   /u/DixitaDevi [link]   [comments]

  • 情报分类：商业与市场研究
  • 分类依据：内容涉及商业、投资或市场动态
  • 信息来源：Reddit · SaaS
  • 发布时间：2026/9/16 12:04:53