Platform
What you pay, what you signed, what exists.
Reconciled per operating company, in its own currency, from files. Cost per megabit delivered is step two, once monitoring is connected.
Request a pilot
Each capability in one paragraph
Inventory
One list of every telecom service the group pays for, across every operating company, with entity, currency, cost centre and circuit role as real columns. Every field carries its source, a conflict stays visible until a person settles it, and carrier confirmation lets each carrier check what you hold for it.
Bills
Carrier invoices turned into lines with their own service periods, checked arithmetically and against the contract, with every conversion naming the rate it used. CSV, XLSX and PDF extraction are built and e-invoicing XML is planned; anything uncertain opens a review item, and a bundle is split to its member services once.
Bandwidth
Step two of the join. Hourly and daily utilisation read from the monitoring system you already run, over one read-level key, with the coverage of every bucket beside its number. PRTG is in progress and the others are planned.
MACD
Moves, adds, changes and disconnects run as one internal workflow: request, group IT review, budget check, procurement and the carrier handoff, then install tracking on its own clock. The handoff reference and the acknowledgement are kept as evidence.
Group view
Spend rolled up through service, site, carrier account, operating company and group, in each entity's functional currency and the group's presentation currency, with budgets against actuals, the cost-flow and estate-map dashboards, and an assistant that answers over your own data.
Security
Isolation at the operating company, enforced in the route, the server action and the database. SSO over OIDC and SAML, SCIM provisioning, MFA and country-scoped grants, with an append-only audit trail, and every certification is named the day an audit backs it.
Inside the six
Each is built today, and each is a section on the capability page it links to.
Contracts and pricing
Price lines per service, site and country, amendments, linked documents, and notice deadlines with alerts. A line billed above or below contract, before go-live, or for a service never delivered opens a finding.
Findings and disputes
Billed but not in the inventory, in the inventory but not billed, outside a contract or its term, no order reference. A dispute is recorded with its evidence attached, ready to raise with the carrier.
Bundles
A managed package priced as one charge, split to its member services so each is costed and none is counted twice.
Carrier confirmation
Send a carrier what you hold for it as CSV or XLSX, by email. Its answers come back as evidence field by field, and each carrier shows a confirmed share.
Budgets
Budgets against actuals per operating company, and a budget check on every order before it reaches procurement.
Group dashboards
The cost flow from group to operating company to carrier, and the estate on a map, in the group's presentation currency.
Identity
SSO over OIDC and SAML, SCIM provisioning, MFA, grants scoped to a country, and an append-only audit trail.
The assistant
Answers questions over your own data, with your own permissions. It runs on your organisation's own AI key.
One join, in two steps
Step one needs only files. Inventory names the service, bills say what it costs, contracts say what was signed, and MACD records every change made to it; reconciled per operating company, they show what is billed but not held, held but not billed, and priced outside its contract. Step two needs your monitoring system: bandwidth measures what was delivered, and the group view compares the same delivered megabit across operating companies. Until then, cost per megabit subscribed works from bills.
How a month runs through the platform
The join described above, in the order it happens each month: files first, then the monitoring system.
- Invoices landEach carrier's invoice for the month arrives as a file and is stored as raw bytes. The bills capability parses it into lines, checks the arithmetic and opens a review item for anything it is unsure of.
- Lines meet inventory and contractEvery line is matched to a service on the spine and priced against its contract. Billed but not held, held but not billed, and priced outside the contract each open a finding, per operating company, in its own currency.
- Utilisation is readStep two. Once your monitoring system is connected, the bandwidth capability reads the month's hourly and daily aggregates and records the coverage of each bucket beside its figure.
- The month is fixedThe group view stores one cost fact per service for the month, freezes the presentation rate onto the roll-up, and publishes cost per megabit subscribed at every scope; with utilisation joined, cost per megabit delivered sits beside it.
Questions about the platform
What does day one need?
Files. The inventory comes first, because everything else joins to it, and bills and contracts follow the moment the first invoices land. Bandwidth needs a read-level key from your network team, MACD needs a process to record, and the group view lights up as soon as two operating companies hold services. Each page carries its own status labels.
What does the platform read from our systems?
Invoice files in whatever form the carrier sends them, one read-level key to your monitoring system, and whatever inventory sources you already hold: portals, contracts, the CMDB, router configs. Every read is outbound from us to your systems' own APIs, and your network stays as your team built it.
How do the capabilities stay consistent with each other?
They share one spine and one vocabulary. A service has one row in the inventory, and a bill line, a monitored interface, a change request and a group figure all point at it. One metric definition, versioned, is used everywhere cost per megabit delivered appears.
Which capability should a pilot start with?
Inventory and bills, from three invoices. That is enough to produce a figure the group can check line by line, and the review queue shows you the machinery at work before any utilisation is joined.
