ОБ ЭТОМ ЭПИЗОДЕ
From the earliest days of DataMasque, Grant de Leeuw made a deliberate choice - this would not be a lightweight SaaS tool chasing fast adoption. The company was built to serve large, regulated enterprises where data privacy, security, and usability collide.
Grant framed the problem clearly. Enterprises need to use real customer data internally for development, testing, analytics, and increasingly AI. But regulation and security controls make that data difficult to use safely.
“Organizations need to leverage their customer data for their own internal purposes… but because of the regulation and security privacy around some of their most important data, they actually really struggle to leverage it internally.”
DataMasque was created to solve that tension by enabling what Grant calls high-fidelity synthetic data - data that is de-identified, but still behaves exactly like production data across systems.
Inside Partnering is a reader-supported publication. To receive new posts and support my work, consider becoming a free or paid subscriber.
Why Usability Matters More Than Perfect Security
A recurring theme in the conversation was that many existing solutions over-index on security at the expense of usefulness. According to Grant, that tradeoff creates downstream problems.
“While they will remove the sensitivity of the data, they’re actually effectively trashing the usability.”
Engineering and product teams need messy, imperfect data to test real-world edge cases. When lower environments are populated with overly clean or unrealistic data, systems often pass through test and QA, but fail in production.
“The messiness of production has to be replicated into these lower environments… otherwise you roll it into production and everything breaks.”
DataMasque’s approach focuses on masking at the field level while preserving relationships across systems, ensuring consistency even in complex, multi-application environments.
The Hidden Risk of Non-Production Environments
Grant highlighted a risk that many organizations underestimate - the size and exposure of non-production data.
“Seventy to eighty percent of an organization’s data footprint can be non-production.”
These environments often have weaker governance and broader access, making them a frequent source of breaches. For DataMasque, this reinforced the need to secure data where it is most widely used, not just where it originates.
Choosing AWS Marketplace as a Core GTM Strategy
Based in New Zealand, DataMasque faced a structural challenge. Their ideal customers were global enterprises, but building a traditional overseas sales presence was cost-prohibitive.
AWS Marketplace became the answer - initially almost by accident.
“I came out of the meeting going, I assume this is what everyone’s buying off Marketplace.”
The early days were slow, but momentum built through a combination of co-build, co-marketing, and co-selling motions. A customer case study and an AWS-authored blog post marked the inflection point.
“Suddenly it was like we had the co-build, then the co-marketing started to happen… and the flywheel started to turn.”
Marketplace enabled DataMasque to transact globally without a US entity or local bank accounts, dramatically lowering the cost of international expansion.
“We could actually do this all from here and done it in an extremely cost effective manner.”
