Skip to content
Requirements & Scoping

How to Gather Requirements From Clients: A 6-Step Process for Agencies

By Danial Pourgolab · 11 min read · November 2026

Part of Client Requirements & Scoping: The Complete GuideTitle card on a white background: the section label "Requirements & Scoping" in blue small caps above the headline "How to Gather Requirements From Clients: A 6-Step Process for Agencies" in dark type, with a short blue rule beneath it and the ReqBrief wordmark in the lower right.

The kickoff went well. The client nodded through the proposal, said the brief looked right and signed. Three weeks into the build they ask where the member login is. They mentioned it to their sales lead once and never to you. Nobody lied. The requirement existed the whole time. It just never made it from their head into your plan.

That is what most requirement gathering failures look like at an agency. It is rarely one dramatic miss. It is a dozen small things that went unsaid on the first call and got half answered in an email thread. They turn up later as 'quick changes' that eat the margin you priced in.

The fix is not a longer form or a longer call. It is a process: a fixed order of work that takes you from 'we should talk' to a document the client has signed. Below is a six step version for agency owners who are tired of finding the real brief in week three. It covers choosing how to ask, what order to ask in, how to chase vague answers and how to lock everything down before anyone opens a design file.


Why requirements go missing between the first call and kickoff

Before the steps, it helps to see where things actually leak. In most agencies the requirements pass through three or four people before work starts. The first takes the sales call, the second writes the proposal, the third sets up the project board and the fourth builds the thing. Each handover drops something, and nobody notices until the gap shows up in the work.

Clients add to the problem without meaning to. They know their business so well that they skip the parts that feel obvious to them. They answer the question you asked, not the question you needed answered. Often they have not made the decision yet, so 'we'll want a blog' really means 'someone in marketing once mentioned a blog'.

So the goal is not to ask more questions. The goal is to ask the right ones in the right order, write down what you hear in a form the client can check and make the gaps visible while they are still cheap to fill.


Step 1: Decide what you need to know before you ask anything

Most agencies start gathering requirements by opening a template and sending it. Start one step earlier. Write down the decisions your team will have to make on this project, then work backwards to the information each decision needs.

For a website rebuild, your team will have to decide:

  1. 1Pages and templates. Which pages exist, and which templates the designer needs to cover them.
  2. 2CMS and integrations. What the content management system has to do, and which integrations the developer must build.
  3. 3Content. What content the client supplies, and when it arrives.
  4. 4Approvals. Who approves each stage.

Every one of those decisions needs an answer from the client. If you cannot name the decision a question supports, you probably do not need to ask it.

This step also shows you what you already know. Read the proposal, the sales notes and the client's current site before you ask them anything. Few things wear down a client's patience faster than being asked to repeat what they told your salesperson last Tuesday.

The rule for every question Every question you send should map to a decision your team has to make. Questions that map to nothing are noise, and noise is what makes clients stop answering properly.

Step 2: Choose the method that fits the client

There is no single right way to collect requirements. The IIBA's BABOK Guide, the standard reference for business analysts, describes a wide range of elicitation techniques, including interviews, workshops, questionnaires and document analysis. For an agency, four of them do most of the work.

  1. 1A live call or interview. This works best for the first conversation and for anything strategic: goals, audience and what success looks like. You can follow up in the moment. The weakness is that what was said lives in someone's notes, and notes are where requirements go to die.
  2. 2A written questionnaire. This suits factual, list-like details such as logins, brand assets, existing tools and page inventories. Clients can answer in their own time and look things up. The weakness is that nobody follows up on a weak answer, so a one-line reply sits there looking complete.
  3. 3A workshop. A workshop is worth the time on larger projects where several stakeholders disagree. With the marketing lead and the operations lead in one room, conflicts come out early instead of at the review stage.
  4. 4Document and asset review. Look at their current site, analytics, brand guidelines and competitor examples, plus the spreadsheet someone uses to run the business. Clients often show you a requirement they would never think to say out loud.

Most projects need a mix. A common pattern starts with a short call for goals and context. A structured set of written questions covers the details, and a review of whatever the client sends over comes last.

Be honest about the limits of a written form, though. Sending a list of fields through a static tool like Google Forms is easy. But the form cannot notice that 'not sure yet' is the answer to the most important question on it. Someone on your team has to read every reply and chase the gaps, and in a busy week that someone is nobody.


Step 3: Ask in the right order

Order matters more than most agencies realise. Ask a client about page layouts before you have agreed what the site is for and you get a wish list. Ask about goals first and every later answer has something to be measured against.

A reliable sequence moves from broad to narrow:

  1. 1Goals. What has to be true in six months for this project to count as a success? Push for a business outcome, not a deliverable. 'More enquiries from commercial clients' is a goal. 'A new website' is not.
  2. 2Audience. Who will use the thing you are building, and what are they trying to do? This is often where you find out the site has two audiences with opposite needs.
  3. 3Scope. What is included and, just as important, what is not. Cover pages, features, integrations and content. Write the exclusions down as clearly as the inclusions.
  4. 4Constraints. Cover budget, deadline, technical platform, legal or accessibility requirements and internal approvals. Constraints quietly rule out half of the wish list, so you want them before anyone gets attached to an idea.
  5. 5Decision making. Find out who signs off, who else has a view and how disagreements get settled. The person on the call is often not the person with the final say.

If you want ready-made wording for each stage, our list of questions to ask clients before starting a project follows this same order and adapts to most project types.

One practical point: ask one thing at a time. A question like 'Who is your audience and what do you want them to do?' gets half an answer. Split it in two and you get both halves. It feels slower, but it saves you a round of follow-up emails.


Step 4: Chase the vague answers

This step separates a usable brief from a polite one. Clients are not being difficult when they say 'modern and clean' or 'simple to use'. They are describing a feeling. Your job is to turn that feeling into something a designer or developer can build to.

Three follow-up patterns cover most cases.

  1. 1Ask for an example. 'Clean' means something different to everyone. Ask for two sites they like and one they dislike, and what specifically they like or dislike about each. The dislike is often more useful than the likes.
  2. 2Ask what happens next. When a client says they need a contact form, ask what happens to the enquiry after it is sent. Who receives it, where does it go and does it need to reach a CRM? A form is one line in a brief, but the workflow behind it can be a week of build.
  3. 3Ask for the number. 'Lots of products' could mean 40 or 4,000, and those are different projects. 'A few languages' could be two or nine. Whenever an answer contains a quantity word, ask for the actual figure or a best estimate.

Watch for answers that sound complete but put off the decision: 'we'll figure that out later', 'whatever you recommend' or 'the usual stuff'. Each one is a requirement that will come back later as a change. You do not have to resolve all of them on the spot. You do have to record each one as an open question, with an owner and a date.

This chasing is where a manual process usually breaks down. On a call it depends on the person asking remembering to probe. On a form it does not happen at all. It is the gap ReqBrief was built to close. It interviews your client one question at a time, follows up when an answer is vague and turns the replies into a structured brief your team can check.


Step 5: Write it back and have the client check it

Requirements that exist only in call notes are not requirements yet. Next, pull everything you have gathered into one document, written in plain language, and send it back to the client to check.

The format matters less than the contents. At minimum the document should cover the goal, the audience, what is in scope, what is explicitly out of scope, the constraints, the open questions and the assumptions you made to fill gaps. Most agencies leave out the assumptions, and they are the most valuable part. A written assumption can be corrected in a minute. An unspoken one gets discovered at the review.

If you need a structure, our project brief template with sections for scope, exclusions and open questions gives you one, and this is the point in the process where it earns its keep.

Ask the client to read the document properly, not to skim it and reply 'looks good'. One useful trick is to ask them a direct question about it, such as 'Is there anything on the out of scope list you expected us to do?' A specific question forces a real read in a way that 'any feedback?' never will.


Step 6: Get sign-off and agree how changes work

The last step turns a checked document into an agreed one. Get the person with final authority, the one you identified in step 3, to approve it in writing before any production work starts. An email reply is enough. A verbal 'yes, go ahead' on a call is not, because nobody will remember which version they agreed to.

Sign-off does not mean the requirements can never change. Clients learn things during a project, and some changes are good ones. What sign-off gives you is a baseline. When something new comes in, you can point to the agreed document and ask a calm question: is this a change, and if so, what does it do to the timeline and the budget?

Agree up front how that question gets answered. A simple written route for new requests, such as a one page change request template used for anything outside the signed scope, turns an awkward argument into routine admin.

Sign-off is also the moment to settle the open questions. Each one needs an owner and a date. Say the client has not decided on the blog by the end of the design phase. The brief should already say what happens in that case, whether that is dropping it from this phase or pricing it separately.


Where this process usually breaks

Agencies rarely fail because they lack a template. They fail at predictable points in the process, and most of those points are habits.

  1. 1Skipping step 1. Teams jump straight to a template, ask forty questions and still miss the one integration that drives the build.
  2. 2Treating the first call as the whole job. The first call is for context. The details come afterwards, in writing, where they can be checked.
  3. 3Accepting the first answer. A short answer is not a complete answer. The real requirement usually sits in the follow-up.
  4. 4Signing off on a summary nobody read. If the client approves a document within two minutes of receiving it, assume they have not read it, and ask the direct question from step 5.
  5. 5No owner for the process. If gathering requirements is everyone's job, it is nobody's. Name one person per project who owns the brief until sign-off, and make it their job to prioritise the open questions.

None of this needs a longer sales cycle. It needs a fixed order, a written record and the habit of following up. Run the six steps on your next project, then compare the change requests that come in against the last project you ran without them.

Good requirement gathering is your first line of defence against overruns. For the rest of the picture, read our guide on how to prevent scope creep before the project starts.

ReqBrief interviews your client one question at a time, follows up when an answer is vague and hands you a structured brief to check and send for sign-off. Try it on your next project and see what the first call missed.

Try ReqBrief free →

Frequently asked questions

What is the best way to gather requirements from clients?

Most agencies get the best results from a mix of methods rather than a single one. Start with a short call to understand goals and context. Then send a structured set of written questions for the details, and review any documents or assets the client already has. Ask in order from broad to narrow: goals, audience, scope, constraints and who makes decisions. Follow up on every vague answer. Finish by writing the requirements into one document the client checks and signs off before work starts.

What questions should you ask a client before starting a project?

Begin with the goal: what has to be true after the project for it to count as a success. Then ask who the audience is and what they need to do. Next, ask what is in scope and what is explicitly out of scope. After that, ask about constraints such as budget, deadline, platform and legal requirements. Finally, ask who has the final say on approvals. Ask one thing at a time, and ask for examples or numbers whenever an answer is vague.

What do you do when a client does not know what they want?

Do not ask them to describe the finished product. Ask about the problem they want solved and what success would look like for their business. Show them examples and ask what they like and dislike about each, because reactions are easier to give than descriptions. Record any undecided points as open questions, each with an owner and a deadline. That way the gaps are visible and agreed rather than discovered halfway through the build.

Who should sign off on project requirements?

The person with real authority over the project should sign off, and that is not always the person who attends the calls. Identify them early by asking who approves the work and who else has a say. Get their approval in writing, an email reply is enough, before production starts. Agree at the same time how changes to the signed requirements will be requested and priced.