Skip to main content
Lumora

Start with proof. Scale only if the data supports it.

Lumora maps AI, SaaS, card, AP, reimbursement, and vendor leakage across the finance stack you already use. Start with a 7-day Leakage Map, then decide whether a 90-day pilot or annual governance layer is justified.

  • No card migration
  • Uses existing finance data
  • Refundable or credited diagnostic
  • Human-approved controls
  • SOC 2 Type II in progress

A 30-minute, finance-led call to map your AI & SaaS leakage and scope a 7-day Leakage Map. No card migration.

  • No card migration
  • Read-only access
  • Refundable or credited
  • SOC 2 Type II in progress

Choose the right starting point

Start with a leakage review. Expand only when the data shows enough savings potential to justify deeper controls or annual governance.

Find leakage

7-Day Leakage Map

From
$3k

$3k-$15k final scope

Refundable or credited

A paid, time-boxed diagnostic. In 7 days, Lumora maps reviewable leakage across your existing cards, AP, reimbursements, SaaS, and AI spend. Refundable or credited if we do not surface material reviewable leakage under the agreed scope.

Best for: Teams that want proof before committing to a pilot.

We’ll scope whether you need Lite, Standard, or Advanced.

Prove workflow

90-Day CFO Control Pilot

From
$15k

$15k-$50k for 90 days

90-day engagement

Run Lumora on real finance data for one quarter. Validate findings, test policy controls, measure realized or preventable savings, and confirm whether the workflow fits your finance team.

Best for: Teams that found meaningful leakage in the map.

Usually starts after a Leakage Map.

Run continuously

Annual Governance Layer

From
$24k/yr

Starting at $24k/year

Scoped by spend reviewed, systems, entities, and control depth

The always-on neutral control layer across cards, AP, reimbursements, SaaS, and AI usage. Lumora continuously detects leakage, models controls, tracks owners, and produces CFO-ready attribution.

Best for: Teams with ongoing AI/SaaS/vendor leakage risk.

Govern at scale

Enterprise AI Spend Control

From
$150k/yr

Custom enterprise scope

For high-spend or multi-entity organizations

Dedicated governance for organizations with heavy AI, software, AP, card, reimbursement, and vendor complexity across many teams or entities. Built for advanced controls, custom reporting, implementation support, and enterprise security review.

Best for: Heavy AI/tool spend, multi-entity structures, custom reporting, or enterprise security review.

Align to outcomes

Verified Savings Alignment

Optional
5-10%

Optional and capped after scope

Available after scope is defined

For teams that want Lumora’s incentives tied to measurable value, part of pricing can be linked to verified realized savings. Savings are counted only when the baseline, action, and attribution method are agreed in advance. Never based on speculative estimates. Always capped.

Best for: Teams that want shared upside or lower fixed commitment.

What affects annual pricing?

Annual pricing follows scope and value: spend reviewed, source systems, entities, and control depth.

ScopeTypical annual range
Smaller spend base, limited systems$24k–$48k/year
Strong mid-market fit$60k–$90k/year
High-spend multi-source finance team$90k–$150k/year
Enterprise / multi-entity / custom securityFrom $150k/year

What does this cost vs. what does it save?

Estimate your savings

Use this illustrative 1-3% sensitivity range to model what avoidable spend could mean across the spend Lumora can review: cards, AP, SaaS, reimbursements, and AI tools.

Modeled spend range: $100,000 to $50,000,000

Illustrative annual savings range

$25,000 – $75,000

Sensitivity only. Actual savings depend on source coverage, policy decisions, and follow-through.

Frequently asked questions

How much does Lumora cost?
Most teams start with a 7-Day Leakage Map, typically $3,000–$15,000 depending on data scope. 90-day pilots typically range from $15,000–$50,000. Annual governance starts at $24,000/year and is scoped by spend reviewed, source systems, entities, and control depth. Enterprise deployments are custom and start from $150,000/year.
Why do you not show one flat annual price?
Because two 200-person companies can have completely different spend complexity. One may have $1M of reviewable SaaS and card spend; another may have $8M across AI tools, AP, reimbursements, SaaS, and multiple entities. Pricing follows scope and value, not headcount alone.
Is there a long-term commitment?
No multi-year commitment is required to start. Most teams begin with a 7-Day Leakage Map before deciding whether a pilot or annual governance layer makes sense.
How long does implementation take?
Most pilots are designed to start in days, not months. Lumora connects to existing card, accounting, HRIS, and SaaS feeds without card re-issuing.
What data does Lumora need access to?
During the pilot, Lumora uses read-only feeds from your card issuer, accounting system, HRIS, SaaS tools, and CSV imports where needed.
Do I have to migrate cards?
No. Lumora layers on top of the existing card program instead of replacing it.
Is the diagnostic refundable?
Yes. If Lumora does not surface material reviewable leakage under the agreed scope, the diagnostic can be refunded or credited.
How does outcome pricing work?
Verified-savings alignment is optional. When used, it is typically 5%–10% of agreed realized savings, capped, and only applies to categories where the baseline, action, and attribution method are defined in advance.
What happens at the end of the 90-day Control Pilot?
You receive a CFO Brief showing what Lumora found, what controls were modeled or activated, and the realized savings — so you can decide whether to move to the Annual Governance Layer.
Is tenant data shared with other customers?
No raw tenant data is shared by default. Optional network intelligence is designed around privacy-minimized, k-anonymized vendor aggregates.
What integrations are available?
The pilot is designed around existing card issuers, accounting systems, HRIS data, SaaS admin data, and CSV imports. Specific integrations are confirmed during onboarding.

Prove the leakage before you commit to the platform.

Start with a 7-Day Leakage Map on your own data — refundable or credited under the agreed scope.

  • No card migration
  • Read-only access
  • Refundable or credited
  • SOC 2 Type II in progress