Zimenezi zimachitika

It builds your site

You leave one sentence. It comes back with a named company and a live site you can open on your phone.

What the log looks like

Every line above is one the employee actually prints. The company in it is an illustration so the log reads as a whole; it is not a customer.

Pa mphindi

Kodi ndi kwa ndani?: A founder who has an idea and no evening free — or no idea yet, and would rather argue with something concrete than stare at an empty page.

Momwe zimagwira ntchito

1. It reads your brief. One sentence is enough. If you asked it to pick instead, it profiles you from what is honestly on file — your email handle, a company domain if it is not a consumer one, the briefs of companies you already run here — then proposes three ideas and commits to one, saying which runner-up it passed over.
2. It sizes up the market. It plans three to six searches covering competitors, pricing and demand, runs them, opens the top result or two, and writes what it found into a research notes document the rest of the build reads from.
3. It picks the name. Five candidates with a reason each, one chosen. Pronounceable, spellable on a phone call, two words at most. The other four stay on the company so you can switch later without inventing anything.
4. It takes an address. A subdomain is claimed and starts answering immediately with a holding page. A dead link during a build is worse than a plain page, so there is never a moment where the address exists and returns nothing.
5. It plans the site. Page set, a section outline for each page, a tone, and design tokens picked from a fixed menu. Home, about, pricing and contact are enforced by us rather than left to the model — a site without a contact page is not a business.
6. It writes each page. One page at a time, against its own outline: a title under sixty characters, a description in the 140-158 band, exactly one heading, and at least two hundred words of specific copy. Placeholder text, lorem ipsum and empty pricing tiers are rejected in code before the page is ever offered for publishing.
7. It publishes what passes. Every page goes through the twelve build rules. Eight of them block outright: a failing page is handed back with the reasons and rewritten once. Anything that still fails is left off the site and queued as the first job of the next shift, and the report says so.
8. It checks the site over the wire. It fetches each published URL as a stranger would and looks for a 200. If a page answers anything else, it does not call your site live — it says which page failed and puts it on the list.
9. It writes the founding documents. Mission, market research and roadmap, grounded in the research notes. Where the notes are thin it says so rather than inventing a source, and the competitor names it lists are the ones the searches actually returned.
10. It queues the first tasks. Three concrete jobs, each finishable in one shift. Any page that failed the rules goes to the top of that list.
11. It wraps up. A welcome note from the company inbox recapping what it built, and a one-page report ending in a single question.

Chifukwa chiyani

• A live web address of your own, serving from the moment the build starts.
• Four pages at minimum — home, about, pricing, contact — plus an FAQ and up to two more if the plan calls for them.
• A company name, with the four runners-up kept so a rename is one tap rather than a blank field.
• A working inbox on its own domain, so replies land somewhere real.
• Mission, market research and roadmap documents written from the research it actually did.
• A receipt for every step, in order, with the model and the timings on each row.

Mafunso pankhaniyi

Makampani ogwirizana

← It drafts what needs your yes · Ntchito zonse · It names the company →