Stage 1 of 5 · Baseline

Establish what is true.

What is actually true about our technology environment?

Most technology environments are not badly run. They are badly recorded. Facts live in different systems, agreements live in folders, and the person who knew the vendor relationship has moved on. The Technology Baseline replaces that with one evidence-backed record of what you actually have, what you are paying, and what nobody can currently prove.

Technology baseline assessment

One record, built from the documents.

The Baseline is assembled from your source material: invoices, agreements, inventories and whatever else describes the estate. Atlas reads it and will not assert what a source leaves ambiguous. Wimbl works out what should exist against what is recorded and keeps the difference visible.

Locations and providers

Every site in scope, and who actually serves it. Not the list someone maintained, the one the documents support.

Services and assets

What is running, where, and what it supports, tied to the location and the agreement that pays for it.

Contracts and obligations

Terms, dates, notice windows and commitments, extracted from the agreements themselves rather than remembered.

Spend

What is actually being paid, reconciled against what was agreed, with the difference visible where there is one.

Supporting documentation

The source behind each line, attached to it, so a figure can be checked instead of trusted.

Gaps and inconsistencies

What is missing, what conflicts, and what is only assumed. Named, not quietly filled in.

The NGX Evidence Standard

A baseline that hides what is unknown is not a baseline.

Every fact carries a grade. The value of the record is not that everything in it is certain, it is that you can see which parts are and act accordingly.

Verified. Evidence directly supports the record.
Supported. Several signals make the record credible, but it has not reached Verified.
Assumed. Believed to be true, without evidence sufficient to support it.
Missing. Information the record needs is absent.
Conflicting. The available evidence disagrees with itself.

How the Evidence Standard works

For IT leadership, the grades are the part that matters: they are what turns an estate you can describe into an estate you can sequence work against. The reading and reconciling behind them is done bynamed AI workers, each with a stated limit.

How a Baseline is scoped

Sized to the environment, not to a seat count.

Scope follows the number of locations in play and how complicated the environment is: how many providers, how tangled the agreements are, and how much of it has ever been written down. Three ways it is engaged:

A paid standalone engagement

The Baseline stands on its own. Plenty of organizations need a defensible view of their environment before they decide anything else, and that is a complete piece of work.

Included with qualifying annual engagements

A Technology Baseline is included with qualifying NarrowGateX engagements of twelve months or more, because the relationship cannot run correctly without one underneath it.

Included with qualifying advisory and execution work

Where an advisory or execution engagement needs the record to be done properly, the Baseline is included as the foundational work rather than billed as a prerequisite.

Platform subscription pricing is published and scales by managed location.See pricing.

Getting started

The first conversation does not need the whole estate.

Two invoices and a contract are enough to begin. We will show you what can be verified from them, what cannot, and what that already tells you about the rest.

See a sample Technology Baseline

The cycle

Govern keeps the Baseline current, and the cycle starts again.

← Govern Benchmark →

Start with the Baseline.

Establish a defensible view of your technology environment and find out what it supports, what it costs, and what is not yet evidenced.

Start a Technology Baseline See the whole model