|
So when exactly should a medtech startup transition from quick and flexible to more structured and process-driven? According to Trey Bobo, a third-generation medical device engineer with 20 years of experience in the medical device industry, there isn't a universal milestone that tells every startup when to make the switch. The answer depends on the technology, the clinical and regulatory pathway, and where the product is in development. For medical device startups, being scrappy is often part of the job. Resources are limited, timelines are tight, and founders have to figure out how to move the technology forward without spending money they don't have. But there comes a point when "scrappy" can stop being an advantage. So when exactly should a medtech startup transition from quick and flexible to more structured and process-driven? Your Process Should Match the Risk Early in development, a startup may have little more than a patent, an idea, or an early prototype. At that stage, building a highly structured organization can create unnecessary overhead before the company even understands what it is building. As Bobo explains, the level of process maturity should "match the risk that's being addressed." That could mean being extremely scrappy when a company is still figuring out the technology and trying to determine whether an idea can work. But as the technology matures and the development path becomes clearer, the company should progressively introduce processes that make the organization more efficient and help manage increasing levels of risk. Class III Devices Require a Different Level of Judgment That distinction becomes particularly important with Class III devices, especially novel technologies going through a PMA pathway. Bobo describes situations where a company may need to remain highly flexible during early development and preclinical work. At that stage, conserving cash and learning quickly can be critical. But being scrappy doesn't mean being careless. For a novel Class III device, the early objective may be to generate enough evidence to determine whether the technology has a viable path forward. As Bobo puts it, the goal is to make sure the technology "has a breath, has a whisper." That mindset can change as the device moves closer to clinical evaluation and commercialization. If there is already an established understanding of the patient population, the therapy, and the expected clinical benefit, continuing to operate with an overly informal approach can create unnecessary exposure. Risks that should have been addressed earlier can become much more expensive to fix later. That's why Bobo recommends continually stepping back and asking whether the way you're working still makes sense given the maturity of the technology. There is No Medtech Playbook One of the biggest mistakes startups can make is assuming that the same approach will work simply because it worked for another device. Bobo points out that medical device development doesn't have a single playbook. Previous experience can provide valuable insight into what might happen, but every product brings its own combination of technology, clinical requirements, regulatory considerations, resources, and external factors. That applies to decisions about what a company should keep in-house, too. A startup might decide to insource everything because that approach worked previously. But bringing too much work in-house can spread a small team's attention across too many areas and create an organization that is capable of doing a lot without actually moving the most important work forward. The opposite extreme can create problems as well. Outsourcing everything may allow a startup to stay lean, but it still requires strong internal judgment and oversight to make sure those external partners are actually moving the company toward its goals. The right answer is often somewhere in between. Scrappy Doesn't Have to Mean Unstructured The real question isn't whether a startup should be scrappy or process-driven. It's where each approach makes sense. A young company may need speed and flexibility in one area while requiring much more structure in another. A company developing a lower-risk device may be able to remain lean longer, while a Class III device with significant clinical and regulatory risk may require more formal processes earlier. The important thing is to make those decisions intentionally. As a startup gains a better understanding of its technology and development path, its processes should evolve with it. The goal is to add structure where it reduces risk, improves efficiency, or creates clarity, without creating bureaucracy simply for the sake of having a process. Looking for more support?
If you have questions about this topic or want to explore how our team can help with your MedTech project, contact us here. Want to see what we do? Visit our Services page or contact us directly to talk through your project and see if we’re the right fit.
0 Comments
Leave a Reply. |
AboutThe MedTech Snapshot Podcast, hosted by Square-1 Engineering’s Travis Smith, features quick insights from industry executives on topics like startups, funding, product development, finance, manufacturing, and more. Archives
October 2026
August 2026
July 2026
June 2026
May 2026
April 2026
March 2026
February 2026
January 2026
November 2025
October 2025
September 2025
August 2025
July 2025
June 2025
May 2025
April 2025
March 2025
February 2025
January 2025
Categories
All
2023
2024
2025
21 CFR 820
Accelerator
Acquisition
AdvaMed
Agile
Artificial Intelligence
Breakthrough Moment
Business Strategy
Career
Clinical
Clinical Trials
Compliance
Contract Manufacturing
CRO
Cyber Security
Embedded Systems
Entrepreneur
FDA
Finance
FMEA
Funding
Global Operations
Government
Healthcare
Hiring
History
Incubator
Industrial Design
International
Investor
ISO
ISO 13485
Jp Morgan
KPI
Leadership
Leadership/Management
M&A
Machine Learning
Management
Manufacturing
Medical Device
Medtech
Medtech Snapshot
Networking
Operations
Orange County
OUS
Outsourcing
Patient Advocacy
Podcast
Policy
Private Equity
Product Design
Product Development
Production
Professional Development
Project Management
Quality Assurance
Quality Systems
RAQA
Regulation
Research & Development
Risk
Risk Management
Root Cause Analysis
Sales
Scope Creep
Snapshot
Software
Southern California
Startup
Start Ups
Strategy
Supply Chain
Talent
Technology
Tech Transfer
Term Sheets
Top Grading
Trends
User Experience
User Needs
Venture Capital
Voice Of The Customer
|
RSS Feed