Strategy memo · Healthspan Wealth · June 21, 2026

The Category Is The Company

Healthspan can be a useful advisor feature or a real enterprise software company. The difference is whether it sells data about longevity or the operating system for what a wealth firm does next.

Healthspan is standing at the most dangerous point in a software company's life: the product is useful enough to be explained incorrectly. The obvious explanation is healthspan data for advisors. That sounds focused. It is also too small. Data is an input. The company is only interesting if it owns the institutional response that follows.

The buyer is not the individual advisor who wants another clever tool. The buyer is the scaled wealth firm trying to make a high-trust service model repeatable across offices, advisors, family members, compliance boundaries, and approved vendors. That is a very different company.

The strategic mistake is to ask how many firms might buy the assessment. The right question is how many firms need a standard way to act when the assessment matters.

First, The Market Disappears

The adviser market looks large until it is useful. The ADV universe has more than 16,000 firms with AUM, but most of those firms are structurally irrelevant for this wedge. They are too small, too advisor-led, or too simple operationally to need a firm-controlled transition layer.

Then the market shrinks. The broad enterprise-adjacent universe is 556 firms. The realistic expansion pool is 196. The tight SEIA-neighborhood market is 92. The first named-review list is 39. This sounds like a problem only if Healthspan is a point solution. For enterprise software, it is the point: the market is smaller because the buyer is more valuable.

The market shrinks; the account gets better Firm count falls as office count, employee count, compliance burden, and process variance rise. All advisers Enterprise buyer Complexity rises 16,309 adviser firms with AUM 556 broad enterprise-adjacent firms 196 core + tight candidates 92 tight neighborhood 39 first named-review list Tight-segment median $18.9B AUM 343 employees 44 offices
Figure 1. The real market is not "all RIAs." It is the small group of firms where operational complexity creates enterprise software budget.

Then The Gap Appears

The incumbent stack is not weak. That is why the opportunity is attractive. CRM is already adopted. Financial planning is already adopted. Document management, portfolio reporting, custody, trading, compliance, and AI notetaking are all served by existing vendors. A weak founder looks at that map and sees no room.

The stronger reading is that the stack has a hole in the middle. None of those categories owns the moment when a household signal becomes firm-approved work. CRM records the relationship. Planning models the money. Documents store artifacts. AI tools summarize meetings. What is missing is the governed path across those systems: signal, trigger, coordinate, route, and prove.

The stack is crowded around the work, not inside it Healthspan should integrate with incumbents and own the transition workflow that crosses them. CRM Salesforce · Redtail · Wealthbox 91% Planning eMoney · RightCapital · FP Alpha 83% Documents ShareFile · Box · DocuSign 51% Portfolio / custody Orion · Tamarac · Schwab Advisor AI Jump · Zocks · Fireflies 43% Vendors / specialists Estate · care · tax · insurance Healthspan target layer Household Transition Orchestration Signal → trigger → coordinate route → complete → prove
Figure 2. The category is not another tool in the stack. It is the path through the stack when a household transition becomes firm work.

Then Pricing Becomes Destiny

This is where the story becomes unforgiving. If Healthspan is sold as healthspan data, the market will price it like a specialty module. That can be useful. It may even be a good wedge. It is not the company.

At $50,000 ACV, 20% penetration of the broad 556-firm market is only $5.6 million of ARR. At $250,000, the same market is $27.8 million. At $500,000, it is $55.6 million. The strategic question is therefore not "what should we charge?" It is "what must the product become for the enterprise buyer to believe this is infrastructure?"

Pricing is not a monetization decision; it is a category decision ARR at 20% capture of the 556-firm broad universe. $0 $20M $40M $60M serious vertical SaaS territory $50k ACV $5.6M priced like a feature $250k ACV $27.8M priced like firm workflow $500k ACV $55.6M priced like infrastructure Assessment content, reports, reminders weak standalone ceiling Operating layer roles, evidence, CRM path, vendor routing the enterprise ACV story
Figure 3. The same market supports different companies depending on whether Healthspan is evaluated as a feature, workflow, or infrastructure.

Finally, The First Customer Becomes The Architecture

The first scaled rollout should not be treated as a custom implementation to get through as quickly as possible. It is the raw material of the product. Salesforce constraints, security review, SSO expectations, advisor adoption, contact-only family access, approved resources, vendor governance, document requests, AI drafts, and evidence logs are not side quests. They are what the enterprise buyer is actually buying.

The lesson is simple and hard: lead with enough service to understand the institution, then turn each recurring constraint into a product surface. If Healthspan does that, longevity is not a niche. It is the wedge into the operating layer for high-trust household service.

The next twelve months should prove repeatability, not breadth Do not chase every firm or every life event. Prove the deployment machine. 1 Make SEIA measurable advisors, households, journeys, docs, vendors, time-to-action 2 Package the packet security, CRM mapping, SSO, AI handling, roles, evidence 3 Win the second firm prove abstraction beyond first-customer decisions 4 Expand domains estate, care, tax, insurance, family governance, special needs The product is the repeatable deployment of a firm standard of care.
Figure 4. The proof path should convert implementation knowledge into product architecture before broad market expansion.
Do nowFinish the reference scorecard: adoption, household activation, journeys, documents, resources, vendors, and evidence completeness.
Do nextSell one 30-day enterprise sandbox assessment to a second scaled firm using the same packet.
Build only what repeatsTurn recurring services into role models, templates, logs, controls, onboarding, and executive reporting.
AvoidDo not call this health data. Do not chase all 556 accounts. Do not become generic advisor AI.

Closing Thesis

Healthspan should become the firm-controlled operating layer for the moments when wealthy households need coordinated guidance across aging, health, estate, care, insurance, family, tax, and service-provider decisions. The firm owns the standard of care. The advisor owns the relationship. Healthspan should own the sequence that makes both scalable.

Sources and caveats. Scenario math is directional. Public price points are list-price signals, not negotiated enterprise contracts. Adoption percentages come from the T3/Inside Information advisor-community survey.