Skip to main content

In development. Registering pilot partners.

Portfolio control.Not portfolio admin.

Lunav is the governance layer for the portfolio you already run. Your rulebook stops being a document and starts being enforced.

Register your interestSee how it works
  • Overlay. Nothing gets migrated
  • Supplier milestones verified
  • Human approval by default

Reads the systems you already run

Read-only. Your tools keep doing their job and nothing is migrated out of them.

  • Jira
  • SAP
  • SharePoint
  • Excel
  • Teams

The governance gap

Your portfolio office was built to report. You are accountable for control.

The rules exist. They are written down, agreed, and applied by hand, by people who are already full. So governance happens when somebody has time for it, which is not the same as when it is needed.

  1. 01

    Your best people spend the week collecting

    The numbers already exist in systems you already own. Your senior people spend the week moving them by hand instead of managing the risk they reveal.

    27% spend more than twenty hours a week collecting status data. More than half a working week, on assembly

  2. 02

    Every business unit reports differently

    Jira in one, MS Project in another, Excel in the gaps. Someone reconciles it by hand, so the portfolio view is only ever as fresh as the last reconciliation.

    50% of organisations have no real-time project indicators

    Wellingtone, State of Project Management 2026
  3. 03

    Suppliers mark their own homework

    A supplier declares a milestone complete, the invoice follows, and nobody has the evidence to argue before it is paid.

    Only 9% are fully confident a supplier milestone is verified against evidence before the invoice is paid

  4. 04

    You find out when it is already a recovery

    The escalation reaches you after the decision that would have prevented it was available to somebody else, weeks earlier.

    68% said leadership found out later than the week the warning signs appeared. 9% could not tell, for want of the data

None of this is a reporting problem, and more reporting will not fix it. Your governance is documented. It is simply not enforced by anything except people remembering to enforce it.

Primary research

The Governance Gap 2026

What 26 project and portfolio leaders told us about governing at scale

Download the full 17-page research report

  • 73%

    see status reports painted greener than reality

  • 59%

    lose at least five hours every week to collating data

  • 68%

    say leadership found out later than the week the warning signs showed

  • 69%

    want status reports generated from data already in their tools

The Governance Gap 2026

Four fields, then the download starts. We will not put you on a drip campaign.

We use these details to send you the report and to understand who is reading it. See the privacy policy for how to have them removed.

Trouble with the form? Ask us for a copy at contact@lunav.io

What changes

The same governance, without the fortnight that goes into it

Your fortnight now

Governance as a manual relay

  1. You chase project managers across every business unit

  2. Some reply late, some reply optimistically

  3. Someone reconciles it all into one spreadsheet

  4. A steering pack gets built in PowerPoint

  5. The gate meeting reviews a two-week-old picture

  6. A supplier invoice is approved because the milestone says green

Elapsed: the reporting cycle. Owner: your most expensive people.

With Lunav

Governance as a running system

  1. Signals are read from every business unit continuously

  2. Agents assemble the status and score the risk

  3. One portfolio view, current when you open it

  4. The steering pack is drafted overnight for your sign-off

  5. Gates pass or block against live evidence

  6. Invoices release only when the milestone is actually evidenced

Elapsed: continuous. Owner: the platform, until a person is needed.

The governance work does not disappear. It stops being done by your most expensive people, by hand, two weeks after it mattered.

The Intelligent Mesh

Why this can enforce what a reporting tool can only describe

Three things working as one system. Every project, supplier and business unit as one graph instead of rows. Specialists that reason across all of it. Your policy, compiled and enforced.

Signals in, read-only
  • SAP
  • Jira
  • SharePoint
  • Excel
OwnerProgrammeMilestoneRiskSupplierBenefitInvoiceStrategic goal

Knowledge graph

Your portfolio as a network, not a table

Projects, milestones, risks, suppliers and strategic goals as linked entities, so a slip in one workstream traces to the outcome it threatens.

  • Time
  • Cost
  • Quality
  • Scope
  • Benefits
  • Reputation
One recommendation, with the basis attached

System-of-Agency

Specialists that act, not a chatbot

Six agents assess a risk in parallel across time, cost, quality, scope, benefits and reputation. A consolidator merges them into one recommendation.

Written in plain English

"Hold a phase gate while residual risk exposure is above 16, and tell the sponsor."

  • Grounded against the graph
  • Compiled
  • Enforced
  • Logged

Governance-as-Code

Your rulebook, compiled and enforced

Write policy in plain English. Lunav grounds it against the graph and executes it. Every evaluation is logged, so the audit trail builds itself.

Executive decisions

Each one arriving with the evidence and the audit trail already attached.

Capabilities

Five things that stop being your job

Each one replaces work somebody in your office is doing by hand this week.

The screens are interface designs from the current build, not photographs of a shipped release.

Status reports that write themselves

Lunav drafts the report from data you already own.

Assembled overnight from whatever each team already runs. No collection round, no chasing.

Drafted overnight, every claim traceable to the record it came from.

A portfolio view that is current

Lunav shows how one delay cascades into everything downstream of it.

One live picture of the whole portfolio, with a slip in one workstream traced to what it hits next.

What is off track, what it threatens, and what is waiting on you.

A risk register that updates itself

Lunav rescores risk as conditions change, not as the calendar turns.

Six specialists score every risk in parallel and draft mitigation with the evidence cited.

Scores move when the project moves, and the reason for each movement is recorded beside it.

Ask the portfolio a question

Lunav answers from your own project history.

Plain-English queries, with every claim citing the milestone or invoice behind it.

Ask what a delay threatens. Get the chain, not a search result.

Stage gates that actually hold

Lunav enforces the gate rather than reminding you about it.

Checked against live evidence, including your suppliers. A gate that has not met its criteria does not pass, and no invoice releases behind it.

A gate that blocks, and an invoice that waits for the evidence.

Architecture and security

What your IT function will ask, answered before they ask it

You will have to get this past someone. Governance software holds the record of who decided what, so it is a higher bar than a task tracker, and these are the answers in the form they will want them.

Your estateLunav

  1. Your systems

    SAP · Jira · SharePoint · Excel

  2. Connectors

    Read-only. Scheduled and event-driven

  3. Knowledge graph

    Cross-domain entities and their links

  4. Agent runtime

    Specialists with full graph context

  5. Governance engine

    Policy evaluation and enforcement

  6. Executive surface

    Dashboard, approvals, audit trail

Every request crosses the governance gateway, whether it comes from a person or an agent.

The security questionnaire, pre-filled

  • Azure-native

    Multi-tenant and cloud-native on Microsoft Azure

  • European hosting

    The platform deploys into European regions. Registrations today sit in Azure UK South

  • Microsoft Entra ID

    MFA enforced. Lunav stores no passwords

  • Role-based access

    People see the portfolio through their own responsibilities

  • Audit logging

    Every policy evaluation and agent action, with its provenance

  • Human approval

    Consequential actions route to a named approver

  • Tenant isolation

    Separate at every layer, encrypted in transit and at rest

  • EU AI Act ready

    AI use made explicit and generated output labelled

Early access

Start with one governance problem

One of your real projects, measured against your own baseline. Pilots are expected to open in the first quarter of 2027, and places are limited.

How a pilot runs

  1. Pick one problem

    One governance failure you can already name. Status you do not believe, a supplier milestone nobody verified, a portfolio view that is always a fortnight old.

  2. Run it for eight to twelve weeks

    Long enough to span two of your reporting cycles, which is what it takes to measure a real improvement rather than a demo effect.

  3. Decide on evidence

    You end with a value case against your baseline, and a clear read either way. If Lunav does not belong in your portfolio, you will know that too.

What registering gets you

  • Founder-led throughout, by someone who has run transformation portfolios on this scale. Not a sales representative.
  • Influence over the roadmap while the governance model is still being shaped.
  • First refusal on pilot places.

What happens next

  1. A reply within two working daysFrom the founder, not an autoresponder.
  2. A 30-minute conversationAbout your governance problem. No slide deck unless you ask.
  3. A walkthrough and a scoped pilotYou see the product as it stands, and we agree what a pilot covers.

Register your interest

Leave your work email and we will be in touch. Nothing else is required.

Trouble with the form? Write to us at contact@lunav.io

Questions

The things buyers actually ask us

Including the ones where the answer is "not yet".

Is this only for very large organisations?

No. It is built for portfolios that have outgrown what a spreadsheet and a disciplined project office can hold, but that cannot justify the cost and disruption of a full incumbent implementation. The useful test is not headcount. It is whether your governance is written down and applied by hand, and whether anyone can tell you the state of the portfolio without asking around first.

Our suppliers deliver a large part of the work. Does that matter?

It is one of the reasons to use it. Most portfolio tools assume delivery happens inside your organisation, so a supplier milestone is whatever the supplier says it is. Lunav treats suppliers as entities in the graph like any other: a milestone they declare complete is checked against the evidence attached to it, and an invoice behind an unevidenced milestone does not release until a named person decides it should.

Does Lunav replace my PPM tool?

No, and it is not trying to. Lunav is a governance layer above your delivery tools, not a competitor to them. Each business unit keeps whatever it already runs: tasks stay in Jira, schedules stay in MS Project, costs stay in SAP. Lunav is the master record only for the entities that cross functions, which is projects, risks, benefits, suppliers and people.

What is the Intelligent Mesh?

Three things working as one system. A knowledge graph holding your portfolio as linked entities rather than rows. A runtime of specialist agents that reason across the whole of it. A governance engine that compiles your plain-English policy and enforces it. Each exists elsewhere on its own. Held together, they are what lets governance run rather than be applied by hand.

Is the AI just a chatbot?

No. Six specialist agents assess a risk in parallel across time, cost, quality, scope, benefits and reputation, and a consolidator merges their findings. Each one reasons over the whole dependency chain rather than an isolated row. Every consequential action routes to a named human approver.

Where does my data live?

The platform is built to run on Azure in European regions, so customer data stays within the GDPR perimeter, and each customer’s data is kept separate at every layer and encrypted in transit and at rest. Being precise about today: the platform is not live, so the only data we currently hold is your registration or a research report request, and those sit in Azure UK South. The privacy policy says so too.

Which systems do you connect to today?

Jira, SAP, SharePoint, Excel and Teams, all read-only. Nothing is migrated and nothing changes for your delivery teams.

Do you hold SOC 2 or ISO 27001?

Not yet, and we will not imply otherwise. Lunav runs on Azure, whose infrastructure is independently certified to both, which gives us a compliant foundation. Lunav’s own certification follows once the platform is in commercial operation.

How does the pilot work?

One governance problem, eight to twelve weeks, on one of your real projects. That spans at least two of your reporting cycles, which is what it takes to measure a real improvement rather than a demo effect. You end with a value case against your own baseline. Commercial terms are not yet settled and we will not quote figures we cannot stand behind.

When will Lunav be available?

It is a working proof of concept today and the first release is in development. Pilots are expected to open in the first quarter of 2027, and pilot partners get access before general availability. Europe is the first market.