Simulated Buyers vs Customer Interviews: Which Question Goes Where in 2026
Use customer interviews to find out what the problem is. Use simulated buyers to choose between versions of your answer. Here's how to route each question.
Use customer interviews when you don't know the question yet: what hurts, who decides, what they use today. Use simulated buyers when you've got a specific choice to make between versions: two prices, three headlines, two segments. Interviews find the problem. Simulated buyers help you pick the answer, in minutes, before you spend real conversations or ad money on it.
Run a pricing check with RightPrice on the price you'd quote tomorrow, then take what it flags into your next interview.
Which questions go to interviews and which go to simulated buyers?
Sort by the type of question. If the answer is a story, ask a person. If the answer is a pick between options you've already written, simulate it first.
| The question you're asking | Send it to | Why |
|---|---|---|
| What does this buyer's week look like? What's broken? | Customer interviews | You need stories about real past behaviour. A simulation only knows what you told it. |
| Who signs off on the purchase? Who can block it? | Customer interviews | Buying committees and approval steps vary company by company. Only the buyer knows theirs. |
| What words do buyers use for the problem? | Customer interviews | Their exact phrases become your headline. You can't simulate language you haven't heard. |
| Is $49 or $79 the better price? | Simulated buyers (RightPrice) | It's a choice between options, and you can test both in one sitting. |
| Which of these three headlines holds a cold visitor? | Simulated buyers (RightMessaging) | You get a clarity score and the phrases that lost them, for each draft. |
| Which of two segments is more likely to buy? | Simulated buyers (RightAudience) | Interviewing both segments properly takes weeks. A scored comparison tells you which to interview first. |
| Will this cold email get a reply? | Simulated buyers (RightEngagement) | You only get one shot at a list. Catch the weak opener before it goes out. |
| Why did this deal stall? | Customer interviews | The reason lives in that buyer's situation. Ask them. |
If you're asking both kinds of question at once, split them. "Will finance leads pay $79 for this?" is really two questions. Whether month-end close hurts enough to pay for is an interview question. Whether $79 or $49 reads better to a finance lead is a simulation question.
How do simulated buyers and interviews fit together?
They feed each other. Interviews give you the raw material that makes a simulation sharp. Simulation tells you which interview questions are worth asking. Run them as a loop:
- Interview five to eight buyers about the problem. Ask about the last time it happened and what they did. Don't pitch. Write down their exact words. Our guide on running customer discovery interviews covers the questions.
- Turn what you heard into specific options. Two price points, three headlines built from their words, two segments that kept coming up.
- Paste their language into the simulation setup. When you describe your buyer in Right Suite, use the job titles, pains and alternatives your interviewees named. The closer the description is to real buyers, the more useful the reactions.
- Run each option. Keep the score, and more importantly the objections and the phrases that triggered skepticism.
- Take the top objections back into interviews. If the skeptic persona says "I'd need proof this works with our ERP", ask your next three buyers what proof they'd need. Now your interviews test something specific.
- Ship the version that survives both, and let real conversion data have the last word.
Each lap of this loop is quicker than the last, because every interview now has a sharper question and every simulation has a better buyer description.
A worked example
For example, say you're building a tool that cuts month-end close time for finance teams at 50 to 200 person companies.
- Interviews (week one). You talk to six controllers. Four describe the same thing: chasing receipts from other departments in the last three days of the month. Two say their CFO signs off on any tool over a few hundred dollars a month.
- Options. You draft two headlines, "Close the month in 3 days" and "Stop chasing receipts at month-end", and two prices, $149 and $299 a month.
- Simulation (one afternoon). You run both headlines through RightMessaging and both prices through RightPrice, with the buyer described in your interviewees' words. In this example, the receipts headline gets the higher clarity score, and the skeptic objects at $299 because "the CFO will ask why this isn't in the ERP".
- Back to interviews. You ask your next three controllers how they'd justify a tool their ERP doesn't cover. Two say a time saved figure for the audit would do it.
- Result. You ship the receipts headline, open the pricing page with the time saved for audit prep, and test $299 with a real CFO on your next call.
When should you skip one of them?
Skip simulation when you have no options yet. If you can't write two versions of the thing you're testing, you're still in discovery, so go talk to people.
Skip interviews, for now, when the choice is small and reversible and you've already done discovery. Picking between two subject lines for a cold email doesn't need three calls. Run RightEngagement, send the winner, and read the replies.
Never skip both before a big spend. A paid campaign, a homepage rewrite or a price change for existing customers deserves at least a simulation and a handful of real conversations first.
If you want the broader picture of synthetic buyers against all forms of user research, including usability sessions and design partners, read synthetic buyers vs user research. If you're comparing tools that use real panels or AI participants, see Right Suite vs Wynter and Right Suite vs Synthetic Users.
FAQ
Can simulated buyers replace customer interviews?
No. Simulated buyers react to what you describe, so they can't tell you about a buying step or a pain you've never heard of. Interviews find those. Simulated buyers are the fast way to choose between options once you know what you're choosing between.
Should I run interviews or a simulation first?
If you don't yet know the buyer's problem, interview first. If you already have specific options on the table, like two prices or three headlines, simulate first so your interviews spend time on the strongest version and its real objections.
How many customer interviews do I need before simulating?
Enough to describe your buyer in their own words: their role, the pain, and what they use today. For many founders that's a handful of conversations. You can simulate before any interviews, but the description of the buyer will be your guess, so treat the result as a first read.
What do I take from a simulation into an interview?
The objections. A Right Suite report lists buyer-level objections and, for copy, the phrases that triggered skepticism. Turn each one into a question about past behaviour, like "What would you need to see before trusting a tool with this?"
Do this next
Write down the one choice you're stuck on this week. If you can write two versions of it, run them through Right Suite tonight and take the top objection into tomorrow's call. Use code FIRST50 for your first month of Starter free.