Start with the decision
Choose the working relationship before the visual style.
A good first conversation identifies the customers, offer, evidence, constraints, and next action the website needs to support. It should make the project easier to define, whether you choose an agency, a larger company, a small studio, or an independent practitioner.
- What the website must help customers understand
- Who owns strategy, content, design, build, and launch
- What is included, excluded, and dependent on a third party
- How existing URLs, analytics, and forms are protected
- Which evidence supports the proposed scope
Start with the buyer journey, not a style reference
Before comparing providers, identify who the site must help, what they need to understand, which proof changes their confidence, and what next action matters. For a trading business that may be product, capability, certification, and an RFQ route; for a professional firm it may be services, expertise, and a useful first enquiry.
Visual references can help communicate a direction, but they do not replace a decision about message, information hierarchy, content, or conversion. Ask each provider how the proposed website will make these practical decisions visible to the customer.
Ask who is responsible for the work behind the screen
A website project includes more than visual design. Clarify who leads discovery, page planning, copy or content preparation, design, responsive development, technical setup, testing, launch, and post-launch support. If another specialist or platform is involved, identify that dependency before the quote is approved.
This is also where a web design agency, a larger company, a small studio, and an independent practitioner may work differently. The useful comparison is whether roles, communication, review points, and accountability are clear for your scope—not whether one label sounds more impressive.
Make the written scope testable before approving it
A clear scope names the pages and templates, language versions, content inputs, revisions, integrations, existing-site work, launch checks, handover, and exclusions. It should also say what happens when an assumption changes, such as a new language, a CRM request, or content that is not ready.
Ask to compare quotes on the same decision criteria. A lower number can leave essential work undefined; a higher number can include work you do not need. The right next step is a scope you can read, challenge, and approve with confidence—not a promise of rankings, leads, or a fixed result that cannot be guaranteed.



