DICERRA.

Dicerra came to us in a familiar shape: a real product, real founders, and a codebase that couldn't carry the company where it needed to go.

The infrastructure was a single-server architecture — fine for a prototype, wrong for a platform that wanted to sit inside hospitals. The product was built for B2C — individual healthcare professionals reporting incidents anonymously — when the actual buyer was a hospital. And the road ahead included SOC 2, healthcare procurement cycles, and infrastructure assumptions a single server was never going to satisfy.

Same problem we'd seen before. Different domain.

Rebuilt the infrastructure for scale and compliance

Migrated from single-server to a high-availability Kubernetes architecture. The kind of foundation a hospital procurement team will actually sign off on.

Took the platform through SOC 2

Healthcare buyers need the certification before the conversation gets serious. We worked through SOC 2 implementation alongside the founders — controls, documentation, evidence, audit prep.

Helped pivot from B2C to B2B

Anonymous reporting is the core. But the buyer is the hospital, not the individual nurse or pilot. We rebuilt the product surface to match — admin views, hospital-level analytics, deployment patterns that fit institutional rollouts.

Learned the domain

Healthcare safety reporting has real depth. Just-culture principles. Non-punitive frameworks. The difference between a near-miss and an incident. The institutional politics of who sees what data. We spent the time to understand it — because you can't build a tool for hospitals without it.

Stepped into the CPO seat

Our founder took on the Chief Product Officer role at Dicerra. Not as an advisor. As the person responsible for the product roadmap and the decisions behind it.

Invested our own money

We put capital into the company. Not because the deck was good — because we'd been working alongside the founders for long enough to know what they were building and how seriously they meant it.

Dicerra is in active paid pilots in two Canadian hospitals. The platform is SOC 2 compliant. The architecture scales. The product is shaped for the buyer it actually has.

And the platform itself keeps evolving. We've integrated AI into the safety reporting workflows — turning unstructured incident narratives into pattern data the system can actually act on, surfacing trends across reports that would have stayed buried in free text, and giving hospital safety leads the kind of insight that makes the platform genuinely useful at the institutional level.

Anonymous reporting is still the foundation. AI is what makes the data underneath it valuable.

We're still in the codebase, still in the leadership conversations, still part of where it goes next.

A vendor delivers what's on the statement of work and moves on. A partner stays long enough to pivot the model, learn the domain, take operational responsibility, and put their own capital on the line.

We're not a dev shop. We're the people the founders call when the codebase needs rebuilding, when the model needs rethinking, and when SOC 2 needs to actually get done.

That's what a long-term technical partnership looks like when both sides are serious about it.