The client interview: prompts that pull requirements in 10 minutes

Let’s be real. The “discovery call” is broken. It is a sixty-minute, soul-draining mess that almost always ends with a vague “So, yeah, just send over some ideas” and a pit in your stomach. You get off the call with a page full of messy notes, a request for a “blue button,” and zero actual understanding of the real business problem.

This is not the client’s fault. They are experts in their problem, not in our process. But it is our fault if we let it happen. We have been trained to be accommodating, to nod along, and to waste an hour just “vibin'” in the hopes of landing the project. That ends today.

We are replacing that chaotic, passive hour with a ten-minute, laser-focused, surgical interview. We are going to stop being order-takers and start being the expert guides our clients are desperate for.

This is your new playbook. This is The Client Interview: Prompts That Pull Requirements in 10 Minutes. It is a high-speed, high-value system for digging past the surface-level “wants” and getting to the “needs” that actually matter. This framework is your permission slip to take control, establish authority, and prove your value before a single cent has been paid. Your days of guessing are over.

Part 1: The Mindset Shift – Stop Asking “What Do You Want?”

The single worst question in the creative and technical world is “So, what do you want?”

This question is a trap. It is a total abdication of your expertise. When you ask this, you are inviting the client to “solutioneer.” You are asking them to do your job, to design the solution, to pick the features. The result is always the same: a Frankenstein’s monster of a project, built on vague assumptions and feature requests from three different departments.

We are not short-order cooks. Our job is not to just “make the logo bigger.” Our job is to be the project’s doctor. A good doctor does not ask, “So, what prescription do you want?” A good doctor listens to the symptoms and then writes the prescription for the patient.

The 10-Minute Mandate: Why It Works

This new mindset is built on one core rule: The discovery interview is ten minutes. No more, no less.

This is not about being rude. It is about being professional. Setting a hard limit of ten minutes does three magical things:

It Forces Focus: There is no time for small talk about the weather or rambling anecdotes about a competitor’s website. Every second is dedicated to high-value questions.
It Respects Everyone’s Time: You are signaling to the client that you are a busy, in-demand professional, and you respect that they are, too. This instantly builds perceived value.
It Prevents “Solutioning”: In ten minutes, there is only time to talk about the problem. There is no time to get lost in the weeds of button colors or font choices.

Decision fatigue is a real drain on cognitive resources (Source: [Behavioral Science Institute, The Psychology of Choice]). By limiting the time, you are making a strategic choice to focus on the highest-impact information, which is exactly what a high-value consultant does. This is your first move in establishing that you are the expert they hired.

Your New Role: The Problem-Finder

From now on, you have one mission in that first call: Find the problem. That is it. You are not designing, you are not pricing, and you are not promising. You are diagnosing.

The client will almost always come to you with a solution.

“We need a new website.”
“We need an app.”
“We need a social media campaign.”

Your job is to smile, nod, and gently hit the reverse button.

“That’s interesting. What problem is the current website causing?”
“An app is a great idea. What is the core user problem that an app would solve?”
“A campaign sounds cool. What is the business objective we are trying to hit?”

This pivot from “solution” to “problem” is the core of The Client Interview: Prompts That Pull Requirements in 10 Minutes. The following script is your scalpel.

Part 2: The 10-Minute Script: 9 Prompts That Pull Requirements

Get on the call. Thank them for their time. Be warm, be energetic, and then get right to it. Say this:

“This is awesome. I am so excited to dig in. I have a 10-minute framework I use to get to the core of a project super-fast. It helps me build a perfect proposal. Are you ready to dive in?”

You have just set the stage, got their permission, and established control. Now, start the timer.

Minutes 1-3: The Problem & The Pain (The “Why”)

We are starting at the 30,000-foot view. We need to know why we are even on this call.

Prompt 1: “If this project is a massive, home-run success six months from now, what single problem will it have solved?”

This is the ultimate opening question. It bypasses the “we need a website” solution and forces them to name the actual, underlying problem. It also frames it in terms of success. You will get answers like:

“Our sales leads will stop drying up.”
“Our customer support team will not be spending 80 percent of their day answering the same three questions.”
“We will finally be seen as a legitimate player, not a cheap knock-off.”

Boom. That is the real brief.

Prompt 2: “What is happening right now that makes this problem so urgent?”

This question uncovers the pain. Problems can exist for years. The pain is what makes them act now. This helps you find the business case.

“We just lost our biggest client because they said our system was ‘unusable’.”
“Our main competitor just launched a new site, and we look ancient.”
“We are burning $10,0-00 a month on ad spend that is not converting.”

Now you know the emotional driver and the financial stake. This is pure gold.

Prompt 3: “How are you trying to solve this problem today? What is not working?”

This is the “what have you tried” question. It shows you respect their efforts, and it stops you from proposing something they have already tried.

“We tried to duct-tape it with a cheap plugin, but it broke.”
“We have three different spreadsheets, and no one knows which one is right.”
“Honestly, we just yell at the intern to fix it. It is not a system.”

You now have a clear picture of the baseline: the problem, the pain, and the failed solutions.

Minutes 4-6: The Audience & The User (The “Who”)

Now that we know the why, we need to know the who. We cannot build anything for “everyone.”

Prompt 4: “Who is the one specific person we are building this for? And, just as importantly, who are we not building this for?”

This is the most powerful segmentation question you can ask. The “who it is not for” part is the secret. It gives them permission to exclude.

“This is for a stressed-out department head who is 50 years old and not tech-savvy.”
“It is not for the 22-year-old developer who wants a million features. It is for the beginner.”

This focus on user-centric design is the only way to build a product that people actually love and use (Source: [Nielsen Norman Group, The Value of User Personas]). You have just saved yourself from “feature creep” by defining the user and the anti-user.

Prompt 5: “Walk me through that person’s day. What do they believe, what do they want, and what is currently stopping them?”

This is an empathy-mapping speed-run. You are asking the client to step into their customer’s shoes.

“She wakes up, is already dreading her inbox, and just wants to find the report before her 9 AM meeting. She believes our current system is hiding it from her on purpose. She is stopped by a password reset screen she has seen three times this week.”

In 30 seconds, you have a story, a motivation, and a clear villain (the password screen). This is infinitely more valuable than “we need a better login flow.”

Minutes 7-8: The “Done” Check (The “What”)

We know the why and the who. Now we define what. We need to know what “success” looks like in a measurable way.

Prompt 6: “Fast forward six months. We have built the solution. How will we ***know*, with data, that we won?”**

This is the “metric of success” question. It forces them to attach a number to their feeling.

“Our support tickets for ‘where is the report’ will drop by 90%.”
“Our lead conversion rate will go from 1% to 3%.”
“We will have 500 new signups for the trial.”

This is your new project goal. You are not building a “pretty website”; you are building a “machine to increase lead conversion to 3%.” That is a million-dollar difference in value.

Prompt 7: “What is the single most important action you want this user to take?”

This question forces prioritization. A website can do 100 things, but it can only do one thing first.

“Sign up for the free trial.”
“Book a demo.”
“Buy the product.”

This is your primary call to action. All design and copy will now be built to serve this one action.

Minute 9: The “Don’t” List (The Constraints)

The most creative briefs are full of constraints. This is where you find the boundaries.

Prompt 8: “What is explicitly off the table? What must this project not do, or what are the hard constraints?”

This is the “anti-goal” question. It is often more illuminating than the goals.

“It cannot integrate with Salesforce. We are migrating away from it.”
“It must not feel corporate or use blue. We are rebranding.”
“The budget is a hard stop at $50,000, and the launch date is October 1st, period.”

This is a critical part of defining project scope (Source: [Project Management Institute, The Importance of Defining Constraints]). You have just identified the budget, timeline, and technical landmines in one question.

Minute 10: The Single Point of Contact (The “How”)

The final, and most crucial, question. This is not about the project; it is about the process.

Prompt 9: “Who is the one person on your team who has the final ‘yes/no’ authority to approve this project and its deliverables?”

This question solves “design by committee” before it starts.

“That’s Susan, the Head of Marketing.”
“Well… it’s kind of me, but also the CEO…”

If you get the second answer, you have to gently push. “For a fast-moving project, we need a single point of contact for all approvals. Who can we agree will be our ‘Project Owner’?” Establishing this single decision-maker is non-negotiable for an efficient project (Source: [Scrum & Agile Methodologies, The Role of the Product Owner]).

Part 3: After the 10 Minutes – The “Reverse Brief”

The call is over. You did it in ten minutes. The client is slightly stunned but incredibly impressed. Your work is not done. You have 20 more minutes.

You are going to immediately write the most powerful email of your professional life. It is called the Reverse Brief. You are going to take their answers and play them back to the client in a clear, organized email.

Subject: Our 10-Minute Call: The Plan

“Hi [Client Name],

That was amazing. I am so excited about this.

To make sure I heard you correctly, here is the entire project on one page:

1. The Core Problem: Your support team is drowning in password reset tickets, which is costing you time and frustrating your new users.

2. The Primary Audience: A non-technical, stressed-out department head who just wants to find her report. We are not building for expert developers.

3. The Definition of Success: We will win when ‘password reset’ support tickets drop by 90% and we get 500 new trial signups in the first three months.

4. The Single Most Important Action: The user must be able to “Sign up for the free trial.”

5. The Hard Constraints: The project cannot integrate with Salesforce and must launch by October 1st.

6. Our Project Owner: Susan will be the final decision-maker for all approvals.

Does this perfectly capture our mission?

If you can confirm ‘Yes, this is it,’ I will have a formal proposal and statement of work in your inbox in the next 24 hours.

So excited to get this started.”

Conclusion: You Are Now the Expert in the Room

You see what you did? You took a vague “we need a website” and turned it into a specific, measurable, time-bound project with a single stakeholder. You did it in ten minutes. You immediately followed up with a “Reverse Brief” that proved you were listening, and you asked for a “yes” to get sign-off on the problem before you even think about the solution.

This is The Client Interview: Prompts That Pull Requirements in 10 Minutes. It is not just a script. It is a new way of working. It is your framework for establishing authority, building trust, and, most importantly, setting up every single project for a massive, undeniable win.

Stop being an order-taker. Stop dreading discovery calls. Start leading.