Most people ask "what do you want?". I ask for your story, then deliver what you really need.
While others build standalone features, I design integrated workflows.
While others add another portal to the stack, I embed solutions where users already work.
While others accept "order-taker" engineering culture, I transform teams from reactive to product-led.

• Product thinking, not feature thinking
  • SVPG-trained + Product Manager certification.
  • Implemented product analytics (Pendo, Gainsight) to drive data-driven decisions.
  • Led customer discovery in pharma and government.
  • Ask "what opportunity or problem are we trying to solve?" before opening Figma.
  • Figma is a tool. Microsoft Paint is a tool. Ever seen someone wear a tool belt to a wedding?
• Technical depth
  • Started coding at 15 in 1995.
  • Shipped production features in Vue, Angular, Blazor, and .NET MVC.
  • Built design systems across multiple stacks.
  • Rapid prototype solutions to validate before engineering investment.
  • Build custom reusable web components.
  • Theme 3rd party component libraries.
  • Git, Branching Strategies, and CI/CD pipelines.
• Design systems at scale
  • Built MMIT's design system focused on developer experience, not design perfection.
  • Created self-service systems that unblocked engineering velocity.
  • Documented in Confluence so teams could ship without design bottlenecks.
• Platform integration expertise
  • Designed Veeva CRM integration modules at MMIT embedding market access data where pharma teams already worked.
  • Saw the need for integration over isolation.
  • Core principle: don't make users leave where they work all day - unless you have something "magic".
• Healthcare & life sciences domain
  • 9 years across pharmaceutical regulatory software (Reed Tech), market access intelligence (MMIT), and government enterprise architecture (Senate).
  • I understand complex workflows, compliance requirements (21 CFR Part 11, GxP), and how to build products for sophisticated users in regulated environments.
• Cultural transformation
  • I identify when talented engineers are trapped in "build what they ask for" mode and transform them into empowered product teams.
  • This requires teaching product discovery, implementing analytics, and sometimes helping people understand they need to adapt or leave.
  • Not every consultant will tell you the hard truth—I will.
• Terms that make me cringe
  • Feature Factory
  • Maintenance Mode
  • Put it in the backlog

I've directed consultants, coached teammates, been put in front of customers because I ask the right questions, and built products used by Fortune 500 pharmaceutical companies.

I'm an 'OG' coder. While working at Burlington back in 1995 I was assigned their corporate intranet. Imagine a time when the web was novel and misunderstood - "assign it to that kid".

I don't have a computer science degree. I have 30 years in design and development.

Let's build something that actually matters.