Webflow CMS → Vercel (NextJS) + Supabase: rebuilding CancelTimeshare.io into one unified stack
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 helped us move quickly, but over time it became increasingly fragmented. Content lived in one system, member functionality in another, and internal workflows in a separate admin tool. It worked — until iteration started getting slower than it should have.
This rebuild was really about consolidation, but also about building on a stack that let us move faster in a different way.
On the frontend side, we used v0 heavily to iterate on UI direction, explore flows quickly, and tighten up the product experience without getting stuck in long design-development loops. On the engineering side, we used Claude Code and Codex to help refine architecture decisions, pressure-test implementation patterns, and speed up the transition from a layered no-code setup into a cleaner application structure.
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.
We also used the rebuild as a chance to introduce agentic tools for users, giving the product a more intelligent layer instead of treating it as just a marketing site plus back office. That shift opened up a much better foundation for guided flows, smarter user interactions, and tooling that feels native to the product rather than bolted on afterward.
A few benefits we’ve felt from the move:
-
cleaner overall architecture
-
less dependence on layered no-code tooling
-
faster UI iteration with v0
-
more flexibility in how content, auth, and operations are modeled
-
better room for custom product logic and agentic features
-
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 — and then using newer AI-native workflows to make the rebuild faster and more deliberate.
Would love to hear how other teams think about that transition point, especially when moving from Webflow-era speed to a more custom Vercel-based stack — and whether tools like v0 and coding agents are changing how you approach that jump.