RELEVANT OUTREACH. BETTER CONVERSATIONS.Let’s talk · 07572224813 ↗
SaaS & technology

Define your SaaS ideal customer by workflow, not just company size

Build a more useful target audience around the job your product helps a team complete.

Editorial illustration exploring define your SaaS ideal customer by workflow, not just company size

A SaaS company can target operations leaders at mid-sized businesses and still reach people with very different needs. Some have a stable workflow they do not want to change. Others are actively trying to replace a manual process. Firmographic filters help organise a market, but they do not explain why a buyer would care about your product now. Start with the work your software supports, then add company and role criteria that make the audience practical to research.

Name the workflow your product changes

Describe the task in the buyer’s language: collecting approvals, assigning inbound enquiries, reconciling project information or coordinating field teams. Identify where the current process becomes difficult and which part your product addresses. Avoid making the definition so broad that every business qualifies. If the product serves several distinct workflows, create separate audience hypotheses rather than putting every capability into the same outbound message.

Identify users, owners and buyers

The person using a tool, the person accountable for a process and the person approving expenditure may be different. Map those roles for your chosen workflow. An operations manager might own a process while IT assesses integration requirements and finance approves a purchase. That does not mean contacting everyone at once. It means understanding who can explain the need and who should be involved if the conversation progresses.

Find observable evidence without inventing intent

Useful research can include the services a company offers, the teams it employs and relevant changes it has publicly announced. Record what you know and what remains a hypothesis. A job advert mentioning a workflow can justify research, but it does not prove that the team wants software. The opening message should allow for that uncertainty. Asking whether a process is a priority is more credible than announcing that you know it is broken.

Test one coherent segment

Illustrative example: a workflow product could begin with regional service businesses coordinating several on-site teams. The campaign would discuss scheduling visibility and handovers, rather than every feature in the platform. Agree exclusion criteria, such as a workflow the product cannot support or a required integration that is unavailable. A well-defined test gives the team a clearer explanation for each company on the list and each message being sent.

Validate against real opportunities

Review whether positive replies lead to conversations about the workflow you selected. Record reasons for poor fit, including missing requirements and lack of urgency. If prospects consistently describe a different job, revisit the hypothesis before increasing volume. An ideal customer profile is a working definition that improves with evidence. It should help sales and product teams recognise suitable opportunities, rather than become a static slide that nobody uses.

Map the workflow before choosing database filters

Sketch the process your product supports in ordinary language. Identify what starts the work, who performs the task, where information changes hands and what the team needs to know when the task is complete. Include the current alternatives: spreadsheets, email, an existing platform or a mixture of tools. This map can reveal that companies with similar headcounts operate very differently. A useful target audience shares a relevant process, not merely an employee range.

Discuss the map with someone who understands implementation. They may identify a requirement that changes who the product can serve, such as a particular data source or an approval structure. Add those constraints to the audience brief. If a requirement cannot be researched publicly, keep it as a discovery question. Do not pretend your list contains perfectly qualified accounts when important operational facts remain unknown.

Distinguish a user inconvenience from a buying priority

A task can be frustrating without being important enough to change. Explore the consequences the workflow creates for the accountable team: unclear ownership, difficult coordination or an inability to answer a recurring operational question. These consequences should be hypotheses supported by your knowledge of the product’s use cases, not assertions about a prospect you have never spoken to. The first conversation tests whether they apply.

Ask what makes the issue worth evaluating now and how the team currently manages it. A workaround may be perfectly adequate for a small operation. In another business, the same workaround may require several people to reconcile information. Understanding that difference helps your team recognise a suitable opportunity. It also prevents an outreach campaign from presenting every manual process as a failure that must be replaced.

Create a practical account research example

Imagine a product designed to clarify enquiry ownership across several service locations. A research record could capture the company’s locations, the services offered, the likely operations role and the source of that information. It should not automatically claim that enquiries are being lost. That claim requires evidence the researcher probably does not have. The campaign can instead ask whether cross-site handovers are a current topic for the team.

Set aside a small sample for a joint sales and implementation review. Ask whether each business could plausibly use the product and what would need confirming. Record disagreements and improve the criteria before expanding the list. This exercise is useful because it tests whether the audience definition makes sense to the people who will evaluate and deliver the opportunity, rather than only to the person selecting database filters.

Use the first conversations to revise the profile

Keep a short list of the conditions that distinguish useful evaluations from polite interest. You may learn that a particular role understands the problem but cannot sponsor a review, or that a seemingly relevant segment depends on an integration your product does not support. Those findings should change the audience brief and the questions used in discovery. They should not remain informal knowledge held by one salesperson.

Review exclusions with the same care as positive signals. Removing a segment that cannot be served can improve the campaign even if the contact list becomes smaller. The objective is a repeatable definition of a suitable customer situation. When your team can explain why an account belongs in the audience, which facts support that view and what still needs confirming, the profile has become a working sales tool.

Your practical checklist

  • Describe one customer workflow.
  • Map the user, process owner and buying roles.
  • Keep observations separate from buying-intent assumptions.
  • Refine the segment using opportunity feedback.
PUT THE IDEA INTO PRACTICE

Need help applying this to your outreach?

Explore our targeted lead lists service, or talk through your audience, offer and current setup with our team.

Published by Galaxy LeadsPro. Sample messages and scenarios are illustrative; adapt them to your service and use only accurate, verified information.