14 Kipu capabilities mapped to every facility type, archetype, and care level.
Know exactly which features to lead with for each prospect. Not every capability matters to every buyer. A PE-backed COO doesn't care about SAMHSA audit trails. An OTP compliance director doesn't care about cross-facility dashboards. Lead with what moves them.
14 capabilities. Each tagged with the facility types and archetypes where it has the highest impact.
Lead with this for: Everyone. It's the foundation.
Lead with this for: PE-backed (EBITDA impact), hospitals (margin improvement).
Lead with this for: High commercial payer mixes. Auth gaps are the #1 denial cause.
Lead with this for: PE post-M&A ("one dashboard across all acquisitions").
Lead with this for: Any OTP prospect. This is the differentiator. No competitor has this depth.
Lead with this for: OTP with dispensing integration needs. The $340K payback prevention story.
Lead with this for: OTP with upcoming SAMHSA survey or post-survey corrective action.
Lead with this for: Nonprofits with SAMHSA block grants or state funding.
Lead with this for: Mixed LOC facilities. The transition gap is where denials hide.
Lead with this for: Facilities with >20% OON payer mix. This is where the biggest revenue leakage occurs.
Lead with this for: Hospital deals where IT approval is the gate. "Additive, not replacement."
Lead with this for: OTP with automated dispensing. The integration gap is the compliance risk.
Lead with this for: OTP with take-home dose programs. This is what SAMHSA looks for first.
Lead with this for: Medicaid-heavy payer mixes (>60% Medicaid).
Which capabilities to lead with for each buyer type.
| Capability | PE-Backed | VC/Growth | OTP | Nonprofit | Owner-Op | Hospital |
|---|---|---|---|---|---|---|
| Claims Validation | Lead | Lead | Support | Lead | Lead | Support |
| Denial Management | Lead | Lead | Mention | Mention | Support | Lead |
| Prior Auth Automation | Lead | Lead | Mention | Mention | Support | Support |
| Multi-Site Dashboard | Lead | Lead | Support | - | - | Support |
| 42 CFR Part 8 Engine | - | - | Lead | - | - | - |
| Dispensing Reconciliation | - | - | Lead | - | - | - |
| SAMHSA Audit Trail | - | - | Lead | - | - | - |
| Grant Reporting | - | - | Support | Lead | - | - |
| ASAM LOC Tracking | Support | Support | - | - | Mention | Lead |
| OON Auth Workflow | Lead | Support | - | - | Lead | - |
| Epic/Cerner Integration | - | - | - | - | - | Lead |
| Dispensing Integration | - | - | Lead | - | - | - |
| Take-Home Dose Tracking | - | - | Lead | - | - | - |
| Medicaid Auto-Follow-Up | - | - | Lead | Support | - | - |
Lead = open with this capability. Support = mention after primary value prop. Mention = reference if relevant. - = don't bring it up.
For existing Kipu EMR customers, every capability gets stronger.
Existing Kipu EMR means clinical documentation, billing codes, and patient data flow natively. No HL7 mapping. No integration middleware. No data translation errors.
RCI multiplier: 1.25x for existing Kipu
Existing customers can be live in 21 days for the first facility vs. 45-60 days for non-Kipu. The EMR foundation is already built. We're adding the revenue cycle layer, not rebuilding the stack.
21 days to live vs. 45-60 for new logo
The #1 denial root cause is clinical documentation gaps. When clinical notes are already in Kipu, the RCM platform can validate documentation-to-billing alignment in real-time. No cross-system reconciliation needed.
The integration story is already told
For new logos, integration confidence is the unlock.
| EMR | Integration Method | Typical Use Case | Timeline |
|---|---|---|---|
| Epic | HL7/FHIR API | Hospital-owned BH divisions | 4-6 weeks integration |
| Cerner | HL7/FHIR API | Hospital-owned BH divisions | 4-6 weeks integration |
| Allscripts BH | HL7 interface | Multi-site residential | 3-4 weeks integration |
| Netsmart | HL7 interface + flat file | Nonprofit BH, community MH | 3-5 weeks integration |
| SimplePractice | API + flat file | Smaller PHP/IOP practices | 2-3 weeks integration |
| InSync | API | Owner-operator residential | 2-3 weeks integration |
| TherapyNotes | Flat file + API | Smaller IOP, solo practices | 2-3 weeks integration |
| Custom / Legacy | Custom HL7/flat file | State/county systems | 6-8 weeks integration |