Describe the missing business result
Start with what you can see from outside the site, not what you think is wrong inside it. A customer says they never heard back. Your address shows a warning in the browser. A page takes ages on a phone. Old links from other sites show an error. These are different faults, and describing the result keeps the first conversation honest and cheap.
Write one or two sentences, add the page address and the builder, and say when you last knew it worked. Do not send logins, customer messages or payment details; nothing in a first enquiry needs them.
- What did you or a customer see?
- On which page or address?
- When did it last work, and what changed around then?
Know who holds the keys
Most builder faults involve three accounts that may belong to three different people: the builder, the domain registrar or DNS host, and the mailbox that should receive messages. Find out who can log in to each before you ask for help. An outside helper should never need your passwords. After a scope is agreed you invite a collaborator, and some jobs need an administrator-level role; we name the exact role and any seat or plan charge before you invite anyone, work through a company-controlled account rather than a personal login, and start nothing until access is agreed in writing. You can remove the access later.
- Builder account: who is the owner?
- Domain and DNS: where is it registered?
- Mailbox: who reads the address that should be notified?
Choose the job that matches the fault
A form that seems to send nothing, a certificate or domain warning, a pasted widget or tracking snippet that broke a page, old links that no longer work, a slow page, a store that needs setting up, and a members-only area are each a separate fixed-scope job with its own test. If several things keep going wrong, a monthly check of forms and embeds is the standing version. If the site itself needs rebuilding, there is a five-page rebuild project.
The collection page for fault diagnosis lists the checks in the order that saves most time.
- Domain or certificate warning: the domain connection job.
- No messages arriving: the form delivery job.
- Page broken after a snippet: the embed and tag job.
- Old links broken after a relaunch: the redirect map job.
What to expect from the first enquiry
You will get a written scope, a price and a test that shows when the job is done, before any access is asked for. Prices are untested proposals, for example from £115 for a domain connection and £145 for a form, and payment follows the agreed checks and your sign-off. Nothing starts, is charged or is booked by an enquiry, and this is a new service with no client history to point to.
Sources and limits
- Wix: exporting or embedding your Wix site elsewhere Checked 2026-10-11.
- A Wix site must run on Wix's infrastructure, which limits what a move can take with it.
- Squarespace: managing form and newsletter storage Checked 2026-10-11.
- Form storage and notification address settings are separate and not updated automatically when an account email changes.