Healthcare risk and compliance isn’t a market where you get second chances. In this episode of Margins & Mandates, Jeff sits down with Ed Gaudet, founder and CEO of Censinet, a healthcare-focused governance, risk, and compliance platform that started in third-party risk management and expanded into enterprise risk and compliance.
Ed shares what it really means to go “all-in” on healthcare—not as a vertical, but as a commitment. The conversation covers early capital raises, building v1 through a design partner program, navigating March 2020, and the operating rhythm that turned weekly customer conversations into a competitive advantage.
Healthcare risk and compliance: why “all-in” is different from “serving a vertical”
Most software companies treat healthcare as a vertical—one segment among many. Ed’s view is different: going all-in on healthcare means accepting a different standard of accountability, a different buyer psychology, and a different set of consequences when things go wrong.
In healthcare risk and compliance, the stakes include:
- patient safety and data privacy,
- regulatory exposure (HIPAA, HITECH, and beyond),
- reputational risk for health systems,
- and third-party ecosystem vulnerabilities that can cascade across the entire network.
That’s not a vertical. That’s a zero-tolerance environment. And it requires a company that’s built differently—from product architecture to customer success to go-to-market motion.
Building a multi-sided network in a zero-tolerance market
One of the most interesting structural choices Censinet made was building a multi-sided network that connects health systems with their ecosystem of third parties.
That decision has compounding effects:
- health systems get a cleaner view of their risk exposure,
- vendors get a more efficient way to demonstrate compliance,
- and the platform gets stronger as more participants join.
In healthcare risk and compliance, this network structure creates a real moat. It’s not just a SaaS tool—it’s a shared infrastructure for managing trust across a complex ecosystem. That’s hard to replicate and hard to replace once embedded.
Raising capital with an idea: the early days of Censinet
Ed walks through what it looked like to raise capital before there was a product—just a thesis, a market insight, and a design partner program that would eventually become v1.
The design partner approach is worth examining for any founder in a complex regulated market:
- it forces early specificity about what you’re actually building,
- it creates real accountability to a customer’s workflow,
- it generates the kind of evidence that makes future investors and buyers confident,
- and it ensures your first version solves a real problem, not a hypothetical one.
For operators building in healthcare risk and compliance (or any zero-tolerance category), the design partner program isn’t just a nice-to-have. It’s a forcing function for discipline.
Launching into March 2020: disruption as a growth phase
Censinet launched into the pandemic. Ed’s candid about what that meant: a market that was simultaneously more stressed, more exposed, and more open to solutions that addressed real risk.
The post-pandemic aftershocks were equally formative. Health systems that had accelerated digital transformation now had expanded attack surfaces, new third-party relationships, and compliance complexity they hadn’t anticipated.
For Censinet, each disruption became a growth phase—not because the company got lucky, but because the product was built for exactly the moments when healthcare risk and compliance pressure peaks.
The strategic pivot: investing in product and biweekly releases
After navigating early disruption, Ed made a deliberate choice: invest in product velocity. The result was a near-biweekly release cadence—an unusual operating rhythm in a highly regulated market.
That cadence only works with:
- strong internal transparency (teams know what’s shipping and why),
- weekly customer conversations (so priorities stay grounded in real needs),
- and a product architecture that can move fast without breaking compliance requirements.
Ed’s view is that in healthcare risk and compliance, speed and safety aren’t opposites. The companies that win are the ones that figure out how to ship fast while staying secure by design.
PE playbooks: filling a leadership void while constraining success
One of the most candid moments in the episode is Ed’s take on private equity playbooks.
PE can fill a real leadership void—especially in growth-stage companies that need operating discipline, financial structure, and go-to-market infrastructure they haven’t built yet. But PE playbooks can also constrain the definition of success: optimizing for outcomes that look good on a timeline rather than ones that build a durable business.
For founders navigating PE relationships, the key is knowing which parts of the playbook to adopt and which parts to push back on—so the business retains its identity in a zero-tolerance market while still accessing the capital and structure PE can provide.
Censinet’s AI approach: secure by design, secure by default
The episode closes with a look at how Censinet is approaching AI—and it’s a model worth paying attention to.
Rather than adding AI features on top of an existing platform, Censinet architected AI into the product from the ground up: secure by design, secure by default, with customers choosing when to enable specific capabilities.
Internally, there’s a mandate for teams to adopt AI in their daily workflows—not as a pilot, but as a standard expectation.
In healthcare risk and compliance, that approach matters. Customers need to trust not just the output, but the architecture. Security and privacy aren’t optional—they’re table stakes. And building AI that respects those constraints from the start is a meaningful differentiator.
Key takeaways for founders and operators in regulated markets
If you’re building in healthcare or any zero-tolerance market, here are the takeaways from this episode:
- Go “all-in” on the market—not just as a segment, but as a commitment.
- Build multi-sided networks where the ecosystem creates compounding value.
- Use design partners to create discipline and evidence before you scale.
- Treat disruption as a growth phase, not just a risk event.
- Adopt PE discipline selectively—and protect the definition of success.
- Architect AI in from the start: secure by design, secure by default.
Ed Gaudet on LinkedIn:
Censinet
Follow Agile Operator newsletter
