You have $8 million in runway, a novel cardiac device, and a 10-patient first-in-human study to execute before your Series A conversation begins. A CRO has just sent you a 40-slide capability deck. The deck opens with a world map covered in pins. It lists therapeutic area expertise across oncology, cardiology, and neurology. It has a slide on “integrated Phase 1–4 capabilities” and another on “global QMS infrastructure.” It closes with a client testimonial from a pharma sponsor who ran a 200-site Phase 3 program.

The deck is professionally produced and factually accurate. It is also almost entirely uninformative for your decision.

Read it the way an FDA reviewer reads an IND submission: with a deliberate bias toward what is absent, not what is highlighted. A well-constructed IND foregrounds safety rationale, device description, and study design. A skilled reviewer immediately turns to what is omitted — the gaps in the risk analysis, the unstated assumptions in the device description, the absence of site-specific data. The omissions are where the decision lives.

CRO capability decks follow the same logic in reverse. They are built to foreground strengths and suppress comparative weaknesses. For a founder making a CRO selection at the most consequential stage of clinical development — the first-in-human study — the standard capability deck is an exercise in strategic omission. This post identifies what to look for in the gaps.

The “Risk-Reduction Partner” Tell

In May 2026, ERGOMED ran a session at OCT Europe in Barcelona titled “Reframing the CRO: From Vendor to Risk-Reduction Partner.” The session is worth examining not as a critique of ERGOMED — it is a thoughtful positioning move for their target market — but as a diagnostic tool for understanding how full-service CROs think about their value proposition.

“Risk-reduction partner” is Phase 3 enterprise vocabulary. In the context it is designed for, it is entirely appropriate. Sponsors running 200-site global oncology programs have a legitimate problem: execution risk at scale. The CRO’s job in that world is to absorb institutional complexity, manage deviation escalation across jurisdictions, and maintain data quality across a program that may run five years and involve hundreds of investigators. “Risk-reduction partner” accurately describes what those sponsors need.

A MedTech founder with $8 million in runway and a 10-patient first-in-human study does not have that problem. The founder’s risk is not execution complexity. It is time-to-data and capital burn before the Series A window. Those are structurally different problems, and they require structurally different operational models.

When a CRO’s conference positioning, capability deck language, and testimonial library are uniformly oriented toward large pharma sponsors managing late-phase complexity, that is a tell. The CRO has built its systems, its hiring model, its regulatory relationships, and its project management infrastructure for that world. When a FIH-focused MedTech founder engages that CRO, they are not in the wrong room — they are in a room designed for a different problem. The capability deck will not surface this distinction, because the CRO has no incentive to name it. The founder has to read it out of the omissions.

The question is not whether a CRO is good at what it does. The question is whether what it does is what you need.

What Gets Emphasized vs. What Gets Omitted

CRO capability decks are designed by marketing and business development teams. They foreground what differentiates the firm in competitive presentations to late-phase sponsors, because that is the primary audience most CROs are selling to. When you receive one as a FIH MedTech founder, you are reading a document optimized for a different buyer.

What is consistently foregrounded:

• Integrated Phase 1–4 capability (breadth signals institutional scale)
• Global site footprint (pin maps create an impression of reach)
• Late-phase QMS infrastructure (relevant to sponsors managing multi-site Phase 3 programs)
• Therapeutic area expertise in high-revenue categories (oncology, CNS, rare disease)
• Client testimonials from pharma sponsors, typically Phase 2–3 programs

What is systematically omitted:

• Per-patient cost ranges at the FIH stage. Capability decks price by service line, not by patient. A 10-patient FIH study in the United States or EU runs approximately $40,000–$75,000 per patient at comparable Latin American sites, the same study costs $15,000–$35,000. That is a $250,000–$400,000 difference on a 10-patient program. No capability deck will surface this unprompted.
• Jurisdiction-specific approval timelines. U.S. academic IRBs average 6.5 months for initial review of a novel device protocol. That number does not appear in any capability deck from a CRO built on U.S. site infrastructure, because it is not a competitive advantage for them. It should be the first number you ask for.
• The percentage of active portfolio that is first-in-human. A CRO that is 90% concentrated in Phase 2–4 programs has built its project management systems, its site relationships, and its hiring model for that concentration. Ask for the actual number.

Reading a capability deck as a regulator reads an IND means asking: what would a competent operator omit from this document if they wanted to avoid a comparison they would lose? Those omissions are where your due diligence should begin.

The 6–12 Month IRB Problem

The most expensive problem in U.S. first-in-human development is not device complexity, not protocol design, and not CRO selection. It is IRB latency, and almost no CRO capability deck addresses it directly.

U.S. Institutional Review Board approval for a novel medical device at an academic medical center averages approximately 6.5 months for initial review. When protocol revision cycles are included — which is the norm, not the exception, for first-in-human device studies — full startup-to-approval timelines routinely exceed 12 months. The FDA CDRH Early Feasibility Study program documentation and MDIC’s 10-year EFS program analysis both identify study startup latency as the primary bottleneck in U.S. FIH device development — not regulatory approval, not site selection, but the ethics review cycle itself.

At typical early-stage burn rates of $500,000–$1,000,000 per month, a 6-month IRB delay consumes $3–6 million in operating capital before a single patient is consented. For a founder with $8 million in runway targeting a 10-patient FIH study, that latency can be program-defining.

Colombia’s INVIMA approves medical device clinical trial applications in approximately 30 days. Ethics committee approval in bioaccess®-managed studies in Colombia has been achieved in 15–18 days, with a typical portfolio range of 4–8 weeks. Argentina’s ANMAT operates under Disposición 7516/2025, which establishes a 62-working-day maximum review standard. These are not anomalies — they are the output of system design and site relationships built over 16 years of operating exclusively in first-in-human studies across 10 Latin American countries.

The question every founder should ask every CRO before reviewing a budget proposal: “What is your documented median IRB or ethics committee approval time in your primary operating jurisdiction over the past 24 months?” If the answer is vague, that is informative. If the answer is specific and it runs past 90 days, that is more informative still.

The First-in-Human Percentage Question

The second question a founder should ask — and the one most CRO capability decks are built to obscure — is: what percentage of your active portfolio is Phase 1 or first-in-human?

The three largest contract research organizations globally — ICON, Syneos, and Parexel — are concentrated in late-phase development. ICON’s 2024 Annual Report shows that the substantial majority of its revenue comes from Phase 2–4 programs; FIH studies represent a small fraction of total portfolio activity. The same is true across the large-CRO sector. This is not a criticism — it reflects where the revenue is. But it has direct operational consequences for a FIH-stage founder.

A CRO with 5% of its active portfolio in first-in-human studies has built its project management infrastructure, its site activation processes, its deviation escalation protocols, and its regulatory file templates for the other 95%. When a FIH MedTech study enters that system, it is managed on infrastructure optimized for Phase 3 complexity: more oversight layers, more standardized QMS requirements, more administrative burden than a FIH study needs or benefits from.

The capability deck will say “Phase 1–4 integrated capabilities.” It will not say that Phase 1 represents 4% of active studies, that the Phase 1 team shares project managers with Phase 3 programs, or that the ethics committee relationships in your target jurisdiction were last activated 18 months ago on a different therapeutic area.

A CRO that has run first-in-human studies exclusively since inception has made the opposite set of tradeoffs. Every hire, every site relationship, every regulatory file system, and every approval timeline benchmark in that organization reflects a single operational context. That specialization compounds over time: 16 years of FIH-only operations across 10 countries produces a very different institutional knowledge base than 16 years of integrated Phase 1–4 operations in which FIH is one service line among many.

Ask the question. Get the number.

The Concurrent OUS FIH + U.S. EFS Structural Advantage

The FDA’s Early Feasibility Study program was designed specifically for novel medical devices at the earliest stages of clinical development. Under 21 CFR 812.28, EFS submissions receive expedited CDRH review, with approximately 70% approved within 30 days. The MDIC’s 10-year EFS assessment documents significant improvements in study startup timelines when founders use the EFS pathway rather than traditional IDE submission.

The structural advantage that no large CRO’s capability deck will surface clearly: a specialized FIH CRO that can execute both OUS first-in-human enrollment (in Colombia, Argentina, or elsewhere in Latin America) and concurrent U.S. EFS enrollment under a single CRO relationship changes the founder’s decision calculus in a material way.

Under a traditional model, a founder chooses: OUS FIH first, then U.S. enrollment — running two sequential programs, often with different CROs, rebuilding the regulatory relationship each time. The concurrent model eliminates that sequencing. OUS FIH data informs the U.S. EFS design in real time. The regulatory file management, the data quality systems, and the sponsor relationship are continuous rather than episodic.

For a large full-service CRO, EFS is one line item in a catalog of hundreds. The EFS capability will appear in the capability deck. What will not appear is how many EFS studies the team has actually executed, what their median CDRH response time has been, or whether the team managing U.S. EFS operations has any continuity with the team that would manage OUS FIH enrollment. For a CRO that has built its OUS FIH operations over 16 years and added U.S. EFS as the logical extension of that same operational model, those answers are specific and documentable.

Ask: “How many EFS submissions has your team submitted in the past 36 months, and what is your documented median CDRH response time?” Then ask the same question about your target OUS jurisdiction. The answers should be specific.

Three Columns: What the Deck Says, What It Omits, What to Ask

The following framework is designed to be used during CRO evaluation, before you engage in formal proposal negotiations. Apply it to every capability deck you receive.

The three-column exercise does not require adversarial questioning. A CRO with genuine FIH specialization will answer every question above with specific, documentable data. The absence of specific answers is itself the answer.

Reading a CRO capability deck like a regulator means treating every foregrounded strength as a signal to ask what is structurally absent on the other side of that strength. The 40 slides are not the decision. The five questions above are the decision.

Next Steps

If you are evaluating CRO options for a first-in-human study and want a direct conversation about how bioaccess®^® structures FIH programs in Latin America — including ethics committee timelines, per-patient cost benchmarks, and concurrent U.S. EFS execution — schedule a consultation at bioaccessla.com/book-a-meeting.

To model the cost difference between U.S./EU and LATAM FIH execution for your specific protocol, use the bioaccess® clinical trial cost calculator.

For the foundational framework this post extends — the five questions to ask before signing a CRO MSA — see Five Questions Every MedTech Founder Must Ask a CRO Before Signing the MSA.

Sources

• ERGOMED OCT Europe 2026 — “Reframing the CRO: From Vendor to Risk-Reduction Partner” session
• FDA CDRH — Early Feasibility Studies overview and IDE program benchmarks
• MDIC — Celebrating Early Feasibility Studies: 10-Year Journey (program outcome data)
• ICON plc — 2024 Annual Report (portfolio and revenue concentration data)
• 21 CFR 812.28 — Early Feasibility Study regulatory requirements
• bioaccess® — Argentina’s New 62-Day Clinical Trial Approval: What MedTech Sponsors Need to Know
• bioaccess® — Five Questions Every MedTech Founder Must Ask a CRO Before Signing the MSA
• bioaccess® — Why the World Needs a First-in-Human CRO