The 30-minute custom website that took us a year to build

Last week we built a custom website for a Brooklyn arepería in 30 minutes.

Not a Squarespace template. A genuinely custom-built, bilingual, mobile-first restaurant site — menu typography that handles Spanish and English at the same density, embedded Google Business Profile, sample imagery labeled honestly, the right schema markup so the site shows up correctly in both Google search and AI answer engines. Tiny video-background hero loop that plays even on mobile. Horizontal scroll for the in-store market section. The works.

30 minutes from "let's pitch them" to a working build to walk into the discovery call with.

The site may need revisions after the prospect sees it — that's fine, revisions are also minutes. But the structural build, the actual hard-decision work, took less time than most agencies spend on their kickoff call.

This is what the previous year of work was for.

The first one was nothing like 30 minutes

Our first real client was Asian Street Gourmet — a Cantonese family kitchen in Brooklyn. Real business, real owners, real production site. Not a sample, not a demo, not practice. Built from scratch on customer request, then improved on customer feedback over months.

That site took a lot of time. We learned by doing — figuring out the bilingual menu typography, the order flow, the admin auth, the database setup, the kitchen-alert integration, the schema markup that helps a Brooklyn restaurant show up when someone searches "Cantonese food near me." The site is live, the client is real, the work was substantial.

But what it taught us went past the site itself. Most of the decisions that took the longest — typography for bilingual menus, the layout language for an order flow, how the admin sits behind the public site, the honesty constraints we set on imagery and reviews — none of those should have to be rediscovered every time we build a website for the next local business.

That's where most agencies get stuck. They take a client's money and learn on the project. The next client gets a slightly improved version, but the agency has to rediscover most decisions again because nothing was systematized. Every new project is a partial rebuild.

After Asian Street Gourmet shipped, we made a deliberate choice. The next site wouldn't be built manually. We'd build a system that compressed every decision we'd already made into something the system itself could make automatically.

What the system is

Three components. None of them are individually exotic — agencies have been talking about systematizing builds for years. The combination is what actually moves the needle.

Claude Code skills. We codified what we'd learned on Asian Street Gourmet into a set of skill files — written instructions that load into Claude Code (the AI coding tool) at the start of every new build session. The skills tell the agent how to make the same decisions we'd already made: which template family to pick for which vertical, which preset to apply, what schema markup to generate, what honesty rules to enforce, what to never invent. Imagine handing a junior developer a stack of "how we do things here" docs that get applied to every new project automatically — that's what the skill files do, with a faster reader.

MCP connections. MCPs (Model Context Protocols) let Claude Code talk to external services without us writing custom integration code per project. We wired up the relevant ones: a brand-extractor that pulls colors and fonts from a prospect's existing online presence, a generative-imagery service for hero stills and ambient video loops, deployment hooks for Vercel, booking integration for Cal.com. With the right MCPs in place, the agent can fetch a prospect's brand, generate visual content, build the site, and deploy it — all in the same session.

Configurations for business variations. This is the most important part. Each vertical of local business needs different patterns. Restaurants need bilingual menu support and online ordering integration. Clinical practices need appointment-booking flow and insurance copy. Contractors need sticky phone CTAs and licensing language above the fold. Real estate firms need photo galleries with strict aspect-ratio handling and virtual-tour integration. We built configuration profiles for each — preset definitions, template choices, schema templates, copy patterns, honesty constraints. The agent loads the right config for the right vertical before it touches a single line of the actual site.

Eight sample sites, each adding one capability

After Asian Street Gourmet, we built eight sample sites. Each one wasn't a portfolio piece, wasn't a speculative pitch, wasn't trying to win that fictional client. Each one was an exercise to add one specific capability to the system.

A taquería sample established the preset system itself — reproducing a real hand-built identity exactly as --site-* design tokens. This was where the whole "one template, many presets" approach got proven.
A dental practice sample built the trust-first clinic template family — credibility-over-spectacle layouts with deliberately omitted motion, because dental owners don't want their site to feel like an art piece.
A physical therapy sample proved that a single template plus a different preset produces a site that doesn't look or feel like the dental one — fresh green, rounded, fundamentally different visual register, same underlying code.
A massage studio sample built the experiential capability — one signature scroll-triggered motion moment using GSAP and Lenis, with a reduced-motion fallback for accessibility. The lesson encoded: pick one signature, never stack effects.
A residential electrical contractor sample built the local SEO capability — locality-anchored content per service area (genuinely unique per page, never doorway content) and a fully compliant review CTA that asks every customer and never sentiment-gates (which is illegal under the FTC rule).
A luxury real estate sample built the generative imagery capability — FLUX stills and Kling image-to-video loops via fal.ai, behind an ambient-field component, gated to desktop for performance reasons.
A patisserie sample built the horizontal Vitrine pattern — a desktop scroll-scrub experience that gracefully degrades to native swipe on mobile, on the same DOM with no hydration switch — and established the "label every sample image" honesty pattern.
A boutique law firm sample built the quiet-authority register — a typographic signature instead of a motion one, editorial drop-caps and hairline rules. Proof that the system can do confident restraint, not just sensory richness.

Eight samples. Eight capabilities. None of them needed to convert into a client to be worth the work, because each one made every future real client's build a little bit faster and a little bit better.

The Venezuelan arepería build

When a Brooklyn arepería approached us recently — bilingual ES/EN, appetite-first, real prospect — the system was ready.

Here's what those 30 minutes actually contained:

The agent loaded the restaurant configuration profile, the appetite-first preset, and the bilingual capability
It pulled in the right template family (the same one as the patisserie sample) and applied a warm food-led palette
It generated a tiny mobile-safe video-background hero loop using the generative imagery MCP, then stitched it to seamlessly using ffmpeg
It built the horizontal scroll signature for the "in-store market" section (because that's the restaurant's differentiator, and the system has that pattern from the patisserie work)
It generated the correct LocalBusiness schema markup with bilingual descriptions and menu data
It embedded the prospect's Google Business Profile as a click-through, not a raw pin
It labeled every sample image honestly ("Sample — the live site uses the restaurant's own photos") and made social proof render-when-present so nothing got invented

What the system didn't do in those 30 minutes: invent prices, fabricate reviews, generate convincing-looking fake photography that could be mistaken for real food, write copy that didn't match how the actual restaurant operates. The honesty constraints aren't post-hoc checks — they're baked into the configuration. The system can't violate them because it doesn't have the option.

The site may need revisions after the prospect sees it. They may want a different photography direction, different copy emphasis, more or fewer sections. Revisions are also minutes — the system handles them with the same speed. What doesn't change in revisions: the structural decisions are already right.

What this means

If you're a local-business owner: the meaningful part isn't that we ship faster. It's what fast unlocks. We can show you a working version of your website at the discovery call, in your vertical, on your phone, while you're sitting there. Not a deck. Not a portfolio dump. The actual site. And revisions to that site can happen during the same call.

The $1,500 starting price isn't a discount. It's what the work actually costs once the structural decisions have been compressed into a system that's already made them. Most agencies have to bill the discovery time, the experimentation time, and the learning-curve time — that's why their proposals start at $5,000. Our system collapsed those into one-time investments that already happened. We don't bill them to you.

If you're a founder or operator reading this: the lesson is that the system is the product, not the output. Each sample site we built wasn't trying to win that hypothetical client. It was trying to add one capability to a framework that compounds across all future real clients. Asian Street Gourmet was where we learned by doing. The eight samples were where we systematized what we'd learned. The arepería was where the systematization started paying off in obviously different shape. Every local business we work with from this point forward inherits the accumulated benefit of all of it.

That's what Kaizhen actually is. Not a website agency that's faster than the others. A website-building system that's been deliberately engineered to compress the work that traditionally took weeks into work that takes a session.

What comes next

We're going to keep adding capabilities to the system. Each new sample isn't decorative — it encodes the next capability. Independent law firms will sharpen the quiet-authority register further. Multi-location physical therapy practices will push the system on owner-dashboard sophistication. Each new vertical we deliberately learn pushes the framework forward, and every client benefits from the most recent version of it.

If you're a local-business owner and you want a real conversation about what your specific business website should look like, the discovery call is free either way. We'll show you a site in your vertical built using whatever the system already does. If your business pushes the system in a new direction we haven't worked through yet, we'll add that capability — and you'll have a site built on a sharper framework than yesterday.

The booking flow is on our websites for local businesses page. No commitment, just a 30-minute conversation about what your situation actually needs.

(That 30 minutes is also enough time to build the site, if it goes well.)