How to Choose a Web Designer: 5 Risks to Check Before Hiring

Knowing how to choose a web designer is a business decision, not only a visual one. The agency or freelancer may influence website security, customer data, accessibility, search visibility and the systems that generate enquiries or sales.

A strong partner explains trade-offs, documents ownership and designs around measurable customer needs. Use the five risk areas below to compare providers before signing a contract.

1. Unclear ownership and access

Your agreement should state who owns the domain, hosting account, source files, design assets, analytics properties, advertising accounts and custom code. Business-critical accounts should normally be registered in the client’s name with appropriate administrator access.

Ask how credentials are stored, how access is revoked and what happens when the relationship ends. Confirm that you can export content and data in usable formats. A provider who avoids these questions may create costly dependence later.

2. Weak security and maintenance practices

A website is an operating system for customer interactions. Ask how the provider handles software updates, backups, restore testing, access control, monitoring and incidents. They should be able to explain the process without promising that a site can never be attacked.

Require least-privilege access and multi-factor authentication where available. Clarify which security tasks are included after launch and which remain the client’s responsibility. Our small-business cybersecurity checklist provides a useful baseline.

3. Designs that ignore real users and business outcomes

A portfolio can look impressive while hiding slow pages, confusing navigation or inaccessible forms. Ask the designer to explain the customer journey, the evidence behind important decisions and how the work will be tested on real devices.

The discovery process should cover target customers, priority actions, content, accessibility, mobile use, connectivity and success measures. For African markets, review the practical considerations in our mobile-first website design checklist.

4. Unlicensed assets and unclear content responsibilities

Images, fonts, video, software and written content may carry licenses or usage restrictions. The contract should identify who supplies each asset, who verifies permission and whether license costs are included.

Do not accept copied competitor text or images taken from a search engine without clear rights. Keep records for stock assets and commissioned work. For privacy notices, terms and sector-specific obligations, obtain qualified legal advice rather than assuming a generic template is sufficient.

5. No plan for performance, measurement or ongoing care

A launch date is not a business outcome. Agree on the events that matter: qualified form submissions, bookings, purchases, calls or other meaningful actions. Confirm how analytics and consent will be configured and who will review results.

Ask for performance targets, browser and device testing, quality assurance, redirects for changed URLs and a post-launch support process. A practical website maintenance plan should define monitoring, updates, response times and reporting.

Questions to ask every web designer

• Which customer problem and business outcome will the website prioritize?
• Who owns every account, asset and deliverable?
• What is included, excluded and treated as a change request?
• How will accessibility, mobile use, speed and security be tested?
• How will existing URLs and search equity be protected?
• What data will be collected, and who is responsible for compliance?
• What training and documentation will the team receive?
• What support is available after launch?

Evaluate proposals using evidence

Compare providers against the same written criteria instead of choosing from presentation style alone. Review relevant work, speak to references when the investment is significant and ask for examples of project documentation or reporting.

A good proposal connects scope to outcomes, states assumptions, identifies dependencies and shows a realistic timeline. The lowest quote can become expensive when content, integrations, migration, testing and maintenance were excluded. The highest quote is not automatically the best; value depends on fit, evidence and execution.

Red flags to investigate

• Guaranteed search rankings or unsupported revenue promises
• Pressure to buy before requirements are understood
• No written scope, acceptance criteria or change process
• Refusal to provide account access or export options
• Unlicensed themes, plugins, fonts or media
• No backup, testing, security or handover plan

Frequently asked questions

Should I hire a freelancer or an agency?

Either can be effective. Choose based on the required skills, accountability, continuity, communication and project risk rather than the label.

How many proposals should I compare?

Two or three well-qualified proposals are usually more useful than a large number of poorly matched quotes. Give each provider the same requirements.

Should the designer also host the website?

That can simplify support, but confirm ownership, backups, service levels, export options and an exit process before agreeing.

If you need an evidence-based website plan before choosing a provider, book a strategy call with Afritech Global.