RevOps playbook · AI Employee: Rev

Account Research Brief

Reps prep meetings in minutes, not hours

Install this playbookBack to marketplace
The problem

Every prospect meeting deserves an account research brief; almost none get one. AE has 3 hours to prep for a discovery call and spends 30 minutes googling and cobbling something together — company website, LinkedIn scroll, news search. Executive briefings need deeper research; the AE either spends a full day or shows up with generic context and hopes the prospect fills in the blanks. Sales enablement can't scale bespoke briefs; the ones they build become stale within a quarter.

At a glance
Trigger
Chat + form
Approvals
None
What it does
Read-only
Systems
LinkedIn · ZoomInfo · Web · 10-K filings
How it feels in production

An hour-by-hour walkthrough.

AE Kiran requests: "@Rev prep me an account brief for Acme Corp, executive briefing on Thursday." Rev assembles a comprehensive account brief in 10 minutes: **Company Overview** - Acme Corp: SaaS DevTools company, 340 employees, Series C ($120M raised), based Berlin with SF office - CEO: Jonas Müller (LinkedIn shows recent conference keynotes on 'developer experience at scale') - Product: developer productivity platform, competes with GitHub Copilot Enterprise, JetBrains - Latest funding: 2026-04, Series C, $80M, Sequoia lead, valuation ~$1.2B **Recent Signals** - Hiring: 45 open roles, majority engineering (React, Kubernetes, ML — suggests platform investment) - News: recent blog on 'moving to microservices,' announcing partnership with Snowflake - Product: shipped SSO + audit-log features in July (moving up-market from SMB) - Tech stack (from BuiltWith): AWS, React, Postgres, uses Segment + Amplitude **Executive Attendees** - Priya Sharma, VP Engineering: 4 years at Acme, prev Google, PhD Berkeley, focus on platform reliability + team scaling - Marcus Chen, CTO: co-founder, ex-consultant, publicly discusses 'engineering velocity' + 'observability debt' **Their Pain Points (inferred)** - Moving to microservices (per blog) — likely fighting observability + operational complexity - Moving up-market — likely need better security posture + reliability guarantees - Hiring surge suggests scaling challenges are top-of-mind **Our Angle** - Our platform reduces observability overhead by X% (case study: Beta Corp, similar profile) - Enterprise-grade security features (SSO + audit + SCIM) align with their up-market motion - Kiran's suggested opener: 'Congrats on the Snowflake partnership — how's the microservices transition going?' Kiran reads for 15 minutes, walks into Thursday's meeting prepared like a consultant, not a rep pitching a product.
How it works

Step by step.

  1. 01

    Detect research request + assemble sources

    Company + executive attendees identified. Public sources: website, LinkedIn, news, funding data, tech stack.

    Reasoning · Company registry · LinkedIn · Crunchbase · News APIs
  2. 02

    Deep company + executive enrichment

    Company signals: hiring trends, product news, tech stack, funding. Executive: role history, public statements, likely pain points.

    LinkedIn Sales Navigator · Crunchbase · BuiltWith · News scraping
  3. 03

    Infer pain points from public signals

    Public signals inform likely priorities: microservices blog = complexity pain; hiring surge = scaling; up-market moves = enterprise readiness needs.

    Reasoning · Pain-point pattern library
  4. 04

    Match to our angle + case studies

    Our positioning aligned to inferred pain. Relevant case studies surfaced. Suggested opener grounded in current-week signal.

    Case study library · Positioning framework
  5. 05

    Deliver brief with executive-briefing quality

    Structured brief: overview, signals, executives, pain, angle. AE-ready in 10-20 minutes vs. hours of manual research.

    Slack · Teams · Web UI · Export formats
Systems and wiring

What you connect to make this run.

LinkedIn Sales Navigator · Crunchbase · Clearbit

read

Company + people enrichment. Executive backgrounds; company vitals + funding.

News APIs · Blog scraping

read

Recent signals from company blog + external news. Timely + specific context beats stale research.

BuiltWith · Wappalyzer · Tech stack detection

read

Company technology signals. Tech stack informs positioning + relevance.

Case study library · Positioning framework

read

Relevant customer stories + our positioning. Matched to inferred prospect priorities.

What changes

Before and after, honestly.

Time to assemble account brief
Before
3-8 hours (or none)
After
10-20 minutes
% of executive meetings with proper prep
Before
30-50%
After
95%+
AE confidence in executive briefings
Before
3.0-3.5 / 5
After
4.5-4.8 / 5
Prospect-perceived preparation quality
Before
Generic pitch
After
Consultant-level
Related

Playbooks that pair with this one.

RevOps

SDR → AE Handoff

Handoff brief is the lightweight version; account brief is deeper research.

RevOps

POC & Pilot Stand-Up

POC discovery uses account brief as foundation.

RevOps

Call Recording Lookup

Historical call intel augments account brief.

Frequently asked

Answers about this playbook.

What about brand-new prospects with minimal public footprint?

Rev flags low-signal accounts + surfaces what's available. AE knows to prioritise discovery over pitch. Small-company approach adjusts positioning.

How does it handle prospects the AE has met before?

Historical context included: prior meetings, prior positions, prior objections. Never starts from zero for repeat interactions.

Can it customize for different meeting types (discovery, executive, technical, negotiation)?

Brief format adapts. Discovery: pain-focused. Executive: strategic + business-outcome. Technical: architecture + integration. Negotiation: procurement + decision-mechanics.

How does it handle international prospects (non-English content)?

Multi-language support for European + Asian markets. Company research + executive backgrounds available across languages; brief delivered in AE's preferred language.

What about competitive intelligence in the brief?

If prospect is evaluating alternatives (per public signal or CRM notes), competitive positioning included. Battle-card highlights matched to their likely evaluation criteria.

See it run on your data.

Free plan, no credit card. Connect the systems this playbook needs and run it against a past event first.

Book a demoMore RevOps playbooks