How to Choose a Website Development Company: Scorecard, Due-Diligence Questions and Red Flags
Compare web development agencies on evidence: pass/fail gates, a weighted scorecard, technical due-diligence questions, a reference-call script and red flags.
Quick answer
Choose a website development company on evidence, not on how polished the proposal looks. First apply five pass/fail gates: you will own the code and accounts, the people who will build it are named, the agency will walk you through real work, change control is written down, and so is acceptance. Then score the agencies that pass on weighted criteria: relevant delivery, technical practice, security, process and communication, contract terms, and support and exit. Ask for evidence behind each answer, call a past client, and walk away from the red flags below. For a disclosed comparison of providers, see our shortlist of web development companies in India.
This guide is vendor-neutral and works wherever you are hiring. For regional detail, see the guides to choosing a web development company in Australia, a web development company in Dubai or a software development company in the UAE.
Key takeaways
- Separate gates (fail one and the agency is out) from weighted criteria (where agencies earn points).
- Every answer an agency gives should come with evidence you can look at: a repository, a pipeline, a test report, a change log.
- Score price separately, on the same written scope, after quality. Cheap and vague usually costs more later.
- Ask the reference client what went wrong after launch, not whether they were happy.
- Keep the domain, repository, hosting and analytics in your name from day one.
Before you compare: give every agency the same brief
Proposals only become comparable when every agency prices the same written scope. A short requirements document with goals, pages, features, integrations and acceptance criteria is enough; see what a website requirements document should include. State outcomes and constraints, and let each agency propose the technology. The UK government's Digital, Data and Technology Playbook makes the same point for public buyers: "Requirements should be drafted to be supplier or technology agnostic", which reduces lock-in.
Decide early whether you are building a website or a web application. Logins, roles, stored customer data and multi-step workflows change which evidence matters; this comparison of websites and web applications explains the difference. If you are still deciding between an agency and an individual, read agency vs freelancer first.
Agency evaluation scorecard, part 1: pass/fail gates
The scorecard has two parts. Part 1 is a set of gates. An agency that fails any gate is out, however good its portfolio is, because each gate protects you from a problem that is expensive or impossible to fix after signing. Part 2 is weighted criteria, scored only for agencies that pass every gate.
| Gate | Passes when | Evidence to ask for |
|---|---|---|
| Ownership | You own the domain, repository, hosting and analytics accounts, or the contract transfers them on a stated trigger, and IP in the work is assigned to you on payment | The ownership and IP clauses in the draft contract; confirmation of whose name each account will be in |
| Named builders | The people who will design and build the work are named, with their role and roughly how much of their time goes to your project | Names, roles and allocation in the proposal; a short call with the lead developer |
| Technical walkthrough | The agency will show you real work: a repository, pull requests and a build pipeline, live or redacted | A 30 to 45 minute screen-share, booked before you sign |
| Written change control | There is a written process for requesting, estimating and approving changes before work starts on them | The change-request process or template the agency actually uses |
| Written acceptance | The contract says how finished work is tested and accepted, and how defects are handled | The acceptance clause, and an example acceptance or UAT checklist |
Pro tip
Gates are about willingness as much as paperwork. An agency that says "we can sort ownership out at the end" or will not show any real work before you sign has already failed.
Agency evaluation scorecard, part 2: weighted criteria
Score each agency that passed the gates from 1 (weak) to 5 (strong) on each criterion, multiply by the weight and add up. The weights below are a starting point, not a standard: change them to suit your project, but agree them before you read the proposals so the scoring cannot drift towards a favourite. If several people evaluate, score separately, then discuss differences and agree one score per criterion rather than averaging.
Price is deliberately not a weighted criterion. Compare it separately, on the same scope, once you know which agencies are good enough. The DDaT Playbook says evaluation should "focus on value over cost in order to avoid a 'race to the bottom'" and that "quality will be weighted higher than cost". That guidance is written for UK central government, but the principle transfers to any buyer.
| Criterion | Suggested weight | What a 5 looks like |
|---|---|---|
| Relevant delivery evidence | 25% | Several live projects of similar type and complexity, with the same people who will work on yours, and a reference client willing to talk |
| Technical practice | 20% | Code review on every change, automated tests that run in CI, separate staging and production, documented architecture |
| Security practice | 15% | Dependencies tracked and patched on a schedule, secrets kept out of the repository, a named approach to secure development |
| Delivery process and communication | 15% | A clear plan with milestones, a named day-to-day contact, regular demos of working software, decisions recorded in writing |
| Commercial and contract terms | 15% | Clear payment milestones tied to accepted work, a change process with priced impacts, a fair warranty and termination clause |
| Support and exit | 10% | A defined support offer, handover documentation, and a credible plan for another team to take over if needed |
Technical due-diligence questions, and the evidence to ask for
Ask these in the technical walkthrough, not by email. Good agencies answer by showing you something; weak ones answer with adjectives. The questions matter most for web applications, but most apply to any custom build.
| Question | Evidence to ask for | What a weak answer sounds like |
|---|---|---|
| Can you walk us through a repository from a comparable project? | Branching, pull requests with review comments, a readable commit history | "Our code is confidential" with no redacted or internal alternative |
| What runs automatically on every change? | The CI pipeline configuration, plus a recent failed build and how it was fixed | "We test everything before release" with nothing automated |
| How do you test? | A recent test report; which tests are automated and which are manual | Testing described only as "QA at the end" |
| Who on this team has built something like this before? | Named people, their past projects, and their time allocation to yours | A team list that changes when you ask who exactly |
| How do you manage third-party dependencies and vulnerabilities? | A dependency list or software bill of materials, and how often updates are applied | "We update when something breaks" |
| How do you handle secrets and environments? | No credentials in the repository; separate staging and production; who has production access | Shared passwords, or one environment for everything |
| What happens to our data during development? | Test data or anonymised copies; production data kept off developer laptops | "We'll just copy the live database" |
| How are changes requested, estimated and approved? | A redacted change log or change request from another project | "We're flexible" with nothing written down |
| What do we receive at launch? | A handover checklist covering accounts, code, documentation and credentials | Handover described as "we send you the files" |
Using security frameworks as a question bank
You do not need to be a security specialist to ask good security questions. Three public frameworks give you neutral wording to borrow. Use them to ask "show me how you do this", not to demand a certificate that most small agencies will not have.
- UK Software Security Code of Practice. A voluntary code from the UK government and NCSC with 14 principles in four themes. Useful questions come straight from it: do you "follow an established secure development framework" (1.1), do you "understand the composition of the software" you ship (1.2), and do you "protect the build environment against unauthorised access" (2.1)? It is written for vendors supplying software to businesses, so treat it as a question bank for a bespoke build rather than a compliance test.
- OWASP SAMM. The Software Assurance Maturity Model "defines five business functions and fifteen security practices". The most relevant to agency selection are Secure Build, Secure Deployment and Defect Management (under Implementation) and Security Testing (under Verification). Ask the agency which of these it does routinely and how.
- OWASP ASVS. The Application Security Verification Standard, currently version 5.0.0, "provides a basis for testing web application technical security controls". For a web application with logins or sensitive data, ask whether the agency tests against it or a similar checklist, and which requirements it treats as in scope.
Worth noting
If you are hiring in the UK, the government's former Digital Outcomes and Specialists buyer guidance (withdrawn on 31 December 2025) described a similar method: score every supplier against the same criteria using a scoring template, and agree scores as a team rather than averaging them. It is no longer current guidance, but the method still works for private buyers.
A reference-call script
Ask the agency for a past client whose project resembled yours, then book 20 minutes. Ask open questions and listen for specifics; "they were great" tells you little. Take notes against the same questions for every agency.
- "What did they build for you, and how similar was it to what we're planning?"
- "Were the people who did the work the same people who pitched to you?"
- "When the scope changed, how was it handled and priced? Were there any surprises on the invoice?"
- "What broke after launch, and how quickly and willingly did they fix it?"
- "Do you have full access to your code, hosting, domain and analytics today, without asking them?"
- "How did they deliver bad news, such as a delay or a problem they had caused?"
- "Would you hire them again for the same kind of project? What would you do differently?"
Pro tip
The agency chooses its references, so expect positive answers. The useful signal is in the detail: how changes were priced, what broke and who owns the accounts now.
Red flags, and what to do about each
One red flag is not always disqualifying, but each should get a direct question and a written answer before you sign.
| Red flag | Why it matters | What to do |
|---|---|---|
| No repository access until final payment | You cannot check progress or quality, and you depend on the agency to release your own work | Require access from the first commit; tie IP transfer, not access, to payment |
| Domain, hosting or analytics registered in the agency's name | Moving supplier later becomes a negotiation | Create the accounts yourself and grant access; see the vendor handover checklist |
| "Unlimited revisions" with no change process | Changes get absorbed until they don't, then arrive as a dispute or a cut corner | Ask for the written change process and an example change request |
| A firm fixed price for a web app after a single call | The agency cannot know the scope yet, so the risk is priced in or pushed back to you later | Ask for paid discovery first; see technical discovery |
| No named developers, or a team that changes after signing | The pitch team may not be the build team | Name key people in the contract and agree how replacements are approved |
| Refuses any technical walkthrough or trial | You are buying on trust alone | Treat it as a failed gate |
| Portfolio links that are dead or cannot be attributed | You cannot verify what they actually built | Ask which parts they built and speak to that client |
| Vague answers on testing, security or acceptance | These gaps surface after launch, when they cost most | Ask for evidence from the due-diligence table above |
Contracts, pricing models and scope changes
The contract model changes who carries which risk. A fixed price suits a well-defined scope; time and materials suits work where you will learn as you go; many projects combine the two, with discovery first. See fixed price vs time and materials for how to choose and which clauses to insist on. Whatever the model, budgets usually overrun through unmanaged changes rather than bad estimates, so read how to control scope creep before kickoff. For what drives quotes up or down, see the website development cost guide.
At minimum, the contract should cover scope (by reference to your requirements document), milestones and payment tied to accepted work, the change process, IP assignment, account ownership, acceptance and defect handling, warranty, support, confidentiality and data protection, and how either side can exit. Take legal advice in your jurisdiction; IP and data rules differ, which is why the regional guides linked above go into local detail.
Hypothetical example: three proposals, one scorecard
This example is hypothetical. A founder needs a customer portal with logins, a CRM integration and an admin area, and sends the same requirements document to three agencies.
Agency A has the most impressive portfolio but registers hosting in its own name and will not show any code before signing. It fails two gates and is out. Agency B passes the gates and shows a pipeline with automated tests and reviewed pull requests, but its portfolio is mostly marketing sites; it scores 3 on relevant delivery and 5 on technical practice. Agency C passes, has built two similar portals with the named lead developer, and its reference client confirms the same team delivered; it scores 5 and 4 on those criteria.
With weights agreed in advance, C comes out ahead of B. Only then does the founder compare the two prices on the same scope, and asks B why its estimate for the integration is so much lower before deciding.
What else to check
Process and QA. Ask how a project moves from kickoff to launch and how testing works across devices, browsers and accessibility. The website development process guide shows what a solid process looks like, and the performance, accessibility and security guides describe good practice to compare answers against.
UX capability. Development quality alone does not make a site easy to use. Ask how design decisions are made and who does the research.
Support and documentation. Ask what post-launch support covers and costs, and whether you will receive documentation good enough for a different team to take over. See the maintenance guide for what ongoing support should realistically include.
Specialist builds. For an online store, use the guide to choosing a Shopify agency; for an app, see how to choose a mobile app development company.
When this scorecard is overkill
For a small brochure site built on a standard CMS theme, a full technical walkthrough and weighted scoring is more effort than the risk justifies. Keep the ownership and acceptance gates, look at two or three comparable live sites and make one reference call. The scorecard earns its time on web applications, integrations, stored personal data, or any project where switching supplier halfway would be painful.
It also cannot tell you whether your idea is right. If you are unsure what to build, spend on discovery or prototyping before you spend on agency selection.
Sources
UK government: Software Security Code of Practice (DSIT and NCSC, voluntary; updated 15 January 2026); The Digital, Data and Technology Playbook (updated 20 June 2023); How to evaluate Digital Outcomes and Specialists suppliers (withdrawn 31 December 2025; cited as historical).
OWASP: Software Assurance Maturity Model (SAMM); Application Security Verification Standard (ASVS) 5.0.0.
Accessed 15 October 2026. Guidance and frameworks are updated from time to time; check the current versions.
Conclusion
Choosing a website development company is due diligence, not a gut-feel decision. Send every agency the same brief, remove anyone who fails a gate, score the rest with weights you set in advance, ask for evidence behind every claim, call a past client and compare price last. Keep the accounts in your name from the start. For the bigger picture before your first vendor conversation, see the complete website development guide, and for larger UK custom builds, our UK custom software buyer's guide.
Want a second opinion on a proposal?
ZSpace Labs is a remote-first technology studio that works with clients globally on website and web application development. If useful, we can walk you through a real repository and our delivery process, or talk through a proposal you have received against the scorecard above.
Common questions.
Relevant experience with projects similar in complexity to yours matters more than general reputation. A portfolio full of simple brochure sites doesn't predict success on a complex web application, and vice versa.
No. Compare what's actually included in each quote (QA, content migration, post-launch support, documentation) before assuming a lower number is better value.
Only if the contract says so. Clarify code and IP ownership before starting, not after the project is delivered, and make sure the repository, domain and hosting accounts are in your name or transfer to you on a stated trigger.
Yes. A reputable company should be able to show relevant past work and, ideally, connect you with a past client for a reference, without you having to press hard for it.
Very, if your project has specific technical requirements. Ask directly about their experience with your chosen (or being-considered) stack, not just general web development experience.
Yes. A company with a documented QA process (device and browser testing, accessibility checks, performance verification) is less likely to hand off a site with avoidable issues.
Scope, timeline, payment terms, IP and code ownership, what happens if scope changes, how the work is accepted, and what post-launch support (if any) is included.
Ask directly what post-launch support looks like and what it costs. Don't assume it's included by default.
Remote work is standard and effective in website development. Prioritise relevant expertise, communication quality and process over physical location, and check that working hours overlap enough for decisions to happen quickly.
You can ask, but a careful agency will protect its clients' confidentiality. Accept a walkthrough of a redacted repository, an internal project or an open-source contribution instead. What matters is that you see real pull requests, review comments and a build pipeline, not slides about them.
Usually not, if the work lives in a repository you own and can access throughout the project. Escrow, where a third party holds the source code and releases it on events such as insolvency, matters more for licensed or hosted software you cannot hold yourself. Most information about escrow comes from escrow providers, so take legal advice on whether you need it.
Three is usually enough to see the range without making the evaluation a project in itself. Send all of them the same written requirements so their proposals are comparable, and score them with the same scorecard.