When we tell people HorizonStack is priced on outcomes, the first question is always the same: what happens when the job does not close? The answer is simple. There is nothing to invoice.
We made that choice deliberately. Usage-based pricing rewards vendors for activity — more calls, more messages, more tokens burned. But activity is not the thing our customers want. They want the renewal bound, the claim paid, the account reactivated. Charging for effort quietly misaligns us with that goal.
If we only get paid when the job closes, then every decision we make points at closing it.
What it changes internally
Outcome pricing is a forcing function. It means we care as much about the ninth follow-up as the first, because an abandoned job is pure cost to us. It means we invest in knowing when to escalate to a human, because a stalled job helps no one. And it means our roadmap is driven by close rate, not by engagement metrics.
It is a harder business to run. It is also the only model we could look our customers in the eye and defend.