We pivoted our marketing vision: Why prompt-generated sites need a real CMS backend

When we first built NextBlock CMS, we positioned it as a developer-focused, high-performance alternative to WordPress and decoupled headless platforms. It featured 100/100 Lighthouse performance, Supabase integration, and a clean Notion-style Tiptap block editor.

However, watching the rise of AI tools like Lovable, Bolt, and v0 highlighted a glaring market issue: The Day 2 Maintenance Crisis.

Prompting a landing page or web app into existence takes minutes. But what happens two weeks later when a copywriter wants to fix a typo, update pricing, or add a blog post?

• You have to open the repo.
• You have to re-prompt the AI (risking layout regressions).
• You have to run a git commit and wait on CI/CD redeploys.

We realized NextBlock solves this problem natively:

1. One-Click Deployment: A completely free Vercel + Supabase deployment pipeline that sets up the database, storage, and app in a minute.
2. Bring Your Own AI Subscription: Cortex AI now acts as an open MCP server. Users plug in their own Cursor, Claude, or ChatGPT accounts to generate pages using tokens they already own.
3. Everyday Visual Editing: AI generations land as structured JSONB inside a visual CMS canvas. Content teams can edit, delete, and duplicate sections intuitively with slash commands without ever seeing a terminal.

We launched a 30-day free trial (completely free to start, no credit card required) to let founders test this bridge between rapid AI generation and long-term site operations.

Would love to hear how other founders manage non-technical client hand-offs after using prompt-based website tools!