HealthBird / OneNest — Technology, Product & Brand IP Assessment

Conservative Valuation Framework

Purpose
A realistic evaluation of what has been built
This presentation provides a conservative, realistic evaluation of what has been built across HealthBird / OneNest product lines and what those assets may be worth as intellectual property, operational systems, and brand/IP today, given:
  • much of the platform was built in 2021–2023,
  • meaningful modernization + reactivation work is required to return systems to prior operating levels,
  • the original engineering team is no longer active, increasing reliance on documentation and structured knowledge transfer,
  • and certain features rely on third-party services whose terms and activation status may need to be reset.

This is not a formal appraisal, audit, or legal opinion. It is an indicative valuation framework intended for internal planning and shareholder visibility.
Asset Inventory
What the company has
The company's asset value is spread across six categories:
1
Software systems
Source code, backend services, portals, mobile apps
2
Infrastructure & operational tooling
AWS environments, configurations, deployment patterns
3
Integrations & workflow logic
Connectors, mapping layers, orchestration logic
4
Documentation & build history
Atlassian tickets, roadmaps, prototypes, technical notes
5
Brand/IP
Names, domains, trademarks where applicable, marketing assets, positioning
6
Go-to-market assets
Funnels, creative assets, campaigns, distribution readiness
Each category holds value, but also carries constraints due to age, dependencies, and reactivation effort.
Technical Foundation
Shared architecture & operational reality
Technology foundation
  • Backend: built largely on PHP + Laravel, implementing business logic, APIs, and workflow orchestration across products.
  • Infrastructure: hosted primarily on AWS, supporting compute, storage, and operational tooling (specific services to be confirmed via inventory).
  • Data & workflows: shared patterns across identity, membership/households, policy and servicing objects, subscriptions/entitlements (where applicable), and document handling.
  • Documentation: extensive documentation and project history exist in Atlassian (tickets, roadmaps, prototypes, technical notes), which materially reduces "knowledge gap" risk given team turnover.
What this means for value
A Laravel codebase with proven patterns and data models can save significant build time versus starting from scratch—even if modernization is required.
Strong documentation increases the likelihood the systems can be reactivated efficiently, but documentation is only fully valuable when it corresponds to reproducible deployments and current environment knowledge.
Main discounts applied
  • Modernization discount: UI/UX refresh, dependency updates, security hardening
  • Reactivation discount: environment setup, keys/credentials, service stability
  • Dependency discount: vendor/API reliance and transferability uncertainty
  • Knowledge discount: reliance on documentation vs. active team
Asset A
PolicyNest Broker CRM + Enrollment Workflows
What it is
PolicyNest is positioned as the broker-facing operating system: broker CRM workflows integrated with the broader HealthBird ecosystem. Materials also describe enrollment and benefits management functionality designed to reduce service inquiries through digital servicing.
Core components
01
Identity & role management
Agent/broker accounts, admin and support roles, permissions, org structures (where implemented)
02
Client record system
Household/family grouping logic, contact history, notes, attachments, policy/enrollment record linkage
03
Workflow engine
Lead → application → enrollment → renewal pipelines, tasks, follow-ups, assignments, escalations, event/audit history
04
Enrollment & product workflow layer
Structured intake and validation logic, document capture and attachments, integration endpoints for enrollment/sales flows
05
Operational reporting
Funnel visibility, workload reporting, agent productivity views (depends on instrumentation maturity)
Why it retains value
  • B2B workflow logic and data models are expensive and time-consuming to recreate.
  • Even when UI requires refresh, the underlying workflow and servicing scaffolding remain valuable.
Why valuation is conservative
  • Modernization likely required (UI/UX, libraries, security).
  • Integrations may require revalidation/reactivation.
  • Knowledge transfer is more expensive without the original team, even with documentation.
Indicative value range (PolicyNest)
$250K
Estimated value today
Lower range
$1.2M
Estimated value today
Upper range
$500K
With documentation pack
Lower range with structured restoration plan
$2.0M
With documentation pack
Upper range with structured restoration plan
Asset B
HealthBird Enrollment Platform + Consumer Mobile App
What it is
HealthBird is positioned publicly as a guided insurance enrollment experience. Materials describe a broader member app strategy: policy management, claims, RX features/discounts, family dashboard ("HealthNest"), and engagement features.
Core components
Member identity + household
Enrollment funnel
Application intake + submission logic, plan browsing/recommendations (as implemented)
Insurance wallet
Digital cards and plan details, document vault patterns
Provider access
Search + appointment flows (often vendor-enabled)
Medication / Rx tools
Discount flows and/or medication list management (often vendor-enabled)
Notifications & support
Notification patterns and member servicing workflows
Why it retains value
Identity, policy objects, document vault patterns, and member servicing UX are meaningful accelerators.
The "hard parts" are less the UI and more the workflow and data model glue.
Why valuation is conservative
  • Mobile apps require frequent refresh (SDK/store/OS changes).
  • Vendor-enabled features may require reactivation and re-testing.
  • Operations release pipelines and instrumentation may require rebuilding.
Indicative value range (HealthBird platform + app)
25%
$150K – $900K
Estimated value today
50%
$350K – $1.5M
With documented restoration plan + stable deployments
Asset C
MedPass Wellness Subscription + Marketing/IP Package
What it is
MedPass is positioned as a subscription wellness membership bundling multiple benefits (telehealth, mental health, fitness/nutrition/wellness, Rx discount). Materials position it as a comprehensive membership with subscription/B2B pathways.

What exists beyond software (important)
MedPass value includes: the brand name + domain + positioning, marketing creative assets (design, copy, campaigns, content), subscription packaging (tiers, offers, conversion flow), and support/onboarding content and operational scaffolding.
Operational/financial reality to acknowledge
Some benefits are vendor-backed, and there may be outstanding vendor payments that can affect the near-term ability to fully deliver benefits until relationships are reactivated/settled under applicable terms. This impacts operability but does not eliminate the underlying IP value.
Core components
Subscription & entitlements
Benefit delivery orchestration
Vendor-enabled
Wellness engagement layer
As implemented
Support layer
Help flows and account support patterns
Why it retains value
  • The go-to-market packaging and marketing footprint reduce re-launch effort.
  • The product is already structured as a membership, not a concept.
Why valuation is conservative
  • Vendor dependence: benefit delivery may require reactivation.
  • Subscription/payment operations must be stable and documented.
  • UI/ops modernization likely required.
Indicative value range (MedPass software + brand + marketing assets)
$350K
Estimated value today
Lower range
$2.0M
Estimated value today
Upper range
$750K
With reactivation plan
Lower range with operations runbooks
$3.0M
With reactivation plan
Upper range with operations runbooks
Asset D
CareBird EHR/HIS — Ecuador Modules + Limited U.S. Beta
What CareBird is (reality-based description)
CareBird is a partially completed EHR/HIS-style platform with two distinct threads:
Ecuador-focused build (more complete, market-specific)
  • Built to match Ecuador-specific requirements and workflows.
  • Approximately four modules are fully completed for the Ecuadorian market (as represented internally).
  • This workstream is valuable primarily as Ecuador-specific implementation IP, not as a portable US-ready EHR.
U.S.-market build (less complete, never commercialized)
  • A front-end and a simple back-end reached beta but was not taken fully to market, largely due to focus on Ecuador.
  • The U.S. version should be treated as incomplete and not production-ready.
What exists today (what can be valued)
  • Completed Ecuador modules (highest-confidence portion)
  • Early-stage US beta scaffolding (lower-confidence portion)
  • Documentation, roadmaps, prototypes, and implementation notes (critical due to team turnover)
Why it is discounted more than other assets
  • Less complete overall compared to PolicyNest/HealthBird/MedPass
  • Highly market-specific for Ecuador
  • Higher finish-cost burden to become a generalized product
Indicative value range (CareBird)
15%
$75K – $600K
Estimated value today
35%
$200K – $1.5M
With clean documentation export + organized module map + reproducible deployment
Asset E
TravelBird Travel Insurance Platform
What it is
TravelBird is positioned as a travel insurance quoting/enrollment product and is referenced in shareholder materials as launched in LATAM markets (as stated). It should be viewed as a productized distribution platform whose operational readiness depends on having an active carrier/partner relationship.
Core components
1
Quote flow UI
Travel details intake (dates, destination, traveler info), plan comparison and presentation, conversion-optimized checkout patterns (as implemented)
2
Enrollment / issuance workflow
Application capture, confirmation flows and policy document delivery patterns, status tracking (where implemented)
3
Admin configuration
Plan setup/offer configuration (where implemented), reporting dashboards (where instrumented)
4
Carrier integration adapter pattern
Data mapping and validation rules, error handling and retry patterns (where implemented), partner-specific issuance workflow logic

Operational constraint to acknowledge
The prior carrier relationship backing TravelBird (Continental Assist) is not currently operating with HealthBird. TravelBird therefore requires either re-establishing that relationship, or swapping in a different carrier/partner.
Why this does not remove the platform's value
A carrier relationship is a dependency, but the platform's underlying value remains in:
  • the quote/enrollment UX,
  • the admin tooling,
  • and the reusable integration adapter structure.
A carrier swap is feasible, but it is real work (mapping, compliance, testing).
Indicative value range (TravelBird)
$150K
Estimated value today
Lower range
$900K
Estimated value today
Upper range
$400K
With carrier swap plan
Lower range with full integration map + test evidence
$2.0M
With carrier swap plan
Upper range with full integration map + test evidence
Asset F
AI Tools Assistant Modules
What it includes
Materials reference AI assistant and AI-enabled features (document scanning, symptom checker, engagement tools, mental health support/mood tracking).
Core components
Orchestration logic and routing
Embedded UI components
Document parsing pipelines
Where implemented
Usage instrumentation
Where present
Indicative value range (AI tools bundle)
Estimated value today
$25K – $200K
With integrated deployments + usage evidence
$75K – $600K
Supporting Assets
Shared Infrastructure + Documentation
What this includes
AWS environments/configuration
Deployment patterns
Shared services
Internal tooling
Atlassian documentation
Tickets, roadmaps, prototypes, technical notes
Why it matters
Strong documentation reduces the "knowledge gap" created by team turnover and supports a structured restoration effort.
Indicative value range (shared layer)
30%
$150K – $900K
Estimated value today
60%
$300K – $1.5M
With clean exports + reproducible runbooks

These values can be treated as embedded across assets or valued as a separate shared layer depending on how the assessment is presented.
Brand & Marketing Assets
Naming IP + Marketing Libraries
What this includes
  • Brand names, domains, and brand identity systems
  • Marketing assets, funnels, campaigns, content libraries
  • Consumer and broker-facing positioning
Conservative treatment of brand value
Brand value is real but harder to prove without objective indicators. Therefore it is best treated as:
  • a separate line item (names/domains/marketing asset libraries), and
  • a multiplier that strengthens reactivation potential when combined with functional software.
Indicative brand/IP value ranges (conservative)
$100K
HealthBird brand
Lower range: brand + domain + marketing assets
$750K
HealthBird brand
Upper range: brand + domain + marketing assets
$100K
MedPass brand
Lower range: brand + domain + marketing assets
$600K
MedPass brand
Upper range: brand + domain + marketing assets
$25K
TravelBird brand
Lower range: brand + domain + marketing assets
$250K
TravelBird brand
Upper range: brand + domain + marketing assets
Summary
Indicative values (conservative)
PolicyNest
$250K – $1.2M
HealthBird app + platform
$150K – $900K
MedPass (software + marketing/IP package)
$350K – $2.0M
CareBird (Ecuador modules + limited US beta scaffold)
$75K – $600K
TravelBird
$150K – $900K
AI tools bundle
$25K – $200K
Shared AWS/Laravel infra + documentation layer
$150K – $900K (if separated)
Brand/IP package (aggregate)
$225K – $1.6M (conservative)

Reminder: These figures are not strictly additive, because shared infrastructure and documentation support multiple product assets.
Total Portfolio Value
$1.375M
Low Range Total
Conservative estimate
$4.84M
Mid Range Total
Average of low and high
$8.3M
High Range Total
Optimistic estimate
Note: These are conservative estimates and not strictly additive due to shared infrastructure.
What strengthens confidence
Supporting materials that increase valuation confidence
The most impactful supporting materials are:
AWS infrastructure inventory + architecture map
Repo/module inventory
Laravel services, integrations, shared libraries
Atlassian exports/index
Tickets, roadmaps, prototypes, runbooks
Vendor dependency matrix
What each vendor provides, what reactivation requires
Marketing/brand asset library inventory
Creative files, campaigns, funnel pages, analytics
Closing summary (realistic but constructive)
The company retains meaningful value in its software systems, operational workflows, documentation base, and brand/marketing assets—even though modernization and reactivation work would be required to return systems to prior operating levels.
Valuation is conservative because it recognizes age of components, dependency reset work, team continuity realities, and the cost of restoring stable operations. The strongest value is concentrated in PolicyNest workflows, the HealthBird member experience foundation, MedPass productization + marketing footprint, and TravelBird as a partner-swappable distribution platform; CareBird is included as a smaller, more market-specific asset with limited completeness outside Ecuador.