Working With a Website Designer: Agree on Responsibilities First

Scroll Down

Two colored pencils contribute to a shared website blueprint, with a blue comment showing an approved design decision.

Working with a small business website designer should start with a clear division of responsibility. You bring the knowledge of your business. The designer brings expertise in presenting it through a usable website.

There is plenty of shared work between those roles. The problems begin when both sides assume the other person is handling it. Before choosing a designer, find out how they define the work and what they need from you.

You remain the authority on your business

A designer can help organize information and challenge unclear explanations. They cannot decide which services you really offer, what promises you can keep, or which customers you are equipped to serve.

Expect to explain the business accurately and approve the facts that will appear publicly. If the website needs specialist legal, regulatory, or other professional wording, agree who is qualified to provide and approve it.

You do not need to arrive with every sentence polished. You do need to distinguish confirmed information from ideas still under discussion. A designer should not have to guess whether “we might offer this” belongs on your live services page.

The designer should explain their recommendations

When reviewing a prospective designer’s work, ask why they made particular choices. A useful conversation connects page structure, layout, and content to the business and its audience.

You can bring examples of websites you like. Explain what attracts you: a calm presentation, clear service explanations, or an approach that feels appropriate for your customers. The designer can then assess what belongs in your project rather than simply copying the appearance.

Imbark’s custom web design service is built around business goals, brand, and audience. Ask how that approach would apply to your specific website, including any constraints the proposed platform or scope creates.

Agree who handles the work between the two roles

Copy preparation is a common example. “Content included” might mean arranging supplied text, editing it, or writing new copy from an agreed brief. Those are different responsibilities. Confirm which one is being offered.

The same applies to photography, third-party services, and features that need information from your team. For each, establish:

  • Who provides the material or makes the initial decision.
  • What the designer will do with it.
  • What needs to be ready before that work can begin.
  • What happens if the requirement changes.

For example, a fictional consultant may want appointment booking. The consultant needs to decide availability, appointment types, and operating rules. The website team can assess the agreed booking requirements and explain the work involved. Neither side should assume that “add booking” settles those decisions.

Choose expectations you can actually meet

Ask the designer what involvement they expect from you and whether that fits your capacity. If you are managing the business alone, say so. Agreeing to provide material you cannot prepare leaves an important dependency unresolved.

Read Imbark’s website design process for the overall stages, then discuss the responsibilities and timing for your own project. A published process gives context; the project agreement needs to make your specific commitments clear.

Also establish where the build ends and ongoing work begins. If you will need help changing the site later, discuss website support before assuming it is part of the original project.

The right starting point is a working arrangement both sides understand: your business knowledge, the designer’s expertise, and no important task left between them.

i 3 Table Of Content

Imbark

Imbark

Imbark