lumrel

LuminousRelevance

Know what your software spend is for.

Lumrel makes the whole technology portfolio visible, then helps leaders decide what matters to the business. An analyst reads the evidence and proposes. A named person approves.

Overlap analysis · Northstar AI Analyst reading evidence
Select a capability to see the analyst's trace. Synthetic example: a fictional company with 17 applications and 8 capabilities, 8 applications and 5 capabilities shown. Savings figures are illustrative.

Every team sees a different slice

Applications arrive one purchase at a time. Each purchase can be reasonable while the portfolio as a whole becomes expensive, fragmented and hard to explain. Leadership needs one answer to a plain question: what are we paying for, what does it serve, and what should we do differently?

Finance

Sees invoices

Which costs are justified, and which savings are credible?

IT

Sees applications

Which tools support which capabilities, and where is the unneeded complexity?

Procurement

Sees contracts

What do we renew, renegotiate, consolidate or retire?

Business owners

See the tools they need

Can we change something and keep the functionality our teams rely on?

Luminous, then relevant

The name is the method. First bring everything into the light. Then judge what matters to the business, one capability at a time.

Part one

Luminous

Understand → Identify → Examine

  • Portfolio visibilityApplications, owners, spend, contracts and usage in one connected view.
  • Overlap analysisPossible duplication, checked against distinct requirements and dependencies.
  • Usage evidenceUploaded usage logs now. Sign-in and device data later, to find tools nobody listed.
Part two

Relevance

Compare → Approve → Measure

  • Decision modelingRenew, renegotiate, right-size, consolidate, replace or retire, side by side.
  • Decision governanceOwners, rationale, reviews and approvals on the record.
  • Execution trackingEach action followed through renewals, migrations and retirement.
  • Value measurementEstimated, approved, implemented and verified value kept apart.
  • Portfolio planningSimplification prioritized across the organization.

A recommendation has to earn its approval

Similar feature lists or low usage alone never justify removing a tool. Before anything can be approved, the analyst checks four gates and shows what it found. A gate that fails blocks the action or sends it back for review.

Gate 1

Contract timing

Is there a renewal or notice window to act in?

Gate 2

Data confidence

Is the usage evidence complete enough to trust?

Gate 3

Adoption effort

What would it take for the affected teams to move?

Gate 4

Dependencies

Which workflows and systems rely on this tool?

EstimatedThe analyst's proposal, with assumptions shown.
ApprovedA named owner signs off.
ImplementedThe change has happened.
VerifiedMatched to an invoice or purchase order.

Value is only called verified after it shows up in the money.

OverlapIQ is where Lumrel starts

The first product takes on one concrete problem: understanding overlapping technology investments and acting on the opportunities that hold up. Lumrel broadens only where customers show repeatable value.

Prototype

Working today

A working prototype runs the full decision path on synthetic data.

  • Capability-based view of applications and spend
  • Overlap analysis that separates true duplicates from similar-but-distinct needs
  • Evidence gates, scenarios, a decision register and outcome tracking
Planned

Next with real teams

The pilot tests how customers define capabilities, weigh alternatives and substantiate savings.

  • Sign-in and free trial
  • Upload of application usage logs
  • Procurement, identity and device inventory connections

Bring one real portfolio decision

We are looking for CIO, finance and procurement teams in B2B SaaS to test the first pilot. Tell us which renewal or overlap question you would want settled.

Write to hello@lumrel.ai Email about the pilot