06-reference/research

hu manity co zombie status

2026-05-18·research-brief·source: deep-research
healthcarecompetitor-scanpatient-data-sovereigntyhu-manitycautionary-talefailure-modespivotblockchain-data-rights

Hu-manity.co — pivoted-away, half-zombie status

Verdict (one line)

Pivoted-away, half-zombie. The original 2018 patient-data-sovereignty / "31st human right" / #My31 healthcare product is dead. The company is still operationally alive in a different shape — generic privacy/consent compliance SaaS ("Privacy Experience™" cookie/consent banners aimed at GDPR/CCPA compliance), 11-50 employees, LinkedIn active within last 2 months, marketing copy intact. Stuck at $5.5M pre-seed since 2018 with no follow-on funding. The healthcare-data sovereignty thesis was abandoned — the website's last press release is May 2019, the copyright header reads 2021/2022. Re-scoring against the 3-leg rubric: 0/3 on the patient-data-sovereignty + outcome-procurement wedge (was 1.5/3 thesis / 0.5/3 execution in the parent brief).

The cautionary tale gets sharper, not softer. Hu-manity pivoted from healthcare data sovereignty to generic web-consent infrastructure — exactly the shape that "patient data ownership" becomes when the operator can't make money on the healthcare leg. The failure-mode lesson: monetization of patient sovereignty rhetoric without a payer-side or outcomes-side revenue mechanism collapses into commodity consent-management SaaS, which is what Hu-manity now sells.

The question

Hu-manity.co status. Live or zombie? If live with new 2026 product, re-score. If zombie, the cautionary tale is sharper and we should harvest specific failure-mode lessons before Phase-1.

What we already know (from the vault)

What the web says

Operational pulse signals

Surface Signal
hu-manity.co homepage Copyright footer 2022 (header 2021). Marketing copy still claims "deployed on over 1 million web properties globally" but no recent dated content. Three pillar offerings shown: trust / transparency / authenticity — all generic privacy compliance language, not healthcare-data-rights language. (source: WebFetch 2026-05-18)
hu-manity.co/category/press/ Most recent press release: May 8, 2019 (Larry Smarr advisor announcement). Zero press in 2020, 2021, 2022, 2023, 2024, 2025, or 2026. The press surface is frozen. (source: WebFetch 2026-05-18)
LinkedIn company page Active. Most recent post: ~2 months ago (Meta Ray-Ban data collection critique). Posts cadence: 9-10 month gaps between meaningful posts but consistent on data-privacy thought-leadership themes. 11-50 employees. The company is still posting, just not press-releasing. (source: WebFetch 2026-05-18)
Tracxn 2026 profile Last employee count update Jul 1, 2024: 20 employees. Consistent with 11-50 LinkedIn band. (source: Tracxn)
PitchBook / Crunchbase / Preqin Total raised: $5.5M pre-seed (2018 only). No follow-on rounds in 7 years. Investors: Rockpool Investments, Frontier Growth. (Hu-manity.co PitchBook profile, Crunchbase)
Product/positioning The 2026 product is "Privacy Experience™" — a cookie/consent compliance SaaS for GDPR/CCPA/international privacy regimes. Help-center docs at hu-manityco.helpscoutdocs.com are organized around "Cookie Compliance Knowledge Base." This is commodity consent-management SaaS, not patient data sovereignty.
Healthcare positioning The #My31 healthcare app and the Betterpath Health acquisition (April 2019) are still referenced in the press archive but no current product page links to them. The healthcare-data thesis appears retired in product, not just dormant in marketing.

Founder/team signals

The pivot is mechanical, not announced. There is no public statement "we are no longer pursuing patient data sovereignty." The marketing surface still talks about "trust" and "human data rights" — but the product is cookie banners.

Convergences and contradictions

Convergences

Contradictions / surprises

Synthesis for RDCO

Re-scoring against the 3-leg rubric (DS + VBC + PI):

Leg Original (May 11) Re-score (May 18)
DS (patient-as-data-source-of-truth) PARTIAL (rhetorical strong, traction weak) NO. The current product is cookie/consent compliance for any web property — not patient-anchored health data. The DS leg has been retired in product.
VBC (value-based contract with payer) NO NO. Unchanged. Never had this leg, never built toward it.
PI (patient cash payouts from savings) PARTIAL-ASPIRATIONAL NO. Aspirational pharma-data-licensing payouts never materialized; current product has no patient-payment mechanism at all.

Updated score: 0/3. Hu-manity is no longer even a 1.5/3 thesis match. They are out of the competitor set entirely. The "closest thesis competitor" slot in the May 11 brief is now vacant.

This strengthens the parent brief's "clean white space" verdict. The closest historical attempt at the patient-data-sovereignty thesis has exited the field, leaving only Embleema (2/3 in form, 0/3 in outcome-tied substance, also stalled) as the residual proxy.

Cautionary-tale lessons — failure modes to actively avoid in Phase 1:

  1. Rhetoric-without-revenue trap. Hu-manity built the "31st human right" rhetorical frame, the #My31 app, the Magna Carta press releases, the UN appearance — all of which generated press but none of which generated revenue. Healthcare-data licensing to pharma never reached the volume needed to pay patients meaningfully. The brand kept the rhetoric and pivoted the product underneath. Lesson for RDCO: the patient cash payout (PI) leg must be operationally specified before product launch, not after. If we can't show patient $-per-month math at concept-stage, we are repeating Hu-manity's path.

  2. No payer-side revenue = collapse to commodity SaaS. Without a VBC contract structure, the only revenue stream was selling de-identified data to pharma. That market is dominated by Datavant/IQVIA at scale and PicnicHealth/Seqster at the patient-anchored tier. Hu-manity couldn't compete at either end, so the company commoditized into consent-banner SaaS where the patient-data-rights brand had no specific advantage. Lesson for RDCO: the VBC leg is structural, not optional. It's what gives the patient cash flow a source other than data licensing. Outcome-savings-pool payouts > data-licensing-royalty payouts on every defensibility axis.

  3. Blockchain was a distraction, not a differentiator. Hu-manity's 2018 launch leaned on blockchain for "tokenized consent" — the technology layer added complexity, regulatory headwinds, and zero customer-perceived value. By 2024 the company's product page barely mentioned blockchain. Lesson for RDCO: any "the patient owns their data on the blockchain" framing in early collateral is a tell that the thesis is rhetorical-first, not operational-first. Avoid.

  4. Founder time-horizon mismatch with payer-cycle time. Hu-manity raised pre-seed in 2018; CMS Innovation Center program cycles run 5-7 years from announcement to first measured outcome. A pre-seed startup cannot survive the policy-iteration cycle without bridge revenue. Lesson for RDCO: if the bet's first revenue waits on a CMS innovation model cycle, the funding/runway architecture must be sized for that, not for typical SaaS sales-cycle math.

  5. The "human rights" frame attracts the wrong investors. Hu-manity's investor base (Rockpool, Frontier Growth) is mission-aligned but not deep enough to fund a payer-contract operator stack. The frame may have actively excluded VBC-experienced healthcare investors. Lesson for RDCO: positioning around "patient data sovereignty" alone risks the same investor-selection problem. The bet needs to read as "VBC operator with sovereignty-aligned data architecture," not "patient data rights startup."

Net for the parent bet: the May 11 brief's recommendation that Hu-manity is the cautionary tale, not a current competitor, is confirmed and sharpened. The white space is clean; the path through it has named failure modes to avoid. This should be folded back into the bet architecture doc at 01-projects/health-and-longevity/2026-05-10-data-sovereignty-outcome-procurement-bet-architecture.md as a Phase-0 "lessons-from-Hu-manity" section before any Phase-1 work begins.

Open follow-ups

Sources