Working remotely with a website designer: from brief to launch

Start with the business, not a collection of effects

A useful website brief explains the business, the people it serves, and the action a visitor should take. You do not need a finished design vocabulary to begin. Describe what customers ask before they contact you, what makes the service different, and what is difficult about the current site. Those answers give the project a direction that a list of favorite animations cannot.

References can still help. Share a few pages you like and explain what you like about each: the reading rhythm, the quality of the photographs, or how a project is presented. A reference is most useful when it helps identify a preference. Asking for a copy of another company’s site gives your own business less room to develop its character.

Agree on what the first version includes

Before design starts, establish the pages, languages, content responsibilities, and integrations. Is the project a focused landing page or a full service website? Will visitors book through an existing platform, send an inquiry to a CRM, or pay online? These decisions affect both the interface and the development work, so they need to be explicit.

Also discuss what can wait. A small first version can be a strong choice when it covers the essential offer and customer journey. Adding a dashboard because it may be useful one day can consume time that would be better spent on content or photography. Scope should follow a concrete business need, and a later addition should be recognized as a new decision.

Prepare material that makes the business believable

Gather the logo you actually use, real project images, service descriptions, contact details, and any customer feedback you have permission to publish. If a photograph or testimonial is missing, say so. A design can account for that gap, but a plausible invented replacement creates a trust problem that an attractive layout cannot solve.

For international work, clarify language needs early. Translation is more than changing the words: longer headings, different contact habits, and right-to-left layouts may affect the page. Review translated sales copy for natural phrasing. Keep locations and project facts accurate even if the overall service is available worldwide. An international positioning does not require hiding where the work was done.

Give feedback that explains the problem

Remote feedback works best when everyone can identify the exact screen and decision being discussed. Instead of saying that the page feels wrong, explain the effect: the heading is difficult to read, the photographs make the studio feel busier than it is, or the booking action is easy to miss. The designer can then address the reason rather than guessing at your preference.

Consolidate comments from the people making the decision, and separate corrections of fact from visual preferences. A wrong phone number is a required fix. A preference for a quieter headline is a discussion about tone. Both matter, but treating them as the same kind of comment makes revisions harder to prioritize. Clear written feedback also helps when working across time zones.

Review the working site, including the uncomfortable states

A design preview shows an intended appearance. A working website must also handle a small screen, a long name, a failed request, and a person navigating without a mouse. Ask to review the real implementation before launch. Read the mobile content in order and complete the inquiry journey yourself, rather than checking only the desktop hero.

For forms, confirm where the information goes and what happens after submission. If the form saves to a lead CRM, test that a successful inquiry appears there. If the network fails, the visitor should retain their details and have a way to retry. A confirmation animation can make success feel satisfying, but it must follow successful receipt and remain readable without motion.

Define the handoff and what happens after launch

Before launch, clarify who manages the domain, hosting, content edits, and any connected tools. Establish how updates and support will be handled without assuming an unlimited ongoing service. The website should leave the business with a usable foundation and a clear understanding of what it can change. Access details belong in a secure handoff, not in a public document.

After launch, gather real questions and feedback from customers. Those observations can guide the next improvement more reliably than adding features because other websites have them. Working remotely does not remove the need for a personal relationship; it makes clear communication more valuable. A good project is built around agreed decisions, real material, and a site that works beyond the presentation.

• Explain the business and the primary visitor action.
• Agree on pages, languages, integrations, and content ownership.
• Share genuine material and consolidate specific feedback.
• Test the working site on a phone and with a keyboard.
• Clarify the handoff, support arrangement, and next review.