Your site is live. What now?

Three doors. One person. The form reaches the builder.

Tell us what is wrong — or what you need changed.

Not sure if it is a change, a fix or billing? Leave it on support. Sorting is our job.

WRITE IT DOWN

WHAT IS THIS ABOUT

Something about a site we made for you: a change, a fix, a question about how it works. Saying which build it is gets it attached to your file and answered in context.

Nothing is sent until you press the button, and your message goes to the studio — not to a mailing list.

What happens next

  • A person reads it

    The builder, not a queue. Usually one business day.

  • Something broken goes first

    Say it in the first line. Check the status page while you wait.

  • The reply comes from the studio's own domain

    From nimoswebsites.com, not no-reply. Check spam once.

Not a client yet? This door still works — say what you are looking at, and the note goes to the same person.

What support covers

You ask for a change

Scoped with a diff before it ships.

Something breaks

Status page first, then a person.

You want out

Repo, hosting, domain, runbook. Documented.

You are not sure who to ask

Use the form. It reaches the builder.

The questions clients actually ask

What happens after launch — is maintenance included?

Care or an optional retainer. Changes get scoped; you approve before we build.

What happens to the site — and can it move with me?

Code, design, content, database are yours. Transfer is documented.

What is automated and what is a person?

Scripted stages. A person reads every page and signs off.

Cost, timing, domains, switching: the FAQ. Anything else — the form above.

What we do not promise

No all-hours monitoring promise. No uptime number we cannot evidence. A person reads the note, usually within one business day.

Not a client? Start at the top or read the terms.

Everything else: the contact form. Same person.