Skip to content
Wisfig logo

Wisfig field guide · Practical website and search planning

How to choose a web designer in Rocklin: compare the work, not the pitch

By Wisfig · Published

The most useful question is not “Can you make a modern website?” It is “Can you explain what this site must do, what is included and how we will know the build is ready?” Use this guide to compare providers—including Wisfig—on the same basis.

1. Write a short brief before asking for prices

Describe the business, the services you want to sell, the customers you can serve and the action the website should support. Bring the current URL and any known problems. Include constraints such as a planned move, a product catalog or a renewal date.

You do not need a complete technical specification. You do need enough context that two providers are quoting the same problem. Use our website brief to record pages, content responsibilities, functionality and ongoing care.

2. Ask who supplies the content and evidence

Copy, genuine photos, product details and permissions are work. If the proposal excludes them, identify who will provide them and when. “Five pages” means little if nobody has decided what each page explains.

Rocklin’s economic-development strategy discusses the Quarry District and local business partnerships. That context can inform useful information for a real business, but it does not justify generic city paragraphs or invented local projects. Ask how the provider will distinguish your actual offer from a template sales pitch.

3. Inspect a customer journey, not only a portfolio screenshot

On an example site, find a service, read its limitations and try the contact path on a phone. Can you use the menu with a keyboard? Are labels readable? Does the page explain what happens after an enquiry? A visual portfolio is useful, but it is not the complete acceptance test.

Ask what accessibility and performance checks are included and what standards the provider is actually agreeing to meet. “Accessible” or “fast” without a testing approach can hide very different scopes. See our practical design principles for specific checks.

4. Protect the existing website history

If you already have a site, ask for a page inventory and a plan for old URLs. Search engines and customers may still use a historical service or article address. A redesign that deletes useful pages without relevant redirects creates avoidable disruption.

The migration checklist explains exact mapping, final destinations, canonical signals and internal links. “We install an SEO plugin” is not an answer to the migration question.

5. Make ownership and ongoing costs explicit

  • Who controls the domain, hosting and business accounts?
  • What deliverables transfer after payment, and what remains subject to third-party licensing?
  • Can your team edit ordinary content, and what requires development?
  • Which hosting, plugin, maintenance or support charges continue after launch?
  • What happens if the relationship ends, including export and access removal?
  • Who applies updates and restores backups if something fails?

6. Compare the proposal against a completion checklist

Ask for the page list, content responsibilities, integrations, revision and approval process, migration work, launch tests and handoff. Separate excluded items from assumptions. A lower initial price may be reasonable; it should not depend on discovering critical exclusions after the build.

Be cautious about guaranteed Google positions, fictional results and undefined “unlimited” support. A real provider can explain the work and its limits. Our web design service and measurement approach show how we frame those decisions; the signed agreement still governs the project.

Use the guide, then define the work

Browse the Wisfig guide library for related checklists. If you want help applying this to a real website, send the project details and the main service or customer journey you want to improve.