Hitmaker Engineering

About

Hitmaker Engineering exists to help regulated-product teams move from insight to implementation.

Medical-device and combination-product development often breaks down at the seams between user needs, product strategy, engineering, regulatory evidence, manufacturing readiness, and sustaining support. We help teams connect those pieces into a coherent development path.

Discipline
End-to-end medical-device & combination-product development
Industries
Diagnostics, drug delivery, connected platforms
Standards
21 CFR 820 / Part 4, ISO 13485, ISO 14971, IEC 62366
Based in
San Francisco, CA

What we help with

We help medical-device and combination-product teams across the full development lifecycle:

  • Translate user research and workflow insight into product direction.
  • Develop architecture, requirements, and engineering solutions that meet user, regulatory, and manufacturing constraints.
  • Connect design controls, risk management, usability, and verification evidence into a coherent submission package.
  • Move products from development into manufacturing, supplier qualification, and launch.
  • Sustain launched products through complaints, design changes, cost reduction, and post-market improvements.

How we work

  • We engage at the points in the lifecycle where decisions cross functional boundaries — not as detached advisors.
  • We do real engineering and design-controls work: architecture, requirements, risk analysis, change-control logic, FMEA, verification strategy, and process-validation planning.
  • We co-own the work with internal teams — embedded leadership for a milestone or phase, a coaching role alongside an internal program lead, or an independent technical owner opposite a contract manufacturer.
  • We coordinate with adjacent functions — regulatory submissions counsel, quality, manufacturing, supply chain — rather than working in isolation.

Where we fit in the lifecycle

We engage at every phase, but the highest-leverage moments are the seams between phases:

  • Translating user research into product direction (Phase 1 → 2).
  • Closing the architecture decision before substantial engineering commits (Phase 2 → 3).
  • Connecting requirements, risk, usability, and design controls in the run-up to design freeze (Phase 3 → 4).
  • Bridging design and manufacturing in advance of transfer (Phase 4 → 5).
  • Turning post-market signals into product improvements (Phase 6 back into the next iteration).

See the full list of services across the lifecycle →

What makes the approach different

  • Lifecycle-integrated, not siloed. We treat user needs, engineering, regulatory, and manufacturing as one development system, because that is how regulated products actually get built.
  • Hands-on. We bring direct ownership experience — Fortune 500 R&D portfolio leadership, FDA combination-product strategy, platform consolidation across multiple programs — and we apply it ourselves rather than pointing at frameworks.
  • Evidence-first. We treat design controls, risk management, and human factors as the architectural backbone of a regulated product, not parallel deliverables to be reconciled later.
  • Cross-functional by default. We are most valuable where product decisions cross functional boundaries — where user needs, engineering feasibility, regulatory expectations, manufacturing realities, and business goals all need to be reconciled.

Recent activity

Recent engagements, talks, and writing

A working list of where the firm has shown up — published writing, industry talks, and notable engagements. Updated as activity accumulates.

Published writing

All insights →

Industry talks & conferences

Coming soon. We are submitting abstracts to BIOMEDevice, MD&M, RAPS Convergence, and AAMI Exchange for the upcoming cycle. Accepted talks will be listed here.

Notable engagements

Many of our engagements are under NDA and cannot be named publicly. Where clients have given permission, brief case summaries will be listed here.

Working on a regulated product?

Most engagements start with a scoping call to map where the product is in the lifecycle and the timeline you are working toward.

Start a Product Development Conversation