Checking References for Web Development Agencies

Asking a web development agency for references is a standard step in procurement, but its value depends entirely on how you conduct those conversations. A reference call is not a rubber stamp. It is a structured opportunity to test whether the agency's claims about process, communication and delivery hold up when you speak to someone who has no incentive to sell to you.

References serve a narrow purpose: they allow you to hear directly from a previous client about what it was actually like to work with the supplier. They cannot tell you whether the agency is the right fit for your specific project, and they should not replace the technical and commercial due diligence you carry out during discovery. A reference from a company that built a marketing website tells you very little about an agency's ability to deliver a multi-tenant SaaS platform or replace a legacy CRM system.

The most useful references come from projects that resemble yours in at least two respects: the type of system being built and the working relationship required. If you are commissioning an internal business system with complex role-based access, document workflows and integrations, a reference from a similar business-system project carries far more weight than one from a straightforward public-facing site.

Questions for a useful reference call

When references matter most

References carry the most weight in three situations. First, when you are spending a significant sum and the financial risk of a failed project is material to your business. Second, when the agency is relatively unknown to you and you lack prior experience of their working methods. Third, when the project involves ongoing support, data migration or legacy modernisation, because the relationship extends well beyond the initial build.

For smaller, well-scoped pieces of work where you can limit risk through clear acceptance criteria and phased delivery, references are still worth pursuing but the consequences of a mediocre reference are less severe.

How many references to request

Requesting two or three references is standard. More than that rarely yields additional insight and can signal distrust before the relationship has begun. Fewer than two leaves you reliant on a single perspective, which may be unrepresentative.

Ask the agency to suggest contacts, but also specify the type of project you want to hear about. If the agency only offers references from flagship clients, ask whether they can also provide a contact from a mid-complexity project. The day-to-day experience on a smaller build often reveals more about an agency's standard working practices.

Structuring the conversation

Treat a reference call as a brief, focused interview rather than a casual chat. Send your questions in advance so the contact has time to gather their thoughts. Keep the call to around twenty minutes.

Useful lines of enquiry include:

• How closely did the final delivery match the original scope, and what changed along the way?
• How did the agency handle changes to requirements or unexpected complications?
• What was the communication cadence like — were you kept informed without being overwhelmed?
• Were estimates revised during the project, and if so, how was that communicated?
• How did handover and the transition to support work in practice?
• Would you commission work of this type from them again?

The last question is often the most revealing. A qualified yes, a pause, or a shift in tone tells you more than a prepared answer about process.

Matching references to project type

Different project types demand different reference questions. For a CRM or internal business system, ask specifically about how the agency handled process mapping, user roles and data migration. For a SaaS product, ask about multi-tenancy, subscription billing integration and how the agency approached roadmap planning beyond the initial release. For legacy modernisation, ask whether the agency conducted a thorough audit before starting, how they managed risk during migration and whether the old system remained operational during the transition.

Treating references as a substitute for discovery

The most common mistake is to rely on references instead of running a proper discovery phase. A reference tells you about a past client's experience. It does not define your requirements, test the agency's understanding of your processes, or establish the acceptance criteria that will govern your own project. Discovery — covered separately in this guide — remains the point at which you actually stress-test the agency's approach against your specific needs.

Asking only positive questions

If every question you ask assumes success — "What did the agency do well?", "Were you happy with the result?" — you will receive only positive answers. Build in questions that invite criticism: "What would you have done differently?", "Where did the project fall short of your expectations?", "Were there any points where you considered ending the engagement?"

Ignoring the passage of time

An agency that delivered an excellent project four years ago may have since lost key staff, changed its delivery model or shifted focus to a different market. Ask the reference when the project took place and whether they have worked with the agency since. If the reference is more than two years old, treat it as background context rather than a current indicator.

Overlooking non-disclosure constraints

Some agencies work under strict non-disclosure agreements, particularly in sectors such as financial services or healthcare. If an agency cannot name a client, ask whether they can provide a reference who will speak on condition of anonymity, or whether they can share a written testimonial with enough detail to be useful. An outright refusal to provide any reference, coupled with NDA claims you cannot verify, is a legitimate concern.

Accepting hand-picked references without scrutiny

Agencies naturally select their strongest relationships. That does not make the references worthless, but it means you should probe for specifics rather than accepting general praise. If a contact says "communication was great", ask what that looked like in practice: scheduled calls, written updates, a shared project dashboard? Vague endorsements are less useful than concrete descriptions of working methods.

Key checks to carry out alongside references

References are one input among several. Alongside your calls, verify the agency's legal standing, check whether they hold relevant certifications or accreditations where these matter for your sector, and review their contract terms around ownership, liability and support. If the agency will handle personal data, confirm their approach to data protection and ask for evidence of current security practices rather than relying on a reference from a client who may not have scrutinised those details.

Finally, compare what the reference tells you with what the agency has told you. Inconsistencies between the agency's account of a project and the client's experience — particularly around scope changes, timelines or handover — are a clear signal to ask harder questions before you commit.

Make the reference comparable

• Ask for projects with similar delivery risk, not simply the same sector.
• Speak to someone who was involved in delivery and acceptance.
• Use open questions before asking about a specific concern.
• Record facts and examples rather than relying on “they were good”.
• Treat references as one input alongside contract, team and discovery evidence.