Usage-based billing

Your Invoice Is Code Output, Not A Contract Line

When revenue is computed rather than agreed, a quiet defect in charge logic is a quiet defect in revenue. The uncomfortable part is that nobody will say a number out loud. Being wrong about revenue in front of finance is career-damaging, so the estimate stays vague and the problem stays funded at zero.

ShippedBilling correctness on a platform where charges were computed per transaction is work we have run, with dated evidence.

Read-only. Measurement and mutation are separate engagements.

What we will not claim
  • No percentage-of-recovery pricing. It makes every finding suspect, and the findings are the product.
  • No recovery figure promised before measuring. The number is the deliverable, not the pitch.
  • We do not apply a reprice ourselves as part of an assessment. Measurement and mutation are separate engagements with separate approvals.
  • Every correction we propose names the exact rows, shows the before-values, and stops. Applying it is your decision, per statement.
A reprice is a write to someone’s money. It should never be a side effect of an assessment.
Who this is for

Revenue That Is Computed

Usage-metered SaaS, per-shipment and per-transaction platforms, marketplaces taking a rate: anyone whose invoice is the output of code rather than of a contract line item. Typically post-product-market-fit, 10–60 engineers, and a finance function that has learned not to fully trust the number.

The invoice is wrong and the customer finds it first
Nothing costs trust faster, and nothing is harder to walk back once it has happened twice.
Charge logic that disagrees with itself
The same rate implemented in several places, drifting apart, with no mechanical way to enumerate them. That is the disease; a wrong invoice is the symptom.
A leak nobody has quantified
Everyone suspects under-billing somewhere. Nobody can put a number on it, so it never gets prioritised against features.
Nobody will say a number out loud
Being wrong about revenue in front of finance is career-damaging. So the estimate stays vague, and vague problems do not get funded.
Reprocessing fear
Even once the bug is found, re-billing correctly feels riskier than the original bug, and often is, if it is done as a bulk re-run.
How we work it

Measure, Then Decide, Then Fix

1

Billing correctness assessment: 2–4 weeks, fixed price, read-only

Where charge behaviour is defined, how many implementations exist, and where they disagree, with the exposure quantified and dated rather than characterised.

2

Reconciliation and leak quantification: read-only

What was under- or over-billed, for which period, on what evidence. A figure you can take to finance with its working attached.

3

Correctness work on the money path

Consolidation to one implementation, with a test suite that pins current behaviour first so the consolidation is provably behaviour-preserving before it is an improvement.

4

Continuous reconciliation

Retained, so the next drift is caught by a check rather than by a customer.

The question that opens every one of these engagements: “How many places would a change to how you charge have to be made?” Nobody knows. That is the finding.
How we work

Why You Can Trust The Number

We disclose leaks we caused

On a billing programme of ours, a recurring leak originated in our own earlier change. We disclosed it in writing, with the figure, while the fix was still in review. A billing review that only ever finds other people’s mistakes is a sales document.

Corrections are surgical, never bulk

A remediation names the exact affected rows and reprices exactly those. A bulk re-run is how a billing fix becomes a billing incident.

A figure we cannot explain is marked unexplained

Never smoothed, never rounded into a story. If the reconciliation has a residual we cannot account for, that residual is in the report.

The calibration basis is stated and dated

So you know what the number was true of, and when. Recalibration is a scheduled task rather than an assumption.

Related

Where This Leads

Talk to us

Ask The Uncomfortable Question

How many places would a change to how you charge have to be made? If the honest answer is that nobody knows, that is the finding, and it is what the assessment turns into a number.

  • Read-only: we do not write to your data
  • 2–4 weeks, fixed price
  • No percentage-of-recovery pricing
  • Corrections named row by row

Ask about billing assurance

We reply within one business day.

No spam. TechJoy will never share your information. We use your phone number only to reply.

Our fit rating for this market is Shipped, from the capability register we maintain internally. No client is named anywhere on this site. Figures from engagement work are quoted only with their measurement basis and date, and only where they sit on our internal claims register. Ask and we will show you the working. We publish no improvement or recovery percentage we have not measured.