Decision maker

At a 50 person SaaS company, three people may influence a purchase, but one person can often approve the budget. That decision maker is the person with authority to commit the company, not simply the person who replies to your email.

The short answer: find the person who owns the problem, controls the budget, or can approve the purchase. Then check whether someone else can block it.

That sounds obvious. A lot of outbound teams still email the most senior name they can find in a database and call the job done. The reply might come back. The deal still dies in finance, procurement, security, or executive review.

What is a decision maker?

A decision maker has final authority, or formal approval power, over a purchase. They may control the budget, sign the order form, approve the business case, or have the authority to say yes when other stakeholders cannot.

They aren't always the most senior person involved. A VP of Revenue may approve a sales tool, while the CFO controls the commercial terms. Security might still have the power to stop the vendor.

The useful question isn't “Who has the biggest title?”

Ask:

Who can approve this purchase, stop it, or force it through an internal review?

Take a 200 person fintech evaluating reconciliation software. The finance operations director owns the mess. The controller checks the numbers. IT reviews the integration. The CFO approves the annual contract. The CFO is the economic decision maker, but the finance operations director may be the person who makes the project happen.

In a smaller company, one person may fill all four roles. As headcount, spend, and risk increase, those roles split apart.

Decision maker, buyer, champion, and user

“Buyer” is often used to describe anyone involved in a purchase. That makes it a poor qualification label.

The user works with the product. A champion wants the project to happen and helps move it internally. An influencer shapes the evaluation. A blocker can delay or reject the purchase through security, legal, finance, or procurement. The decision maker controls the final approval or the route to it.

These people don't need separate titles. One person can be the user and champion. Another can own the budget but barely understand the workflow.

For example, a 90 person HR technology company is choosing an outbound platform. The SDR manager defines the workflow. Revenue operations compares vendors and models productivity. The VP of Sales owns the budget. The CEO approves unusually large contracts.

So who is the decision maker? It depends on the contract value, company rules, and the reason for buying.

This is why titles are clues, not proof. “Head of Sales” might mean final approver at a 30 person company. At a 1,000 person company, it might mean one layer below the person who approves the spend.

How to find the decision maker

Start with the business problem. Don't start with a title search.

Suppose a Series B software company is hiring 20 salespeople and opening a second SDR team. The person responsible for the pipeline target is a better first contact than a random executive. If the company has just received a SOC 2 audit finding, security and finance may control the purchase even if the department head wants it.

Look for the person who owns the affected metric, the person who controls the budget, and the person who signs or approves the agreement. Those may be three different people.

A recent trigger helps you work this out. Funding, an executive hire, a new market launch, a processor change, an audit finding, or a sudden hiring push can show you which team is under pressure.

Consider a payments company with 75 employees that has changed payment processors. The controller may be dealing with the reconciliation work every day. The CFO may still approve the software, but leading with the CFO alone could produce a polite referral with no useful context.

Map both people.

This is where an ideal customer profile should do more than describe firmographics. “B2B SaaS companies with 100 to 500 employees” is a market description. A useful ICP also names the trigger, the problem owner, and the likely approval path.

Why “go straight to the top” is bad advice

The common advice is to contact the executive first. I think teams get this wrong more often than they admit.

An executive may approve the purchase, but they usually won't investigate every workflow detail. A CFO considering expense software cares about savings, risk, adoption, and implementation. They probably don't care about the fifth feature in your comparison table. The finance manager does.

Bypassing the people who will use or administer the product can also create resistance. An executive forwarding your email to the relevant team isn't buying intent. Sometimes it's just inbox cleanup.

Start with the person closest to the measurable problem, then find the person who approves the investment. Your SDR should know whether the first contact owns the outcome, influences the decision, or can introduce the approver.

A 120 person logistics software company might need to cut customer onboarding from 14 days to 7. The implementation director owns that metric. The COO owns the operating target. Procurement handles the vendor process. Start with the implementation problem. Once the business case is credible, build the path to the COO.

That approach is more work than sending one email to the CEO. It also reflects how companies actually buy.

A database contact isn't proof

A contact is a record. A decision maker is a role in a buying process.

CRM fields flatten that distinction. A contact gets labelled “primary,” “senior stakeholder,” or “lead” without evidence that they can approve anything. Some databases infer authority from a title. Useful clue, not proof.

Before treating someone as the decision maker, ask whether their team owns the affected metric, whether the contract is material to their budget, and whether they normally approve this category of spend. Recent hiring, public comments, planning documents, and the person's answers can tell you more than a senior title.

One question is especially revealing:

“How are purchases like this approved internally?”

A director who says, “I’d bring finance in after the pilot, and our COO signs agreements above $25,000,” has given you real buying information. The database probably hasn't.

Your cold outreach should make it easy for the contact to correct your assumption:

“You may not own the final approval, but you appear to own the onboarding target. Is reducing implementation time on your team’s agenda this quarter?”

That can get a useful reply from the operator, the approver, or the person who knows how to connect the two.

What to ask on the call

Confirmation comes from conversation, not enrichment data.

Ask who owns the result the project is meant to improve. Ask how similar purchases get approved. Ask who else needs confidence before the project moves forward. Ask whether the budget already exists or needs a new business case.

Listen for words such as “approve,” “own,” “sign,” “allocate,” “sponsor,” “block,” and “review.” If someone says, “I’ll need to get finance involved,” you haven't lost the opportunity. You’ve learned that you may be speaking with the operator or champion rather than the final approver.

And don't treat every contact as either the decision maker or worthless. The point of the first conversation is to work out who has authority, who carries the risk, and who can help the purchase move.