Web Agency Reference Questions: What to Ask an Agency’s Past Clients

A reference call is the only part of agency vetting where you hear from someone who has already paid the invoices. Portfolios show what was built. Reviews show how people felt. A reference can tell you what it was like to be the client for six months, including the parts that never make it into a case study.

Most reference calls waste that chance. The buyer asks “Were you happy with them?”, hears “Yes, great team,” and hangs up with nothing new. The questions below are built to get past that. They focus on events, not opinions: what was agreed, what changed, what broke, who fixed it and how long the relationship lasted.

This guide is neutral about providers. It does not rank agencies, and it works whether you are comparing a large firm, a boutique studio or a freelancer. If you are still building your list, start with our guide on how to find the best web development companies in the USA, then come back when you have two or three finalists.

What are web agency reference questions actually for?

Good web agency reference questions test one thing: whether the way the agency describes its process matches what a real client experienced. Everything an agency tells you during the sales process is a claim. A reference is a witness to how those claims played out on a real project.

That framing changes what you ask. You are not collecting compliments. You are checking specific promises against specific memories. If the agency said it runs weekly status calls, ask the reference how often they actually heard from the team. If the proposal says scope changes go through written change requests, ask the reference what happened the first time they wanted something new.

A reference call also covers what nothing else can. Directories and maps tell you about volume and sentiment; our guide to vetting a web development company through Google Business Profile reviews covers that side. Case studies tell you about outcomes the agency chose to publish. Only a conversation with a past client tells you about the months between kickoff and the last support ticket.

A reference call is useful when it turns the agency’s promises into questions about events: what was agreed, what changed, what broke and who fixed it.

When should you call references in the hiring process?

Call references late, after you have a proposal in hand and before you sign. Calling too early means you do not yet know what the agency has promised you, so you cannot test those promises. Calling after signing means the answers can no longer change your decision.

The sequence that works for most buyers looks like this:

1. Shortlist. Narrow to two or three agencies using portfolios, directories and first calls. Our one-week shortlisting process lays out the days.
2. Proposal. Get a written scope, timeline approach, ownership terms and support terms from each finalist.
3. Reference request. Ask each finalist for references on projects similar to the one in the proposal.
4. Reference calls. Run the same script with every reference, ideally within the same week.
5. Follow-up. Bring anything unclear back to the agency before you sign.

There is one exception. If a project is unusual, such as a migration with a lot of stored content, a complex integration or a regulated industry, ask early whether the agency can provide a reference for that kind of work at all. If it cannot, you have learned something important before investing time in a full proposal.

How many references should you ask for, and which ones?

Ask each finalist for two or three references. One reference is an anecdote. More than three rarely adds much, and it costs you and the agency’s clients time. What matters more than the number is how well each reference matches your project.

Be specific in the request. Instead of “Can you send some references?”, write something like: “Please share two or three clients whose projects were similar to ours in scope, ideally a lead-generation website with a CRM integration, launched within the last two years, and at least one who has worked with you after launch.”

Asking for a project that had problems may feel awkward. Mature agencies usually understand the request, because they know that how they handled a difficult project says more than a smooth one.

Do agency-chosen references still count, and how do you find others?

Agency-provided references are selected. Nobody hands a buyer the name of an unhappy client. That does not make these calls useless. A selected reference still lived through a real project, and specific questions about events will surface details even from a friendly witness. It does mean you should add at least one reference you found yourself.

Independent references come from a few places. The agency’s portfolio lists live sites, and some of those businesses will answer a polite email. Footer credits on client sites, LinkedIn posts that mention a launch and peer groups in your industry are other routes. Our guide to finding web developers through Reddit, LinkedIn and peer referrals covers how to approach people you do not know.

When you contact an independent reference, be transparent. Say who you are, that you are considering the agency, and that you would value ten minutes of their honest experience. Never pretend to be something else to get the conversation.

It is also fair to tell the agency you plan to contact some clients independently. A confident team will not object. If you want a second opinion on your shortlist before you start these calls, a Blueprint Briefing with us is a short conversation about what your website has to produce, and the questions in this guide apply to us too.

How should you set up a reference call?

A little preparation doubles what you get from twenty minutes. Send a short email first so the reference knows what to expect and can say no easily. Something like this works:

“Hi Dana, [agency] suggested I contact you about the website they built for [business]. We are considering them for a similar project. Would you be open to a 20-minute call this week? I will ask about how the project ran, what changed along the way and what support has looked like since launch. Happy to send the questions in advance.”

Offering the questions in advance is not a weakness. It gives the reference time to check dates and remember details, which produces more accurate answers than memory on the spot. A coached reference will be friendly either way. A prepared reference gives you facts.

Before the call, prepare three things:

• The agency’s promises. Pull the key commitments from the proposal: communication rhythm, change process, testing, ownership, support.
• The reference’s site. Open the live site, check it on a phone and note anything you want to ask about.
• The same script. Use identical core questions for every reference across every agency, so the answers can be compared.

Should you take notes or record the call, and how does consent work?

Take structured notes, and only record the call if everyone on it agrees at the start. Notes in a fixed format are usually enough, and they are easier to compare than recordings.

On recording, the legal picture varies by state. Federal law, in 18 U.S.C. § 2511, generally allows a person who is part of a conversation to record it, but a number of states require the consent of every participant. Calls between states add more complexity. The practical rule avoids all of it: ask “Is it all right if I record this so I can take accurate notes?” at the start, and continue only with a clear yes from everyone. This is general information, not legal advice.

A consent-based method for comparable answers looks like this:

1. Ask permission. Ask to take notes, and separately ask before any recording.
2. Explain the use. Say the notes are only for your hiring decision and will not be published or shared with the agency word for word.
3. Use one template. Write each answer under the same question number for every reference.
4. Mark the type. Label each note as a fact (“launch moved three weeks”), an opinion (“they were great”) or unclear.
5. Read back. At the end, summarize two or three key points and ask if you understood correctly.

Respect the reference’s limits. If someone prefers not to discuss budgets, move on. Asking a client to share confidential contract figures puts them in a difficult position, and the pattern of how changes were handled matters more than the exact amounts.

Which opening questions establish context?

Start with questions that tell you how comparable the reference’s project is to yours. Without context, every later answer is hard to weigh. A glowing review of a five-page site says little about a complex build with integrations.

• What did you hire the agency to build, and what was the main business goal?
• When did the project start, and when did the site launch?
• What platform was the site built on, and what did it need to connect to?
• Who on your side worked with the agency, and how much time did that take?
• Why did you choose this agency over the others you considered?

The last question is revealing. If the reference chose the agency for reasons that match yours, the rest of the call is more relevant. If they chose on price alone and you are choosing on technical depth, weigh their answers with that in mind.

Listen for dates. A reference who launched four years ago experienced a team that may no longer exist in the same form. That is not a problem on its own, but it is a reason to ask the agency who from that project still works there. Our guide on what makes a web development company established covers team continuity in more depth.

Delivery and communication: what should you ask?

Communication problems cause more frustration in web projects than technical problems. Ask about communication in terms of events and habits, not adjectives.

• How often did you hear from the agency, and in what form: calls, email, a project tool?
• Who was your main contact, and did that person change during the project?
• When you sent a question, how long did a useful answer usually take?
• Did you always know what stage the project was in and what was expected from you?
• Were deadlines communicated in advance when they moved, or did you find out afterward?
• How did the agency present design work and collect your feedback?

The question about deadlines matters most. Timelines move on almost every project, often because of the client side: content arrives late, decisions take longer, a stakeholder joins halfway through. What separates good agencies is whether they tell you early, explain why, and propose a new plan.

Who actually did the work on the project?

The people in the sales meeting are not always the people who build the site. That is normal in agencies of every size, but you want to know who actually did the work. References can tell you which roles they saw and how stable those people were.

• Who designed, built and tested your site, as far as you know?
• Did you speak directly with the people doing the technical work, or only with a manager?
• Did the team change during the project, and how was the handover handled?
• Did you ever have the sense that parts of the work were done by someone outside the agency?
• When something technical came up, could someone explain it in plain language?

Outsourcing parts of a project is not wrong by itself. Many agencies use specialists or partners. What matters is whether it was transparent and whether the agency stayed accountable for the result. If a reference was surprised to learn that their site was built by another company, that is worth raising with the agency. Our guide on how to verify a US-based web development company covers delivery locations in more detail.

Compare what the reference says with what the agency told you. If the proposal says a senior developer will lead your build, ask the agency whether that same person led the reference’s project. Consistency between the two stories is a good sign. A large gap is a question to bring back before you sign.

Budget and changes: how did scope and cost hold up?

Almost every web project changes during the build. New pages appear, an integration turns out harder than expected, a stakeholder wants a different direction. The question is not whether the scope changed but how the agency handled it.

• How close was the final project to the scope you agreed at the start?
• When you asked for something new, how did the agency respond?
• Were extra costs explained before the work was done, or did they appear on an invoice?
• Did you ever feel pushed into additions you did not need?
• Was anything in the original scope quietly dropped?
• Looking back, did the final cost feel fair for what you received?

You do not need the reference to tell you numbers. A reference may not be allowed to share them, and the amounts would not transfer to your project anyway. What transfers is the pattern: written change requests with a cost and a time estimate, approved before work started, are the mark of a team you can budget with.

The question about dropped items is underrated. Some projects stay on budget because parts of the scope disappear without anyone saying so. A reference who remembers that the blog migration, the second language or the booking integration never happened is giving you important information.

What happened when something went wrong?

Every project has problems. A reference who says nothing went wrong either had an unusually simple project or is being polite. Ask in a way that makes honesty easy.

• What was the hardest moment in the project?
• What was the biggest problem, and how did the agency handle it?
• Did the agency ever admit a mistake? What happened next?
• Was there a point when you considered stopping the project?
• If you had a disagreement, how was it resolved?

Phrasing matters. “Were there any problems?” invites “No, it was fine.” “What was the hardest moment?” assumes there was one, which is almost always true, and gives the reference permission to describe it.

Listen for ownership. The strongest answers sound like this: “The integration broke right before launch, they told us the same day, explained what happened and fixed it over the weekend.” The weakest sound like: “There were some issues, but it worked out eventually.” Vague answers are not proof of a bad agency, but they give you nothing to compare.

Also note whose problem it was. Some difficulties start on the client side: late content, changing priorities, slow approvals. An agency that handled those situations with clear reminders and a revised plan is showing exactly the behavior you need when your own project hits a snag.

Launch quality: what did launch day look like?

A launch shows whether testing happened before the site went live or after clients found the problems. References remember launches well, because a messy one is stressful.

• How did the launch go, and were there problems in the first days?
• Did the agency give you a testing plan or a list of what they checked?
• Did forms, phone links and integrations work from day one?
• Did you lose search traffic or rankings after launch, if you had an old site?
• Were analytics and tracking working when the site went live?
• How quickly were launch issues fixed?

For a redesign, the question about search traffic is important. Moving to a new site without redirects from old URLs is one of the most common ways to lose visibility. A reference who saw traffic hold steady, or who remembers the agency mapping old pages to new ones, is describing a careful process.

Tracking is the other launch detail buyers forget to ask about. If analytics was set up weeks after launch, the reference has no clean before and after. Every site we build launches with GA4 and Google Search Console connected, tracking form submissions, phone clicks, WhatsApp clicks and bookings, so the measurement starts on day one. Ask every agency, including us, what is in place at launch. If you want to walk through a launch checklist for your own project, you can book a Blueprint Briefing.

Post-launch experience: what happened after the final invoice?

The subtitle of this guide asks what happened after the final invoice, and this is the part of the call buyers skip most often. The build may take a few months. You may live with the site and the agency for years.

• Are you still working with the agency? If not, why did the relationship end?
• When you needed a change or a fix after launch, how did you request it, and how long did it take?
• Was support part of an agreement, or handled case by case?
• Did the agency suggest improvements on its own, or only respond to requests?
• Has the site needed major repairs since launch?
• Would you hire them again for your next project?

The last question is the most diagnostic of the whole call. A reference who has already hired the agency again, or plans to, is giving you the strongest evidence a past client can give. A long pause before the answer is information too.

For support, separate response from resolution. “They always answered within a day” is good, but ask whether the problem was actually fixed within a reasonable time. A quick acknowledgment followed by weeks of silence is a common pattern that a simple “Do they respond fast?” will not reveal.

Access and handover: does the client control the site?

Ownership is rarely discussed until it becomes a problem. Ask references directly, because many of them only found out what they owned when they tried to make a change.

• Do you have admin access to the website, the domain and the hosting?
• Are the domain and hosting accounts in your company’s name?
• If you wanted to switch to another team tomorrow, could you?
• Did you receive documentation or training on how to update the site?
• Can you edit content yourself, or does every change go through the agency?

A reference who answers “I am not sure” to the access questions is not describing a bad agency, but it is a sign that ownership was not explained during the project. Ask the agency how it handles access, and get the answer in your contract.

Our own position is written on our web development page: the domain, hosting account and code are yours, whether the site is custom-coded or custom WordPress, and another team can maintain it if you ever choose to. Whatever agency you hire, ask for the equivalent in writing and confirm with a reference that it worked that way in practice.

How do you ask about results without leading the reference?

Buyers often want to know whether the site “worked.” The difficulty is that a leading question produces a polite answer. “Did the new site bring you more leads?” invites “Yes, definitely.” Neutral questions get more honest answers.

• What did you hope the new site would change for your business?
• What has actually changed since launch, as far as you can tell?
• How do you measure whether the site is doing its job?
• Did anything else change in your business at the same time, such as advertising or pricing?
• Is there anything you expected the site to do that it does not?

The question about other changes is important. Results after a launch often come from several sources at once. A reference who can separate them is giving you careful evidence. Our guide on what a credible web development case study should show explains baselines and attribution in detail.

Be careful with search results in particular. If a reference says the agency got them to the first page, ask for which searches and since when. Positions vary by searcher, location and time, and no agency controls them. We do not promise rankings or AI citations to anyone, and a reference describing guaranteed positions from any agency deserves a follow-up question.

How do you read between the lines of a friendly reference?

Most references want to be helpful and kind at the same time. That means the most useful information often comes indirectly. Learn to listen for a few patterns.

Specific versus general. “They launched two weeks late because our content was late, and they told us a month ahead” is specific. “They were great to work with” is general. Specific answers can be compared across references. General ones cannot.

Hesitation. A pause before “Would you hire them again?” or an answer like “For the right project, yes” deserves a gentle follow-up: “What kind of project would you not hire them for?”

Faint praise. Phrases such as “they got it done” or “no major complaints” are often polite ways of saying the experience was average. That might be fine, but it is not a strong endorsement.

Unprompted detail. When a reference volunteers a story you did not ask about, positive or negative, it is usually what they remember most clearly.

Relationship. Ask how the reference came to know the agency and whether they received anything for acting as a reference. In advertising, the FTC expects material connections such as payments or discounts to be disclosed, as its Endorsement Guides questions and answers explain. A private call is not an ad, but the same logic is a fair question.

When you are ready to compare these signals across finalists, the scoring sheet later in this guide helps, and a Blueprint Briefing is a good place to test how we answer the same questions.

Which answers are red flags, and which are false alarms?

Some reference answers deserve real caution. Others sound worrying but usually have an ordinary explanation. Treat each as a question to bring back to the agency, not as a verdict.

The biggest red flag is not an answer. It is an agency that becomes defensive or evasive when you bring a reference’s concern back to it. A team that explains what happened, what it learned and what it does differently now is showing you the behavior you want.

What does a complete reference-interview script look like?

Here is the full script, in the order that works best. It fits into about twenty to thirty minutes if you keep follow-ups short. Use the same core questions for every reference.

For each answer, write one line of notes and a label: fact, opinion or unclear. If a reference declines a question, write “declined” and move on. That is a valid answer, not a failure of the call.

How do you compare reference answers across agencies?

Reference calls blur together quickly. By the third call, you will remember the friendliest voice, not the most useful facts. A simple scoring sheet keeps the comparison honest.

Score six areas from 0 to 2 for each reference: communication, scope and changes, problem handling, launch, post-launch support and ownership. Use these meanings:

Add a separate yes, no or conditional for the rehire question. Do not add it to the score. It is the summary judgment, and it deserves its own column.

Then look for patterns rather than totals. Two references who independently describe slow post-launch support are more meaningful than one perfect score. One low score in an area that does not matter to your project, such as design iteration on a site where you supply the design, can be set aside.

Keep the scores with the rest of your vetting. Directory reviews, covered in our comparison of Clutch, DesignRush and GoodFirms, the portfolio and the proposal all feed the same decision. References carry the most weight on support and problem handling, because those are the areas nothing else can show you.

How do we handle the same questions at GoSocial?

It would be easy to write this guide and exempt ourselves. So here is what we can say publicly, and what you should check with us the same way you check anyone else.

GoSocial is a custom web design company in Boca Raton, Florida, working with businesses across the United States since 2016, and we have built 2,500 websites. We are one accountable team, CEO-led: the people who plan the site build it. Our process runs from discovery and strategy to architecture, design and content, development, testing, launch and measurement.

On the topics references are asked about:

• Ownership. The domain, hosting account and code are yours, and another team can maintain the site if you ever choose to.
• Measurement. Every site launches with GA4 and Google Search Console connected, tracking form submissions, phone clicks, WhatsApp clicks and bookings.
• Promises. We do not promise a score, a ranking or an AI citation. We build for the metrics and show you the measurements.

Use the script in this guide with us. Ask about our past projects that are closest to yours, look at live work in our portfolio, and bring whatever a reference tells you back to the conversation. You can also reach us through our contact page.