AI Simulation vs. Causal Experiments: Structuring Research for a Consulting Engagement
A consulting engagement has two different research jobs, and they need two different methods. Early in a project, the team is forming hypotheses, prepping for a workshop, or anticipating stakeholder objections: speed matters more than statistical rigor, and a directional AI simulation of likely reactions is a reasonable tool. Later, when the team has to defend a recommendation in front of a client's board, the standard changes. A role-played reaction from an AI stand-in is not evidence a partner can put in front of a skeptical CFO. That stage needs a controlled experiment with a defined population, defined alternatives, and a measurable effect.
Confusing the two is the actual risk. Presenting a directional, uncontrolled AI read as if it were a defensible causal finding collapses under client or board scrutiny, and the damage lands on the firm's credibility, not just the deliverable.
Where consulting research time actually goes
A typical engagement spends its time on: stakeholder interviews (identifying the right people, scheduling across time zones, running roughly 45-minute conversations, transcribing, and synthesizing; a strategy project typically runs 15 to 25 of these), expert interviews sourced through paid networks, primary research when the client's question requires data that doesn't exist in secondary sources, workshop preparation, and the final synthesis into a recommendation. Not all of this compresses well with simulation. Some of it does.
Where directional simulation earns its speed
Three points in a consulting engagement are well suited to a fast, directional AI read rather than a full primary study.
Pre-workshop stakeholder prep
Before a strategy workshop, consultants need a working sense of each participant's priorities and likely objections. That means pre-interviews with 8 to 15 stakeholders; scheduling alone eats into the timeline. Building simulated stand-ins for each stakeholder type (a CFO skeptical of unproven technology spend, a CTO frustrated with legacy systems, an operations lead wary of disruption) and running the proposed strategy past them surfaces likely objections before the room does. This does not replace real conversations with the 3 to 4 most senior stakeholders; it reduces how many pre-interviews are strictly necessary and sharpens the ones that still happen.
Early market-reaction hypotheses
When a client asks how target customers will react to a market entry move or a pricing change and wants an answer fast, a directional simulation across modeled buyer segments (the satisfied incumbent, the actively-shopping switcher, the price-sensitive buyer, the early adopter) gives the team a structured first read, including which segments look more or less receptive. It is a hypothesis-generation tool, not a market-sizing study.
Pre-presentation stress testing
Before recommendations reach the client's leadership, teams traditionally rehearse internally, with partners playing devil's advocate. Running the deck past simulated stand-ins for the actual decision-makers in the room, built on real stakeholder characteristics rather than a colleague's guess at what the CFO would say, surfaces weak points in the argument before they surface in the boardroom.
Where a controlled experiment is required
The pattern above only holds for internal preparation. The moment a finding leaves the building and becomes the basis for a client-facing recommendation, the bar changes. A role-played reaction from a simulated stand-in answers "what might this type of person say," not "what would this population actually choose, and by how much." Subconscious runs a controlled discrete-choice experiment: a defined population evaluates defined alternatives, and the result is a causal effect with a confidence interval, not a scripted reaction (see the causal fidelity paper). When the client's decision is large enough to need defensible evidence (a pricing move, a positioning claim, a market-entry bet), that is the stage that needs it. Where audience scale matters, Subconscious can also run studies against a person-level audience graph covering 800 million real people, which is a reach claim about the graph, not a claim about how many people are recruited into any one study.
How simulation and controlled experiments fit together
| Consulting activity | Directional simulation's role | What still needs a controlled experiment |
|---|---|---|
| Stakeholder mapping | Quick initial read, narrows how many pre-interviews are necessary | Interviews with senior stakeholders whose sign-off matters |
| Market sizing | Tests hypotheses before commissioning primary research | The commissioned primary research itself |
| Customer reaction testing | Rapid, segment-level directional read to iterate hypotheses | The client-facing recommendation on pricing, positioning, or entry |
| Strategy workshop prep | Anticipates dynamics and objections ahead of time | Facilitation and the workshop's own synthesis |
| Final presentation | Stress-tests the argument against simulated decision-makers | The evidence base the recommendation is actually defended on |
Practical considerations
The quality of the simulated stand-ins matters more here than in consumer research. Consulting applications need more depth than a generic buyer profile: organizational role and internal politics, decision-making authority, known positions on similar past issues, and communication style. That input has to come from public material (LinkedIn profiles, published interviews, company reports) and the project team's own prior knowledge of the client, not invention.
Treat the shift from simulation to experiment as a pilot, not a wholesale swap. Run the directional read in parallel with the traditional method on one project, compare the two, and only fold simulation into standard methodology once it's clear where it usefully narrows scope rather than replacing judgment.
Moving from a simulated read to a defensible one does not mean changing the question. When a directional hypothesis needs to become client-facing evidence, a team can move from a simulated experiment to real-human validation without changing the underlying causal question being tested.
Limitations
A controlled causal experiment does not replace stakeholder interviews, expert calls, workshop facilitation, or a consultant's own synthesis and narrative judgment; those remain human work. It also does not run as an open-ended conversation with a persona.
See /research for how Subconscious structures a controlled experiment, and /case-studies for how the method has been applied. For engagements where a recommendation has to survive board-level scrutiny, /how-we-work covers the process end to end, and a demo is the fastest way to see where a client-facing question in a live engagement fits.