Webflow CMS → Vercel + Supabase: rebuilding CancelTimeshare.io into one unified stack
Post:
We recently migrated Cancel Timeshare from Webflow CMS to Vercel + Supabase and, in the process, replaced Memberstack plus a separate no-code admin panel with a more unified architecture.
The original stack got us moving fast, but it became increasingly fragmented. Content lived in one system, member functionality in another, and internal workflows in a separate admin tool. That setup was workable — until it started slowing down iteration.
The rebuild was really about consolidation.
By moving to Vercel + Supabase, we were able to bring the frontend, data model, auth, and internal workflows into a setup with fewer handoffs and more control.
A few benefits we’ve felt from the move:
-
a cleaner overall architecture
-
less dependence on layered no-code tooling
-
more flexibility in how content and operations are modeled
-
easier room for custom product logic
-
one stack that feels built for the business, not patched around it
For us, this was less about “no-code vs code” and more about recognizing when a project had outgrown a stack made of separate tools.
Would love to hear how other teams think about that transition point — especially when moving from Webflow-era speed to something more custom on Vercel.