Proposal: Allodial and Hippocrates Wellness

In brief

We propose that Allodial take over all development of HNS now, stabilize and secure it, and then build HOS, the Hippocrates Operating System, to replace it one module at a time while your teams keep working. On top of HOS come the applications your teams have asked for: an employee app, a guest app, Hippocrates at Home, an alumni and ambassador app, and a new website with online booking.

We offer three options. They differ in pace and cost, not in quality. The first 90 days are the same in each, at our current rate of $25,000 a month.

Why we are doing this

Hippocrates' mission matters to us personally. Decades ago, Hippocrates' work in San Diego made a lasting difference in the lives of members of Jesse Wilson's family. Helping Hippocrates run on software worthy of that mission is work we want to do.

That is why our initial engagement of $25,000 a month is a below-market, friendly rate. We will keep offering Hippocrates most-favored-customer rates: no customer will pay less than Hippocrates for the same work on the same terms.

We also have to be realistic about our costs. At full corporate salaries, a three-person senior team like ours would cost about $1 million a year. Each of us also directs a fleet of AI agents, and some companies now budget AI tooling at about the same level as salaries. Allodial pays for all of its AI tooling, so that cost is built into our rates. Together, the market cost of this team is about $2 million a year, or roughly $167,000 a month. Every option below is a fraction of that.

What we have done so far

Since our call on October 7, working on our copy of the code SDSOL delivered in June, we have found 390 issues in HNS that were not in your August report and fixed 242 of them (as of October 12, 3:50 PM ET). None of these fixes is in the system your staff use yet: getting them there is the first step below.

What we will deliver

HOS architecture — Figure 1. HOS: five applications over shared services and a new core that replaces HNS module by module.

1. The first 90 days: custody, stabilization and supported platforms

Custody: Hippocrates holds its code, data, credentials and accounts, in its own name.
Stabilize and secure: the fixes reach your live system in small, reversible steps, and the most serious defects in money, bookings and scheduling are closed, each with a test.
Supported platforms: HNS moves to versions of .NET and Angular that still receive security fixes.

2. HOS, replacing HNS module by module

In order: reporting, itineraries, scheduling and events, inventory and purchasing, payments and the folio ledger, and reservations.
Each module runs alongside HNS until its records and money match to the cent, and only then takes over. HNS is retired when every module has taken over, and stays available read-only for a year after.

3. The applications, each built on HOS

Guest app and employee app (Phase 1): itineraries, schedules, change requests, clean-room requests, tasks and announcements.
Hippocrates at Home: courses, ecommerce and outreach, moved off Kajabi onto systems Hippocrates owns.
Alumni and ambassador app: referrals and commission statements, after a legal review of referral payments.
Website: a redesign first, then online booking and payment on the HOS reservations module.

How we work: speed, quality and flexibility

We would rather agree on values than on dates.

Speed. We move fast, release often and show you the results every month.
Quality. We don't trade quality for speed. Every change is tested automatically and reviewed before it merges, and every HOS module has to match HNS to the cent before it takes over.
Flexibility. In our experience, every customer asks for changes along the way, and those changes usually make the result better. We want to be able to say yes.

That is why we don't guarantee completion dates. At the start of each phase we hold a planning session with you, estimate the effort and agree the priorities. The durations below are our best estimates today, not commitments. When priorities change, the plan changes with them, and we tell you what moves.

Software is never "done". Every system needs security updates, platform upgrades, bug fixes and new features for as long as it runs. Each application we add stays in our care alongside everything before it, so the work grows as Hippocrates' software grows.

Ongoing work only grows — Figure 2. Systems in active development or maintenance over time. Each one stays in our care once started; only HNS leaves, when HOS replaces it.

Three options

The order of work is the same in every option; what changes is how much runs at once.

	Option A	Option B	Option C
Estimated time to deliver everything above	About 12 months	About 18 months	About 24 months
First 90 days	$25,000 a month	$25,000 a month	$25,000 a month
Then	$90,000 a month, months 4–12	$55,000 a month, months 4–9; $65,000 a month, months 10–18	$40,000 a month, months 4–12; $50,000 a month, months 13–24
Total during the build	About $885,000	About $990,000	About $1,035,000
Share of the market cost of the team	Up to about 54%	Up to about 39%	Up to about 30%
What it means	Several workstreams at once from early in the year; every application in use within about a year	The core first, then the applications in steps	One application at a time; the lowest monthly fee

Slower costs more in total. The longer the build, the longer HNS and HOS run side by side and the longer each finished application is maintained during the build. That is why Option C has the lowest monthly fee and the highest total.
Every option's fee rises over time as systems are added, because each one needs ongoing care.
You can change options at the start of any phase, at the planning session.

The same order of work at three paces — Figure 3. The same order of work at the three paces. Indicative: the overlap changes, the order doesn't.

Figure 4. Monthly fee by option during the build, against the market cost of the same team.

After the build

Once everything above is in use, the work continues as maintenance and new features for the systems in service. We will propose that ongoing rate at the planning session for the final phase, based on the systems in service and what Hippocrates wants next, and it will stay at most-favored-customer terms.

What the fees include, and what they don't

Included: the whole Allodial team, our AI tooling, project management, testing, security reviews, documentation and a monthly report you can check.
Not included, paid by Hippocrates directly: hosting, domains, payment processing and other third-party services, in accounts in Hippocrates' name; photography, video and copywriting for the website; legal review of ambassador payments.
Ownership: Hippocrates owns all code, data and accounts from day one.

What we need from Hippocrates

One sponsor with authority to decide priorities and approve each phase. We suggest Blake Clement.
One contact in each department, for a short weekly session while that department's module is built, and to confirm results during its parallel run.
Custody: SDSOL's handover of the code, data, credentials and accounts, using the questionnaire we have prepared.
A business-associate agreement before we work with any real guest data.
Timely decisions, so open questions don't hold up the work.

Next steps

Choose an option. You can change it later.
Sign the engagement agreement and the business-associate agreement.
Start custody, and hold the first planning session.