Choose a website designer by comparing relevant work, a written scope, account access and a clear plan for checking and maintaining the finished website.
Give each provider the same business brief and ask for evidence behind their proposal. A nearby address, polished screenshot or low starting price cannot answer those questions on its own.
Does your website designer need to be nearby?
Location matters when it supports the way you need to work together. If you want meetings in Fresno, on-site photography or an in-person handover, ask whether those activities are available and included. Confirm who you will work with and how reviews, questions and approvals will be handled.
Apply the same checks to a remote team. Ask how it will learn your services, coverage and customers, and agree when you can communicate. Being local does not establish a particular response time or understanding of your business. Ask the proposed designer to explain your customer's decision before presenting a solution.
If you have not established why the current website needs replacing, start with the business plan before a new website. This guide focuses on comparing providers once there is a clear problem to address.
What should you check in a designer's portfolio?
Open a relevant live example and follow a customer task. Can you understand the service, find the area covered and reach the next step on your phone? Inspect more than the homepage. Ask which parts the provider designed or built, when it worked on them and whether the current site has changed since handover.
Our selected website gallery includes BluEmber Lighting, Riverpark Pet Hospital and MBS Accountancy among nine examples. You can open the sites from that gallery. Use them as starting points for a conversation about relevant work; a public preview does not establish a project's scope, ownership terms or business results.
If a proposal includes a performance claim, ask for its dates, measurement and context. Did the figure count visits, enquiries or completed sales? Was advertising or another change happening at the same time? A testimonial can describe a client's experience without proving that one design change caused a revenue increase.
Read attributed client feedback alongside the work. Ask for a relevant reference when appropriate, with the client's permission.
What should a website proposal make clear?
Compare the work and responsibilities before comparing totals. Give each provider the same priority services, audience, existing website and desired customer action. Ask it to identify what is included, what is excluded and which decisions depend on your input.
- Pages and content: the purpose of each page, who supplies or writes the words, which images are available and who approves factual claims.
- Functions: the forms, booking tools or other integrations required, including any separate subscriptions and who manages them.
- Migration: how existing content and important URLs will be assessed, which addresses will stay and who will handle necessary redirects.
- Review and delivery: the review stages, included revisions, approval responsibilities and what happens when the agreed scope changes.
- Costs: one-time work, recurring services, third-party charges and work that would need another quote.
Ask for the assumptions behind a schedule, including content, approvals and access the provider needs from you. This is a comparison of the proposed commitments, not a universal price or delivery-time benchmark. Our marketing budget guide covers the separate question of how an investment fits business economics.
Who will control the domain, accounts and finished work?
Clarify what your business will own, license or subscribe to, and how access will work during the project and afterward. Put the agreed arrangement in writing instead of assuming that paying for a website includes every asset or account.
Ask whose account holds the domain registration and hosting, who can administer the content system, and how your business will access analytics and search reporting. Identify the business contact responsible for recovery and renewals. Keep account ownership separate from the permission a designer needs to do the work.
Also ask what can be exported or transferred if you change providers, what happens to licensed images or software, and whether handover or migration carries a separate charge. If a system cannot move as a complete website, understand what would have to be rebuilt before choosing it.
How will you check that the website is ready?
Agree observable acceptance checks for the customer tasks in your brief. A design approval and a working enquiry path are different checks; both deserve an owner before launch.
- Find the right information. Review the key service pages on a phone and computer. Check readable text, accurate coverage, meaningful link labels and navigation that works with a keyboard.
- Complete an agreed test enquiry. Confirm that the request reaches the intended destination, the visitor sees an accurate confirmation and the team knows who will follow up. Check how a failed submission is explained.
- Check measurement. Distinguish contact-button clicks from successfully received requests. Agree how tests, duplicates and consent choices affect reporting.
- Check the launch transition. Test important old addresses, the intended public pages and the agreed search settings. Record who will investigate a broken link or delivery problem after release.
Ask for the results of those checks, rather than an assurance that everything is optimized. A working launch does not guarantee search rankings. If a live page is absent from Google, the website indexing guide explains how to investigate that specific problem.
What happens after the website launches?
Separate handover, routine maintenance and ongoing marketing. Ask who updates service information, manages software and backups, handles a failed form and pays for renewals. Establish how you request help, when support is available and which work costs extra.
Ask for a practical handover: the agreed access, account and renewal record, instructions for common edits and a named route for support. Confirm whether training is included and which updates your team can make independently.
Ongoing SEO, new content and advertising may be useful, but they should have their own defined scope. Do not assume a maintenance fee includes every future change or that a website build includes an ongoing marketing program.
How do you compare the final answers?
Use the same short record for each provider. Mark an unanswered point as unresolved; do not treat it as included. Follow up on the gaps that matter to your business before choosing.
| Decision | Evidence to record | Question to resolve |
|---|---|---|
| Relevant work | A live example and the provider's stated contribution. | Does that work address a similar customer task? |
| Scope and cost | Included work, exclusions and recurring charges. | What still needs another quote or your input? |
| Control and continuity | Account access, licenses and transfer arrangements. | What happens if you change providers? |
| Readiness | Agreed checks for content, enquiries and launch. | Who confirms the checks passed? |
| Aftercare | Handover, support scope and named responsibilities. | Who handles the next problem or update? |
The useful outcome is a proposal you can assess and a working relationship you understand. To explore AMÁRQUEZ's approach, see website design services and website design in Fresno, then bring your brief and outstanding questions to the conversation.