How to evaluate a website development partner
The questions that reveal how an agency actually works — including the ones that make an unsuitable partner uncomfortable.
Most website projects that go badly were not sold badly. They were sold on a portfolio and a price, and the problems appeared later — in ownership, maintainability, performance or the cost of the first significant change.
These are the questions worth asking. The answers matter, but so does whether the question is welcome.
Who owns the code?
Ask directly, and get it in the contract. You want ownership of the source code and assets on final payment, along with repository and deployment access. If a company retains ownership or builds on a proprietary platform you cannot leave, you are renting your website — which is a legitimate model, but you should know you are choosing it.
What happens if we change developers?
A good answer describes mainstream technologies, documented architecture and a clean handover. A poor answer is vague or slightly offended. You are not planning to leave; you are checking whether you could.
How is security handled?
Ask when security is considered and what specifically is done. Answers along the lines of 'we use SSL' or 'the platform handles it' indicate it is not really part of the process. You are looking for dependency management, access control, input handling and configuration review as named activities in the build.
How will performance be measured?
Ask for the target and how it will be verified. Core Web Vitals thresholds agreed up front and tested on mid-range mobile hardware is a substantive answer. 'It will be fast' is not.
What does the first change after launch cost?
This is the most revealing question in the list. Systems built as a set of one-off pages are expensive to change; systems built as components are not. The answer tells you what you are actually buying.
What is explicitly not included?
Content, migration, integrations, training and post-launch support are the usual gaps between a quoted price and a working website. A partner who volunteers their exclusions before you ask is one worth shortlisting.
One question with no wrong answer, only a revealing one: ask what they would advise if the right solution were a product they do not sell. Willingness to say so is the clearest signal of how advice will be given later.
Written by
RegenByte
Articles are written by the RegenByte team from work on client projects. We publish what we have actually done rather than summarising other people’s posts.