Short answer: A CFO and a CMO ask AI about the same service in different words. Because the model matches each question to the asker’s criteria, two different shortlists come out. Persona-based AI visibility depends on a company describing its service in each decision-maker’s own decision language. A site written in one persona’s language gets lost in the other decision-maker’s question.
A machinery manufacturer decides to buy B2B marketing and demand generation services to build a dealer network in Europe. The marketing director initiates the project. The finance director will approve the budget.
Both ask AI in the same week. They write different questions:
Decision question · CMO
“Which B2B agencies are strong in account-based marketing and LinkedIn campaigns for industrial brands in Europe?”
Decision question · CFO
“Which firms offer performance-based pricing for B2B demand generation and report return on investment? How does the risk compare with a fixed fee?”
The two lists overlap on only one name. The CMO’s list has agencies with award-winning campaigns. The CFO’s list has firms that publish their pricing model and reporting approach. The marketing director’s favorite agency doesn’t appear in the finance director’s answer at all.
The scenario is fictional. In B2B buying, though, the pattern is familiar: one persona’s answer creates the shortlist, another persona’s answer tests the budget approval.
Why does the model give two personas two different lists?
The question carries the asker’s decision criteria. The CMO’s question contains channels, creativity, industry experience and brand. The CFO’s contains cost, risk, payback period, contract structure and measurability.
For each question, the model looks for sources that carry evidence on those criteria. Campaign case studies and award news match the CMO question. Pricing pages, contract model explanations and measurement methodologies match the CFO question. If a company’s content is only of the first kind, nothing matches the second question.
The two questions side by side: criteria, evidence, gap
| CMO question | CFO question | |
|---|---|---|
| Decision criteria | Channel expertise, creative quality, industry experience | Total cost, risk, payback period, flexibility |
| Evidence the model looks for | Campaign case studies, client references, awards | Pricing model, contract structure, measurement approach |
| Typical question pattern | “Firms strong in …” | “Cost, risk, return on …” |
| Common gap | Site written in technical language, no case studies | Site with case studies only, no pricing or contract information |
The Communication GAP: the message exists, but for the wrong person
Recro classifies three types of gap. A Content GAP means the information isn’t published. An Authority GAP means external confirmation is missing. A Communication GAP means the information is published but not framed in the decision-maker’s language.
Most marketing service providers naturally build their websites for the CMO: case studies, creative work, channel expertise. Yet the same firm has strong things to say to a finance director too. Monthly reporting discipline, a performance-based fee option, three-month termination flexibility, how cost per acquisition is tracked. This information is in the proposal, not on the website.
The reverse is common too. A software or consulting firm that writes in financial and technical language leads in the CFO question and gets lost in the CMO’s or team lead’s question. In both cases, the gap is in the framing, not the information.
Who holds the veto?
In B2B decisions, the shortlist is often created by the answer given to the persona who initiates the purchase. The finance director’s check comes later, at budget approval. If the question asked at that point brings different firms forward, the decision reopens, or at worst the shortlisted firm is eliminated as “expensive and risky”.
The broader the buying committee, the stronger this effect. Procurement, legal and information security each ask their own questions. Every new persona is another test of whether the brand stays in the answer.
Does each persona need a separate page?
Not always. In most cases, adding a layer to existing service pages that answers the second persona’s question is enough: pricing approach, contract structure, measurement model, risk sharing. A separate “for finance teams” page makes sense in enterprise sales with large buying committees.
Consistency is what to watch. If the same service is described to two personas with different promises, the model sees a contradiction and stays cautious in both questions. The service described should be the same; only the emphasis and evidence change.
How does Recro make this gap visible?
The Recro Insight Model simulates each buying committee member’s question separately for the same service. The output shows which personas’ lists include the brand, which don’t, and which GAP explains the difference.
One simulation · 4 key pillars · 90+ steps
What sets Recro apart is four pillars built from scratch for each brand. Together they form a single simulation of 90+ steps, with each pillar producing the input for the next.
- Persona builder: Decision-maker profiles that represent the brand’s real buyers, specific to its sector and sales structure.
- Question builder: The brand-specific decision questions these people ask AI along their buying journey.
- Report builder: A report that reads the answers against the brand’s goals and competitors, together with the sources behind them.
- Action recommendation builder: A prioritized list of actions that closes the sector-specific signal gaps.
Sample finding format · illustrative
- Question: Same need · CMO and CFO · Turkish
- Status: The brand is on the list in most CMO questions and in none of the CFO questions.
- Reason: Competitors on the CFO list describe their fee model and reporting approach on their websites.
- Class: Communication GAP
- Action: Add a fee model, contract flexibility and measurement approach layer to service pages.
Executive summary
- CFOs and CMOs ask about the same service with different criteria and get different shortlists.
- A site written in one persona’s language gets lost in the other decision-maker’s question. This is a Communication GAP: the information exists, the framing is missing.
- The initiating persona creates the shortlist, the approving persona tests it. A firm missing from either answer gets eliminated at the final stage.
Frequently asked questions
Can we appear in the CFO question without publishing our prices?
Describing the pricing model instead of the price is often enough: fixed fee or performance-based, minimum term, termination terms. What the CFO question looks for is predictability and risk structure more than a number.
Which persona should we prioritize?
The one with veto power in the decision. For most B2B services, that’s finance or procurement. A simulation shows in which persona’s question your largest gap lies.
Is this difference only seen in marketing services?
No. It appears in every B2B service with a multi-person buying committee: software, consulting, logistics, training. In the decision question map for corporate training and HR services, we showed the same split between the HR director and the CFO.
Does persona-based content create duplicate-topic risk in SEO?
If you write the same topic twice, yes. The recommended approach is to add a section to the existing page that answers the second persona’s question. A separate page should be created only when the search intent is genuinely different.
How can we measure the difference?
By repeatedly running question sets that ask the same need in each persona’s words and comparing the brand’s appearance rate on each list. We explain the criteria in measuring AI visibility.
When your client’s CMO shortlists you, will you still be there when their CFO asks AI about the same service? Recro simulates the questions of every persona in your buying committee and shows the communication gaps.
Request a persona simulation →
This article was prepared with AI assistance and published under the review of Mehmet Semih İpek.
