Maturity: Beta
CareAI Assistant
Dementia care management for families and caregivers: a rule-based pattern-detection engine, a two-mode AI voice companion, and a caregiver-wellbeing module.
Focus
Health and Wellness
Care management, caregiver support, wellness and fitness, and the data, consent and safety governance that health-adjacent software requires.
The problem, in your words
- “We run a care or wellness service and we need software that respects the fact that the people using it are vulnerable.”
- “We want an AI feature, and it must never give clinical advice it is not allowed to give.”
- “Consent, data and safety rules are the whole product, not a compliance appendix.”
What we know about this market
- Dementia care management with a rule-based pattern-detection engine, a two-mode AI voice companion and a caregiver-wellbeing module built on the Zarit burden scale, in CareAI Assistant.
- AI-generated training and nutrition plans behind a deterministic recommendation engine, in Body Balance.
- A women's health specification with a configurable clinical safety rule engine, crisis routing, clinician-reviewed content and an explicit launch boundary stating what the product will never claim to do.
What we do about it
- Care and wellness product design
- Products for care management, caregiver support and wellness, with the safety boundary written before the first screen.
- Clinical safety rule engines
- Deterministic, configurable rules for anything with a safety consequence, with crisis routing and clinician-reviewed content.
- Health data and consent governance
- Consent as a record, not a checkbox; data minimisation; audit; and a published boundary of what the product will never claim to do.
Products in this focus area
Maturity: Beta
Body Balance
AI-generated training and nutrition plans behind a deterministic recommendation engine.
Maturity: In specification
Women's health platform
A women's health product specified with a configurable clinical safety rule engine, crisis routing, clinician-reviewed content and an explicit launch boundary stating what the product will never claim to do.
Public name to be announced
How the engagement runs
| Stage | You supply | We produce |
|---|---|---|
| 01 Boundary firstWe write down what the product will and will not do before anything is built. | Clinical or care expertise, and the rules the product must obey. | A product-boundary table and a safety-rule specification. |
| 02 Specify and buildWe specify and build against that boundary, with a human review queue for generated content. | Reviewers for generated content and test users. | A PRD, then working software with QA passes. |
| 03 Release under the standardRelease is a recorded GO decision against the published standard. | Sign-off. | A released product with a runbook. |
Typical duration: A discovery sprint runs two to three weeks; a build is scoped in the proposal.
Deliverables
- A product-boundary table separating what the system may do from what requires a human
- A configurable safety-rule specification with crisis routing
- A build-ready PRD and, where scoped, the product itself
- A consent and data-governance design
Sector-specific compliance considerations
- Health-adjacent data is treated as sensitive by design: minimised, consented, audited and never used to train a model.
- Anything with a clinical or safety consequence is a deterministic rule, not a prompt. AI is confined to conversation, extraction and drafting.
- Generated content that reaches a user passes a human review queue, and the product states plainly what it does not do.
Proof
Maturity: Beta
CareAI Assistant
Dementia care management for families and caregivers: a rule-based pattern-detection engine, a two-mode AI voice companion, and a caregiver-wellbeing module.
Maturity: Beta
Body Balance
AI-generated training and nutrition plans behind a deterministic recommendation engine.
Maturity: In specification
Women's health platform
A women's health product specified with a configurable clinical safety rule engine, crisis routing, clinician-reviewed content and an explicit launch boundary stating what the product will never claim to do.
Public name to be announced
Partnership and licensing
Related practices: Information Technology ConsultingInformation Systems Consulting
Who leads it
Brevard Nelson
Chief Executive Officer
Next step
Book a conversation with the practice pre-filled, or send a short enquiry.