Dab Media LLC
One person who has cleaned up enough of these.
Murphy is a one man show. You should know that before you give it a read key, so it is on this page rather than three conversations in.
I have spent most of my career on billing systems at companies somewhere between three and two hundred and fifty million in revenue. Different stacks, the same job: the pricing changes, the migration runs, and six weeks later somebody notices a number that has been wrong the whole time.
I am not naming those companies. Their incidents are not mine to publish and their logos are not mine to borrow, so the catalog describes mechanisms and never accounts. If a failure in it reads like it was written from the inside, that is because it was, and that is as much as I will say about whose inside.
What all of them had in common is that the billing bug never announced itself. It was found by a spreadsheet, by a customer, or by nobody. In every case the information needed to catch it on day one was sitting in the billing provider, unread, because nothing was reading it.
Murphy is that reader. It is small on purpose: it does not run your billing, it does not write to it, and it does not want to be a platform. It re-derives what your invoices should have said and tells you when that disagrees with what you charged.
What one person means for you
- You get me on support, not a tier. The person who wrote the check is the person who answers when it misfires.
- Murphy holds a copy of your billing objects, so how that is held and what happens if I stop is written down rather than implied.
- The roadmap is short and the catalog is long. New checks come from failures somebody actually hit, including yours.
Talk to me directly
If you are weighing this up, the fastest useful conversation is you describing your billing and me telling you which parts of it Murphy would have something to say about, including the parts where the answer is nothing.
Talk to us