Twenty Years in Regulated Environments
I’ve spent over twenty years building software where getting it wrong has real consequences – regulatory, financial, and operational. A decade in defense and financial services, then the last twelve years deep in healthcare on both the payer and provider sides.
That dual healthcare perspective is uncommon. Most engineers and consultants specialize in one. I’ve designed, built, and scaled platforms across both, which means I understand how data actually flows across the ecosystem and where it breaks down. I came up in environments where security and auditability aren’t aspirational – they’re table stakes – I bring that instinct to every engagement.
I started Ressik Labs because too many health tech companies learn the hard way that architecture decisions in regulated environments carry more weight than they expected. The integration that looked straightforward until two health systems had different assumptions about the same data model. The compliance certification that turned into a six-month retrofit because controls weren’t designed in from the start. The migration that stalled because nobody mapped the regulatory dependencies before writing code.
I’ve seen those problems enough times to help you avoid them. The throughline across all of it is the same: compliance and velocity aren’t a tradeoff if you build things right from the start.
How I Work
I don’t run a one-size-fits-all practice. How I engage depends on where you are, what’s urgent, and what your team looks like.
Advisory – You have the talent but need a sounding board. Architecture reviews, compliance readiness assessments, technical due diligence, strategic guidance from someone who’s been through it before.
Collaborative – I embed with your team to solve a specific problem together. I work alongside your engineers, help them build confidence with regulated-environment patterns, and leave your organization stronger than I found it.
Hands-on – Sometimes the situation calls for someone who can do the work directly. System design, integration builds, compliance-driven architecture – I’m comfortable at the keyboard when that’s what moves you forward.
Most engagements evolve. What starts as an architecture review often surfaces integration or compliance work. What starts as hands-on building often shifts toward advisory as the team levels up. That’s by design – the goal is to make the right kind of help available at each stage.
The Name
Ressik comes from a place where someone learned that the most meaningful work comes from paying close attention to the world around you and building things that matter. If you recognize it, you probably understand the kind of work I care about.