Toybird Labs BlogThe organization, product and exchanges below are fictional training material. They are not customer research, a real AI conversation, or evidence of improved sales results.
Choose the information you need to discover
The customer is a sales-operations lead in a company with 40 salespeople. Departments submit spreadsheets for a monthly report. The lead consolidates them and has no current plan to replace the process. Extra work for the team is a concern.
Your objective is to understand the workflow, the conditions under which it becomes difficult, and what could be checked next. Getting a demo booked at any cost is not the objective.
Play the customer in an early discovery conversation.
You are the sales-operations lead of a company with 40 salespeople.
You collect departmental spreadsheets for monthly reporting. You have no current plan to change tools and are concerned about rollout workload.
Respond naturally as the customer, one issue at a time.
Do not reveal every problem, budget and decision-maker before I ask.
Answer relevant questions. Do not disagree merely to make the exercise hard.
If I assert an unsupported feature or result, ask me to substantiate it.
Do not coach, score or give model answers during the roleplay.
When I say “finish,” stop playing the customer.
Begin: “Our current process isn't causing any major problems.”
This is fictional; do not infer facts about a real company.
A pitch can hide the question you needed to ask
Customer: Our current process isn't causing any major problems.
Seller: Our service makes reporting more efficient. Let me show you a demo.
Customer: We already produce the report. I don't want the team to learn another tool.
Nothing here establishes how reporting works or what the effect of a change would be. Treating this as an objection to overcome skips the discovery work.
Four exchanges from the same opening
| Step | Seller | Customer |
|---|---|---|
| Understand the process | How does the monthly report get completed today? | Departments send their sheets; I align the fields and consolidate them. |
| Find the difficult condition | When does that process become harder to finish as planned? | When different departments define the numbers differently, there are extra questions back and forth. |
| Understand the impact | Which part of your work is affected by that back-and-forth? | The report is still on time, but there is less time to analyze it before the meeting. |
| Agree a useful next check | Could we review a shareable example of the fields and definitions before discussing a tool change? | I cannot share live data, but a sample with field names is possible. |
The result is not a proved need for your product. It is a clearer issue: inconsistent definitions reduce analysis time. The next conversation can examine definitions and workload instead of presenting every feature.
Use actual statements as feedback evidence
Finish the roleplay.
Review my statements against these questions:
1. Did I learn the current workflow?
2. Did I distinguish difficult conditions from their business impact?
3. Did I avoid claiming a solution without evidence?
4. Did I make the next check concrete?
For each, mark established or not yet established and cite a short statement from my side.
Suggest one improved question. Wait for my response before starting another round.
For the example above, the workflow and impact have been explored. The frequency of the problem and who approves shared definitions remain unknown. A useful next question is: “Who would need to agree if the departments used a common definition?”
Change one condition, not the entire scenario
Repeat with the same workflow but add “the team cannot change its process this quarter.” Practise agreeing a small investigation without treating immediate rollout as inevitable. Compare the questions you asked, not an AI-generated likelihood of winning the deal.
Prepare each rehearsal with Prompt Ready
Use Prompt Ready to organize the stage, customer role and rehearsal objective. Include the rule that coaching waits until the conversation ends. The AI you paste the request into plays the role; Prompt Ready does not predict the real customer's response. Rebuild the brief when the stakeholder or sales stage changes, and keep genuine confidential account details out of an unapproved environment.