Your reps are already paying for bad research with their time. They're bouncing between CRM tabs, LinkedIn, spreadsheets, and stale notes just to write one opener, while the day disappears into admin and internal cleanup. In a lot of teams, that means the same people who should be creating pipeline are stuck hunting for enough context to avoid sounding generic.
That's the problem with account based prospecting when it's done manually. The strategy is sound, but the execution gets crushed by research debt, and the fallout shows up fast in weak outreach, stalled cross-sell motions, and reps who've stopped trusting their own lists. For multi-solution B2B companies, that friction is expensive because every account already has more expansion potential than a one-product seller, but only if someone can find the right signal quickly.
Why Manual Research Drains Sales Productivity
A weekly outbound meeting usually tells the same story. One rep has three tabs open trying to confirm the right contact, another is copying and pasting notes from LinkedIn, and a third is rewriting the same email because the first draft sounds like it was written for a stranger. Nobody is short on effort. They're short on clean, relevant inputs.
That's exactly where the process starts leaking. Salesforce's 2026 State of Sales says reps spend 60% of their time on non-selling tasks like hunting for sales materials, manual CRM entry, and approvals, according to Salesforce's 2026 sales statistics. Another 2026 summary cites Salesforce data showing teams spend 70% of their time on non-selling tasks and only 30% selling, with research and preparation among the recurring time sinks, from Everstage's sales productivity analysis. That's not just inefficiency, it's quota math working against you.
Practical rule: if a rep has to research the same account twice, the process is already broken.
The damage is worse in cross-sell motions. Existing customers should be the easiest accounts to expand, but manual research turns them into another pile of tabs, notes, and guesswork. Reps fall back to broad messaging because they don't have time to verify which product, which problem, and which recent trigger matters.
That's why generic cold email keeps underperforming. When the opener isn't grounded in an account's current situation, it reads like a volume play, not a reason to reply. If your team is feeling that drag right now, a faster workflow matters more than another debate about messaging. A practical place to see what this looks like in action is PitchSmart's demo, because the core bottleneck isn't creativity, it's research time.
Understanding Account Based Prospecting Fundamentals

Account based prospecting is not a prettier version of lead blasting. It starts with specific accounts, then works backward to the people, signals, and product context that justify outreach. That's different from one-to-many email, where the list comes first and the message stays mostly the same, and it's different from marketing-led ABM, where campaign orchestration usually leads the motion.
By 2020, 61% of companies surveyed had a full ABM program or were in a pilot, and 27% planned to start within six months, according to UserGems' ABM statistics. That matters here because it shows the market had already moved toward account-level prioritization. Account based prospecting lives inside that shift, but it's the sales and RevOps side of the motion, where the question is not just which accounts matter, but which accounts deserve outreach this week and why.
What Changes In A Multi-Solution Company
For a single-product company, account research can be broad. For a multi-solution business, it has to be product-specific. A finance software company might sell one product into FP&A, another into close management, and another into planning workflows. The same account can be a fit for all three, but the buying signals won't be the same, and neither will the opener.
That's where most generic ABP advice gets thin. It stops at persona mapping and leaves out the harder part, which is tying a solution to the exact problem the account is trying to solve. A hiring surge in FP&A roles says something different from a company evaluating budgeting tools, and a rep needs to know which signal maps to which line of business.
Practical rule: the account is only half the unit of research. The other half is the specific product motion you're selling into that account.
The strongest ABP programs treat fit and signal as separate filters, then combine them before outreach. Fit says the account belongs in the list. Signal says it belongs in today's queue. That distinction is what keeps teams from burning hours on accounts that look good on paper but aren't moving.
PitchSmart's account research guide is useful context for teams standardizing that process, especially when multiple solution lines need different qualification logic.
Crafting Your Account Based Prospecting Playbook

A useful playbook starts with list construction, not messaging. If the account list is noisy, no amount of personalization will save the sequence, because the rep will keep writing to the wrong problem. The goal is to build a queue of accounts that are both a fit and currently showing some sign of movement.
Start With Product Fit, Not Just Firmographics
Firmographics still matter, but they're too blunt on their own. A good target list should reflect the account's industry, size, and structure, then narrow further based on the product you're selling and the problem that product solves. That's especially important for companies that grew through acquisition, where one customer base may need different products surfaced at different times.
For outbound teams, this means uploading or syncing the list you already own, then checking it against the motion you care about. For revenue enablement and expansion leaders, it means ranking the installed base by which account has a plausible cross-sell path, not just which account has spend.
Layer Signals Before You Rank Accounts
Single signals are noisy. Multiple aligned signals are where the work gets interesting. Industry guidance on account-based signals points to five core categories, website engagement, competitive activity, tech stack changes, hiring signals, and recency-weighted CRM interactions, according to 6sense's 2024 benchmark guidance. That mix matters because one signal can be a coincidence, while several together usually mean an account is active.
For a finance software seller, a hiring surge in FP&A roles plus a budgeting-tool evaluation is a much cleaner trigger than either one alone. For a service business, a new executive hire plus recent website research might be enough to move the account up the queue. The point is to rank accounts weekly, not to treat every signal as a finished conclusion.
A simple working sequence looks like this:
- Filter for fit first. Keep only accounts that match the product motion you're selling.
- Score the signals second. Weight concurrent activity more heavily than a single event.
- Separate outreach queues. Keep cross-sell, upsell, and net-new motions distinct.
- Use source-backed notes. Reps need to know where the signal came from so they can write a real opener.
Research In Parallel, Not One Account At A Time
Bulk research changes the economics of the process. Instead of one rep manually researching one account at a time, the team can run the full list through a parallel workflow, then review only the accounts that clear the threshold. That's where tools built for account-level research matter, because the bottleneck stops being data collection and starts being judgment.
Practical rule: if research can't be done in batches, it won't survive contact with a real outbound team.
A structured playbook should end with a prioritized list, a reason for priority, and a next action. If it stops at “interesting accounts,” the team will still waste time deciding what to do next. The stronger workflow is simple, repeatable, and tied to one product motion at a time.
PitchSmart's solution to account research fits this kind of operating model because it starts from what you sell, then researches the account against that definition rather than a generic profile.





