What has to happen next?

The first milestone is a real, timed start with a facility-defined baseline, an accountable operating record and a result the facility can inspect.

October 20, 2026 · plan

Launch the selected product scope. Real-data operation remains subject to security, source and permission readiness. Publish an honest capability view.

December 31, 2026 · goal

One signed agreement, a two-week baseline and one real start timed end to end. Separately, one clinician’s check accepted at a second facility.

March 31, 2027 · goal

Three operators or ten sites in paid pilots. Review the operating evidence and change the plan if adoption misses that goal.

Founder-set plan and goals, October 1, 2026. These dates describe intended milestones, not achieved outcomes.

The capital plan is organized around the work required to earn repeatability: product and readiness, founder-led customer development, and the evidence needed to decide what expands next.

The first operating result depends on commercial scope, product behavior, source access, security readiness and a facility team able to accept the work. These streams can advance together. Their outputs must converge on the same eligible workflow rather than produce unrelated checklists.

Commercial preparation

Confirm the buying authority, scope, pricing unit, baseline owners and agreement. Keep historical letters separate from the current paid proposal.

Operating preparation

Confirm requirements, handoffs and decision owners with the facility. Identify an end-to-end path and its immediate dependencies; continue broader mapping alongside it.

Product and source readiness

Demonstrate the permitted source and destination routes, evidence freshness, access boundaries, recovery and actual completion record for that path.

Release readiness

Complete the applicable security and activation requirements. Model approval is a separate dependency when the scope uses AI; a synthetic workflow is not real-data release evidence.

Measurement preparation

Agree the cohort, timing events, cost lines and total effort budget. The baseline must be accepted before an operating improvement is claimed.

A missing requirement can hold the affected path without holding every unrelated piece of product work. It cannot be bypassed by changing a status label or calling the same operation a test.

For the first start, retain the agreed opening event, current requirements, source evidence, named decisions, destination acceptance and proof of first worked shift. Preserve the incomplete and failed cases in the surrounding cohort so the result can be interpreted.

For cross-facility reuse, identify the eligible item, clinician permission, source freshness, the receiving facility’s requirement and its actual acceptance. Measure the repeated work avoided. A downloaded file or an internal demonstration is not that result.

For the March paid-pilot goal, report operators, sites, executed agreements, payments and activated scopes separately. Three operator relationships are not automatically ten live sites. The goal is evidence of a repeatable commercial and delivery process, with the observed cost of each deployment visible.

Interest does not become signed scope

Revisit the buying authority, urgency, pricing unit and proposed outcome. Keep the original prospect set visible and distinguish a procurement delay from a rejected value proposition.

Activation is delayed

Publish the specific unmet dependency and revised path. Continue eligible preparation and synthetic rehearsal, while preserving the real-data and action boundaries.

A start works, but support stays high

Find the repeated manual step, improve the workflow or reduce scope. Hold expansion until comparable outcomes can be delivered within an agreed effort budget.

Reuse is refused

Record why: freshness, source rights, local policy, identity or insufficient evidence. Improve the item where possible and retain the first facility’s value independently.

Benefits are too small

Reconcile the baseline and full cost with finance. Change the package or stop that deployment rather than converting staff hours into unsupported cash savings.

The broader plan includes the clinician career network, a connected facility workplace and permissioned operating intelligence. Initial career utility can develop alongside workforce operations. Wider departmental work, community participation and new intelligence buyers still need their own demand, authority, data rights and operating evidence.

The next scope should be selected for a specific connected outcome, its cost to deliver and what it teaches. A large vision can guide the data model and interfaces now without promising that every workflow ships in the first release.

The round’s priorities follow this sequence: become ready to operate, produce an accepted result, show that customers continue, and then demonstrate that the process repeats at a sustainable cost. The capital chapter connects those priorities to the financing case.