Building in healthcare is often described as “hard,” but that word doesn’t capture the full reality. Hard implies friction. Healthcare regulation is something else entirely: it’s a system designed to protect patients, and it shapes nearly every decision a startup makes—from what you build, to how you document it, to how you prove it works, to how you convince investors that you can deliver on timelines that are never fully in your control.
In a recent Build Mode conversation, BioticsAI founder and CEO Robhy Bustami sat down with Isabelle Johannessen to unpack what it actually takes to build in a highly regulated healthcare environment, particularly when FDA approval is the destination. The discussion wasn’t a motivational speech about perseverance. It was closer to an operational field guide: what changes when compliance becomes part of product development, why fundraising in healthcare demands a different kind of storytelling, and how “cutting through red tape” turns into a daily discipline rather than a one-time hurdle.
What emerged most clearly is that in healthcare, building the product is only half the job. The other half is building the pathway—through evidence, documentation, risk management, and stakeholder alignment—while keeping a team energized enough to sustain the grind.
FDA approval doesn’t arrive at the end—it arrives at the beginning
One of the most important reframes Bustami offered is that FDA approval isn’t simply a milestone you reach after shipping features. It’s a design constraint that starts early and keeps tightening as you move forward.
When you’re building in less regulated categories, teams can iterate quickly, learn from user behavior, and adjust the roadmap based on what the market rewards. In healthcare, iteration still matters—but the “learning loop” is constrained by what regulators will accept as evidence. That means the questions you ask internally are different. Instead of “Will users like this?” the more urgent questions become “How will we demonstrate safety and effectiveness?” and “What data will we need, and how will we collect it in a way that stands up to scrutiny?”
Bustami emphasized that FDA-driven development forces a kind of upfront clarity. You can’t treat documentation as an afterthought. You can’t assume that a later study will magically validate earlier decisions. Even seemingly small choices—how you define endpoints, how you structure clinical workflows, how you handle data quality, how you manage versioning—can ripple into regulatory timelines and costs.
This is where many healthcare startups underestimate the work. They think the regulatory burden is mostly paperwork. But the deeper reality is that compliance changes the engineering process itself. It affects how you plan experiments, how you validate performance, how you manage traceability between requirements and outcomes, and how you ensure that what you built is what you claim you built.
In other words, FDA approval shapes the product’s “audit trail.” And once that audit trail becomes central, speed becomes a different kind of speed. Not “move fast and break things,” but “move fast while preserving integrity.”
The timeline problem: you can’t compress uncertainty
Another theme that surfaced is that healthcare timelines are not just long—they’re uncertain in ways that investors and founders often don’t fully appreciate until they’ve lived through them.
In many startups, delays are frustrating but manageable: a feature slips, a launch date moves, a hiring plan adjusts. In regulated healthcare, delays can be structural. If evidence isn’t sufficient, if study design needs revision, if data quality issues emerge, or if regulators request additional information, the schedule can shift in ways that aren’t simply “project management problems.”
Bustami’s point wasn’t that startups should be pessimistic. It was that they should be realistic about what can be controlled. The work is not only building; it’s building toward a moving target of expectations—expectations that are shaped by regulatory standards, scientific evidence, and the practical realities of clinical data collection.
That reality changes how teams plan. It also changes how they communicate progress. A healthcare startup can’t always point to “we shipped X” as the primary proof of momentum. Sometimes the proof is “we completed the evidence package for the next step,” or “we validated the workflow under conditions that match the intended use,” or “we resolved a risk category that would have blocked advancement.”
This is a subtle but crucial difference in how you measure progress. It’s also a subtle but crucial difference in how you keep morale high.
Fundraising in healthcare is about risk translation, not just vision
If FDA approval shapes product development, fundraising shapes the emotional and strategic bandwidth required to survive the process. Bustami described healthcare fundraising as a layered challenge: investors need clarity on risk, compliance, and execution—not just the ambition of the technology.
In many sectors, investors can underwrite uncertainty with a belief in iteration. In healthcare, uncertainty has a different weight. Investors must understand what regulatory path you’re on, what evidence you already have, what evidence you still need, and what could derail the plan. They also need to understand how you’ll manage the operational complexity of clinical-grade work.
Bustami’s framing suggests that fundraising in healthcare is essentially a translation exercise. Founders must translate their scientific and regulatory work into a narrative that investors can evaluate. That narrative has to answer questions like:
What exactly is the product’s intended use?
What claims are you making, and what evidence supports those claims?
What regulatory strategy are you pursuing, and why?
What are the critical risks, and how are you mitigating them?
What milestones will determine whether you advance, pivot, or stop?
This is not the same as pitching a consumer app. It’s closer to pitching a mission with measurable gates. Investors want to know where the gates are—and what it takes to pass them.
And because healthcare fundraising often involves longer horizons, the stakes of miscommunication are higher. A vague plan can be fatal. A plan that ignores compliance realities can look naive. A plan that overpromises timelines can create credibility damage that’s hard to recover from.
So the best fundraising stories in healthcare tend to be grounded in operational specificity. They show that the founder understands the system and has built a credible path through it.
Cutting through red tape is not a sprint—it’s an operating system
“Cutting through red tape” sounds like a heroic phrase, but Bustami’s perspective makes it clear that it’s not a one-time battle. It’s a recurring operational challenge.
Red tape in healthcare isn’t just bureaucracy for bureaucracy’s sake. It’s the mechanism by which patient safety and data integrity are enforced. That means the “tape” is often tied to real constraints: how you document processes, how you validate systems, how you manage quality, how you ensure consistency across versions, and how you maintain traceability.
For a startup, the danger is treating these constraints as obstacles rather than as inputs to design. When you do that, you end up reacting—scrambling to fix documentation gaps, reworking evidence, or rebuilding parts of the workflow because the original approach didn’t align with regulatory expectations.
Bustami’s implied lesson is that the team needs an operating system that treats compliance as part of the product lifecycle. That includes building internal processes that anticipate regulatory questions before they’re asked. It includes aligning engineering, clinical, and regulatory functions so they don’t operate in silos. It includes creating a culture where documentation is not seen as overhead but as a form of engineering rigor.
This is also where “speed” becomes a cultural issue. If the team believes compliance slows them down, they’ll resist it. If they understand compliance as a way to reduce rework and prevent dead ends, they’ll treat it as a tool.
Keeping teams motivated when approvals are the bottleneck
Regulatory work can be demoralizing because it often feels like progress is waiting on external decisions. Even when a team does everything right, the next step may depend on review cycles, requests for additional information, or the timing of clinical data availability.
Bustami highlighted that keeping teams motivated matters as much as the regulatory work itself. That’s not a generic leadership platitude. It’s a practical recognition that healthcare startups can burn out when the work is both high-stakes and slow-moving.
Motivation in this context comes from clarity: knowing what “done” means, understanding how each task contributes to the next gate, and seeing tangible outputs even when the final approval is not immediate.
A team can stay engaged if it can connect daily work to a larger evidence plan. That requires leadership to communicate progress in the language of milestones and outcomes, not just activity. It also requires managers to protect focus—because in regulated environments, distractions can lead to costly rework.
There’s also a psychological dimension. When you’re building something that could affect patient outcomes, the work carries moral weight. That can be motivating, but it can also increase pressure. Bustami’s message suggests that the healthiest teams are those that channel that pressure into disciplined execution rather than anxiety.
The unique challenge: healthcare AI isn’t just “AI”—it’s a medical product
While the conversation centers on FDA approval and fundraising, there’s an underlying point that applies broadly to healthcare AI and healthtech: the product is not merely a model or an algorithm. It’s a medical product with a defined intended use, a specific workflow, and a set of claims that must be supported.
That distinction matters because it changes what “performance” means. In consumer AI, performance might be measured by accuracy, engagement, or user satisfaction. In healthcare, performance is tied to safety, reliability, and clinical relevance. It’s also tied to how the system behaves in real-world conditions, including edge cases and data variability.
Bustami’s emphasis on documentation and evidence aligns with this. Regulators don’t just want to know that the model works in a lab. They want to know how it works, under what conditions, and how you manage risks when it doesn’t behave perfectly.
This is why healthcare startups often need cross-functional maturity. Engineering alone isn’t enough. Clinical expertise, regulatory strategy, quality systems, and data governance all become part of the core product capability.
A unique take: the “build” is really three builds at once
One