Category: Founder Resources

  • How To Read A CRO Capability Deck Like A Regulator (What The Marketing Doesn’t Say)






    How to Read a CRO Capability Deck Like a Regulator (What the Marketing Doesn’t Say)


    How to Read a CRO Capability Deck Like a Regulator (What the Marketing Doesn’t Say)

    Published May 11, 2026 | bioaccess®®

    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.

    What the Deck Says What It Omits What to Ask to Fill the Gap
    Integrated Phase 1–4 capabilities Percentage of active portfolio that is Phase 1 or FIH “What percentage of your active studies are first-in-human or Phase 1, and what was that percentage 24 months ago?”
    Global site footprint Ethics committee / IRB approval timelines in target jurisdiction “What is your documented median ethics committee or IRB approval time in [your target country] over the past 24 months?”
    Service line pricing / budget proposal Per-patient cost isolated for FIH stage “Please provide a line-item budget with per-patient cost isolated from site management and overhead fees.”
    FDA acceptance language EFS submission volume and documented CDRH response times “How many EFS submissions has your team managed in the past 36 months, and what is your median CDRH response time?”
    Therapeutic area expertise Medical device FIH-specific experience vs. drug/biologic Phase 1 “What percentage of your Phase 1 portfolio is medical device studies under IDE or EFS, vs. drug or biologic IND?”

    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


  • Five Questions Every Medtech Founder Must Ask A CRO Before Signing The MSA






    Five Questions Every MedTech Founder Must Ask a CRO Before Signing the MSA


    Five Questions Every MedTech Founder Must Ask a CRO Before Signing the MSA

    Published by bioaccess®® | May 2026

    The Most Expensive Vendor Decision You Will Make Before Your Series B

    The master services agreement you sign with a CRO at the first-in-human stage is not just a vendor contract. It is a commitment to a timeline, a data architecture, a regulatory strategy, and — in ways most founders do not fully price until they are inside the engagement — a bet on whether that organization has ever actually done this before.

    Most MedTech founders spend more time negotiating SaaS subscription pricing than interrogating the operational fitness of the CRO they are about to trust with their first human study. CROs are practiced at presenting capability decks that are both technically accurate and structurally misleading: yes, they have run first-in-human studies. The questions are how many, how recently, where, and with what kind of dedicated team.

    Getting this wrong is costly in ways that do not appear on the MSA. A generalist CRO that applies Phase 3 operational logic to a 10-patient FIH study produces delays and data packages that do not travel well to FDA. The five questions below are designed for use in an actual vendor conversation, written so that an organization built specifically for first-in-human work answers all five without hesitation and a generalist CRO with Phase 3 heritage struggles on at least three. The contrast is the diagnostic.

    Question 1: “What percentage of your active studies are first-in-human?”

    This question cuts through every capability deck. Most large CROs list “Phase 1-4” as an integrated capability — and that is technically accurate. ICON, Syneos Health, and Parexel all offer first-in-human services. What their materials do not disclose is the proportion of revenue, headcount, and operational attention that FIH commands relative to their Phase 2-4 and post-market portfolio. According to the ICON plc 2024 Annual Report, the company’s growth narrative is anchored in Phase 2-4 and functional service offerings. Syneos Health’s service model is similarly configured around integrated biopharmaceutical solutions at scale — not the 10-patient device feasibility study a seed-stage founder needs to execute.

    The operational implication: when FIH is a small fraction of a CRO’s active portfolio, the project managers on your study are people who primarily run Phase 3 logistics. They understand protocol compliance and site management at the multi-site scale. What they may not have is the judgment that comes from running dozens of first human exposures — the real-time risk calculus of dose escalation, the site selection nuances that matter when you have ten patients rather than three hundred, and the FDA communication posture that FIH-specific experience produces.

    The follow-up question matters equally: “Who on your team has personally run more than ten first-in-human studies from device selection through first patient in?” An organization that cannot surface a dedicated FIH unit with named individuals and verifiable track records has not built FIH as an operational discipline.

    Red flag: Any CRO that cannot give you a clean percentage of active studies that are first-in-human has not built FIH as an operational core. It is a line item in a service menu. A CRO for which FIH is the only practice answers this question with a number above 90 percent — because there is nothing else on the portfolio.

    Question 2: “What is your documented median time from IND/IDE submission to site initiation in your primary jurisdiction?”

    Timeline is not a soft preference. It is a capital efficiency variable. Every month between IND/IDE equivalent submission and first patient in is a month of runway consumed and a month of competitive exposure while your device sits in regulatory review.

    The documented benchmark for ethics committee approval in Latin American FIH programs — for organizations with established site relationships and a mature submission infrastructure — is 4 to 8 weeks. In Colombia, where the regulatory framework has been shaped by over a decade of FIH execution, approval instances as fast as 15 to 18 days have been recorded. This is the result of site-level relationships, submission formatting that ethics committees recognize, and a regulatory team with institutional familiarity with the FIH protocol type.

    The U.S. comparison is not subtle. The average IRB/EC cycle in the United States for a novel device IDE study runs 6 to 12 months from submission to site initiation when you account for FDA review, IRB submission, site contracting, and institutional compliance review. In the EU, a 6-month horizon from IDE equivalent to first patient in remains the conservative planning assumption most regulatory counsel will give you.

    Illustrative Ethics Approval Timeline Comparison
    Jurisdiction Documented Range Basis
    LATAM (Colombia, established sites) 4-8 weeks (fastest: 15-18 days) bioaccess® operational track record, 2010-present
    United States (IDE pathway) 6-12 months (submission to site initiation) FDA CDRH IDE review statistics
    EU (CTR pathway) 3-9 months (submission to site initiation) EMA Clinical Trials Regulation implementation data

    When you ask this question, you are asking for documented median performance, not a best case. An organization that cannot answer with data has not been measuring what matters.

    Question 3: “Have you produced a data package accepted by FDA from a non-U.S. trial in the past 36 months?”

    The most persistent misconception among U.S. device founders about outside the United States clinical data is that FDA will not accept it. This misconception is expensive, because it leads founders to dismiss LATAM and other OUS execution pathways as regulatory dead ends when the regulatory framework explicitly accommodates foreign clinical data.

    21 CFR 312.120 permits FDA acceptance of foreign clinical data when the trial was conducted in accordance with Good Clinical Practice and under a protocol FDA would consider adequate and well-controlled. 21 CFR 812.28 extends parallel provisions to device studies, explicitly addressing acceptance of data from foreign investigations in support of IDE and PMA submissions.

    A first-in-human study conducted in Colombia, Brazil, or Peru under a GCP-compliant protocol, with a data architecture designed to meet FDA standards, can generate the foundational data package that supports a U.S. IDE submission. The LATAM study is not a workaround. It is a legitimate regulatory pathway.

    Executing it correctly requires a CRO that has actually done it. “We could produce FDA-compatible data” is not the same as “we have produced FDA-accepted data from an OUS trial in the past three years.” Ask for the latter. Ask for the regulatory outcomes. Ask whether the data traveled to FDA and what the response was.

    A CRO that has never navigated 21 CFR 312.120 or 812.28 in practice — regardless of what their regulatory affairs team says in a capabilities presentation — is asking you to be their learning case at the stage where you cannot afford that tuition.

    Question 4: “What is your per-patient cost range for a 10-to-15 patient FIH study in your primary jurisdiction?”

    Per-patient cost for a FIH study is the single most compressed way to understand the financial architecture of a CRO engagement before you are inside one. Cost transparency at the proposal stage is not a courtesy — it is a due diligence requirement.

    The documented range for per-patient costs in Latin American clinical trial sites runs from approximately $15,000 to $35,000 per patient for a first-in-human medical device study. The equivalent range in the United States and European Union runs from $40,000 to $75,000 per patient for comparable FIH work. That differential — roughly 59 percent lower cost per patient in LATAM — reflects the structural economics of clinical site operations in markets where investigator compensation, institutional overhead, and support cost structures differ materially from U.S. and EU norms.

    On a 10-patient FIH study, the arithmetic is direct: U.S. execution at $40,000-$75,000 per patient produces a $400,000-$750,000 direct study cost. LATAM execution at $15,000-$35,000 per patient produces a $150,000-$350,000 direct study cost. The difference — $250,000 to $400,000 — is material capital at the seed or pre-Series A stage. It extends runway. It funds the follow-on safety cohort. It covers FDA pre-submission preparation. It is the difference between a founder who enters their Series A with FIH data and remaining runway, and one who spent it all to generate the same data in a U.S. site.

    A CRO that deflects to “it depends on the protocol” without offering a range for a standard FIH configuration has either not run enough FIH studies to have a stable cost model, or does not want you comparing numbers before you have signed.

    Question 5: “Can you execute an EFS submission and manage a concurrent OUS FIH study under a single operational team?”

    The FDA’s Early Feasibility Study program is one of the most underutilized regulatory tools available to U.S. MedTech founders. According to the FDA Early Feasibility Study Program, the EFS pathway is designed for early-stage devices where clinical data is needed to inform device design — precisely the stage at which a FIH study occurs. The MDIC 10-Year EFS Journey analysis documented that approximately 70 percent of EFS submissions receive FDA response within 30 days — a timeline that makes concurrent OUS and U.S. enrollment operationally feasible within the same funding window.

    The strategic logic of concurrent execution is about data architecture, not just speed. A LATAM FIH study generating safety and early efficacy signals in parallel with a U.S. EFS enrollment produces a richer, more FDA-defensible data package than either study would generate independently. The LATAM cohort contributes patient volume and diverse population data; the U.S. cohort generates data with direct site-level FDA familiarity. Together, they build an IDE submission or PMA dataset from a position of evidence rather than assumption.

    Executing this dual-track strategy requires a CRO that can manage both pathways under a coherent operational structure — not two separate vendor relationships requiring a founder as the integration layer. The question diagnoses whether a CRO has built the capacity to hold both regulatory tracks in a single team, or is offering LATAM execution on one hand and a referral to a U.S. partner on the other.

    The U.S. EFS pathway and a concurrent LATAM FIH study are not competing strategies. They are the same strategy, executed in parallel, by an organization that understands both regulatory environments as a single integrated operation.

    How to Use This Checklist

    These five questions are not adversarial. They are clarifying. A CRO that has built its operations around first-in-human work will not find them uncomfortable — they will find them efficient, because the answers surface quickly from an organization that lives in this space every day.

    Use the questions in the initial capabilities conversation, before you have a proposal on the table and a timeline pressure that makes switching feel costly. The moment to evaluate operational fit is before you have signed anything, not after you are inside a study running six months behind the timeline the capabilities deck implied.

    • What percentage of your active studies are first-in-human?
    • What is your documented median time from IND/IDE equivalent submission to site initiation?
    • Have you produced a data package accepted by FDA from a non-U.S. trial in the past 36 months?
    • What is your per-patient cost range for a 10-to-15 patient FIH study?
    • Can you execute an EFS submission and manage a concurrent OUS FIH study under a single operational team?

    If the answers satisfy all five questions, you are talking to a CRO that may be able to run your first human study competently. If they do not, you have learned something before the signature, not after.

    Ready to Run the Evaluation?

    bioaccess® works with MedTech founders at every stage of FIH preparation — from regulatory strategy through first patient in. If you want to talk through your specific program against these five criteria:

    Sources