At a mid-size company the CFO signs, and the controller or VP of finance usually starts the search and runs the evaluation. The person who runs the process daily, such as the payables lead, judges fit, and IT checks integration and security. Sell to the owner of the broken process, with the case the CFO needs.
Which finance role owns which purchase?
Ownership follows the process the software touches. The table is our working map for companies of roughly 50 to 500 staff, where one person often holds two of these roles.
| Software category | Who starts the search | Who signs | Who can block it |
|---|---|---|---|
| Payables, expenses and spend control | Controller or payables manager | CFO | IT, over the ERP integration |
| Close, reconciliation and consolidation | Controller | CFO | The external auditor's view of the controls |
| Planning, budgeting and forecasting | Head of FP&A or VP of finance | CFO, sometimes with the CEO | Department heads who must enter data |
| Treasury, cash and payments | Treasurer, or the CFO directly | CFO | Banking partners, IT security |
| Tax and digital asset accounting | Tax lead or controller | CFO | The outside tax adviser or auditor |
Two patterns hold across the rows. The CFO signs almost everything, because the budget sits in finance. The person who starts the search is the one who feels the problem each month, and that person writes the shortlist.
What does a mid-market CFO want from new software?
They want it to work with what they already run. Cherry Bekaert surveyed 200 CFOs and senior finance leaders at US companies with $5 million to $250 million in revenue (Cherry Bekaert, November 2025). The figures below come from that survey.
| Finding | Share of respondents |
|---|---|
| Integrating or tuning existing finance tools before buying new ones | 77% |
| Blocked from key decisions by poor data quality | 49% |
| Say technology experts lack finance knowledge | 44% |
| Say finance teams are uncomfortable with technology | 40% |
Read those numbers as a brief for the pitch. Show which system the tool connects to and which data problem it removes. Name the person on the finance team who will run it, and how long they need to learn it. A tool that adds one more system to reconcile will lose to the option of fixing the current stack.
How many people join the decision?
More than most sellers map. 6sense's 2025 buyer survey, with nearly 4,000 responses, found buying groups of 10 or more people on deals averaging $250,000 (6sense, 2025). In our experience a finance tool deal at a 200-person company draws a smaller group, but the same roles still appear, with fewer people holding them.
Timing matters more than group size. In the same survey, buyers first contacted a seller at 61% of the way through their journey, buyers started 79% of first contacts, and 95% of purchases went to a vendor on the buyer's first-day shortlist. By the time a controller sends a request for proposal, the shortlist is set. Reach the controller before the search begins.
Which events start a finance software search?
These events give a finance team a new problem, a new owner or a new deadline:
- A new CFO or controller. A new finance leader reviews the stack in their first months. Among large listed companies tracked by Russell Reynolds, CFO appointments reached 316 in 2025, a seven-year high, and 57% were first-time CFOs (Russell Reynolds, February 2026). That data covers listed companies only, so check job changes at mid-size targets on LinkedIn.
- An ERP change. Every tool that connects to the old system gets reviewed when the ledger moves.
- An audit finding. A control weakness gives the controller a deadline and a reason to spend.
- A new entity or country. Consolidation, intercompany and local tax rules arrive at once.
- A raise or a new lender. Investors and lenders ask for faster, cleaner reporting.
- A departure in the finance team. Work that one person did by hand needs a system when they leave.
We rank these and other events by how well they predict a purchase in which buying signals predict a B2B purchase.
Whom should the first email go to?
Pick the first contact by what the product changes. Use this rule:
- The product fixes a monthly process (payables, close, reconciliation, expenses). Write to the controller or the process owner first. Copy the CFO only after the first reply.
- The product changes a number the board sees (cash runway, forecast accuracy, margin by product). Write to the CFO first, then bring in the head of FP&A or the treasurer.
- The product touches tax or regulatory filings. Write to the tax lead or the controller, and expect the outside adviser to join before signature.
Whoever you write to, give them material they can forward: one paragraph on the problem in their words, the system it connects to, and the hours or days it removes from the close. The controller can then send it to the CFO unchanged.
Checklist before you build the list
- Name the software category and find its row in the role table.
- List the starter, signer and blocker for each target account.
- Lead the pitch with the integration and the data problem it fixes.
- Watch for a new finance leader, an ERP change, an audit finding or a new entity.
- Reach the starter before a formal search begins.
- Send the CFO a forwardable case after the first reply.
Contact data on finance teams goes stale between list build and send, as set out in how fast verified B2B email lists decay.
To map the controllers, finance leads and signers at your target accounts, start with The Diagnostic at $2,500.