in production

Atlas Desk

A telecom bill, read the way a person would read it, if a person had the afternoon.

Built during my internship at UTR Global and running there now. You drop in a carrier bill or a spreadsheet and work on it in plain English: audit the charges, reconcile the lines against what the company actually owns, check the rates against the contract, compare one month to the last.

The part I care about is that it shows its work. It does not hand back a number and ask to be trusted. It lists what it checked, what it found, what it expected instead, and where the two do not tie out.

Where: UTR Global, in production
Built with: Electron and TypeScript, with Claude doing the reading
Reported: UTR Global says it has saved a client over $12,000 a year
On this page: A run against a synthetic test workbook. No client data.

Atlas Desk on open, with three suggested checks and a 1,378-row workbook loaded beside them — The workbook goes in whole, all 1,378 rows of charge detail. The three cards are the jobs people actually open it to do.

The finished audit: summary figures, a tie-out warning and a variance table beside the workbook — The audit, finished, next to the bill it came from. Nothing moves the reader away from the source document.

A list headed "What was checked" with twelve categories and counts for each — What it checked, with counts, before it says what it found. Twelve passes over the same bill: the tie-out, rates against the plan catalog, duplicates, idle lines, people who have left, suspended lines, unused add-ons, equipment, orphan numbers, cramming, tax and usage.

A warning that the front page does not tie to the detail, with both totals and the unexplained difference — The first thing it says is whether the bill adds up to itself. Here the front page claims $13,423.92 and the itemised detail comes to $12,076.02.

A finding opened up: three lines billed for data overage, each with charged, expected and delta — Open a finding and you get the lines behind it, with what was charged, what should have been, and the gap. This one is data overage billed while the shared pool still had room.

Four summary tiles: credit-eligible per month, per year, fix-ourselves per month, and 129 findings — The totals, split by what you can claim back and what you have to go fix yourself. On this test workbook, 129 findings.

The screens here show a run against a synthetic test workbook: 1,378 rows in, 129 findings out, $9,670.68 a year of them. No client data appears on this site.