The Mechanic Who Sells You the Car

What happens when a product is designed to solve a problem, but the company selling it also profits from that problem persisting?

Think about it like a mechanic who also sells you the car. If the car never breaks, the shop goes quiet. So the mechanic doesn't sell you the most reliable car on the lot — they sell you the one that runs well enough to drive home happy but keeps you coming back for service. The car's not bad. It's just not as good as it could be. And it never will be, because making it better works against the business that sold it to you.

Now apply that to compliance software.

The software doesn't need to be as good as it could be. It just needs to be better than the next option. Once it clears that bar, every additional improvement is a threat to the service revenue sitting next to it. So the product roadmap finds a natural ceiling — not set by what's technically possible, but by what's financially safe.

That ceiling holds as long as every option in the market has the same conflict. The bar stays where it is because nobody has a reason to raise it.

So what happens when someone enters a market whose only business is making the product as capable as it can possibly be? Every improvement they ship raises the bar — and everyone else has to choose between matching it or protecting their margins.

Now imagine the same mechanic doesn't post prices. What you pay for the car depends on which door you walked through, who referred you, and how much they think you can afford. There's no sticker on the windshield. No standard rate card. The same car, at the same dealership, costs different amounts depending on who's buying it.

What does that do to trust?

In most industries, when you buy something, you know what it costs. The price is on the website, or on the quote, or on the sticker. You can comparison shop. You can budget.

What happens when a product doesn't have a published price? When distributors and resellers set their own margins and there's no standard rate card? What does the buyer experience look like when the same product, at the same type of facility, costs different amounts depending on who's selling it?

Maybe the answer is: the market sorts it out, and everyone gets a fair deal. Maybe.

But in an industry where the stakes are 50,000 pounds of anhydrous ammonia and the health of every person in that building — is "maybe" good enough? Is opacity in pricing acceptable when the product exists to protect people?

At iPSM, we made a few decisions before we wrote a single line of code.

We will never sell consulting services. Not because consultants aren't valuable — they are. But because the moment we start billing hours for compliance work, we've created our own ceiling. Our only job is to make the software as good as it can possibly be. No second revenue stream to protect. No reason to stop improving.

We will never allow opaque pricing. If a partner distributes iPSM, their customers will know what iPSM costs. There is no mystery markup. No variable margin that depends on the relationship. The price is the price.

We will never build a system designed to keep you dependent. If you leave iPSM, your compliance documentation is yours. Your data is yours. We don't hold your PSM program hostage because we're afraid you'll realize you can manage it yourself.

What that commitment produces over time is a different kind of relationship between a facility and its compliance software. One where the software gets better because making you more capable is the business model, not a threat to it. Where you stay because the product earns it, not because leaving is painful. Where every update is designed to give you more control, not less.

Would your compliance software vendor publish their full pricing — every tier, every add-on, every partner margin?

Would they build software designed to make their own consulting services unnecessary?

Would they make it easy for you to leave and take your data with you?