How it works

See the finding before you connect anything.

Start with a synthetic example. If the problem is real for you, repeat the same process with one period of your own aggregate data.

Try it without your data

A synthetic example shows how provider cost missing from usage records can reverse the margin conclusion.

Try the example

Inspect before connecting

The CLI previews every statement before opening a connection or reading a credential.

Aggregate inside your environment

The read-only CLI reduces usage to customer-level totals before producing the evidence bundle. Raw rows, prompts and responses are excluded.

Add the business terms locally

Revenue, contract type, target margin and the provider statement are processed in the browser and are not retained.

Confirm what belongs together

NemulAI proposes exact and normalized customer matches. Ambiguous records remain unresolved until a person confirms them.

Reconcile the whole provider bill

Assigned cost, unmatched usage cost and provider cost absent from usage records must account for the statement. Missing amounts are never silently assigned.

Receive the finding

The result states which customer economics are defensible, which require a decision and what the evidence cannot determine.

Start with the example.

Try with synthetic data Read the CLI guide