Hey IH, I just launched Sheetflow.
It is a tool that syncs Google Sheets to Webflow CMS so teams can manage content in spreadsheets and push it into Webflow without manual imports or fragile automations.
I built it for use cases like:
A few useful features:
Would genuinely love feedback on the positioning, landing page, or product itself.
Clean idea — this is one of those “should already exist” tools.
One thing I’d push on:
“Sheetflow” sounds functional, but it doesn’t really signal the outcome (syncing → publishing → control).
Most people landing won’t think “flow,” they’ll think:
“push data live”
“sync CMS faster”
“no manual updates”
Might be worth testing positioning that leans more into outcome > mechanism.
Curious — are users coming more for automation, or for removing CMS friction?
Super helpful, thank you. 🙏 I think the main pull is removing CMS friction, with automation as the bonus on top. People already work in Sheets, so the pain is publishing that content into Webflow cleanly and reliably.
Also agree the messaging should lean more into the outcome. Definitely something I’m going to test. :)
Yeah that makes sense — removing CMS friction is the real pull.
I’d lean hard into that.
Something like:
publish from Sheets to Webflow without breaking things
update your CMS without touching Webflow
treat Sheets as your CMS
The clearer that outcome feels, the less explaining you need.
Right now it’s strong — just needs to hit faster when someone lands.
Launch day for a tool like Sheetflow is mostly about watching where people get confused, not just counting signups. Worth manually onboarding the first few users and asking what they thought it would do before they tried it, naming-driven expectations can be surprisingly strong with spreadsheet products. That usually gives cleaner roadmap signal than feature requests.