Mine Glassdoor reviews for internal pain signals at a target account
Extracts operational intelligence from employee reviews of a target account — broken tooling, manual process complaints, understaffing, leadership churn — with an explicit bias check on the sample, a department-level read, and the selling implications. It also draws the hard line: this intel shapes strategy and discovery questions, and never appears in outreach.
You are an organizational analyst who reads employee reviews for a living. You know Glassdoor is a biased sample — the thrilled and the furious write, the middle stays silent — and you correct for it. Read right, it's the only public window into how a company actually runs: tooling, process, leadership churn, and where the duct tape is. I'll paste employee reviews of a target account (Glassdoor, Indeed, Comparably). You produce: 1. SIGNAL THEMES — recurring operational complaints grouped: broken tools, manual processes, understaffing, leadership churn, priority whiplash. Frequency and a near-verbatim snippet each. Ignore pure compensation-and-culture griping unless it's operationally revealing. 2. DEPARTMENT WEATHER — which functions the complaints cluster in, and specifically anything from the department I sell to. 3. BIAS CHECK — how skewed this sample looks (review count, date spread, ratio of extremes) and how much to trust each theme. Small angry samples get flagged, not amplified. 4. SALES READ — 2 to 3 implications for selling into this account: pains my product touches, adoption risks (a change-fatigued org buys slowly), champion clues (a department drowning in manual work wants rescue). 5. HANDLE WITH CARE — a reminder list of what NEVER goes in outreach from this research. Employee reviews inform my strategy; they must never be cited, hinted at, or paraphrased to the prospect. Rules: work only from what I pasted, never fabricate a review. Weight recent reviews over old ones. If the sample is under roughly 8 reviews or all older than 18 months, say the read is weak and treat everything as speculative. Before you analyze, interview me. Ask me these questions ONE AT A TIME, waiting for my answer each time: 1. What company, and roughly how big is it? 2. Paste the reviews — include dates, ratings, and the reviewer's role/department when shown. 3. What do you sell, and which department would use it? 4. What stage is this account — cold target, active deal, or renewal risk? Once you have my answers, run the analysis.
How to use it
- 1
Copy the prompt into Claude, ChatGPT, or any LLM.
- 2
Collect 10-25 recent reviews from Glassdoor or Indeed, prioritizing reviewers from the department you sell to; copy text, dates, ratings, and roles.
- 3
Answer the interview, then read the BIAS CHECK before anything else — it tells you how much weight the whole analysis can bear.
- 4
Convert the SALES READ into discovery questions ('how manual is that process today?'), never into email copy.
- 5
Combine with the hiring-signals prompt: complaints about understaffing plus matching open roles is confirmation across two independent sources.
Best practices
Filter reviews by the department you sell to when the site allows it — ops reviews for ops tools, sales reviews for sales tools; general culture reviews are mostly noise for this purpose.
Adoption-risk signals matter as much as pain signals: repeated 'constant reorgs' and 'flavor-of-the-month tools' complaints predict a brutal rollout — factor that into deal strategy and pricing conversations.
Honor HANDLE WITH CARE absolutely: referencing employee reviews to a prospect, however obliquely, reads as surveillance and ends conversations.
Recent beats voluminous — five reviews from the last six months outweigh thirty from three years ago.
Example: what this looks like in practice
A sales leader at a workflow-automation company evaluates a 600-person insurance brokerage before committing ABM budget. Her SDR pastes 18 Glassdoor reviews. Themes: 'systems from the stone age' (6 mentions, operations reviewers), chronic understaffing in policy servicing, and praise for leadership stability — a good adoption signal. SALES READ: strong pain fit in operations, likely champion in policy servicing management, low change-fatigue risk. Discovery questions get drafted around processing volume per head. Three calls later the ops director describes exactly what the reviews foreshadowed, unprompted — and the account moves to tier one with real conviction behind it.
Best fit
This prompt is one gear in a bigger machine. We orchestrate 20+ tools into outbound systems our clients own — and guarantee the results.
Apply for a Pilot Spot → →Frequently asked questions
Yes — as strategy input, never as outreach material. Employee reviews reveal operational reality no company page admits: broken tools, manual processes, understaffed teams. That intel sharpens your pain hypotheses and discovery questions. The hard rule: nothing from employee reviews is ever cited or hinted at to the prospect, because it reads as surveillance.
More account & prospect research prompts
Build a 10-minute company deep-dive brief before you touch an account
Produces a one-page, source-backed account brief with a fixed six-section structure: snapshot, revenue logic, recent momentum, evidence-based pressures, two outreach angles, and landmines to avoid. It compresses the hour of tab-hopping most reps do before a tier-one account into ten minutes, and forces every claim to carry a source.
Scan an account for trigger events: news, funding, leadership moves, layoffs
Runs a structured six-month trigger-event sweep on one account — funding, leadership changes, layoffs, launches, expansion, legal news — and returns a dated, sourced signal log, the top three events ranked by outreach value, a ready-to-adapt angle for the best one, and an honest timing call including 'no trigger exists.' It turns 'why now' from a guess into evidence.
Audit a prospect list for quality before a single email goes out
Audits a prospect list before launch: completeness and duplicates, out-of-ICP rows, stale-data risks, deliverability hazards like role-based emails and sequence collisions, and an honest A-F grade with a prioritized fix list. It catches the problems that get misdiagnosed as 'copy issues' three weeks and one burned domain later.