Who gets involved in a software buying decision?
It changes with the size of the company. In Alium’s interviews, the team that wants the tool is commonly involved at every size: in more than nine answers in ten under 1,000 employees, and about three in four at 10,000 and up. The other participants differ. Under 200 employees, 32% of answers name the CEO, founder or owner, against 20% naming IT. At 10,000 employees and up the CEO, founder or owner is named in 7%, while IT is named in 45%, finance or procurement in 33%, and legal, security or compliance in 16%. Larger-company answers also name more of these functions per decision. That is consistent with more specialized technical, commercial and contractual reviews; it is not evidence that the CEO formally gives up authority, or that every function named can approve or stop a purchase.
What it means to be named in the decision
Every figure on this page classifies buyers’ answers about who takes part in technology purchasing at their company. Some answers describe the general process; others describe a specific purchase or evaluation the buyer was weighing. A function counts as named when the buyer describes it proposing, evaluating, being consulted on, approving, negotiating or reviewing a purchase. It does not count when it appears only as a user of the tool, or when the buyer says it is not involved.
Named is not the same as holding a veto. Roles are not exclusive, since one answer can name several functions, so the shares do not add up to 100%. An answer that names finance may mean the CFO signs off on the budget, or only that finance sees the numbers: being named does not mean final authority, a veto, or choosing the vendor. The unit is an interview answer, not a unique company or a buying committee, and an answer about the general process may differ from what happened in any one transaction. A function a buyer did not mention is not necessarily absent. The people answering are mostly marketing, ecommerce and digital leaders, so the findings mainly reflect the view from the team asking for the tool.
| Function named | Under 200 | 200–999 | 1,000–9,999 | 10,000+ |
|---|---|---|---|---|
| Named less as companies grow | ||||
| CEO, founder or owner including a speaker who is one | 32% | 15% | 10% | 7% |
| Named more as companies grow | ||||
| IT or a technology team CIO, CTO, engineering, data | 20% | 31% | 44% | 45% |
| Finance or procurement CFO, sourcing, purchasing | 16% | 26% | 21% | 33% |
| Legal, security or compliance | 5% | 10% | 11% | 16% |
| Other business teams sales, ecommerce, product, operations | 30% | 28% | 41% | 40% |
| A parent company or group | 1% | 3% | 6% | 10% |
| No clear trend with size | ||||
| An unnamed executive or leadership group | 28% | 23% | 29% | 22% |
| A marketing leader other than the person answering | 11% | 16% | 19% | 15% |
| The board or investors | 1% | 2% | 2% | under 1% |
Size bands use the employee count on the buyer’s company record. Every band rests on hundreds of answers. Shares are of answers that described who takes part; the team asking for the tool, usually the person interviewed, is in most of them and is not shown as a row.
Under 200 employees: the owner’s call
At the smallest companies the decision is short and runs through the top. Under 200 employees, about a third of answers name the CEO, founder or owner, and under 50 employees it is about four in ten. About one answer in five names no one beyond the person answering and their own team, against fewer than one in ten at 1,000 employees and up. A co-founder of a small apparel brand puts it plainly: “It’s really just my decision.” Control functions are present but thin: at least one of IT, finance or legal appears in a third of answers.
Where does the CEO drop out?
Mentions of the CEO, founder or owner become much less frequent after the smallest band, but they do not disappear: 32% of answers under 200 employees, 15% at 200 to 999, 10% at 1,000 to 9,999, and 7% at 10,000 and up. Over the first two bands, IT rises from 20% to 31% and finance or procurement from 16% to 26%. That suggests a greater role for specialist teams alongside leadership, not a universal employee count at which the CEO stops approving. The middle band is where the two overlap: the chief executive is still named in some answers, and the CFO and a technology lead appear beside them.
Fewer mentions of a named CEO, founder or owner do not mean leadership disappears from the decision. Buyers also describe leadership teams, executive committees or unnamed senior executives, and that group appears in roughly a quarter of answers in every band (between 22% and 29%), with no consistent trend by size. What changes most clearly is how often the buyer names the CEO, founder or owner in person: 32% under 200 employees, against 7% at 10,000 and up. The interviews do not show that an unnamed group replaces the CEO’s involvement at larger companies, or that it holds equivalent authority.
Why does IT arrive before finance, legal and security?
In these interviews, IT is mentioned more often than the other control functions through the middle and larger bands. It rises from 20% of answers under 200 employees to 44% at 1,000 to 9,999, and is about level at 45% at 10,000 and up. Finance or procurement is less uniform: 16%, 26%, 21% and 33% across the four bands. Legal, security or compliance rises from 5% to 10%, 11% and 16%. These are differences in reported participation across sizes, not evidence that companies add review functions in a fixed order. At the largest companies, a quarter of answers name two or more of the three control functions, against about one in fourteen under 200.
When buyers explain why these functions take part, they describe different reviews. IT or technology teams may assess integration, implementation and who will own the tool once it runs. Finance may review the budget and the case for the spend; procurement may compare vendors or negotiate price; legal may review the contract; security or compliance may assess data handling, access and requirements. These vary by organization and by purchase, and the interviews identify who takes part, not a universal approval workflow or who can stop a purchase. One marketing technology director at a large distributor describes buying moving from the business to IT: “It’s in IT’s hands now.” The business still pays, the buyer says, but IT is now central to the decision.
Some buyers in multi-brand organizations describe parent or group teams that manage shared contracts, coordinate purchasing or sign off on certain vendors. A parent company or group is named in about 1% of answers under 200 employees and one in ten at 10,000 and up, so these teams appear more often in the largest companies’ answers; that does not mean every purchase there needs group approval. The board or investors are rarely named at any size, in at most about one answer in forty.
Being named is not the same as deciding
Several large-company buyers separate the business team that identifies requirements and recommends a vendor from the technical, commercial and contractual reviews other departments run. In some accounts the team asking for the tool builds the shortlist, procurement negotiates, and technology or security teams check requirements. That is a recurring example, not a universal process: depending on the organization, a reviewer may advise, set conditions or hold formal approval, and the figures on this page record participation, not authority.
The counter-current: the team that asks for the tool stays
The marketing, ecommerce or digital team that wants the tool often stays involved: it appears in more than nine answers in ten under 1,000 employees and about three in four at 10,000 and up. It is less consistently mentioned at the largest companies, but still common. A marketing leader other than the person answering appears in about 11% to 19% of answers across the bands, with no consistent trend. The larger-company pattern is review functions appearing around the team asking for the tool, not IT or procurement taking over the choice.
Want your own stack read the same way?
Get mine →What this means before you start a purchase
Our recommendations are implications of these accounts, not a process the interviews establish. Because different functions may take part in technical, commercial and contractual reviews, identifying the likely stakeholders early helps a buyer understand the requirements before choosing a vendor. The figures show how often each function was named in each size band, not which reviews are mandatory, who has final authority or how long approval takes. The questions below are the ones we would ask; which ones matter depends on your own company, not on the average for your size band.
- Does the CEO, founder or owner take part, and at what stage? They are named in about a third of answers under 200 employees, but not every small-company purchase needs their approval. Confirm whether their role is consultation, budget authorization, vendor choice or final sign-off, and involve them at the stage your process requires.
- Who reviews or authorizes the spend? Finance or procurement is named in about 21% to 26% of answers between 200 and 9,999 employees, and 33% at 10,000 and up. Find out whether the purchase needs budget approval, a procurement process, competitive bids, a return-on-investment case or formal sourcing; those requirements depend on company policy and on the purchase.
- Does the purchase need a technology review? IT is named in more than 40% of answers from 1,000 employees up. Identify the requirements for integrations, identity and access, data architecture, implementation and ownership, which technology stakeholders need to review them, and whether their input should shape the shortlist.
- Are legal, security or compliance reviews required? They are named in about 16% of answers at 10,000 employees and up, and they may go unmentioned when buyers name only the stakeholders most visible to them. A security review can apply even to a purchase one team makes on its own budget. Confirm whether data access, security requirements, contract obligations or regulation trigger a formal review, and plan those steps within the evaluation.
- Does a parent company or central team control an existing agreement? About one answer in ten at 10,000 employees and up names a parent company or group. Check whether central contracts, approved-vendor lists or shared platforms affect your options; they may constrain a local team, but authority and exceptions vary.
This page is about who joins the decision. For how formal the process becomes and what goes into the document, the category pages carry the detail: how to write a CDP RFP, how to run a loyalty platform evaluation, and the RFP and evaluation guides. For a category where the committee runs on a requirements document rather than a trial, see the CRM nobody leaves.
What not to read into this
The shares on this page say who buyers named as taking part in a software decision. They do not say who holds a veto, who makes the final choice, or how a company’s formal approval rules are written, and they are not shares of companies. An answer reflects what one person thought to mention when asked, so a function that was involved but went unmentioned is not counted, and a function that was mentioned may have had only a small role. The people answering are mostly on the team asking for the tool; buyers in IT or finance might describe the same decisions differently. Company size travels with industry, regulation and ownership, so this does not show that headcount itself brings IT, finance and legal into the decision. And every figure is an average for its size band, so it does not predict who will be involved in any one company’s purchase.
Common questions
Who is involved in a software buying decision?
It changes with company size. In Alium’s interviews, the team asking for the tool is involved in more than nine answers in ten under 1,000 employees and about three in four at 10,000 and up. Under 200 employees the CEO, founder or owner is named in about a third of answers, and IT in one in five. At 10,000 employees and up the CEO, founder or owner is named in 7%, IT in 45%, finance or procurement in a third, and legal, security or compliance in one in six. Being named means taking part, not holding a veto.
Does the CEO approve software purchases?
At small companies, often. Buyers at companies under 200 employees name the CEO, founder or owner in about a third of answers about who takes part in a software decision, and about four in ten under 50 employees. The share falls by more than half by 200 to 999 employees and is 7% at 10,000 and up. An unnamed executive or leadership group appears in roughly a quarter of answers at every size, with no consistent trend, so it does not stand in for the named CEO at larger companies. Being named is not the same as approving.
When does procurement get involved in buying software?
Finance or procurement is named in about one in six answers at companies under 200 employees, a fifth to a quarter between 200 and 9,999, and a third at 10,000 and up. Several large-company buyers describe procurement negotiating price and terms after the business team has shortlisted vendors, rather than choosing the product, though its role varies by organization.
When does IT get involved in buying marketing software?
IT or a technology team is named in one in five answers under 200 employees, three in ten at 200 to 999, and about 45% from 1,000 employees up, where it levels off. It is named more often than finance, legal or security in every size band, while finance or procurement and legal or security are named most often at 10,000 and up. These are differences in reported participation, not a fixed order in which companies add reviews.
Does everyone involved in a software purchase have a veto?
No, and these figures do not measure one. A function counts as named when the buyer says it takes part, whether that means approving the spend, negotiating the contract, reviewing security or simply being consulted. Several large-company buyers describe procurement and IT reviewing the purchase while the team that asked for the tool makes the final choice; depending on the organization, a reviewer may advise, set conditions or hold formal approval.
Related reading: how company size shapes the stack, on what companies of each size run; does company size change how buyers rate software?; how software buyers find vendors, on what happens before the shortlist; and build or buy?, on when the decision is whether to buy at all.
Your stack, read by the buyers who've run it
Peer-powered: built from hundreds of verified buyer interviews, and fitted to the tools you already run. You get a shortlist for your stack and your next steps.
Get my stack readFree · no password · your answers are anonymized before they inform research like this.