Engineering
Two doors into the studio
Some people arrive with a paragraph and a problem. Some people would rather talk it through. A good contact page gives both people a clear first step and does not make either one guess.
A brief is not a sales form
The project brief asks enough to understand the work: what is being built, which services are involved, the rough budget and timeline, and how to reply. It does not ask for an account, a phone number in a hidden field, or a company size that has nothing to do with the project.
The callback form is shorter on purpose. A name, an email, a phone number, and a time that usually works. It uses the browser's timezone so the person does not have to describe their location.
One destination per button
Start a project goes to the brief. Request a callback goes to the callback. The same two phrases are used in the header, hero, closing block, footer, and floating shortcut. A person should never have to work out which button is the real one.
When a form has a problem, the error appears next to the field and in a summary with the fields named. The form is not allowed to reload or replace a real answer with a generic success message.
What happens next
The page states the reply expectation before the form is sent. We do not promise an automated response, a calendar booking, or a quote before we understand the scope. The next step is a conversation, then a written scope and quote.