"We really like ReactWise. But we can't go ahead." That was the outcome of a call a few months ago, and it was the most useful feedback we've had.

"We really like ReactWise. But we can't go ahead." That was the outcome of a call a few months ago, and it was the most useful feedback we've had.

The problem wasn't the science. They'd looked at the platform and liked it. Their data simply could not sit on infrastructure they didn't control, and no amount of certification was going to change that.

We had just finished ISO 27001 and SOC 2 Type II, so I had answers ready about encryption, access control, audit trails, and data residency.

None of it was relevant. This wasn't a concern about whether we were secure. It was a policy that predated us, applies to every vendor, and isn't negotiated.

That was the useful part. It taught me the difference between an objection and a constraint. 

An objection is something you can address with better information. A constraint is a boundary in someone's world, and your choice is to build for it or walk away.

So we built for it.

Since then, we've built a full on-premise deployment of @ReactWise to the client’s own cloud environment  alongside the SaaS platform hosted version in our AWS environment. Same platform, same capabilities, running wherever your data is allowed to live.

The lesson I keep relearning: when someone tells you why they can't buy, the temptation is to argue. It's usually more useful to listen.

‍