Business operationProject management
Let AI build your Airtable — and flag what to fix by hand
I let an AI agent build Airtable bases through the API, and flag what I must finish by hand.
▶ 3 min · Jun 2026
Business operationAINoCode Development
Ship your own website with an AI code agent
I left Framer's €24/month to build my own site with an AI agent — full design control, near-zero cost.
▶ 4 minJun 2026Difficulty 3Cost: Free
Story behind
I used to host this site on Framer. It cost me €24/month, the upkeep was heavy, and its built-in AI vibe-coding wasn't great. I moved off Framer to save time and money — but mostly to get full design freedom without fussing over every pixel.
An AI code agent makes that trade work: it writes the actual code, so the site is fast, owned, and as custom as I want. The catch is you have to direct it well. Tell an agent "build me a website" and you get generic AI sludge — same font, same purple gradient, same three rounded cards. The quality comes from the process, not the prompt:
code
Discovery → Design system → HTML demo → Build + deploy (what for) (how it looks) (prove it) (own it, live)
Discovery decides what the site says and to whom. The design system keeps every page consistent. The HTML demo lets me judge the look before committing to code. Then the agent builds the real thing and ships it.
Why this helps you
You own it — the code, the content, and the domain are yours. No platform can raise rent or sunset a feature you depend on.
Custom, not template — a real point of view in the design system means it looks like you, not like every other AI-built site.
Cheap to run — free hosting to start and a ~€12/year domain replace a recurring builder subscription.
Editable forever — describe a change in plain English and it ships in a minute; update content by editing a row.
A repeatable method — discovery to deploy works for the next site, and the next client's, too.
How to
Hover a step to open it, or click to toggle.
Before any pixels: who's the reader, what should they feel, and what's the one job of each page? I run this like a design-thinking session with the agent — empathise, define, map each section's purpose. The output is a short brief: positioning, audience, page list, the one idea the site must land.
Good to know
Judge the demo, not the promise — never approve a look from a description. Make the agent show you the HTML first.
Verify the deploy, not the local build — a site that builds on your laptop can still fail on the host. Check the live URL, not just the green checkmark.
The demo is your safety net — flat HTML is throwaway-cheap to iterate. Spend your opinions there, before there's code to refactor.
Design tokens are the multiplier — decide colour, type, and spacing once, name them, and every page inherits consistency for free.
More how-tos