Original Summary

Video above: Framer version on top, the Next.js rebuild underneath (same site, owned rebuild, not the HTML export). Looking for advice from people who’ve been through this. Problem space: a lot of marketing sites are built in no-code tools. Some founders later want a real codebase they own (e.g. Next.js), not an export that still feels locked to the tool. The “full SaaS” version would try to productize that migration. In practice, quality is the hard part: layout, motion, assets, edge cases, support if output is mediocre. So I’m considering sequencing it like this: 1) Document the manual method first (playbook / DIY process) 2) Do a few done-for-you migrations to learn real failure modes 3) Only then productize the repeatable bits into SaaS My hypothesis: for many buyers, a clear method now beats waiting for an incomplete automation. The risk is obvious too: you train people / create content and never get to the SaaS. Questions: • Have you launched a playbook/info product before the SaaS in a technical niche? Did it help or distract? • Where do you draw the line between “learning via services” and getting stuck as an agency? • If quality/support risk is high, would you skip SaaS entirely and stay method + services? Not selling anything here. Genuinely trying to pressure-test the sequencing before I commit months to the wrong path.   submitted by   /u/Due_Peace_5114 [link]   [comments]

  • 情报分类：商业与市场研究
  • 分类依据：内容涉及商业、投资或市场动态
  • 信息来源：Reddit · SaaS
  • 发布时间：2026/10/5 00:06:46