PICA Member Spotlights
Q&A with independent consultants who successfully “made the leap” and created the consulting career of their dreams
Q: Who are you and what’s your business?
A: My name is Kevin Shea and I run Driftpin Consulting, where we help life sciences organizations design, implement, and validate digital systems—especially in clinical operations, data management, and lab environments, and increasingly in healthcare. The focus is on systems that generate or manage critical data. I support teams in selecting and shaping technology that aligns with how the business actually operates, satisfies regulatory expectations, and scales appropriately with risk. That includes ensuring AI and automation are applied in the right ways, for the right reasons.
Q: How long have you been independent?
A: I’ve been running Driftpin for 10 years and have worked in life sciences technology for more than 24. My background spans enterprise tech, industry, and services—so I’ve had a front-row seat to the common friction points between stakeholders.
Q: Why did you become an independent consultant?
A: I became a consultant to help bridge the gap between business and technology. Most systems don’t fail because of the software—they fall short because the implementation doesn’t reflect the team’s actual workflows, risks, or business goals. I focus on right-sized, risk-based solutions that are grounded in how the system will be used. I translate across functions, negotiate trade-offs, and help clients build systems that are fit for purpose—whether that’s in clinical trials, lab operations, or enterprise quality.
Q: How did you “make the leap”?
A: It was gradual. I started in tech at Oracle, moved into industry with a CRO, then into services with an FSP. Each role gave me more perspective on how systems succeed—or fall short—in regulated environments. Over time, I realized I could offer more value as an independent, where I could focus entirely on the client’s needs rather than selling a product or fitting a preset model.
Q: How did you get your first client? And your second?
A: My first client came through a long-time professional relationship—someone who trusted me to come in, assess the situation quickly, and build a pragmatic, compliant path forward. The second was a referral. That pattern has continued: most of my work comes through repeat engagements or word of mouth.
Q: What’s one thing you know now that you wish you’d known before you started?
A: That subject matter expertise alone isn’t enough—you also need to think critically, communicate clearly, and recognize when the team needs clarity more than detail. I’ve learned to work through ambiguity, reduce unknowns, and help teams make good decisions early—before complexity takes over. Being risk-aware doesn’t mean being risk-averse; it means understanding what could go wrong and shaping the system to absorb or avoid it. That mindset pays off when things don’t go as planned.
Q: What’s surprised you the most about being self-employed?
A: How much hinges on strong communication. Clients appreciate direct, honest, and consistent messaging—especially when a project gets off track. That kind of communication creates the space to solve problems without blame and keep momentum going. You don’t need to have all the answers on day one—but you do need to create the conditions where the team can work through complexity together.
Q: What’s been your biggest challenge, and how did you figure it out?
A: Managing scope and expectations—especially when teams are under pressure or under-resourced. The fix usually isn’t adding more process—it’s creating clarity around goals, constraints, and risk tolerance. I’ve learned to define success early, document assumptions, and design systems that are resilient enough to evolve without collapsing under their own weight.
One of the biggest lessons has been the central role of validation. It has to be part of the conversation from day one through go-live—and that’s just the beginning. If your validation strategy is weak, if the vendor isn’t in sync, or if you haven’t resourced it properly, you’ll feel the pain for the life of the system. Every upgrade, every change, every audit becomes harder. Get it right early, and the rest is more manageable.
Q: What does the word “solopreneur” mean to you?
A: To me, it means full accountability. You’re responsible for asking the hard questions, supporting the team, and making sure the system actually works—not just technically, but operationally. It’s not about being the hero or the loudest voice. It’s about creating alignment between people who see the same project from very different angles—and helping them succeed together.
Q: What is something that many aspiring solopreneurs think they need that they really don’t?
A: A polished brand or “thought leadership” platform. What you actually need is clarity—about the value you bring, who benefits from it, and how to show up when it matters. A good reputation and a well-earned referral are far more powerful than a clever tagline.
Q: Is there a particular quote or saying that you use as personal motivation?
A: “Slow is smooth, smooth is fast.” It’s especially relevant in regulated environments. Rushing leads to rework. Staying methodical and risk-aware gets you further—even when the pressure’s on. Rush the process and you’ll be redoing it later. Take the time to think critically and plan with risk in mind, and you’ll move faster in the long run.
Q: What’s next for you and your consulting business?
A: Continuing to support teams working with emerging technologies—especially around AI, automation, and compliance. I’m also putting more energy into writing and content—via Substack and LinkedIn—to help clients and vendors think more clearly about validation, data integrity, and system design before the project kicks off.
Q: How can people find out more about you or your business?
A: You can reach me at kfshea@driftpin.com or +1 610-772-5726, and find me at www.driftpin.com, on LinkedIn, or at driftpin.substack.com. I’m always happy to connect with teams working in life sciences, biotech, pharma, or health tech—especially those looking for grounded, systems-minded help in tech, validation, and compliance.
~ ~ ~ Additional PICA Resources ~ ~ ~
