How to choose a website design and development company: a practical checklist

You do not need a full specification, but you do need to know what success looks like. Companies can only give useful advice and realistic estimates when they understand the problem. A good brief fits on one page and answers:

• What you want to achieve, and why now.
• Who will use the website or application, and what they need to do.
• The must-haves for the first version, and the nice-to-haves that can wait.
• Existing systems, content or code the project has to work with.
• Deadlines that are fixed (a launch, an event, a funding round) and ones that are flexible.
• A budget range. You do not have to share it, but a range helps a good team propose the right scope instead of guessing.

Our free project brief template walks through each of these.

Relevant, working examples

Screenshots show taste; working products show skill. Ask to click through live sites or apps similar to yours, and ask what the company did on each one. A newer team may have fewer examples, so look harder at its process, its people and how clearly it explains its decisions.

A process you can follow

Ask how often you will see working software. Regular demos (we run two-week sprints with a demo at the end of each) mean problems surface early, while they are still cheap to fix.

Who actually does the work

Find out whether design and development happen in the same team or are passed between vendors, and who your day-to-day contact will be.

Ownership, security and support

• Ownership: you should own the code, the designs and every account (domain, hosting, analytics, app stores) once the work is paid for.
• Confidentiality: ask whether they will sign an NDA before you share details.
• Security: ask how they handle user data, passwords and form submissions.
• After launch: ask what support looks like, how bugs are reported and how quickly they are handled.

A pricing model that fits your project

A fixed price suits a well-defined scope with a clear finish line. Time and materials suits products whose priorities will change as you learn. A dedicated team suits continuing product development. A good company will tell you which fits, rather than pushing one model for everything.

• They quote a fixed price without asking questions or writing down what is included.
• They cannot explain trade-offs in plain language, or every answer is “yes”.
• Ownership of the code, designs or accounts is vague, or stays with them after you have paid.
• There is no written scope, no definition of “done” and no process for handling changes.
• You will not see working software until the very end.
• Nobody mentions what happens after launch.

1. What would you build first, and what would you leave for later?
2. What are the biggest risks in this project, and how would you reduce them?
3. How will we communicate, and how often will I see progress?
4. What do you need from us (content, access, decisions) and when?
5. How do you handle changes to scope once work has started?
6. What does support look like after launch?

The Questions to ask any software team template lists these and more, with notes on what a good answer sounds like.

Two quotes for “the same website” can differ widely because they describe different work. Put them side by side and check:

• Scope: which pages, features and integrations are included, in writing.
• Assumptions and exclusions: content writing, hosting, third-party fees and testing are common gaps.
• Milestones: what you will see, and when.
• Acceptance: how you will agree that each part is finished.
• Change process: how new requests are estimated and approved.
• After launch: warranty period, support options and ongoing costs.