- What is a Discovery Sprint and why does it exist?
- Most healthcare software projects fail at the requirements stage. A Discovery Sprint gives you a written architecture doc, risk assessment, and buy-vs-build recommendation before any code is written — so the engagement starts with alignment, not assumptions.
- How is Product Build scope defined?
- We work with your clinical and technical stakeholders to define a fixed scope document before work begins. Milestone-based invoicing means you pay on delivery, not by the hour. Scope changes after sign-off are handled via a lightweight change order process.
- Is a HIPAA BAA included in all engagements?
- Yes. A BAA is executed before any PHI enters the build environment, on every engagement tier. For enterprise deployments, we also support DPA execution under GDPR.
- How does AXIFI SaaS pricing differ from a studio engagement?
- AXIFI is a productized SaaS platform — you license it per seat. A studio engagement is a custom build where we design and build a product to your spec. Many clients start with a Discovery Sprint and then decide which path is right for their organization.
- Do you offer pilots before committing to a full engagement?
- Yes. A Discovery Sprint is the structured on-ramp: two weeks, fixed fee, creditable toward the next engagement. For AXIFI specifically, we run structured 30-day pilots with 3–5 providers so you can evaluate it on real workflows.
- What EHR systems do you integrate with?
- We support FHIR R4 and HL7 v2 natively, covering Epic, Cerner, Athenahealth, and most major EHRs. Custom EHR integration is included in Product Build and above.