LUNARI
Resources · Getting Approved

Evaluation is a demo. Approval is a sale.

The best finance platform in the world will still die in procurement if the case is wrong. This guide is for the champion inside the company — and the vendor who wants them to win the room you'll never see.

90 KB · PDF · 3 pages

Evaluation and approval are two different games with two different rulebooks. Most champions only ever learn the first.

The approval principle
Why good tools die in approval

The reasons are rarely about the product.

6 failure patterns
Failure 01

You solved your problem, not the company's.

Framed as 'this makes my life easier,' the request competes with every other function's life-easier request and loses. Approved tools are framed as company problems: risk, audit exposure, headcount avoided, a close blocking the board timeline.

Failure 02

There's no number attached.

'It'll save us time' is a feeling. Approvers sign against numbers: hours reclaimed × loaded cost, the FTE you avoid hiring, the audit finding you prevent. No quantification, no approval.

Failure 03

You're the only person who wants it.

A single champion is a single point of failure. Deals that get approved have a coalition — IT comfortable with security, an ops peer who benefits, a finance peer who'll nod.

Failure 04

Procurement and security were an afterthought.

Vendor-security review, data residency, the SOC 2 gate. The deal hits a wall you didn't know existed and stalls in a queue with no urgency behind it.

Failure 05

It looks like a new line item, not a swap.

Every new tool is net-new spend unless framed against what it replaces: the spreadsheet army, the contractor you rehire every close, the module you're overpaying for.

Failure 06

The timing is invisible.

'Whenever' is not a reason to act now. Without a deadline the company already owns — the audit, a new entity, the fundraise, a migration — the decision drifts to next quarter forever.

How to get it approved

Reshape the decision so it survives the people who sign.

6 winning moves
Move 01

Translate your pain into their language.

Not 'the intercompany close is killing my team.' Instead: 'we have a manual process that's a material-weakness risk and a bottleneck on board reporting.' Same tool, different problem — theirs.

Move 02

Bring one number they can defend.

One credible, conservative figure they can repeat upward. 'Roughly two FTE-weeks per close, across twelve closes, is most of a headcount we're about to have to hire.'

Move 03

Build the coalition before the ask.

Get IT to pre-bless the security posture. Make the peer who also benefits a co-sponsor. By the decision meeting, the answer should already be socialized.

Move 04

Clear the procurement path early.

Ask for the security package — SOC 2, data residency, DPA — on day one and hand it to security before you're committed. A tool already cleared can move the moment budget says yes.

Move 05

Frame it as a swap.

Name what it replaces, in dollars. 'We're not adding cost, we're moving it from something worse to something better' is the sentence that unlocks budgets.

Move 06

Attach it to something already urgent.

Don't create urgency — borrow it. Tie the tool to a deadline the company already owns. The decision becomes 'how do we hit this date,' which always gets answered.

For the vendor

Your job is to arm the champion.

The champion who loves your product but walks in unarmed will lose to a worse product with a better internal seller. Your real product, past the demo, is making them win that room.

  • Hand the champion a pre-built, conservative business-case number.
  • Deliver the security package before they ask: SOC 2, data residency, DPA.
  • Write the one-paragraph internal email that reframes the problem in CFO language.
  • Name the swap: the contractors, modules, and spreadsheets this replaces.
  • Identify the two peers most likely to co-sponsor the decision.
Download the full guide

The platform you love stops being a browser tab you keep meaning to close.

The PDF includes the complete argument, the six failure patterns, the six winning moves, and the vendor's champion-enablement checklist.

Download PDF
Ready when you are

Losing approvals for tools you know are right?

We can help you build the business case, the coalition, and the procurement package — so the best tool is also the best-sold one.