Telecom

Revenue assurance exists because the volume defeated inspection.

Service delivered against service rated. Rated against billed. Billed against collected. Your interconnect traffic against theirs. Each is two records that ought to agree, over a stream too long to read — which is why the work was built on samples.

Where the decision happens

Records you already keepSpread across the systems you already run.
One finding, with its evidenceDrawn together into a single proposed action.
A person approves itBy name, and nothing goes out before they do.
The work goes outAnd the reason stays on the record.

Where it goes wrong

A rating change right for the promotion, wrong for a legacy plan

The affected population is small. It moves no monthly aggregate, fires no threshold, and rarely turns up in a sample.
A sample gives you a rate, not a name

A monthly sweep produces an estimated error rate. To fix anything, operations needs the affected accounts individually.
Two parties, one stream of traffic

Traffic as you recorded it, as the counterparty recorded it, and the agreement that sets the rates. Three sources, one difference that matters.
Rollout across many small sites

Site builds and equipment purchases follow the plan, approve, procure, spend sequence of any capital programme — spread over many small sites, which makes sampling worse.

Who owns this

One function in telecom already does this work by hand. The rest inherit the same shape.

Revenue assurance

The comparison runs at the transaction, not as a monthly sweep, so the remedy is a configuration correction and a re-rate.
Interconnect and partner settlement

Both parties' records of the same traffic, read against the agreement that sets the rates, continuously rather than at period end.
Finance and procurement

"Where is our risk concentrated across plan to books?" has an answer that updates rather than one that gets compiled.
Compliance and data protection

Rules about subscriber data are applied to the flows, and the evidence that they operated is written as the work happens.
Engineering and IT

Reasoning runs on your own hardware; records and credentials stay on your systems.

What changes

The population tested is the population, so exceptions come back as named accounts, not an estimated rate.
Each item carries the observation, the rule it invoked, the records it cited, a severity and a proposed action.
The queue is sorted by impact and by how confident an independent assessment is, so the first hour goes to what is material and clear.
That assessment can decline: unable to judge is recorded as unable to judge, never as agreement, and goes to a person.

How you will know it worked

The figures below are yours, not ours. Write down where you stand today, before anything changes — a baseline stops being recoverable once things start improving.

The measure	Your figure today	What moves it
Rating accuracy, and the usage it under-bills	The rating error rate revenue assurance reports upward, and the sample size and month behind it. Then a month of mediated usage against what billing charged.	It stops being an estimate: each account's rated output is read against its own plan terms, so under-rated usage arrives as named accounts a re-rate can still fix.
Credit notes and billing disputes — volume, value, days to resolve	Credit notes raised against billing errors over the last four quarters, from the billing ledger, with opened and closed dates.	Volume down, because the error is caught before the invoice goes out. Days to resolve down, because each item carries the records it came from. Billing-dispute churn follows.
Interconnect and wholesale settlement differences	Your last settlement cycle with each major counterparty: value in dispute, open items, age of the oldest.	Fewer reach dispute, and those that do age less, because your traffic, the counterparty's and the agreed rates are read against each other while both sides still hold the detail.
Capital committed against equipment in service	For the current rollout programme: approved spend, purchase orders, equipment received and sites carrying traffic, side by side. If that view takes a week to assemble, the lag is part of the measure.	The gap narrows, because equipment at a site that was never turned up shows as an exception the day the records disagree. Order-to-activation becomes a standing figure.
Time from a control failing to somebody knowing	Your last few rating, provisioning or settlement incidents: the date the fault began against the date someone was told.	Down — and it governs the rest, since each of them depends on how long a wrong rule ran unnoticed. Comparisons run as the traffic arrives, so the interval is set by the process, not the reporting calendar.

Two things that make the above possible

Your records stay on machines you own

The reasoning runs on hardware you own. Subscriber records, usage detail, contracts and credentials are read where they already live. Nothing goes to an outside model provider.

What you would notice

Call-detail and subscriber data sits under telecoms privacy and interception law and mostly cannot leave your estate. Measure this as the length of the security review before work can begin, and as whether a regulator's question about who saw what is answered from a record rather than an investigation.
Research on the open web that nobody sees you doing

When something has to be checked in public — a competitor's tariff, a supplier, a regulator's notice — the system reads the web itself, with its own browser. No outside search company sits in the middle.

What you would notice

The question is often more sensitive than the answer: researching a rival's bundle pricing through an outside search vendor tells that vendor what you are about to launch. Measure it by what your commercial team is willing to check at all.

Who you would be working with

Runink is founder-led. The person in the first meeting is the person who designed the thing being discussed.

Dan Paes

Chief executive and technical founder

Dan Paes has spent more than twenty years inside other people's enterprises, running digital transformation and full-scale modernisation programmes for global organisations. The long kind: what is being replaced is what the business is running on that morning, and the work is judged on whether anything broke.

He founded Runink and runs it as chief executive. Technical founder is the more useful half of that title — he sets the architecture and works in the code, so the person answering an architecture question in a first meeting is the person who decided the answer, and the distance between a question and a change is short.

It is also why the platform is shaped the way it is. It runs on hardware the customer controls, and the reasoning about their data stays there. That is the more expensive way to build it and it closes off the convenient route, which is the kind of decision that has to be settled by whoever owns the architecture rather than left where it can quietly be traded away.

He is a FINOS Ambassador. FINOS is the Fintech Open Source Foundation, part of the Linux Foundation, and the work there is interoperability between institutions that share a market but not their infrastructure and never their data. It is the same problem this platform is pointed at, argued in the open, in front of people who say so when it is wrong.

20+ years

Digital transformation and full-scale modernisation for global enterprises.
CEO and technical founder

Runink. Sets the architecture and writes code in it.
FINOS Ambassador

Fintech Open Source Foundation, a Linux Foundation project. Open source interoperability, in public.

Check any of it

See whether it fits

Bring one comparison and the agreement that governs it — rating output against plan terms, or a month of interconnect traffic against the settlement. Half an hour is usually enough to see whether the differences that matter are the shape this finds. Bring today's figures for the measures above too; they are your baseline.

Book a consultation Read the CORE paper

The long version: what gets read, what a finding contains, how a second independent judgement is formed, and who approves.

Where the decision happens

Where it goes wrong

A rating change right for the promotion, wrong for a legacy plan

A sample gives you a rate, not a name

Two parties, one stream of traffic

Rollout across many small sites