Account Research for B2B SaaS Founders

When your customer base is small, it is tempting to search for job titles first: “VP Sales,” “Head of Operations,” or “CISO.” That shortcut creates activity without showing whether the company has the problem your product solves. Research the company first, then decide which people are most likely to care, influence the purchase, or block it. Write a one-sentence account hypothesis before opening LinkedIn or an email finder. Use this format: “This company may need [outcome] because [observable condition], and [function] is likely responsible.” For example: “A 250-person logistics software company may need better renewal-risk visibility because it is expanding its customer-success team and adding enterprise customers; the customer-success and revenue-operations functions likely own the problem.” Treat the hypothesis as provisional. Its purpose is to direct your research, not to prove that the account is qualified. If you cannot find evidence for the condition in a few minutes, do not invent a story around a familiar logo. Move the account to a lower-priority queue or discard it. Your first decision rule is simple: only research accounts where you can name a plausible operational reason the problem could exist. “They are in our target industry” is not enough. A trigger, constraint, strategic priority, or change in company circumstances is stronger than a broad firmographic match.

Before building a list, create a short account scorecard based on what your earliest customers or best prospects have in common. With only a few customers, avoid pretending you have a statistically complete ideal customer profile. Instead, distinguish between facts you have observed, patterns you suspect, and assumptions you need to test. A useful scorecard should focus on conditions that affect the likelihood and urgency of adoption. Company size matters only if it changes the workflow, budget, data volume, compliance burden, or number of stakeholders involved. A 30-person company can be a better target than a 500-person company if your product solves a painful process that appears at 30 people and becomes political or slow at 500. Score each condition as yes, no, or unclear. Do not use false precision such as 83 out of 100 when your evidence is thin. If an account has two strong positive signals and no obvious disqualifier, it is usually worth a deeper look. If it has only a broad vertical match, keep it out of the first outreach batch.

• Core fit: Does the company have the workflow, team structure, or customer type your product was built for?
• Trigger: Is there a recent event that may make the problem more urgent, such as a hiring push, new market entry, product launch, funding event, leadership change, or stated strategic initiative?
• Ability to buy: Is there likely a budget owner and a buying process proportionate to your price point?
• Access: Can you identify a credible first contact and a reason they would recognize the issue?
• Disqualifiers: Is the company too early, locked into a channel you cannot support, in a restricted geography, or clearly solving the issue internally?

Use the same sequence for every account so that research remains fast and comparable. Start with the company website, especially its product pages, customer pages, pricing, careers page, and leadership page. You are looking for what the business sells, whom it serves, how complex its offering is, and how it describes its priorities. Note direct language rather than translating everything into your own product vocabulary. Next, inspect public evidence of change: job openings, press releases, founder or executive posts, product announcements, webinars, partner pages, and public interviews. A hiring page can reveal more than a company description. For instance, multiple implementation, solutions engineering, or compliance roles may indicate a move toward larger customers. That does not prove your software is needed, but it can strengthen a focused hypothesis. Then map the operating context. Ask what must happen internally for the company to deliver its promise to customers. A SaaS business selling to regulated enterprises may need security reviews, procurement coordination, and repeatable implementation. A marketplace expanding supply may need recruitment operations, quality controls, and regional execution. This translation from business model to internal workflow is where account research becomes useful.

• Capture five fields in your account record: company situation, supporting evidence, likely affected workflow, probable owner, and open question.
• Separate evidence from inference. “Hiring two enterprise account executives” is evidence; “they need our territory-planning tool” is an inference.
• Set a time limit of 10–15 minutes for a first pass. Go deeper only when the account clears your scorecard.

A problem map links an observed company condition to the work that becomes harder because of it. This prevents generic outreach based on superficial personalization. Instead of saying, “I saw you are growing,” identify the specific operational consequence of growth that your product addresses. Consider a hypothetical founder selling software that helps revenue teams standardize account research. A target company announces an enterprise sales motion and is hiring account executives across three regions. The relevant hypothesis is not merely that it is growing. It may be that new representatives need consistent account context, while managers need a repeatable process without adding manual research work. Evidence to look for includes sales-enablement hires, new regional leaders, longer enterprise-oriented case studies, or a revised product positioning. Write two competing explanations when evidence is ambiguous. If a company is hiring customer-success managers, it could be responding to expansion, churn, a new segment, or normal backfill. Your outreach should not assert the least certain explanation. Phrase the message around the visible condition and ask about the associated workflow: “With the enterprise expansion, how are new reps currently preparing account context?” Choose accounts where the problem map has a clear chain: business event, affected workflow, consequence, and plausible value from your product. If the chain has a missing link, you may still contact the account, but use a learning-oriented message rather than a strong product claim.

The right first contact is not always the most senior person. Choose based on proximity to the problem and ability to move the conversation forward. In an early-stage motion, one informed reply is often more valuable than sending a polished pitch to five executives who have no reason to respond. Map four possible roles: the daily user, the functional owner, the economic buyer, and an internal influencer. For a workflow tool used by sales teams, an operations leader may own the process, sales managers may experience the friction, representatives may use the product, and a revenue leader may approve budget. The company research tells you which of these roles is likely to be active now. Use a contact decision rule. Start with the functional owner when there is a clear process owner and your product needs cross-team adoption. Start with a manager or practitioner when you need to validate whether the problem is real, the product is inexpensive, or the owner is difficult to identify. Escalate to an executive when the trigger is strategic, the cost of inaction is material, or the purchase changes multiple teams. Do not contact everyone at once. Begin with one or two contacts who have distinct reasons to care. Add another person only if the first role is clearly wrong, the account has a multi-threaded buying process, or you have a materially different message for that role. Puffle helps teams find relevant people, research them, and prepare email and LinkedIn outreach for review.

• For each chosen contact, record: why this role, what they likely own, the evidence behind that view, and the single question you want answered.
• Avoid a title-only assumption. At a smaller company, a Head of Sales may own operations; at a larger company, a dedicated RevOps leader may own it.
• If you cannot explain why a person should care in one sentence, keep researching the account rather than sending a message.

Your first 25 to 50 researched accounts are an experiment. Keep a simple log of your initial hypothesis, chosen contact, message angle, reply outcome, and what you later learned. The goal is not to prove your targeting was right; it is to identify which assumptions are producing useful conversations. Review the log after each small batch. If operations leaders reply but executives do not, that may mean the pain is operational rather than strategic—or simply that your executive message is weak. If accounts with a certain hiring pattern consistently engage, elevate that pattern in your scorecard. If a high-scoring segment never responds, inspect whether the buying process, price point, or problem severity is mismatched. Use negative evidence deliberately. A company may look ideal but have no relevant team, no trigger, or a product strategy that makes your solution unnecessary. Mark it as “not now” with the reason. This protects your time and gives you a future re-entry condition, such as a new leader, expansion announcement, or shift toward the customer segment you serve. The practical standard is not perfect account knowledge. It is enough evidence to make a responsible contact choice, write a specific opening, and learn from the response. With a small customer base, disciplined learning from each account is a competitive advantage over a larger but generic prospect list.

If you want help doing this work, these Puffle pages show the product in more detail.

• How Puffle works
• Outbound automation
• Browse all GTM guides