How it works, documented.

The system.

Most studios sell hours and manage them with meetings. We run the same five stations every time — the brief, the scout, the design, the build, the audit — with a human who reads every page before anything ships. One evening of answers from you; those stations turn them into the build.

1. The brief

   You fill a short form in the evening: what you sell, who buys it, what the site must do. Twelve plain questions, and no upload.

   YOU SEE — A form, not a discovery process. No 40-page workbook, no alignment call.

   IT PRODUCES — A written brief. Within one business day: scope and price in writing — what gets built, what it costs, when it's live.

2. The scout

   Research agents map your market: what competing sites do well and badly, what your customers search for, the exact words they use.

   YOU SEE — Nothing yet — unless something in your brief doesn't add up, in which case you get a question, not a guess.

   IT PRODUCES — A content plan: what every page must say to be found and to convince a visitor to contact you instead of the next listing.

3. The design

   A design system is picked and tuned for your category: type scale, spacing, colour, AAA contrast, phone-first layouts.

   YOU SEE — Nothing yet — or the whole site, if you're up late.

   IT PRODUCES — A design system, not a one-off page. Every page you add later inherits it, so the site still looks right in three years.

4. The build

   Real code: Next.js on your GitHub repo, deployed to Vercel, data on Neon Postgres, transactional email through Resend, Stripe or Shopify when you sell.

   YOU SEE — A review link, fast — and a client dashboard that updates as the build moves.

   IT PRODUCES — A production site on standard infrastructure. No page builder, no platform subscription, nothing proprietary to escape later.

5. The audit

   A human reads every page. Every link checked, every form tested end to end, every claim verified against your brief.

   YOU SEE — The audit result on your dashboard before launch.

   IT PRODUCES — The green light. The site goes live on your domain, in your accounts.

The lifecycle.

One pass, plainly. You brief, or you buy a plan, and the scope and price are written down — immediately on the plan page, within one business day from a brief. From there we give you a date range and name what we need from you and by when. We do not publish a launch date before we have written one — a date without a written scope behind it is the one promise we would break. When it goes live, you choose whether we keep running it or you take it; either way the work is yours.

The surfaces.

Three ways into the same system — for you, for us, and for the agents that run it.

What you get.

The full written lists are on the What you get page. Scope and price land in writing within one business day of your brief; the number you agree to is the number you pay.

BUILDS — ONE TIME

• The Page

  ONE-TIME BUILD

• The Site

  ONE-TIME BUILD

• The System

  ONE-TIME BUILD

• The Operation

  CUSTOM, QUOTED IN WRITING

AFTER LAUNCH — PICK HOW IT RUNS

• Care

  THE DEFAULT AFTER LAUNCH

• Growth

  OPTIONAL MONTHLY MANAGEMENT RETAINER

• Operator

  OPTIONAL MONTHLY MANAGEMENT RETAINER

The list for each is on /build. Overflow at any tier is quoted per request before it's built — never silent scope creep, never unpaid heroics.

Changes.

A change isn't an email into a void. You ask from your portal; it becomes a tracked job with a visible state — received, in the works, shipped — the same way your build progress is real. When it ships, you see it on your live site, and the trail stays.

Windows are set for each option and agreed in writing before they are relied on. Care changes are queued and done when we are in there. A management retainer carries a stated response window — when we acknowledge, not when a fix lands. Bigger work gets scoped first. Bigger additions get scoped and quoted first — you approve the number.

The work.

Three real builds — not demos. They run on the same doctrine this page documents.

David Andrew Furniture

A real furniture procurement business, online at last. Education-first: dealer markups, landed cost, real project numbers in plain English — with a costed plan preview before anyone commits.

Motion Menu

597 numbered, working motion patterns — a design library real enough that other developers build with it. The site funds the product; the product is the proof.

Nimos OS

The business cockpit that runs Nimos itself: agents on a fixed schedule, honest queues, receipts for everything. The same doctrine that runs this platform.

After launch.

The site runs on our stack by default — that is how a build ships and keeps working. Accounts are opened in the business's name, and the logins and the record of what was opened are handed over.

Once an invoice is paid, the code, the design, the content and the database are delivered, and they belong to you. Running it is a separate choice: keep it on our stack for a monthly hosting rate, or take the repository, the deployment project, the domain and the database into your own accounts. The second one is started the day the final invoice clears and walked with you on a call — two of the steps need you to accept an invitation in your own account, because nobody can push ownership into an account that has not authorised it. Nothing is withheld to keep you.

The honest parts.

• Service windows, not heroics.

  Changes run on business-day windows by arrangement. We do not promise 24/7 monitoring or instant response — anyone who promises that is selling you a story.

• No guaranteed business results.

  We build fast, accessible, well-structured sites and stand behind the work. We don't guarantee revenue, traffic, or rankings — nobody honestly can.

• A human reads everything.

  Fast on assembly; a person signs off every page before launch and every claim before it ships.

• Your data stays yours.

  Ask us to delete an enquiry and we will do it and confirm it in writing. Analytics stay aggregate. We don't sell personal information, ever.

Legal.

The short version, numbered the way contracts read. The full documents govern:

Made with.

Thirty-one tools carry the platform. Official marks, real roles — each one earns its place, none are decoration.

Every tool has a deep dive — what it is, what it does for your business, and its honest proof. Live status, checked in real time: /status.

How this page was made.

The document is itself the smallest proof of the system. Same rails, same gates, same trail — no special case.