What Bloom pulls from a client’s call vault: who actually buys, the words they use, and the roadmap the starter team works first. This sample is a composite. Identifying names and other figures are masked as X.
Scroll the report. Lavender arrows mark what you receive in a real findings pack. The report is yours whether you install a team or not.
How we mine the call vault
Bloom scored the client’s live call archive, not a stated ICP slide. Evidence came from recorded sales and delivery meetings, plus the language already sitting in email threads. The filter was best-fit accounts (retention, recency, and whether the buyer matched the work), not whoever had the prettiest case study.
The vault covered about 3,347 meetings across the live archive. Pattern files from research were used as a second pass so a single loud call could not set the ICP.
HubSpot and Salesforce show up as stack categories in the quotes below. Named companies, people, and commercial figures are stripped.
Verbatim from the call vault
This is the emotional core. Language is verbatim or near-verbatim from the vault. Each block: what they say, then what it feels like.
Inherited machine nobody understands
“The person who built it is gone. The workflows still fire. Nobody knows why.”
“Overly complicated, somewhat black-box custom solution. Nobody really understood the logic.”
“Single point of failure.” / “House of cards.”
Fear of looking incompetent a few weeks in. Urgency without bandwidth. They want an outside forcing function, not another hire who will get swallowed by tickets.
Marketing cannot prove what is working
“I can’t with any confidence tell you where leads are coming from.”
“Marketing can’t prove ROI to the CEO.”
“Attribution … swallowed by a Direct bucket.”
“Only X% of leads … with correct lead sourcing.”
“Hours of manual forensic work each week.”
The team is already working hard. Leadership keeps asking for proof. The reflex is “make more content,” which makes the shame worse. Post-migration orphan attribution (HubSpot or Salesforce after a move) is a repeating cause, not a one-off ticket.
Flying the sales org blind
“Zero ability to forecast. Zero ability to track sales activity.”
“Performing a pipeline review with X-day-old data, and nobody knows. There’s no baseline.”
“Sales moved off [CRM] onto Excel.”
“HubSpot for X months … essentially no value.”
Anger at the IT backlog, plus quiet dread before forecast calls. They have already stopped waiting.
The system and reality do not match
“The data doesn’t match what the team is experiencing.”
“Shadow spreadsheet.”
“We know it’s wrong, but we don’t know how wrong.”
Learned helplessness. The CRM became a tax. The real source of truth left the building. Dual-CRM sync debt (picklist mismatch, records that will not stick) shows up as delivery pain, not a footnote.
I believe it. I cannot sell it upstairs
“Didn’t come away with a clear understanding of what they’d be getting.”
“He left skeptical enough to say he’d call cheaper, more experienced alternatives.”
“He remains open… but won’t push it to the decision maker without stronger justification.”
“Adding headcount without fixing top-of-funnel infrastructure will repeat burning through reps.”
“Board approval is the blocker, not internal alignment.”
The champion is bought. The CEO, CFO, or board was not in the room. Without ammo, the deal dies politely. “Don’t hire another seller until the funnel exists” is the upstairs sentence that keeps landing.
Who to hire the team against
Self-research personas (site and search) are the first two. Referral and deal-support is the third. Channel work on LinkedIn is the fourth. An emerging fifth is a board motion, not a search bet.
| ID | Who | What they feel | Trigger |
|---|---|---|---|
| R1 | New in-seat GTM leader (including Head of Sales) | Inherited CRM. Clock running. Cannot trust the data. | New exec hire in the first weeks in seat. Undocumented CRM. PE value-creation pressure. |
| R2 | Overwhelmed operator, including post-migration orphan | Attribution broken after a HubSpot or Salesforce move. Sync they do not trust. | Leadership asking what is working. Direct-bucket / forensic reporting. |
| R3 | Revenue exec. Blind-spot sales engine | Pipeline looks fine until it is not. Spreadsheet as the real CRM. | Stale reviews. Zero forecast confidence. Flat net growth. |
| R4 | PE portco plus PE portfolio channel | Firm wants repeatable RevOps across the book. | New exec plus board / operating-partner urgency. First audit as a door in. |
| R5 | Headcount before systems | Board wants more sellers. Champion wants the funnel first. | Growth mandate on a broken top of funnel. |
Hottest live champion is still the new in-seat leader, now including Head of Sales / SVP Sales. Static title lists that start at CFO / COO miss the two titles that dominate the vault.
Where they research vs where they decide
Generic path: problem identification, solution exploration, engage and discover, supplier selection, then experience. Website-class touchpoints are search, site content, and case studies they can forward. Revenue executives rarely self-research. They arrive by referral and events.
| Persona | Awareness | Consideration | Decision |
|---|---|---|---|
| New in-seat GTM leader | Organic search. RevOps communities and webinars. Non-paid LinkedIn. Referrals. | Website content and case studies. Discovery call. | Audit / roadmap as an executive summary. Proposal they can send up. |
| Overwhelmed operator | RevOps communities. Technical non-paid LinkedIn. Referrals. | Technical site content and case studies. Diagnostic call. | Roadmap packaged as exec-ready materials. The deal converts with a sponsor above them. |
| Revenue exec | Referrals and events. Almost no self-search. | Warm intro. A simple case they believe. | Confidence in the plan and the team before they commit. |
| PE operating partner | Relationships, LinkedIn, peer forums. Cold outreach can work here. | Portfolio playbook. Repeatability across companies. | Intro to the portco champion. The operating partner rarely signs the contract. |
Content that earns the meeting opens on inheritance, black boxes, Direct bucket, and “prove it to the CEO.” Decision-stage sales assets do not belong as blog posts.
Site words vs buyer words
Open with the left column. Category labels come second, if at all.
| Buyers say (use this) | Company / site often says (soften) |
|---|---|
| Black box / house of cards / inherited mess | CRM optimization / RevOps transformation |
| Visibility problem | Content strategy / demand gen |
| Shot in the dark / X-day-old data | Pipeline visibility solutions |
| Dev team said they would build it. It has been a year. | Integration services |
| Banging the drum / third party | Fractional partner |
| Shadow spreadsheet | Single source of truth |
| Cannot prove what is working / prove ROI to the CEO | Attribution modeling / ROI dashboards |
| Direct bucket / forensic reporting | Multi-touch attribution |
| The person who understood why left | Knowledge transfer / documentation |
| Sell it upstairs / clearer case for the team | Feature lists / service menus |
| Burning through reps / headcount before systems | Sales capacity planning |
| Google Sheets rather than Salesforce | Adoption / change management |
Questions before they say yes
These are the questions that stall a yes even when the champion likes the work. A findings report answers them in buyer language, then gives the champion a page they can forward.
What the starter team works first
Customer Intelligence works this first. Production and sales teams inherit the same vault.
You keep this report either way. If you hire a starter team next, the 90-day plan maps how Bloom stands that team up from this language.
Book a call. Bloom mines the vault you already have and hands you the ICP report you keep either way.