- Company sizes or stages where this product is overkill or insufficient
- Organizations with low patient volume, a single facility, and manageable duplicate rates may not require a full consulting engagement.
- Industries or use cases where competitors are clearly more aligned
- If an organization requires a persistent identity resolution/hMDM platform integrated into multiple enterprise data pipelines (beyond episodic clean-up), platform vendors (e.g., Verato) may be a better fit.
- Technical requirements that this product cannot meet
- If procurement requires publicly documented SOC 2 / ISO 27001 evidence during early vendor screening, Just Associates may be blocked unless they can provide artifacts under NDA.
- Budget constraints that make alternatives more appropriate
- If predictable low-cost tooling is required, internal process improvements and EHR-native tuning (DIY) may be more feasible than external remediation teams.
- Specific workflows or integrations where the product falls short
- If an organization needs real-time, automated matching APIs and developer-oriented integration, a technology vendor may align better than a consulting-led model.
- Red flags in the buying process
- Lack of transparent pricing and limited independent reviews increases diligence burden.
- If the vendor cannot clearly define validation methodology for “duplicate found” and “false positive” rates, ROI claims may be difficult to validate.
- Current limitations acknowledged by the vendor
- The vendor does not publish an explicit list of known issues in the accessible materials.
- Features on the roadmap (not yet available) — note estimated dates if available
- Not publicly documented.
- Scale limitations (at what volume/size does it break down?)
- Not publicly documented. Services scale is likely bounded by staffing capacity; buyers should ask about throughput (records/day), validation staffing, and concurrency.
- Security or compliance gaps
- Public-facing SOC 2 / ISO 27001 documentation was not found in the accessible materials.
- Buyers handling PHI should require clear contractual terms (BAA), security controls, secure transfer methods, and auditability.
- Technical debt or architectural limitations mentioned in reviews
- Not available in public sources.
- API limitations or integration constraints
- Not available in public sources.