10 Questions to Ask a Website Designer in Fargo

Use these questions in your next website meeting. They are designed to get specific answers you can compare afterward, whether you are hiring a Fargo designer, a freelancer or a larger agency.

Take notes in three columns: the answer, the evidence promised and who will follow up. A provider does not need an instant answer to everything. It does need a clear way to resolve the open items. If you are still building a shortlist, start with our website design company selection guide.

1. What should this website help our business achieve?

A useful answer connects the website to your customers and a defined action. Ask the designer to describe the first visit, the question the page should answer and the next step. Avoid accepting page views as the only business outcome.

Ask: “How will we tell the difference between more traffic and better inquiries?”

2. Can you walk us through a comparable live project?

Have them open the site and explain their contribution, the original problem and a design decision. Try the navigation on your own phone. A relevant process can matter more than an identical industry example.

Ask: “Which parts did your team deliver, and what changed after launch?”

3. Who decides the pages and writes the content?

Get a page list and responsibilities for drafting, reviewing and approving copy. Include real photographs, image permissions and any required translations. Decide who supplies the details only your business knows.

Ask: “What do you need from us, and what happens if content arrives late?”

4. How will you protect useful content and old addresses?

Ask for an inventory of important old pages, a keep/combine/remove decision and an appropriate destination for changed URLs. Useful content should not disappear because a new layout has less space. Rankings can move during a migration even when the work is careful.

Ask: “Who approves the URL map and checks the redirects after launch?”

5. Can our team edit the site, and what are the limits?

Request a live demonstration: change a service paragraph, add an image and preview the result. Ask which changes need a developer. Understand the platform, hosting model and exit options rather than choosing by a brand name alone.

Ask: “What can we take with us if we change providers?”

6. What will you test on phones and with a keyboard?

A clear answer covers layout, navigation, forms, focus visibility, text readability and error messages. Ask which checks are automated and which need a person. Accessibility needs an agreed standard and scope; a test score alone is not proof of complete usability.

Ask: “Can we see the test evidence and try the important tasks ourselves?”

7. Where will every form or booking request go?

List the destination for sales inquiries, support, applications and bookings. Decide what information is necessary, who receives it and what the visitor sees if something fails. Test a real delivery before calling the connection complete.

Ask: “Who owns the receiving account, and how will missed messages be noticed?”

8. What decisions can hold up the schedule?

Ask for milestones, review windows and dependencies. A useful schedule includes content approval, integration access, testing and launch review. Identify one decision-maker on your side so conflicting feedback does not become a hidden delay.

Ask: “What is the change process if we add scope or miss a review?”

9. Who controls the domain, accounts and finished work?

Write down domain registration, hosting, source or platform access, analytics, licenses and backups. Clarify what is owned, rented or transferable. Keep business access independent of one employee or one vendor login.

Ask: “Can you show the handoff checklist and explain any transfer fees or restrictions?”

10. What is the full cost, and what happens after launch?

Compare the build fee with recurring hosting, maintenance, licenses, integrations and change requests. Ask what support includes, how urgent issues are reported and who handles updates. A lower initial quote can include a different level of responsibility.

Ask: “What is excluded, what renews and what would trigger an extra charge?”

Compare the answers while they are fresh

Do not invent a numerical score for answers you cannot verify. Mark them clear, unresolved or unsuitable for your needs. If a critical answer remains unresolved, make it a condition of the proposal rather than a verbal assumption.

Use our SEO and design guide to understand the testing discussion and our platform comparison for the ownership conversation. You can also review Spotlight’s website process and book a meeting with the team with your questions ready.