Faro

1. Limited third-party user review coverage is a procurement requirement

• Faro has limited visible coverage on mainstream review platforms (G2, TrustRadius, Gartner Peer Insights) in this research run. Organizations that require substantial third-party reviews may prefer alternatives with broader review footprints.

2. The primary requirement is EDC/CTMS/eTMF functionality rather than protocol digitization and SoA intelligence

• Faro is positioned to complement, not replace, core clinical operations systems. Organizations that need a primary eClinical suite should evaluate platforms such as Medidata, Veeva, Oracle, or OpenClinica first, and then consider Faro as an upstream layer.

3. Insufficient budget or willingness for change management

• Implementing a "protocol as data" approach requires governance, training, and workflow redesign.

4. Requirement for transparent, self-serve pricing

• Faro does not publish pricing on its public site. Alternatives with public pricing may be preferable for self-serve procurement models.

5. Need for publicly documented security artifacts beyond SOC 2 Type II

• SOC 2 Type II is documented, but other security details (ISO claims, feature checklists) were not consistently verifiable in this research run and should be requested directly from the vendor.

Faro references integrations and an API in CDISC materials, but detailed API documentation was not publicly available in this research run.

• CDISC webinar PDF mentions "Faro API": https://www.cdisc.org/sites/default/files/pdf/CDISC-Faro%20webinar-Feb-2026.pdf

Unique selling points supported by available evidence (phrased objectively):

• The vendor emphasizes converting protocol/SoA into structured data intended to support downstream automation and integration efforts.
  • Source: https://farohealth.com/study-designer/
• Faro has communicated integration messaging with Veeva Vault EDC through partner program participation.
  • Source: https://www.digitaljournal.com/pr/news/accesswire/faro-health-joins-veeva-product-1626591813.html
• Vendor-cited academic work references a peer-reviewed study on quantifying SoA impacts, which provides a point of technical reference beyond pure marketing materials; buyers should review the original publication for methodology and results.
  • Source (vendor cites paper): https://farohealth.com/

Where competitors may have clearer advantages:

• Medidata / Veeva: broader installed base and ecosystem maturity
• OpenClinica: greater pricing transparency and modular packaging

For Faro (a specialized clinical development tool), mainstream B2B review platforms have limited or no product-level review coverage that was discoverable in this research run:

• Gartner Peer Insights: no clearly accessible Faro listing surfaced.
• G2 / TrustRadius / Capterra: searches did not return an obvious Faro product page with substantive user reviews.

This is common for specialized clinical R&D tools where buyers may rely on references, pilots, and analyst networks rather than mass-market review sites.

Because product reviews were scarce, this report draws from:

1. Vendor-published testimonials and partner references (which may be biased)
2. Employee reviews (Glassdoor; useful for organizational context but not a substitute for customer outcomes)
3. Community discussion referencing Faro-related published work (for example, a Merck/UCSF/Faro paper mentioned in a community forum)

Vendor testimonial (vendor-published)

• Faro’s homepage quotes an academic-style reference connected to Merck protocol applications that describes using Faro to quantify impacts of changes in an SoA and produce recommendations for potential savings. This appears on vendor-owned materials and should be validated against the original publication.
  • Source: Vendor website and vendor-published materials

Employee reviews (mixed)

• Glassdoor provides a limited sample of employee sentiment with both positive and negative comments about culture and management. Employee commentary is helpful for organizational context but should not be interpreted as direct evidence of customer service quality or product effectiveness.
  • Source: Employee review site

Community mention of Faro-related research (neutral-to-positive)

• A community post referenced the Merck/Faro/UCSF paper and described it as a potential roadmap for simplifying schedules of assessment using a lean design process.
  • Source: Community forum thread referencing the published paper

Because accessible product reviews are limited, it would be speculative to assert frequent product issues (bugs, missing features, or support problems) based solely on small samples.

What can be stated from available sources:

• Organizational change risk: Faro attempts to change entrenched protocol workflows; adoption friction is likely even if the software meets functional requirements (inference).
• Startup dynamics risk: Glassdoor feedback includes employee concerns about management style and reactivity; these comments reflect employee perspectives and do not directly document customer support quality.

Faro’s homepage cites a peer-reviewed paper: Cummings SR, Chetham S, Lee A. "A Method to Redesign and Simplify Schedules of Assessment and Quantify the Impacts. Applications to Merck Protocols." Therapeutic Innovation & Regulatory Science (published 2024).

Critical evaluation:

• Strength: Reference to a peer-reviewed publication is stronger evidence than vendor-only marketing materials, because the methodology and results can be examined in the published paper.
• Limitation: The vendor excerpt emphasizes recommendations for potential savings, which appear to be modeled. Buyers should review the full paper and confirm whether outcomes were realized in operational trials.

Faro announced a partnership with Recursion to apply the platform for protocol design optimization.

• Vendor source: Vendor newsroom announcement
• Third-party coverage: Industry media coverage article

Critical evaluation:

• Partnerships indicate industry engagement but do not by themselves demonstrate measured, reproducible outcomes. Prospective customers should request scope details (which trials), adoption depth, and any quantified before/after process metrics.

Most plausible fit:

• Mid-size to large biopharma sponsors and CROs with multiple concurrent studies and high protocol complexity
• Teams large enough to benefit from standardization (libraries, reusable modules) and integration automation

Typical organizational scale (inference):

• Sponsors: mid-sized to very large biopharma organizations
• CROs: mid-sized to enterprise-level CROs
• Also innovation teams and digital R&D groups within large pharmaceutical companies

Faro is a B2B SaaS platform focused on digitizing and optimizing clinical trial protocol design. The platform converts protocol content (often written and maintained in Word/PDF) into structured, reusable study data that can be used for:

• Study design & schedule of assessments (SoA) modeling and benchmarking
• Protocol document authoring (including AI-assisted drafting)
• Downstream automation (for example, EDC build acceleration via integrations)

The vendor describes the platform as using AI techniques applied to aspects of clinical development, with functionality covering protocol design, authoring, and downstream automation. Vendor marketing claims include "real-time insights," reduced patient/site burden, and faster study startup; these are vendor-reported claims and should be validated by prospective customers before relying on them for procurement decisions.

Key product modules/capabilities described by Faro include:

• Study Designer workspace for collaborative, digital-native protocol design and feasibility impact analysis
• Document Authoring with AI-assisted draft generation and reusable content modules
• Workflow Automation for downstream artifacts such as automated EDC build and other startup workflows

Official product positioning emphasizes converting protocol documents into structured protocol definitions that downstream systems can consume.

Primary official sources:

• Vendor homepage and platform overview
• Product feature pages (Study Designer)
• Product feature pages (Study Design)