March 8, 2026 5 min read
The Case for a Zero-Code CMS on Every Client Project
A restaurant should not need a developer to change their menu. That single sentence has shaped every client project I have shipped.
ProductClient WorkEngineering
When I built Tomatello, a premium Italian dining brand in Europe, the founder had one non-negotiable. She never wanted to email a developer to update the menu. She wanted to open her laptop on Sunday night, edit dishes, and see them live on Monday morning. That reframed the project.
Why not just use WordPress
WordPress works. It also brings 400 megabytes of database, a plugin ecosystem that will eventually be a security problem, and a page speed score that hurts SEO from day one. For a small business it is overkill in the wrong direction. Powerful where they do not need power, weak where they do.
What a zero-code CMS actually is
For most client projects I build a small custom admin panel on Firebase or Supabase. The client logs in and edits menu items, blog posts, gallery images, whatever their content actually is. The public site reads that content at build time or on demand. Total code footprint is usually under 800 lines of React. Total monthly cost is often zero on free tier.
- Client owns the content, permanently. No developer in the loop for basic changes.
- Site stays fast because it is not running a legacy CMS engine.
- Analytics can be layered in without a plugin marketplace.
- When the client grows and wants to add ordering, subscriptions, or a mobile app, the data model is already clean and ready to extend.
Where this changes the business relationship
The client stops seeing you as a cost center they have to email every time something needs to change. You stop being on the hook for a "small update" that turns into a two-hour context switch. You get to focus on the next thing worth building for them.
The website stops being a marketing brochure and starts being a real operating layer for their business. That is the shift that turns a $3K website contract into an ongoing relationship worth ten times more over three years.
A website you cannot update yourself is not a website. It is an invoice waiting to happen.
Keep reading
Why I Am Building AI Consumer Products Solo in 2026
For the first time in software history, one engineer can ship a real consumer AI product in a weekend. Here is why I left founding engineer roles to focus on it.
The Founding Engineer's Playbook: What You Actually Do in the First 90 Days
Founding engineer roles look glamorous from outside. Inside, the first 90 days is a specific sequence of unglamorous decisions that either set the company up or break it.