The Buyer Authority Signal Reference: Reading Budget Power From a Title

You found a prospect's title, seniority label, and function online, and now you need one thing before you spend outreach on them: can this person approve, influence, or block a purchase? This is a lookup reference for founders, account executives, SDR leads, and partnerships teams. Jump to the row that matches the signal in your hand, read what it proves and how it lies, and leave with a working classification.

Most published sales guides do one of two things. They name every seat on a buying committee, or they rank a list of named contacts for first touch. Neither helps when you have a single ambiguous profile open and thirty seconds to decide whether it is worth a message. This document resolves that. Each signal gets treated as evidence with a known failure mode, because a title that overclaims is worse than no title at all.

What a title proves and what it never does

A title proves nothing about budget power on its own. Buying authority tracks a spend-approval threshold, and that threshold scales with company size and revenue, not with the words in the title. The identical title flips roles across two accounts.

The clearest anchor: a $5,000 purchase might be routine for a $50 million company but requires CFO approval at a $10 million organization. Same dollars, different owner, because the approval matrix moves with revenue. This is why the question "does this job title have buying authority" has no answer until you know the firmographics behind it.

There is a break point where titles start meaning something. Below roughly 100 to 200 employees, it is no longer sustainable to have scrappy operators holding vague, inflated titles - so above that band, a title is more likely to map to a real rung. Below it, treat every senior-sounding stem with suspicion.

Read a title as a hypothesis about a spend ceiling, then test it. The rest of this reference is the set of tests.

Spend-approval owner by company size

Authority resolves to who signs off at a given dollar amount, and that owner shifts by both headcount and revenue. Use this table to convert a title plus a company size into an estimated approval ceiling.

For a company of 100 to 250 employees, a common starting point is auto-approve under $500 with a purchase-order match, manager approval to $5,000, Controller approval to $25,000, and CFO approval above that. Under 50 employees with a single accounts-payable person, a manager-approves-everything rule often holds. At 1,000-plus employees with a dedicated procurement function, source-to-pay platforms own the flow and the title you found may not touch the decision at all.

The lesson for a rep: if your average deal is $30,000 and the person's estimated ceiling is $5,000, their yes is an influence signal, not an approval. You are looking one rung too low.

How to read seniority from a LinkedIn title

The LinkedIn seniority label is an AI-assigned category, not a stated org rank, and its boundaries are fuzzy. Read it as a hint that needs confirmation, never as proof of authority.

The filter values, from lowest to highest, are Unpaid, Training, Entry, Senior, Manager, Director, VP, CXO, Partner, and Owner. LinkedIn assigns users to this Seniority Level using AI elements, which means it makes systematic errors you can anticipate.

The trap that catches the most reps is "Senior." It is one of the most misunderstood options. It does not mean senior leader - it means individual contributors who have the word Senior in their title. A Senior Engineer is an IC, not a decision-maker. The AI also misfiles top titles in the other direction, showing some Presidents and Directors under Entry Level. So the label lies both up and down.

Practical rule: when you see "Senior" or "Head of," mark the profile unresolved and move to the scope and headcount checks. Every other label you can provisionally trust, then verify live.

Scope modifiers and the "Head of" problem

Scope words widen or narrow authority, but "Head of" is the single most inflation-prone stem and rarely proves budget power by itself. Treat it as an unresolved flag until you find direct reports or profit-and-loss responsibility.

"Head of" often means the most senior person currently responsible for a function, not one standardized rung. A Head of People might be the CEO's top people partner with real authority, while a Head of Content might be a senior individual contributor building the capability alone. Same stem, opposite reality. Startups make this worse: they routinely use VP, Director, and Head of as substitutes for more competitive salaries, so the stem is a pay hedge, not a seniority claim.

Other modifiers give softer hints. "Global" and "Group" tend to widen scope; "Regional" and "Deputy" tend to narrow it. Precise authority spans for these are not established in primary sources, so use them as direction-of-travel hints only, never as proof.

The refolk index makes the inflation visible at scale. In Refolk's index of professional profiles there are 21,258 US CMOs at CXO seniority against 8,510 US VPs of Marketing - a ratio of 2.50 to one. There is no world with two and a half times more chief marketers than mid-tier marketing VPs. The senior-sounding stem is simply cheaper to hand out, which is exactly what title inflation looks like in the data.

Refolk index title counts and what they warn you about

Title counts from Refolk's index expose two biases you carry into every ICP: senior-stem inflation and geographic drift. Use them to correct a heuristic before it costs you outreach.

Two reads. First, "Head of Sales" at Director level is 28% more common in the UK than the US - 4,541 against 3,539. A US-built ICP heuristic imported to the UK will over-weight that stem and pull in more ICs and solo operators than expected. Second, the CMO-to-VP ratio confirms the inflation pattern above: the more impressive the stem, the more freely it is issued.

The correction is not to distrust every title, but to distrust the stem in isolation and lean harder on the headcount discount below the 100 to 200 employee break point.

Firmographic and event signals that outrank the title

Firmographic and event signals often beat the org chart, and recent funding is the strongest of them because it is the only common signal carrying both budget and urgency. Many signals indicate budget or urgency but not both; funding uniquely combines the two, since the company has money and pressure to spend it strategically.

The documented outreach window is 60 to 90 days after funding. Earlier and the company lacks bandwidth because it is still hiring key decision-makers; later and budgets are already locked into vendor relationships. Verify the announcement date every time, because a stale funding signal spends your best card after the table has closed.

Two more event signals worth capturing:

• Role change under 90 days. Job changers are 62% more receptive during their first 90 days. A new leader is looking to make a mark and has not inherited vendor loyalty.
• Active departmental hiring. Open roles in the buyer's function signal an expanding budget and an unsettled tooling stack.

One caution on numbers you will see elsewhere: a widely repeated "4.3x more likely to buy" post-funding figure appears only on a vendor blog with no cited primary study. Do not carry it into a business case. It is not established.

When you can combine a firmographic filter, a size band, and a recent event in a single ask, you skip most of the manual resolution this reference describes. Refolk is built to take that request in plain English and return the people, so you spend your judgment on the classification rather than the search.

The signal reference: what each proves and how it lies

Each signal proves something narrow and misleads in a specific, predictable way. This is the core lookup. Find your signal, read the proof, and read the trap.

• Title stem (e.g. VP, Director, Head of). Proves an intended rung. Lies when the company is under ~100-200 employees or uses the stem as a pay substitute - a "VP of Sales" at a 40-person company does not control enterprise budget.
• Seniority label (LinkedIn). Proves an AI's category guess. Lies systematically at "Senior" (means IC) and misfiles some Presidents and Directors as Entry Level.
• Scope modifier (Global, Regional, Deputy, Head of). Proves breadth or narrowness of remit. "Head of" lies most - it can mean functional owner or solo IC. Confirm with direct reports and P&L.
• Function (Sales, Finance, IT, Marketing). Proves which budget line the person touches. Lies when the deal crosses departments; 89% of decisions involve two or more.
• Firmographic context (headcount, revenue, stage). Proves the spend ceiling that sits behind the title. Rarely lies, which is why it should override the stem when they disagree.
• Funding event. Proves budget and urgency together. Lies only when stale - outside the 60 to 90 day window it deflates fast.

The verification target is always the economic buyer, and it is confirmed by two non-title markers: profit-and-loss responsibility, and access to discretionary funds that are not budgeted. If a profile shows neither, no stem earns them the economic-buyer label.

The classification procedure

Run these seven steps in order on any single profile. The first five take a rep about five minutes at a desk; the last two happen live and in the account.

Sources disagree on step six, and the disagreement matters. Some Sales Navigator guides say "Director and above equals buying authority," which is a filter heuristic. MEDDICC warns against the CEO error - assuming the most senior person is the economic buyer - and notes the buyer is often a department head. When they conflict, the live verification step overrides the filter heuristic every time. The documented verification question is simple: ask about the approval process for investments of a similar size, such as "who typically needs to give the final sign-off on initiatives like this?"

How this classification goes wrong

This is the most valuable section, because every failure below produces a confident classification that is wrong. Each has a false positive and a one-line check.

The seventh failure sits above all of them: single-threading. Treating one confirmed yes as a closed deal ignores the rest of the committee. Reported buying-group size ranges from 5.4 (Challenger Customer, 2015) to 6.8 (HBR, 2017) to 13 (Forrester, 2024) to 5-16 across up to four functions in Gartner's 2024/25 survey of 632 buyers. Even the older "6 to 10" figure came from two Gartner articles that now redirect to a generic page, so treat any single number as approximate. The direction is not in doubt: the committee is large and growing.

It gets harder still: 74% of B2B buyer teams show unhealthy conflict during the decision. So a single confirmed economic buyer is necessary but not sufficient. Multi-threaded outreach reaching five or more stakeholders closes at 30% versus 5% single-threaded - a six-fold gap - and early decision-maker involvement lifts win rates by 55%.

Before you commit outreach

Run this checklist on the profile before you send the first message. If any item fails, you are not ready to spend the touch.

Keeping the reference current

Titles, filters, and buying-group numbers drift, so treat this reference as a living document and re-check the mechanisms rather than memorising the values. Three things move.

First, the seniority filter taxonomy and its AI behaviour change without notice. Re-confirm that "Senior" still reads as IC by spot-checking a handful of known profiles against their actual reporting lines. Second, buying-group size estimates get revised every year, and old figures live on in blog posts after the primary articles are pulled - always trace a number to a dated survey with a stated sample before you quote it. Third, approval thresholds shift with each company's revenue, so the ceiling you estimated last quarter may be wrong after a growth round.

The durable move is to source people by the signals that outrank the title in the first place - size band, function, and recent event - so you resolve fewer ambiguous profiles by hand. Refolk lets you ask for exactly that combination in plain English, which is where the manual work in this reference stops being necessary.