The best workflow customer interviews don’t start with “Would you use an app that…?” They start with a recent piece of work: what happened, who got involved, which tools they used, and where the process slowed down or went wrong.
That distinction matters. People are usually good at describing what they did and what frustrated them. They’re less reliable at predicting what they’ll buy, adopt, or change. If you’re doing customer interviews for a workflow product or a productized service, your goal is to understand the job as it actually happens—not to collect compliments about your idea.
For agency teams, this kind of problem discovery can reveal costly friction hidden in everyday handoffs: a client request buried in email, an invoice waiting on an approval, or a team member copying information between tools. These small inefficiencies compound. They can erode margins, frustrate clients, and make growth harder than it should be.
Below are practical questions to help uncover those problems, understand their impact, and identify buying signals without leading the conversation.
Why Workflow Interviews Should Focus on Real Events
A workflow is rarely a neat sequence that lives in one system. It is the combination of people, decisions, deadlines, documents, and tools that moves work from request to completion. The official process may say one thing, while the real process involves reminders, personal spreadsheets, forwarded emails, and someone who “just knows” what to do next.
That gap is where opportunity often lives. Frustration can be the seed of a durable business when it points to a repeated, expensive problem—not just a temporary annoyance. The key is to learn how often the problem occurs, what it costs, and what people already do to get around it.
In customer interviews, ask about the last specific instance rather than a hypothetical future. “Tell me about the last time a project was delayed” is more useful than “Do projects get delayed?” The first invites a story. The second invites a quick yes or no.
Start With the Customer’s Role and Context
Before digging into a workflow, learn who you’re speaking with and what responsibility they carry. A founder, account manager, finance lead, and delivery specialist may experience the same process very differently. Their answers help you understand whose pain is most acute—and who might have authority to act on it.
- Can you tell me about your role and the work you’re responsible for? Which parts of the client or delivery process do you personally handle? What kinds of work are most common for your team? How has your team or workload changed over the past year? Who else is involved when this process needs to move forward?
Listen for context that changes the stakes: a lean team handling more clients, a growing agency with new layers of approval, or a specialist trying to protect billable time from administration. These details help you avoid treating every workflow problem as if it were equally important.
Ask Questions That Reconstruct the Workflow
Choose one recurring process—such as onboarding a client, handling a change request, delivering a project, or sending an invoice—and walk through a recent example from start to finish. Don’t assume the workflow begins where your product might begin. Follow the work back to the original request or trigger.
What triggered the process? Was it a signed agreement, a client email, a form, a meeting, or an internal decision? What happened next? Who took the first action, and how did they know it was theirs to take? What information did you need? Where did that information come from, and was anything missing? Who else had to act or approve? How were they notified, and what happened if they were unavailable? How did you know the work was complete? Was there a clear handoff, status, or record?Helpful follow-ups include “What happened after that?”, “Can you show me an example?”, and “How did you handle it that time?” If the participant says, “We usually send agency workflow automation tools an email,” ask what the email contains, who receives it, and what the recipient does with it.
Be especially curious about unofficial steps. A team may say that invoices go out when a project is complete, but in practice someone might check a project board, ask an account manager for approval, search email for a scope change, and then recreate the invoice manually. That sequence is the workflow worth understanding.
Find Friction, Workarounds, and Tool Sprawl
Tool sprawl isn’t simply having many apps. It’s the effort required to keep them connected in people’s heads and through manual work. Teams may use email for requests, a project tool for assignments, a spreadsheet for tracking, and an accounting system for invoices—with no reliable link between the records. The tools can each work as designed while the overall process remains fragile.
Ask questions that reveal how people cope with the gaps:
- Which step takes longer than it should? Where do requests or important details most often get lost? What do you have to copy and paste from one tool to another? Which information do you track outside your main systems, and why? What reminders or follow-ups do you send repeatedly? When something goes wrong, how do you find out? What part of this process depends on one specific person’s memory?
Try not to label the problem for the customer. “Is your email workflow messy?” invites agreement or disagreement. “How do you keep track of requests that arrive by email?” encourages them to describe what they actually do.
Also ask about workarounds without dismissing them. A spreadsheet may look like a temporary patch, but if everyone relies on it, it is part of the operating system. Find out who maintains it, how often it is updated, and what breaks when it is wrong or out of date.
Measure the Cost of the Problem
Frustration is useful evidence, but frustration alone doesn’t establish a viable business opportunity. A problem becomes more compelling when it has a measurable consequence: lost time, delayed cash, rework, missed deadlines, client dissatisfaction, or capacity the team can’t sell.
Use questions such as:
- How often does this happen in a typical month? How much time does your team spend handling it? What happens if the task is delayed by a day or a week? Has this caused rework, a missed deadline, or a client escalation? How does it affect project profitability or the time available for client work? What does the current workaround cost in staff time or outside support?
For agency operations, tie the answer to delivery and margin. If an account manager spends an hour chasing approvals on every project, that effort may be invisible in the project budget—but it still reduces the margin. If an invoice goes out late because a final approval is buried in email, the team may be doing the work but waiting longer to collect cash.
Avoid forcing precise numbers when the customer doesn’t have them. Ask for ranges, examples, or what they use as a proxy. “How many invoices were delayed last month?” may be answerable even when “What is the exact cost of invoice delays?” is not.
Understand Agency and Productized-Service Pressures
Agencies and productized-service teams often face a specific tension: they need consistent delivery to protect margin, but client work brings variation. A service can be packaged and priced clearly while the operating reality still includes custom requests, scope changes, exceptions, and different approval paths.
Questions that expose this tension include:
- Which parts of delivery are standardized, and which still vary by client? What happens when a client request falls outside the agreed scope? How do you record a change and make sure it reaches the delivery and billing teams? Where does work tend to pile up when client volume increases? What would become difficult if you took on 20% more clients without adding staff? Which step is hardest to delegate to a new team member?
Listen for signs that the workflow problem limits growth. Perhaps senior staff must inspect every project before an invoice is sent. Perhaps the service is repeatable in theory, but each client’s information arrives in a different format. The strongest opportunity may be a clearer intake and handoff—not a bigger project-management system.
Ask About AI Expectations Without Chasing Hype
AI has raised expectations that many manual processes can now be automated instantly. Some tasks are good candidates for assistance, such as extracting details from an email or summarizing a client request. But AI does not automatically solve unclear ownership, missing information, inconsistent service definitions, or weak approval rules.
Ask practical questions before discussing AI:
- Which repetitive task would you most like to reduce or remove? What information would a system need to complete that task reliably? What mistakes would be unacceptable? Which decisions require a person’s judgment or approval? Have you tried automation or AI for this already? What happened? How would you verify that the result is correct?
If a participant says, “AI should handle our invoices,” clarify the job. Do they mean identifying billable work, drafting invoice descriptions, checking rates, routing an approval, or sending the invoice? Each task has different data requirements and risk. This kind of detail prevents inflated expectations from turning into an unreliable solution.
Recognize Buying Signals in Customer Interviews
Positive reactions are not the same as buying signals. “That sounds useful” is a polite response; it doesn’t prove urgency, budget, or willingness to change. Stronger signals are grounded in present behavior and commitment.
Signal What it may indicate Useful follow-up They already pay for a workaround The problem has a recognized cost or priority What does that cost, and who approved it? They can describe a recent failure in detail The pain is real and memorable What did your team do afterward? They ask about implementation or migration They are considering how adoption would work What systems or people would need to be involved? They offer to share a sample or introduce a decision-maker They are investing time beyond the interview Who should review this with you? They ask about pricing, timing, or a pilot There may be active intent to buy What needs to be true for you to move forward?You know what's funny? test the evidence gently. Ask how the team evaluates new tools or services, who owns the budget, what alternatives they have considered, and whether there is a deadline for addressing the problem. The goal isn’t to turn a discovery interview into a sales pitch. It’s to distinguish a painful, funded priority from a general preference.
Questions to Avoid—and Better Alternatives
Leading questions can make weak ideas look validated. Replace opinions about your proposed solution with questions about the customer’s recent behavior.
- Avoid: “Would you use a platform that manages all your client emails and invoices?” Ask: “How do client requests move from email into delivery and billing today?” Avoid: “Would this save you time?” Ask: “How much time did the last example take, and what else could you have done with that time?” Avoid: “Do you think AI could automate this?” Ask: “Which steps have you tried to automate, and what still requires manual review?” Avoid: “Is this your biggest problem?” Ask: “What are the other operational problems competing for attention right now?”
A Simple Structure for a 30-Minute Interview
Context, 5 minutes: Learn the participant’s role, team, and responsibilities. Recent example, 10 minutes: Reconstruct one real workflow from trigger to completion. Friction and impact, 10 minutes: Explore workarounds, frequency, consequences, and current spending. Next steps, 5 minutes: Ask what they have tried, who else should be involved, and whether they are open to a follow-up.Take notes on what the customer did, not just what they said they want. Capture the trigger, tools, people, handoffs, delays, workarounds, and consequences. After several interviews, compare patterns: Which problems repeat? Which roles feel them most? Which issues have a clear cost or active budget?. Pretty simple.
Turn Frustration Into Useful Problem Discovery
Good customer interviews don’t validate your first solution. They help you find the narrow, repeated problem that customers already spend time, money, or attention trying to solve. For workflow businesses, that problem often sits between systems and people: an email that never becomes a task, a change request that doesn’t reach billing, or an approval that depends on someone remembering to follow up.
Ask for recent examples. I remember a project where thought they could save money but ended up paying more.. Trace the handoffs. Look for tool sprawl, workarounds, and consequences. Pay attention to buying signals that involve real commitment rather than friendly enthusiasm. And treat AI as a capability to test against a specific job, not a promise that every messy process can disappear.
Frustration is a strong starting point for a durable business—but only when your interviews reveal who experiences it, how often it occurs, what it costs, and what they are already willing to do about it.