Forus

Name: Forus
Brand: Forus
Rating: 4.7 (5 reviews)

AI NativeLeader

Accelerating medicine for the people who need it, prescribe it, and create it.

Est 2023|Valuation $3B|Raised $197.4M|12 Ref Customers

LinkedIn 18K|Web traffic 33K|FTEs 39|HQ New York, New York, US

Published Sep 16, 2026

01Common complaints

- Company sizes or stages where this product is overkill or insufficient - Very small practices with low PA volume may be adequately served by incumbent ePA tools that are already available through EHRs. - Industries or use cases where competitors are clearly more suitable - Organizations whose workflows are optimized around CoverMyMeds or Surescripts inside their EHR and that primarily require standardized ePA submission rather than a broader operational layer. - Technical requirements that this product cannot meet (based on public documentation) - If your procurement policy requires explicit data residency guarantees, a public security architecture, or a public compliance pack listing SSO/SAML/SCIM/audit logs and penetration-test summaries, these were not found in the public materials and may be unavailable without an NDA and vendor security review. - Budget constraints that make alternatives more appropriate - Although the vendor states there is no direct charge to providers, the practical costs of staff time, implementation, and change management may make existing EHR-native ePA workflows more suitable for organizations that cannot allocate resources for adoption. - Specific workflows or integrations where the product may not be ideal - If an insurer requires a specific specialty pharmacy and any intermediate routing adds friction, patient-perceived delays or confusion may result. - Red flags in the buying process - Lack of transparency on funding sources, data use, or routing incentives should prompt contract-level clarification (BAA, DPA, subprocessor list, and explicit data use restrictions) before entering production. - Current limitations acknowledged by the vendor - The vendor indicates the product only supports e-prescriptions transmitted through EHR systems. - If an EHR does not support integration, practices may need to provide documentation uploads when required, reintroducing manual steps. - Roadmap / future capabilities - No detailed, dated public roadmap was identified in the materials reviewed. - Scale limitations - Not publicly documented in accessible sources. - Security or compliance gaps - The vendor states compliance with HIPAA and SOC 2 Type II; however, detailed public documentation of enterprise security controls (SSO/SCIM/audit logs) and data residency options was not found. - Technical debt or architectural limitations mentioned in reviews - There is insufficient third-party technical review coverage to assess technical debt or architecture at scale from public sources. - API limitations or integration constraints - Public materials do not clearly document supported integration standards (FHIR/HL7/SMART-on-FHIR) or the exact methods used for EHR connectivity; this should be validated during technical due diligence.

Deal disqualifiers: what makes a POOR fit

Organizations that require publicly documented enterprise security controls (SSO/SCIM/audit logs) prior to engagement and cannot obtain these under NDA
Practices with policies that prohibit third-party routing influence or outsourcing of operational steps
Use cases that depend on non-electronic prescriptions; the vendor indicates the product supports electronic prescriptions routed through the EHR

02Why they buy

- Capabilities reported by customers and emphasized by the vendor - Customer testimonials and vendor materials report reductions in staff administrative time and reduced uncertainty in PA handling. - Features and capabilities that differentiate the product from some competitors - The vendor emphasizes a broader operational scope that includes appeals letter generation, pharmacy routing, enrollment in affordability programs, and patient communications, in addition to PA initiation. - Areas where independent evidence is limited - Independent third-party review coverage is sparse; differentiation is primarily supported in public materials by vendor-published case studies and testimonials rather than broad independent reviews. - Areas where competitors have documented advantages - Incumbent vendors have established network effects, standardized integrations, and deeper embedding within many EHRs and pharmacy networks.

03Field reports

Direct quotes (vendor site testimonials)

- "The difference I feel today compared to before is honestly just a huge sigh of relief. I prescribe what is right for my patient, click Forus, and send it. No more worrying about rejections." — testimonial on the vendor homepage. - "We’ve had multiple patients who tried for months at another practice and couldn’t get approved. We were able to get it done. When they ask how, staff say they used Forus." — Nicole Bartlett, Clinical Manager & Biologics Coordinator (homepage). - "Before Forus, we were spending a large portion of our day on the phone — now it’s down to a much smaller portion." — Eyana Walker, Practice Manager (homepage).

Direct quotes (community/social)

Negative/concern (patient experience; delays and control over routing)
- In a patient forum thread describing perceived delays and routing concerns, a poster describes being contacted by the vendor after an appointment and feeling that it may have delayed access; another commenter suggested requesting that prescriptions be sent directly to an insurer-mandated specialty pharmacy rather than routed through a third party.

Review platforms (attempted but limited/inconclusive)

Searches did not surface a dedicated Forus listing on widely used review platforms in accessible results; searches returned general platform pages or unrelated similarly named entities.

Reasons customers chose the product (inferred from vendor materials)

Practices appear to adopt the product to reduce manual administrative work (forms, faxes, calls), to accelerate PA submissions and appeals, to obtain real-time tracking and patient messaging, and because the vendor states the product is offered at no direct charge to providers.

Reasons customers left or potential churn drivers

No systematic churn analysis or offboarding reviews were identified in publicly accessible sources.
Community posts indicate potential failure modes, such as perceived delays in fulfillment, confusion about pharmacy routing, or misalignment with insurer-mandated specialty pharmacy workflows.

Specific outcomes customers reported (with metrics when available)

Vendor- or investor-published metrics include claims of faster PA approvals (examples include cited large proportional improvements), and case-study style reports of increased throughput (e.g., substantial increases in PAs processed per day). Methodologies and independent verification were not provided in the public materials reviewed.

Vendor case studies (examples)

- "Faster approvals & stronger appeals: Family Allergy & Asthma’s prior authorization transformation" - The case study describes changes in denial cycles and claims that the vendor automatically retrieves clinical history to generate stronger appeal letters. - Critical note: mechanisms and success-rate improvements are presented narratively; independent benchmarks or audited methodologies are not provided. - "How a GI Biologics Coordinator increased her PA throughput" - This case study reports a several-fold rise in daily prior authorizations after switching from manual tools. - Critical note: reported throughput gains may result from workflow redesign rather than the tool alone; baseline comparability, case-mix, and independent controls are not shown.

Investor/VC narrative metrics

Investor and partner materials cite provider-reported reductions in PA turnaround time and nursing administrative workload.
Critical note: these metrics are not presented as results of independent studies and may reflect selected or best-case customers.

Mixed results / struggled projects

No formal public case studies describing failed implementations were found in the accessible materials.
Community discussion indicates that reduced provider administrative work does not guarantee a consistently improved patient-perceived experience; routing and payer policies remain potential bottlenecks.

04Best fit

Company sizes

Likely relevant customer profiles (inferred):
- Specialty practices ranging from single-site clinics to multi-site specialty groups.
- Health systems may consider the product, but would require detailed security and integration diligence.

Industries and verticals where adoption is strongest

Specialty outpatient practices with a high prior authorization burden and frequent specialty medication usage, including:
- Dermatology
- Gastroenterology
- Allergy & asthma

Roles and personas

Decision makers
- Practice administrators
- Clinical operations leaders
- Specialty pharmacy/biologics program managers
End users
- Medical assistants and prior authorization staff
- Biologics coordinators
- Prescribers seeking a simplified submission workflow

Pain points and challenges the product addresses

High administrative overhead (forms, calls, faxes)
Denials requiring appeals and complex documentation
Lack of status visibility during authorization workflows
Patient drop-off due to delays or affordability barriers

Qualification criteria: what makes a GOOD fit

High prior authorization volume and frequent appeals
Consistent workflows where automation can be templated and improved over time
Willingness to standardize internal processes and permit an external platform to manage defined steps under contractual terms

Real customer examples

Family Allergy & Asthma (vendor case study)
Digestive Health Specialists (vendor case study snippet)
Optima Dermatology / Goodman Dermatology (vendor homepage testimonials)

05The pitch

What the product does (core value proposition in objective terms)

- Forus (formerly Tandem) is a healthcare workflow automation product focused on reducing administrative time from prescription to final fulfillment by automating steps such as benefits verification, medication prior authorizations (PAs), appeals, enrollment forms, specialty pharmacy routing, and patient communications. - The vendor presents the product as covering multiple steps across the medication access workflow and states it is offered at no direct charge to providers and patients.

Target market and market positioning

- Primary users: prescribing practices and their staff (medical assistants, biologics coordinators, practice managers) responsible for medication access workflows. - Adoption appears strongest in specialties with high specialty-med and biologic volume (e.g., dermatology, gastroenterology, allergy/asthma), based on vendor case studies and customer testimonials. - Forus is described by the vendor as a workflow automation layer intended to replace manual ePA tools and fax/phone workflows and to provide automated processes with human oversight where necessary.

Get a comprehensive analysis of Forus including market position, competitive landscape, adoption trends, and peer benchmarks.

Download full report →