synthmind

Billing says they stopped paying. Sales says they still get it. The app still lets them in.

A review list for your add-on: access to correct, decisions to make, evidence still missing. Every line shows the agreed rule and the source rows. No account is changed.

Send one disputed account 600 € a month · one add-on · up to 5,000 accounts · the first account is free

Illustrative example · the gold add-on, four accounts

Your policy, as we read it back to you: an account has the add-on while its subscription includes it, or while a written exception for it is in force.

Correct: access without entitlementnord-ab

access enabled access.csv line 40

subscription cancelled 2026-08-01 billing.csv line 131

no exception on file crm.csv read to its end

Not entitled under either half of the rule. The account has had the add-on for two months without paying for it.

Decide: the systems disagreeacme-co

billing: subscription cancelled 2026-09-30 billing.csv line 212

crm: subscription renewed 2026-10-01 crm.csv line 88

Two systems of record disagree about the subscription itself. Both rows are shown and nothing is picked. Someone with the authority decides, once, and the next run carries it.

Entitled by exceptionpine-ltd

subscription cancelled 2026-09-30 billing.csv line 9

written exception in force until 2026-12-31 crm.csv line 52

The second half of the rule holds. A lookup keyed on billing alone would have cut this customer off.

Not yet: evidence missingrook-oy

no billing row for this account billing.csv read to its end

crm: active crm.csv line 140

A blank is never read as "no". The line waits on the billing export and says so.

What you get back

CorrectionsAccounts with access they are not entitled to, and accounts entitled but switched off.

DecisionsAccounts where your systems disagree, with both values and their sources.

Missing evidenceAccounts a system has no row for, named as missing rather than guessed.

Every line carries the rule and the source rows needed to review it, down to the file and line, so the list reads like a bank statement: each line is something you can go and look at.
The rules we wrote, each beside the sentence of your policy it came from. When you change a sentence, you see exactly which accounts move.

Check it yourself

Nobody has to trust us, and nobody has to read the code. The list is built so whoever owns the add-on can check it.

Ten accounts at randomPick any ten lines. Open the export, go to the row, compare. A minute each, no help from us.

One planted faultBefore the first full batch we alter one row in a copy of your exports. The list names the account that moved, or says “not yet” and names the gap. We tell you which row afterwards. Alter one of your own as well and don’t tell us.

The same answer twiceSend the same three exports again and the list comes back byte for byte the same. Change one row and exactly the accounts that rest on it move, each shown with its old and new grounds.

A refusal you can seeA line that cannot be shown from the rows is refused and named, never printed. The example above has two: acme-co, where the systems disagree and nothing is picked, and rook-oy, which waits on a billing row.

How it runs

Once a month, or before a review, you upload three exports: billing, CRM, application access. Account ids only, no payment details. You tell us once which column means what; we keep the mapping. The list comes back the same working day after we accept the files; files accepted before 12:00 CET count for that day.

Price

600 € a month

One add-on. One batch a month, up to 5,000 accounts. Policy setup and one corrected re-run included. Invoiced monthly from your first batch, cancel any month. The first disputed account is free, so you see your own line before you pay anything. If your exports cannot support the review, we say so and nothing is charged.

Not included: connectors, proration, tax, refunds, changes to anyone's access, or interpreting a bespoke contract.

What the list establishes

That each line follows from the agreed rule and the rows you supplied, and that a separate checker confirmed it from the rows. It does not establish that your exports are complete or that a source is right. The list is built so you can check those yourself: every line names its rows, and every gap says what is missing.

Who runs it

Harri Sarsa, Sarsa Formation OÜ, Tallinn. One person reads your policy, writes the rules you approve, runs each batch and keeps your column mapping. Before this: chief product officer at AppGyver, acquired by SAP in 2021, and at ASILAB.

The list is one run of synthmind, a reasoning engine whose every answer carries the rows it rests on and whose checker is separate from the part that computes. No language model is involved anywhere in it.

Start

Send Harri Sarsa one disputed account and the exports it appears in. You get its line back, with the grounds, the same working day. No charge.

hello@muoto.xyz