The person with the greatest urgency may not have the mandate

This comparison is based on the original Finance target-group cards: pain points, fears, objections, desired outcomes, evidence and preferred routes. Descriptions have been shortened editorially without changing their meaning.

The controller experiences the same problem every month. Each manual file consumes time and introduces another opportunity for errors. The source card even gives an illustrative customer line: 'If this saves me two days a month, I want it tomorrow.' The two days are part of the card's illustrative voice, not a measured product result.

The finance director manages a whole process and team. A tool that saves two days but takes three difficult months to deploy may not be an improvement. The concern is whether closing becomes more reliable without creating extra work.

The CFO weighs the same investment against capital, risk, compliance and multi-year priorities. That does not mean adding more slides. It means presenting a different class of evidence. Start with the recurring operational problem, translate it into process outcomes, and only then into financially defensible value and risk management.

The card describes a controller caught between the information demands of the business and what finance systems can deliver. The underlying problem is fragmented systems and data that repeatedly needs cleaning. The biggest fear is not missing a nice new feature; it is an error in the numbers that causes management to make the wrong decision.

A generic ROI calculator is rarely the best first proof for that role. Show a demo on securely supplied company data or a representative sample. Demonstrate what steps disappear, how reconciliation works, how exceptions are flagged and which ERP integrations are established. Ask which report they struggle to deliver ahead of management meetings.

A useful first step may not be a purchase at all. It may be a clear problem inventory that lets the controller explain internally where time is lost and which risks the proposal would reduce.

The finance director is responsible for financial processes, reliable figures and team workload. The source card points to outdated systems, missing integrations and too much processing work. Its objections are concrete: will it fit existing systems, how much does implementation cost, and what happens if the project slips?

Do not sell only the ideal destination. Make the route testable. Specify involved systems, the effect on month-end, the workload required from the internal team, implementation cost and what is fixed contractually. Provide close-time comparisons and similar-system references if you actually have them.

This role also operates within a budget cycle and defined authority. A decision that falls inside the finance director's mandate can follow a different route from one requiring the managing director or CFO. Establish that decision path before preparing the final proposal.

For the CFO, the cards emphasise financial health, company value and risk management. The biggest pain is insufficient timely, dependable information for steering the business. Regulatory, banking and reporting requirements add another layer. The most serious fear is an investment that fails to deliver or an exposure that harms the organisation.

A deck featuring hours saved is therefore incomplete. Show total cost across licensing, implementation, internal capacity, maintenance and migration, along with the cost of doing nothing. Separate documented outcomes from assumptions. Make downside scenarios visible, including what happens if adoption or integration is slower than expected.

The source card highlights introductions through accountants, banks and fellow CFOs. That is not a universal rule for reaching every CFO. It does suggest that trusted references and independent credibility belong early in the sales strategy rather than at the end.

These values come directly from rows 44-46 of the Finance cards. BIS and BAS use separate 0-10 scales. k is a different parameter describing the relative weighting of sooner versus later outcomes within the profile model. It is not a percentage, purchase probability or personal diagnosis.

The cards give k 0,25 for the controller, 0,15 for the finance director and 0,08 for the CFO. Those values fit the different moments when results become meaningful: the next closing cycle, the current budget year and a multi-year financial plan. They do not define fixed purchasing deadlines. A CFO confronted with immediate liquidity or fraud exposure may act very quickly.

You can, however, change your presentation sequence. Start with the next closing cycle for the controller. For the finance director, address budget, implementation and process KPIs. For the CFO, lead with total value, assumptions and risk scenarios before descending into operational details.

Likewise, high BIS does not mean all three reject change. Their avoidance concerns differ: incorrect figures for the controller, implementation overrun for the finance director, and broader financial harm for the CFO.

Imagine selling a platform that combines reports from multiple systems and automates parts of month-end. This is a fictional sales example, not an observed Neurofactor case or EEG finding.

The controller asks: 'Can I reconcile exceptions faster and still verify the figures?' The finance director asks: 'What will deployment cost, can we keep closing on schedule and will the team actually gain capacity?' The CFO asks: 'What return will this produce over the whole contract period, what risks are covered and how reliable will the management information be?'

Same software. Different conditions for taking the next step. Sending all three the same demo and same efficiency claim creates confusion. Keep the core proposition, but adapt the supporting evidence and the next decision.

Treat the purchase as a chain of decisions. Each role needs enough evidence to answer its own question and pass the proposal on responsibly.

These are editorial examples based on the cards' language anchors, not quotations measured in a campaign.

Winning internal support seems sensible. But there is a limit. The card gives the controller restricted purchasing authority and a heavy existing workload. Asking them to produce a lengthy internal sales case adds work to the very role you promised to help.

Make handover light: a one-page summary of the current problem, the test outcome, required integrations, implementation impact and open questions. Involve the finance director in the cost and deployment work. Once those elements hold up, a CFO discussion becomes more valuable.

In some organisations the CFO joins from the start; elsewhere the finance director can sign within their mandate. The cards describe patterns, not universal reporting structures.

These three roles should not receive one generic 'finance transformation' message. A controller is more likely to find detailed month-end, reconciliation and analysis content relevant. A finance director weighs budget discipline, team capacity, integration and reliability. The CFO is better served by rigorous analysis of return, cash flow, compliance and downside exposure.

The cards also describe different preferred routes: practitioner webinars or peers leading to a hands-on demo for the controller; peer or accountant recommendations followed by implementation discussion for the finance director; and a trusted financial network introduction for the CFO. These are source-card preferences, not measured LinkedIn conversion rates.

So do not write three posts that change only the job title. Change the underlying question. For more depth, review evidence requirements, buyer objections and time preference k.

It can be tempting to start with the controller, secure enthusiastic feedback and immediately request a CFO presentation. The cards suggest a more robust sequence. First validate which errors or manual tasks actually disappear. Let the finance director judge whether implementation and budget make sense. Then present the investment to the right decision-maker.

This changes your proposition. For the controller, sell fewer avoidable manual steps. For the finance director, a more dependable process. For the CFO, a decision that can withstand financial challenge. One product must answer three different accountability questions.

The follow-up articles CFO versus controller and CFO versus finance director explore those handovers in depth.

Finance does not purchase time savings, efficiency and return as three unrelated products. The controller sees the error-prone task, the finance director the process that must keep running, and the CFO the capital and risk that must be justified.

If you only win the controller's enthusiasm, you do not yet have an approved business case. If you only speak to the CFO, you may miss the daily problem that makes the case credible. The strongest finance pitch starts with work that truly changes and ends where the investment can be defended.