Build it,
hand it off,
walk away.
Every site you ship ends the same way. It goes live. Then the emails start. Can you change this headline. How do I update the prices. The contact form stopped emailing me. You meant to ship a website. You accidentally signed up to be the IT department.
Lanlan is the platform that lets you actually leave.
Because after the handoff, your client makes those changes themselves. They type change the headline to … into Tell Lanlan, right in their dashboard, and it edits the site — with the same tools you built it with, following the brand guide you set up. No AI subscription to buy, no MCP to configure, no you.
+ Mostly written for developers shipping client work, but every recipe holds for in-house builds and indie projects too. If you're shipping for yourself, you're just on both sides of the handoff.
type lanlan anywhere · press t for tools · ? for shortcuts
build
You and your agent. Files are HTML/CSS/JS. Edits are surgical. Deploys land in 15 seconds.
invite
One email. The client lands in a dashboard they actually understand, and can change the site on day one: they tell Lanlan what they want, in plain words. Analytics, forms, version history and billing sit alongside.
detach
Drop yourself to admin. Or leave entirely. The site is theirs. So is the Stripe, the domain, and the form submissions. The next change request goes to Lanlan, not to you.
Not all of it is MCP back-and-forth.
Every site you build comes with this. Analytics, forms, version history, billing, sharing — the dashboard your client lands in when you hand it off. And Tell Lanlan: the same tools you drive from your agent, with Lanlan's own agent at the wheel, so after the handoff your client asks for changes in plain words instead of emailing you. It reads the PDFs, Word, Excel and PowerPoint files they drop in, and on a site that waits for Publish nothing goes live until they say so.
app.lanlan.site — if you're already signed in, this drops you straight there.
What this means in practice.
Every bullet below is a specific email you do not get.
-
The "can you change this headline" email you don't get.
They ask Lanlan instead. Tell Lanlan is built into their dashboard: they say what they want, it makes the edit, and they see it on the page. Swap a photo, update the prices, add a page for the new service. If their site waits for Publish, nothing goes live until they press it.
-
The 7pm "I broke the homepage" email you don't get.
Every published version is kept. The client hits Restore. They're fine. And if they'd rather check changes first, their site can wait for them to press Publish.
-
The "the contact form stopped working" email you don't get.
Forms ship with the platform. Submissions hit their inbox, not yours. Spam protection on by default.
-
The "Google Analytics is asking me to verify something" email you don't get.
First-party analytics. No tag to embed, no cookie banner to write, no GA console to log into.
-
The "the domain expired" email you don't get.
Domains are end-to-end. Bought through Lanlan, they renew automatically while the site is Pro. Connected ones never leave the client's registrar.
-
The "how do I take payments" email you don't get.
Stripe is a primitive. The Stripe account is theirs, not a connected account routed through us.
-
The "the new page I made looks weird" email you don't get.
The site has a brand guide. The agent reads it on every edit — yours, or Tell Lanlan in their dashboard. Six months from now, new pages still look like the site you built.
Here's how it actually works.
A real session, start to finish. Edit a client's site, ship it, hand it over.
Cursor, Codex, Antigravity, opencode, Cline, Continue, Zed — the install path looks similar. The engine doesn't care which agent's driving.
What's between you and a live site.
Five hops. No proprietary glue between any of them.
Open standards on every hop. MCP from agent to server. HTTP from server to engine. Files at rest. Nothing locks you in. Tell Lanlan, the agent built into the dashboard, calls the same tools through the same dispatch — whatever you can do from your agent, your client can do from theirs.
The stack you didn't have to assemble.
Every Lanlan site ships with the standard internet plumbing already wired. Eight things you'd otherwise spend an afternoon configuring — or, for the last two, a quarter building.
- Analytics Embed GA4. Write a cookie banner. Set up consent. First-party. No tag, no banner, no console.
-
Sitemap & robots
Generate one. Update it on every page change.
sitemap.xmlandrobots.txtregenerated on every deploy. - llms.txt Hand-author it. Keep it in sync. Generated automatically. The agents reading your site know what's there.
- OG & meta tags Per-page boilerplate. A preview-card debugger tab open all afternoon. Per-page metadata is part of the page. Previews land right the first time.
- Custom domains Cloudflare/Vercel/Netlify console. DNS records. SSL provisioning. Redirects. Bought, connected, and HTTPS-served from one tool call.
- Snapshots & rollback Git ritual. Preview deploy chase. "Which build was the good one again?" The last 20 published versions kept. One click restores any of them.
- A place to build & edit Bolt a CMS onto the site. Or build the client an admin panel. Train them on it. Field the emails when they can't find the button. Tell Lanlan, built into the dashboard. The client says what they want in plain words, and Lanlan builds the page or makes the change.
- Inline editing A visual editor, a WYSIWYG library, editable regions wired by hand, and a save path back to the source. Edit on the page. Click the words or a picture and change it in place, with Undo. It saves to the same files you wrote.
None of this is the headline product. All of it is the reason a site ships in an afternoon and stays shipped.
Today, agents. Tomorrow, anything that speaks HTTP.
MCP is one door into the engine. The protocol allows others.
Today, agents. The full handoff loop runs through any MCP-speaking client. Tomorrow, anything. A Slack command, a GitHub Action, a webhook from your CMS — if it can send an HTTP request, the protocol can carry it.
Your site, as a directory.
Every Lanlan site is a folder of files. Here's this page's neighborhood.
lanlan.site/ ├── _brand/ │ └── brief.md # the design tokens, in markdown ├── _partials/ │ ├── nav.html # shared across pages │ └── footer.html # shared across pages ├── css/ │ ├── style.css # one stylesheet, hand-written │ └── dev.css # this page ├── js/ │ └── dev.js # ~10kb, no framework ├── dev/ │ └── index.html # you are here ├── index.html # / ├── pricing.html # /pricing └── faq.html # /faq
Most builders make you trust their proprietary block model. This is HTML. You can read it. There's no magic underneath.
Every tool, on the table.
Press t to search, or just start typing. Hover any tool to see what it does.
See the handoff.
Build a site, invite a fake client, drop yourself to admin. Five minutes from now you've felt the whole arc.