Nick Ruffin

What I Do

I own commercial data delivery for a pharmacy-data monetization program built on NCPDP pharmacy transactions, and I manage the engineering team that builds and runs it. We deliver across three motions: de-identified patient-level tokenized claims, identified PHI delivered into customer-controlled AWS or Azure environments, and cross-source combined feeds joining multiple pharmacy systems.

The program serves patient-journey and real-world evidence platforms, market access and payer intelligence, life-sciences market and competitive intelligence, prescriber-level commercial analytics, financial and alt-data research, and community-pharmacy clinical networks.

I also manage the delivery of reporting back to drug manufacturers for our copay assistance, voucher, and clinical programs, where I own the engineering and the delivery commitments rather than the programs themselves.

From Engineer to Program Leader

I spent my early years as an engineer solving problems in code. What moved me past that was watching where the real constraints actually sat: not in the application, but in the agreement behind it, the compliance posture that gated whether work could be sold at all, and the question of which team owned which piece. Those decisions were being made somewhere I was not, and they determined whether anything I built mattered.

So I moved toward them. Owning a program means holding the engineering and the commercial reality in the same hand: what we can commit to in a contract, what the compliance evidence will actually support, and what the team can operate on Monday. The engineering background is why that judgment holds up, because I have never had to guess whether a commitment was deliverable.

Discipline

I am in the gym five days a week, and it has very little to do with the gym. Showing up on the days I do not feel like it is the same muscle as carrying a program through a quarter that is not going well, and I have never found the two to be separable. When I let the physical slide, my thinking gets sloppy within a week.

Staying in good physical shape is how I stay in good mental shape, and I treat both as the entry fee for operating at the next level rather than as something I get to the moment work calms down. It never calms down. The discipline has to come first or it does not come at all.

Why I Build

I am a father, and that is the part of this that actually sets the direction. My daughter is the reason I think past my own career, because anything worth the hours has to outlast the job that paid for it. It starts with my name meaning something, and it ends with her inheriting more than a story about how hard I worked.

That shapes how I choose work. I would rather own the outcome than rent a seat next to it, rather build an asset than collect a wage for maintaining someone else's, and rather be the person accountable when it breaks than the one who gets to point upward. Every decision in my career has bent toward building something that keeps compounding when I am not in the room.

What I Am Working Toward

Long term, I want to go deeper in this domain rather than wider. Retail pharmacy data is narrow, technical, and heavily regulated, and the people genuinely fluent in it are few, so depth compounds here in a way breadth does not. I would rather know this space to the bottom than have touched ten adjacent ones.

In the meantime I want to keep doing exactly what I do now at a larger scale: own a commercial data program end to end, be the person the contract and the compliance posture and the delivery all route through, and grow leaders under me who outpace what I could do alone. The ceiling I am interested in is how much I can be trusted with, not what the title says.

Technical Focus

Background

Before RedSail I was Director, Full Stack Development at Nimble Solutions from 2021 to 2025, where I built out, hired into, and ran the software and RPA engineering teams across the US and Hyderabad, plus a project manager, and later took on the data team. I owned the accounts receivable platform: collectors had been working unpaid claims out of spreadsheets at roughly 20 touches a day with no way to tell which were worth the call, and we replaced that with a work queue ordered by recoverable revenue, lifting throughput past 30 claims a day per rep.

The data behind it sat in practice management systems and clearinghouses, so the software team built cloud function apps and custom API integrations where an interface existed, and the RPA team automated report extraction where none did, feeding the warehouse through ETL. That path is what made each newly acquired system a configuration problem instead of a rebuild across four healthcare acquisitions, where I was the CIO's technical partner on due diligence alongside our VP of Infrastructure and CISO.

Prior to Nimble, four years as Senior Full Stack Developer at Core & Main building enterprise data applications on C#/.NET and SQL. Twelve years of engineering across pharmacy, healthcare data, and enterprise systems. Bachelor of Science in Computer Science, University of Phoenix.

Get In Touch

If you are working on commercial health data, real-world evidence, or pharmacy data products and think there is something worth talking about, reach out. The contact page goes straight to me.