How to Choose a Web Development Company

You have three web-development proposals open. One is 60% cheaper than the highest. All promise a modern design, responsive development and support, but none uses the same scope or definition of “done.” The price column is easy to compare. The terms that will decide whether the website becomes a transferable business asset are scattered across assumptions, exclusions and missing clauses.

Learning how to choose a web development company means converting promises into testable commitments. You need to know who owns the code and accounts, what discovery produces, which measurable standards apply, who will actually deliver the work, and what happens after launch. A cheap build that another competent supplier cannot take over may carry the highest total cost.

The proposals look similar. The outcomes will not.

A website rebuild is a commercial project expressed through design and technology. Before judging screens, define what the site must change: qualified enquiries, online transactions, self-service completion, recruitment applications, partner confidence or another measurable action. Without that definition, subjective design approval becomes the project plan.

Use one comparison sheet. Normalise each proposal by template count, content responsibility, integrations, migration, accessibility, performance, analytics, hosting, support, third-party fees and tax. Mark an item “excluded” or “unclear” rather than treating silence as inclusion. Then assess the nine criteria below.

What actually goes wrong with agency website projects

• Discovery is skipped. Hidden audiences, content, integrations and approval steps surface during development. The buyer then pays through change requests, delay or a reduced site.
• The agency owns operational accounts. The domain, hosting, repository, analytics or tag manager sits under a supplier account. Leaving becomes a negotiation instead of an administrative handover.
• “Fast” and “accessible” remain adjectives. No metric, conformance target, test method or remediation duty appears in the contract, so acceptance is subjective.
• Nobody owns month four. The launch team moves on, software ages, forms fail quietly and the client discovers that support was only a short defect warranty.

These are operating failures, not visual preferences. Each can consume budget after the quoted build is “complete.”

Criterion 1: ownership of code, accounts and content

Ask for the ownership and licence schedule before signing. A proprietary platform may be a valid choice, but “you own your website” is inaccurate if you only license a non-transferable system. The proposal should distinguish custom source code, open-source packages, commercial plugins, fonts, stock media, agency tools and client-supplied assets.

Require the domain registrar, DNS, primary hosting account, source repository, analytics property, tag manager, search console and advertising integrations to be created in your organisation’s name where the service permits. Give the agency role-based access. State when custom work and approved content are assigned, what remains licensed, and what you receive at exit: repository history, database, media originals, credentials or access transfer, infrastructure record and build instructions.

Test: “Please identify the contract clause and account owner for every code, domain, hosting, data and analytics asset, plus the handover deliverables.”

Criterion 2: discovery before anyone builds

An agency that fixes a price before understanding content, systems and decisions is pricing assumptions. That can work for a tightly defined template; it is risky for a rebuild with migration, multiple stakeholders or integrations. If you do not have time for discovery, you have even less time for mid-build disagreement.

What a good discovery deliverable looks like

Expect a sitemap, page-level content plan, conversion actions, integration map, analytics measurement plan, migration inventory, decision log and wireframes for reusable templates. You do not need a polished mock-up of every page. You need written scope boundaries and a shared definition of what the site is meant to change commercially.

Test: “What artefacts will discovery deliver, who approves them, and which price or timeline assumptions will they validate?”

Criterion 3: measurable performance and accessibility standards

Put the target, population, tool, test environment, responsibility and remedy in the acceptance criteria. Google’s current Core Web Vitals guidance defines “good” as Largest Contentful Paint of 2.5 seconds or less, Interaction to Next Paint of 200 milliseconds or less, and Cumulative Layout Shift of 0.1 or less at the 75th percentile of page loads, assessed separately for mobile and desktop. Field data needs real traffic, so agree how laboratory tests will be used before enough field data exists.

For accessibility, specify the actual version and level. W3C advises WCAG 2.2 for future applicability; Level AA conformance requires every Level A and Level AA success criterion for the full page, not a favourable score from an automated scanner. The contract should cover design, code, keyboard use, forms, content supplied by each party, manual testing, assistive-technology checks where appropriate, issue severity and remediation.

The legal floor differs across the USA and Europe

Do not ask the agency to declare your entire organisation legally compliant. Ask it to build and document the defined technical scope, then obtain advice for your market, service and content.

The EU Accessibility Act applies through member-state law to specified products and consumer services. The directive covers services provided after 28 June 2025 including consumer banking, e-books, parts of passenger transport, electronic communications and e-commerce services, with detailed scope and exceptions. In the USA, DOJ guidance says Title III applies web-accessibility duties to covered businesses open to the public; it does not establish one universal WCAG contract clause for every private website. Confirm applicable federal, state, national and sector rules with qualified counsel.

Test: “Which performance thresholds and WCAG version and level will be contractual, how will you test them, and who fixes a failed acceptance test?”

Criterion 4: onshore, nearshore or offshore delivery

An offshore team can understand your market only if you give it access to customers, language, evidence and decision-makers. It will cost your team supervision time. It can save budget and extend capacity when there is an accountable local-facing lead, overlapping working hours, recorded decisions, strong written briefs and direct access to the delivery team. If the work is ambiguous, politically sensitive or requires continuous executive workshops, onshore or nearshore leadership may be worth more.

Ask whether “offshore” means employed staff, a managed dedicated offshore team or unreported subcontracting. The location matters less than the visible chain of accountability.

Test: “Name every delivery location, employer or subcontractor, overlap window, client-facing lead and escalation route.”

Criterion 5: post-launch ownership and support

Agree operation before the build begins. Separate the defect warranty from ongoing maintenance. Define hosting, backups, restore tests, software and dependency updates, certificate and domain renewal, uptime monitoring, security response, form or checkout monitoring, analytics checks, content support and release approval.

Require response and restoration targets by severity, support hours, included effort, out-of-scope rates and an emergency contact. Training should enable your team to edit the content types it owns without breaking the design. If the agency hosts the site, compare its responsibilities with the separate terms for managed web hosting.

Test: “Please quote the first 12 months of operation and state the support window, severity definitions, response targets, maintenance tasks and exit process.”

If you want one accountable scope for strategy, build, hosting and support, review OveliTHub’s web development services and book a website scoping call. The call should still be judged against this checklist.

Criterion 6: a named delivery team and decision process

The senior architect on the sales call may not be available after signature. Ask for roles, allocation, relevant experience and the conditions under which people can change. Meet the actual project lead and technical lead. Define your product owner, content approver, legal or compliance reviewer and executive escalation point too.

Require a delivery rhythm: backlog or plan, weekly demonstration, decision log, risks, dependencies, acceptance process and one source of truth. State how long your team has to review work and what happens when either party misses an input.

Test: “Who will do the work, at what allocation, and what named meeting or record controls scope, decisions, risks and acceptance?”

Criterion 7: security, privacy and data responsibility

Map the data the website collects, sends and stores. Ask about development and production separation, least-privilege access, multifactor authentication, secrets, dependency management, vulnerability handling, logging, backups, deletion, incident notification and secure handover. Define who configures consent tools without pretending a banner alone solves privacy compliance.

If an agency processes personal data on your behalf under GDPR, the European Commission explains that there must be a contract or other legal act with processor safeguards, and a processor cannot appoint another processor without prior written authorisation. International transfers can require additional analysis and safeguards. Have your privacy adviser define roles and terms for the actual data flow.

Test: “Provide the data-flow, access and subcontractor list, security schedule, incident-notice term, deletion process and applicable processing or transfer terms.”

Criterion 8: transparent price and change control

The cheapest quote may genuinely be more efficient. It may also omit content, migration, quality assurance, accessibility, analytics, project management, environments, launch, licences or support. Compare total cost across build, internal effort, third-party fees, operation and eventual handover.

Make assumptions testable: number of templates and revision rounds, supported browsers, content and data volume, integrations, client turnaround and included launch support. Require a written change request containing reason, scope, price, schedule effect and approver before work begins. Hold a reasonable final payment against accepted deliverables and handover, not mere deployment.

Test: “List every assumption, exclusion, third-party fee and rate, then show the change-control and payment-to-acceptance schedule.”

Criterion 9: verifiable work, references and exit readiness

A portfolio screenshot proves very little. Open the live site, confirm what the agency actually delivered, test representative pages, and ask how long ago it launched. Request a reference with similar complexity and operating model, not only the same industry.

OveliTHub reports more than 130 delivered projects across healthcare, real estate, construction and eCommerce, with client names including Zillow, Duracell and Allegheny Health Network. Those names should start due diligence, not end it. Ask for a scope-relevant example, the people involved and a reference conversation subject to permission and confidentiality.

Exit readiness is proof of operational maturity. A supplier should be able to describe how another competent team receives code, accounts, data, documentation and current issues without threatening the live service.

Test: “Show a comparable live project, define your contribution, provide an appropriate reference, and demonstrate the standard handover pack.”

How to read a proposal in 15 minutes

1. Find assumptions and exclusions. If they are missing, the price cannot be interpreted.
2. Find deliverables and acceptance. Count templates and functional outcomes, not vague phases.
3. Find ownership and licences. Identify every asset you cannot transfer freely.
4. Find change control. Confirm who can approve extra cost and schedule movement.
5. Find payment milestones. Tie them to evidence you can accept.
6. Find the delivery team. Separate sales participants from allocated practitioners.
7. Find operation and exit. If support and handover are absent, add their cost before comparing.

A missing section is not automatically a disqualifier. It is an unresolved risk. Put the question in writing and evaluate the precision of the answer.

Questions to ask a reference client

1. What changed between the signed scope and the delivered site, and why?
2. How were change requests explained, priced and approved?
3. Did the named senior people remain involved through launch?
4. Can your internal team edit its normal content without agency help?
5. How long did the last material support issue take to receive a useful response and reach resolution?
6. Would you choose the same agency for a different project, and what would you contract differently?

Red flags that should end the conversation

• no written source-code, content, domain and account ownership terms;
• no access to the proposed delivery lead before signature;
• portfolio items that cannot be found live or explained accurately;
• refusal to define maintenance, handover or exit;
• claims of guaranteed legal compliance without scoped evidence;
• pressure to sign before assumptions and discovery are written; or
• credentials, domains or production access intended to remain under an individual account.

Choosing well is mostly about asking earlier

Choose the company that makes ownership, discovery, standards, people, security, price, support and exit easy to inspect before you commit. The best proposal is not necessarily the longest or most expensive. It is the one whose assumptions and responsibilities can survive contact with the real project.