> Matt and I came to this project after we built similar internal billing systems at previous jobs and we realized how error-prone these systems can be—one incident might have even undercharged a client by a few million dollars!
This honestly doesn't lend me the confidence in your solution that I assume you think it does ;P. "We've done this before, and dude... we failed at it SO BAD, you just don't understand: this is HARD. So, instead of doing it yourself, you'd be much better off out-sourcing that effort... to us." :( It is a subtle difference, I admit, between versions of this pitch that work and the ones that don't, but this one just didn't work for me.
I edited that sentence when I was helping these guys with their text and it's possible I introduced a misleading connotation. The way I understood what they originally wrote is that they had observed such a billing lapse inside some organization, but not that they were responsible for it.
On the other hand, even if so, there's the classic proverb about 'expensive training' etc...
Yeah to add more color to this, we just observed the failure of a process and system we weren't a part of. Basically there were manual elements in the billing and aggregation of usage data on a SaaS platform and those were forgotten about over the course of many months which lead to the company under billing.
This honestly doesn't lend me the confidence in your solution that I assume you think it does ;P. "We've done this before, and dude... we failed at it SO BAD, you just don't understand: this is HARD. So, instead of doing it yourself, you'd be much better off out-sourcing that effort... to us." :( It is a subtle difference, I admit, between versions of this pitch that work and the ones that don't, but this one just didn't work for me.