Newsroom
Notes from the platform.
How we think about billing, agents, and the finance back office — not launch theatre. Organised by who is writing: the founder, engineering, the product team, and the field.
From the founder
Why the chain is built this way, in plain sentences.
Why we don't have a logo wall
We don't have named customers to publish yet. Here is what we do instead of inventing them.
Contract-to-cash is a chain, not a feature list
Why Sonic is built as one data model from the agreement to the journal — and why stitching five tools is the actual competitor.
Bring a real contract. We mean it.
The best demo we ever ran was on a customer's messiest carrier file. Here is why a slide deck is the wrong way to evaluate a billing system.
Engineering notes
How the platform actually works, for the people who will ask hard questions.
Idempotency is a product feature, not a database detail
Why every usage row, seat snapshot, and bank statement line in Sonic carries an explicit identity — and what happens when a file gets uploaded twice.
Billed is not recognised
The waterfall is the story. The journal is the books. Freight recognises on the shipment date.
Rate index branches, without silent fallback
Default is the series. A branch is a complete table for listed carriers. A gap is a gap.
Product playbook
How to run billing, collections, and revenue on Sonic in practice.
Shipment billing is not a monthly schedule
Freight bills movements. Sonic rates each haul from the carrier contract, the mapping, and the index branch that belongs to that carrier.
Choosing between subscription mode and shipment mode
The same platform bills two different grains. Here is the decision, in one page, before you set up a single catalog.
Migrating off spreadsheet billing without a big-bang cutover
A practical order of operations for moving from a workbook to a live schedule — catalog first, one cohort at a time, old and new running in parallel until they agree.
Field notes
What finance teams hit in the wild, before the spreadsheet becomes a risk.
The Monday morning reconciliation problem
A deposit lands. Nobody matches it. Collections keeps chasing a customer who already paid. Here is why bank rec is the off switch collections cannot find on its own.
Two systems, one truth: connecting payments and the ledger
Stripe or Razorpay collects the cash. Your ERP owns the books. Here's what has to be true for the middle to not become its own source of error.
What a signed PDF actually contains
A contract is not a form. It is prose with an operative price buried in clause 14(b), a renewal that changes the fee, and a deferred instalment nobody flagged. Here's what reading one for billing actually requires.