Connect with COBALT

How quickly can BLUE deploy into a new acquisition?

For portfolio companies activated under an existing COBALT fund relationship, BLUE deployment begins within 5–10 business days of BAA execution and data environment provisioning. The change of ownership and day-one compliance protocols within BLUE are specifically designed for rapid deployment at acquisition close. Initial compliance baseline, provider re-enrollment initiation, and payer contract review begin in the first 30 days.

Does each portfolio company get a separate data environment?

Yes — without exception. Every portfolio company under COBALT receives its own isolated data namespace, its own BAA, and its own independent BLUE deployment. There is no shared data environment between portfolio companies. Fund-level analytics are constructed from anonymized aggregates only — no identifiable company data is exposed at the GP layer or across portfolio company boundaries.

What happens at exit — does the portfolio company keep BLUE?

At exit, the portfolio company's BLUE deployment can be structured for transfer to the acquiring party or wound down, depending on the transaction terms. COBALT's exit readiness infrastructure generates documentation packages — compliance history, audit trail exports, HIPAA program attestations — specifically designed to support buyer due diligence. The data environment separation ensures a clean exit from the fund's COBALT environment without disruption to ongoing company operations.

We have 12 portfolio companies but only 4 are healthcare. How does pricing work?

COBALT pricing applies only to healthcare portfolio companies — defined as companies in scope for HIPAA compliance and operating as covered entities or their business associates. Non-healthcare portfolio companies in a mixed fund are not counted toward the per-company fee. The fund base fee covers the GP-level infrastructure regardless of total portfolio size. We'll confirm the applicable company count in discovery.

Can COBALT support a due diligence sprint on a target we haven't acquired yet?

Yes. DD sprint capacity is part of the fund-level COBALT infrastructure. For targets under active LOI or exclusivity, COBALT can deploy compliance, revenue cycle, payer contract, and clinical operations assessment capacity without a full per-company activation. This is structured as a fund-level engagement — no separate BAA with the target entity is required unless PHI access is needed, which is assessed case by case.

We already have some internal ops capacity. Does COBALT replace or augment it?

COBALT is designed to work alongside existing internal operating teams. Most PE funds with internal ops capacity find that COBALT extends coverage depth at the individual company level — particularly for HIPAA compliance, payer contract management, and revenue cycle optimization — without requiring an expansion of headcount. COBALT does not displace internal operators; it provides the infrastructure that makes them more effective across a larger portfolio.

What does "Aether" mean in the COBALT context?

Aether is CYPHR's proprietary AI operating architecture — the cross-portfolio intelligence layer that aggregates anonymized signals from all portfolio company deployments to produce fund-level benchmarks, compliance pattern recognition, and operational intelligence. Aether operates strictly on anonymized data. No identifiable portfolio company data crosses entity boundaries. The intelligence Aether generates becomes increasingly precise as the portfolio grows.

What's the minimum engagement commitment?

COBALT engagements are structured on annual commitments at the fund level. Per-company activations within the fund relationship can be added or deactivated on a rolling basis with 30-day notice, consistent with portfolio activity. There is no minimum portfolio company count — the fund base fee of $35,000/month covers the GP infrastructure regardless of the number of active portfolio company deployments at any given time.