How to research an enterprise account before a first meeting
Research an enterprise account before a first meeting by learning four things: what the business does, what changed in the last year, what its teams are building, and where your product connects. Then turn those four things into a point of view you can say in two or three sentences.
Most reps stop at the company overview. The buyer already knows the overview. The meeting is won on the second, third and fourth questions.
The four things to learn
What the business does and how it makes money. One paragraph is enough. Which products bring in the revenue, who buys them, and how big the company is. Skip the history.
What changed in the last twelve months. Acquisitions, divestitures, layoffs, new executives, earnings surprises, breaches, new regulations. A change is the reason a company buys something it did not need last year.
What the teams are building. Strategy decks say where a company wants to go. Job postings say what the company is paying people to build right now. Whatever team you sell to, its plans usually show up in job postings before they show up anywhere else.
Where your product connects. Which of those changes or projects makes your product more useful, and which team owns that work. The answer tells you who to talk to and what to talk about.
Where to look
Annual reports and earnings calls. The 10-K names the risks the company worries about. The earnings call transcript has the CEO saying what matters this year in plain words. Search the transcript for your category.
Investor days and executive interviews. Investor day presentations lay out the multi-year plan. Podcasts and conference interviews with the executives say the same plan in plainer words, and often name the problems the company has not solved yet.
Press releases and news. The last twelve months of press releases cover acquisitions, partnerships and product launches. News adds the parts the company did not announce, such as layoffs, outages and lawsuits.
Job postings. The single most useful source for a first meeting. Read the titles, then read the requirements. A posting that asks for experience migrating off a named tool tells you what the team is replacing. A posting for a new head of a function tells you a program is being built from scratch.
LinkedIn posts from the account's leaders. Leaders and hiring managers post about the projects they are staffing and the problems they are proud of solving. A few minutes on the buyer's own posts tells you what the buyer cares about.
Engineering blogs and conference talks. Large companies publish how they build. A blog post about moving 450 services into one repository tells you more about a company's engineering priorities than any analyst report.
Customer case studies and vendor announcements. Vendors publish case studies about their customers. A search for the account's name plus "case study" often shows which tools the account already runs, and which vendor you are up against.
Leadership moves. New executives in the function you sell to change vendors in their first year. Check who joined or was promoted in the last twelve months.
Turn the research into a point of view
A point of view is three sentences: what changed, why the change matters to them, and the question you want to ask. For example: "You closed two acquisitions this year and both teams still ship on their own tooling. Most companies that size end up consolidating within eighteen months. Has anyone started on that yet, or is each team still running its own?"
A buyer hears pitches all day. A buyer rarely hears a rep describe the buyer's own business back accurately. Hearing that is when the meeting turns into a conversation.
Check every fact
Every fact you say in the meeting should point to a source you can name: the filing, the press release, the posting. One wrong fact costs more credibility than ten right ones earn. Be careful with general AI chatbots here. A chatbot starts from zero each time, does not know what you sell unless you tell it, and can state something confidently without a source. Use a chatbot to draft. Check each fact against its source before you say it out loud.
Doing this for a whole book
Two hours of research works for one meeting. Two hours per account does not work for a book of eighty. AccountPulse does the research for every account you own. Upload your accounts and describe what you sell, then come back later. What you sell is entered as pitches: each is one value your product delivers, with the hires, projects, incidents and announcements that mean an account needs that value listed under it. Every account has a research brief and scored signals from the news and the job postings for the roles you sell to. Every account with a real reason to call has a Why reach out that connects what changed to what you sell, with a source behind every claim. AccountPulse keeps watching every day, and the research is current when the meeting lands on your calendar. See how it works or start a trial.