The big issue you’re going to run into is maintenance. Updating copy, updating design, updating images / logos, etc…
Right now you can do it yourself, and maybe you even have the time to export and re-integrate every little copy, logo, image, design, and color change.
What typically happens is you get busy.
You’re the founder of a SaaS, and other things become bigger priorities as interest grows from your product.
You’ll find yourself not having the time to make a change in Webflow, export, and re-integrate.
If all goes well, you’ll want to hire professionals to handle the marketing copy on your public facing website.
They’re non-technical and don’t know how to re-integrate with your application code.
The most common result is that your public facing website become stale, outdated, and doesn’t help you turn visitors into customers.
This has a negative effect on your business.
What most do is separate their application code from their Webflow site via subdomains.
example.com ← Webflow hosted site, easy updates for non-tech
example.com/blog ← Webflow hosted blog, easy updates for non-tech
app.example.com ← application, everything behind a login, programmers only
For the application side, the layout, design, css, etc… it’s typically all very basic and color themes are kept in sync. That’s usually a simple task.
Now you can host on Webflow for your site + blog.
- Make rapid changes based upon market conditions
- Update messaging
- Refresh branding
- Create relevant blog posts
Make product updates without the laborious task of re-integrating application code.
Without requiring any engineering resources (or their time).
…all done by non-technical folks who are experts in those areas (branding, design, blogging, SEO) while the engineering experts stay focused on making an awesome product.
In fact, this is a big use-case for Webflow.
Here are a few examples:
Hope that helps!