Who to contact when the SaaS user and buyer are different people
A B2B SaaS purchase rarely has one decision-maker. A department head may feel the problem first but not control the budget. A commercial leader looks at revenue and team speed; an operations leader looks at manual work and errors; an IT leader looks at integrations, access and security. The founder usually becomes involved when a subscription changes work across several departments or represents a meaningful commitment.
| Product | First recipient | Question for the first email |
|---|---|---|
| CRM or sales platform | Head of Sales or Commercial Director | How do you currently keep overdue opportunities visible? |
| HR platform | HR Director or Head of Recruitment | Where do candidates get lost between application and interview? |
| Finance platform | Finance Director or Chief Accountant | How are payments approved and plan-versus-actual tracked today? |
| Platform for IT teams | CTO or Head of Engineering | What do you currently use for this part of the development workflow? |
Do not send the same message to every role. A Head of Sales starts with pipeline visibility and manager discipline; an IT leader starts with what implementation will require. A technical recipient will usually ignore a promise to increase sales, just as a sales leader will ignore an API discussion with no link to the operating process.
Which company signals make a useful SaaS prospect list
A company directory is only the start. For SaaS, it is more useful to build a list around signs of a specific task: hiring, a new office, team growth, new branches, a website refresh, expansion of the sales function or a partner-network launch. A vacancy for a CRM analyst does not prove a purchase is coming, but it gives you a legitimate reason to ask how the company handles the task before that person joins.
- Define the ICP: industry, team size, geography, existing stack and recipient role.
- Build the account list from public business registers, industry directories, job boards, event participant lists and company websites.
- Record a reason for each account: a vacancy, new branch, team expansion, leadership change or stated public priority.
- Find and verify a working address for the relevant role; records without both a role and a reason do not enter the first wave.
For a request-management platform, for example, the list should focus on multi-location businesses, operator vacancies and branch-opening announcements—not every company in a broad industry code. That gives the message context without pretending that you know the company’s internal situation. See <a href="/en/services/lead-list-building/">B2B lead list building for Russia and CIS</a> for the wider preparation process.
Why generic demo offers are deleted and process questions are read
A weak opening says: “We are an automation platform. We can show you a demo and offer a discount.” It gives the recipient neither a relevant problem nor a reason to reply now. A stronger approach is: “We saw that you are opening a second sales team. Do new managers work in one pipeline, or does each unit run a separate process? If useful, we can send a setup outline without booking a call.” The recipient is offered a safe next step, not the entire product.
For a product with a short implementation, offer something concrete: a request-flow review, reporting template, integration map or migration estimate. For more complex SaaS, propose a focused check of which data must move, where access is affected and who will own the process. A demo belongs after interest in the task has been established, not in place of a reason for the first reply.
When a recipient asks for a proposal, do not send a generic deck. First clarify whether they are comparing services or have already selected an implementation scenario. Then send a short, relevant document and suggest a conversation with the right owner. The message structure can be developed through <a href="/en/services/sequence-copywriting/">B2B cold email sequence copywriting</a>.
How to handle “we already have a system” and “there is no budget”
“We already have a system” is often not a final rejection. It means there is an existing process and switching carries risk. Instead of arguing, ask what the current solution handles well and what the team still manages manually. A specific gap moves the conversation away from brand comparison and toward a defined piece of work.
Do not answer “there is no budget” with a discount. Ask about the timing: should you return after planning, or is the task not currently on the agenda? If the purchase is planned later, record the date and reason in the CRM. If there is no task, do not create an artificial follow-up—the response is still useful market information.
- “We have our own developer” — ask what the team has already automated and where it stopped.
- “Write to the general inbox” — ask which role owns the process instead of forwarding a message into an unaddressed mailbox.
- “Not interested” — thank the recipient and remove the contact from the sequence; do not try to reverse the answer with another sales email.
When meaningful conversations appear and what to check along the way
Before sending, agree the ICP, roles, exclusions, reason for each segment and reply route. Launch a limited first wave, read the wording of replies and only then expand coverage. In SaaS, the quality of early conversations matters more than volume: they show whether the stated problem matches the buyer’s language and whether the product has a clear entry point into the process.
Across OT9 campaigns, 48,100 companies replied out of 811,200 contacted companies. This is aggregate data across different campaigns, not a forecast for SaaS. Your campaign report should separately show the company, respondent role, contact reason, reply wording, qualification status and next step. <a href="/en/services/crm-integration/">CRM integration for outreach leads</a> helps make the handoff to sales traceable.
- Sales has an owner for each conversation on the day a reply arrives.
- The demo is tied to the stated task rather than delivered as a general presentation.
- The CRM distinguishes interest, non-target replies, deferred demand and refusals.
- The team has decided in advance which segments to stop after the first substantive replies.
When cold outreach is not the right channel for SaaS
Cold outreach is not a universal channel. It is a poor fit when your product’s value cannot be linked to an observable task for a specific role: early SaaS without a confirmed ICP, a service positioned for “any business,” a solution without a clear process owner, or a product that cannot be explained without a long workshop or access to closed data.
Do not launch if your team cannot accept a reply within one working day, diagnose the need and move a suitable contact to the next step. It is also a weak fit when the product is unstable, the implementation path is unclear, required integrations lack documentation, or you have no evidence of a workable use case in even one segment.
Economics matter too. For very low-ticket SaaS, the cost of finding accounts, verifying contacts, tailoring messages and handling replies may exceed the margin. Outreach can also be weak for long tenders, rigid procurement processes or sales that depend on brand trust a new provider has not yet earned. If your immediate task is to validate a segment rather than book meetings, start with <a href="/en/cases/">when B2B outreach is the right move</a>.