- Company sizes or stages where this product is overkill or insufficient
- Solo practitioners or very small clinics that need an immediately deployed, self-serve AI scribe with published pricing may find a demo-led, integration-focused sales model unsuitable.
- Industries or use cases where competitors are clearly superior
- U.S. health systems standardized on Epic/Cerner that require vendors to demonstrate extensive enterprise-scale Epic/Cerner integration references may prefer vendors with those established enterprise footprints (for example, ambient-scribe vendors with broad enterprise references).
- UK NHS buyers whose procurement and governance needs are tightly coupled to DTAC/MHRA pathways may prioritize vendors with established NHS procurement experience.
- Technical requirements that this product cannot meet
- If a buyer requires confirmed native integration with bidirectional structured writeback into specific EHR fields, they should verify Delphyr's integration depth for the target EHR before selecting the product.
- Organizations requiring HIPAA BAAs and U.S. data residency should verify suitability; the vendor's publicly stated posture emphasizes European processing.
- Budget constraints that make alternatives more appropriate
- Buyers needing published, predictable pricing should consider vendors that publish per-user plans or self-serve options.
- Specific workflows or integrations where the product falls short
- If the primary need is only ambient transcription and templated note drafting without deeper retrieval/summary needs, simpler embedded or extension-based alternatives may be more appropriate; in Bricks specifically, Noteless provides browser-extension-based SOAP note drafting that overlaps with certain workflows.
- Red flags in the buying process
- Certification statuses presented as "in progress" without clear timelines, certificate scope, or independent evidence
- Lack of published security documentation (SSO/SCIM, audit logs, encryption details) to support early-stage procurement evaluations
- Current limitations acknowledged by the vendor
- MDR certification is presented as "in progress" in vendor materials. This indicates a current regulatory process rather than a completed certification (public status should be verified at contract time).
- Features on the roadmap (not yet available) - note estimated dates if available
- MDR certification expectations are referenced in vendor content; buyers should verify the current status and timelines at the point of evaluation.
- Scale limitations (at what volume/size does it break down?)
- No public documentation of scale limits or performance degradation by volume was identified.
- Security or compliance gaps
- Publicly verifiable proof of SOC 2 Type II or ISO certificate identifiers and the scope of audits was not found in the materials reviewed.
- Technical debt or architectural limitations mentioned in reviews
- No independent reviews were located that discuss technical debt or architecture constraints.
- API limitations or integration constraints
- The vendor emphasizes integration-first deployment, but public materials do not provide a comprehensive list of supported EHRs, standards compliance (FHIR/HL7) details, or specific writeback capabilities; buyers should request integration specifications and reference implementations.