Why I moved from pure no-code to AI-assisted development

For years, pure no-code was enough. Glide alone could take a client from a spreadsheet to a working internal tool in a week — and for a lot of small businesses, that's still the right answer.

But somewhere in 2024 the ceiling moved.

The old shape of a project

A typical Glide build looked like this: talk to the client, sketch the data model, wire up screens, add computed columns for anything remotely custom, and negotiate around the parts the platform couldn't do. If they wanted a specific integration or a piece of logic that didn't fit into visual components, my honest answer was usually "not without a real backend."

What changed

With Claude writing production-quality code and Lovable generating and iterating on a real full-stack app in the browser, the "not without a real backend" answer stopped being true. I can now sit with a client, describe what they need, and have a working prototype — real database, real auth, real logic — inside an afternoon.

That doesn't make Glide obsolete. It makes it a choice instead of a constraint. For a lot of internal tools, Glide is still faster and easier to hand off. For anything with real business logic, custom integrations, or a public-facing surface, I reach for Lovable + Claude.

What this means for clients

The practical impact: projects that used to be "sorry, that needs a developer" are now on the table. And projects that used to take three months take three weeks — because I'm not translating between "what the client said" and "what the platform can do." I'm just building what they asked for.