01
Information without a home
Messages, notes and documents live in different places and lose their operational context.
Software asset acquisition
The operating system for a family’s Care House.
CarePilot is a Family Care Coordination OS for adults caring for ageing parents. It brings tasks, appointments, records, family roles, review queues and source-aware AI assistance into one calm, human product world.
USD 2,400 asking price
Pre-revenue software asset
Buyer due diligence required
Product evidence, not a concept mock-up
The screens shown here are rendered golden-test outputs from the supplied project archive.
The family-care problem
Care work is real work. Its context is usually scattered.
Families often coordinate through message threads, paper records, separate calendars and memory. That fragmentation makes it harder to know what happened, who owns the next step, and whether a detail came from an original source or an AI suggestion.
02
Responsibility without clarity
Tasks may be discussed by everyone yet owned by no one.
03
Appointments without shared preparation
Dates can be remembered while questions, documents and follow-up actions are not.
04
Sources detached from action
A record may exist, but the task or question it supports is not linked back to it.
05
Uneven family context
One relative has the latest update while others act on older information.
06
Review pressure
Suggested items need a clear path from draft to human approval, not silent automation.
07
Emotional load
The practical burden compounds the emotional strain of caring for an ageing parent.
08
Truth-state ambiguity
Families need to distinguish original information, inferred suggestions and confirmed care work.
The product solution
One Care House, built around reviewable coordination.
CarePilot treats the family’s care activity as a connected environment rather than a collection of isolated forms. Nura lives inside that environment as a guide: she can organise, clarify and prepare work, while permissions, guardians and trusted controllers preserve human authority.
- Home, Care, Family and Records form the main product rooms.
- Documents remain sources, not silent truth replacements.
- AI suggestions stay reviewable before sensitive actions are committed.
- Roles and permissions shape what each family member can access or change.
How the system works
A visible path from raw input to trusted family coordination.
The implementation separates understanding from authority. An AI layer may identify and propose; source references, human review, permission validation and trusted controllers determine what may become a saved care item.
1
CaptureMessage, document, voice or direct entry2
UnderstandExtract likely tasks, dates and notes3
Link to sourceKeep provenance visible4
Human reviewApprove, edit or dismiss5
Permission validationCheck role and scope6
Trusted commitUse the owning controller7
Family coordinationShare the confirmed care workMain product experiences
A connected product foundation, not a single-purpose checklist.
The supplied archive contains implemented screens, repositories, routing and tests across the core Care House. These selected screens are real rendered outputs from the project’s golden-test suite.
“I can help organise what the family already has, but people remain in control of what is saved or acted on.”
Nura, the living intelligence
More than a chat window. Less than an authority.
Nura is designed as the living guide inside the Care House. Her value comes from product context, source awareness, uncertainty handling, emotional range and a controlled route into existing care workflows—not from pretending to be a clinician or autonomous decision-maker.
May understand and organise
Clarify intent, connect records, prepare drafts, surface sources and suggest next steps.
May explain uncertainty
Ask for missing detail, identify source conflict and state when the available evidence is insufficient.
Must not diagnose or prescribe
No clinical judgement, treatment decisions, dosage changes or emergency monitoring.
Must not bypass people
Permission guardians and trusted controllers remain the authority for protected actions.
Buyer value
Acquire product discovery, architecture and continuity—not just screens.
Starting from zero means deciding the ontology, interaction model, trust boundaries, AI role, permissions, data structures and care workflows before implementation begins. CarePilot provides a substantial foundation for that work, subject to technical and legal verification.
1
Care ontology
A connected model for tasks, appointments, notes, documents, family roles, review items and sources.
2
Existing UI foundation
A distinctive, responsive Care House design system with tested mobile and wide-screen behaviours.
3
Nura design
A defined persona, source voice, uncertainty behaviour and serious-context treatment.
4
Permission boundaries
Family-scoped rules, role checks and trusted action handoffs are represented in code.
5
Source model
Suggestions and care work can retain links to the information that supported them.
6
Continuity and tests
The archive includes extensive product documentation, regression tests and rendered golden evidence.
Product status and roadmap
A serious foundation with visible completion gaps.
CarePilot is offered as a pre-revenue software asset. The archive shows meaningful implementation, but it does not prove a public launch, production operation, regulatory compliance, market validation or a completed release process.
Core Care House interfaces
Home, Care, Family, Records, tasks, appointments, notes, documents, Care Inbox, review queues, Nura Desk, memory and timeline/report surfaces exist in code.
Connected services
Firebase repositories, functions, notifications, external intake, voice and scheduled routines exist, but require deployment configuration and production validation.
Product and trust system
Design-system, Nura, security, privacy and phase evidence documents are included. Documentation is not treated as proof where code or runtime evidence is absent.
Launch, compliance and ownership
Final legal review, asset ownership, third-party terms, Firebase transfer, device testing, release signing and market validation remain buyer due-diligence items.
Potential business model
Commercial paths a buyer could validate.
These are strategic options, not claims of current revenue or proven demand. The product’s family-centred coordination layer could support multiple go-to-market directions after validation.
Family subscriptions
A paid household plan with coordinated care rooms and shared family access.
Premium family plans
Higher-tier memory, reporting, document and coordination capabilities.
Care-professional partnerships
A family-facing companion offered alongside non-clinical care-navigation services.
Employer caregiver benefits
A benefit for employees managing care responsibilities outside work.
White-label licensing
A configurable foundation for organisations serving family caregivers.
B2B2C partnerships
Distribution through insurers, ageing-services networks or caregiver-support programmes, subject to compliance review.
Acquisition package
What is included—and what is not assumed.
The package should be transferred through a written agreement after ownership and third-party rights are verified. Private infrastructure credentials and personal accounts are deliberately excluded.
Included in the supplied asset package
- Flutter and Dart application source code
- Firebase Cloud Functions source, Firestore rules, Storage rules and indexes
- Owned CarePilot vector brand mark and project-generated UI visuals
- Product-experience, architecture, Nura and phase-evidence documents
- Golden screenshots, Flutter tests and Node test suites
- Draft in-app privacy and terms copy
- This acquisition website and interactive sample-data demo
- Deployment and due-diligence handover notes
Excluded or subject to verification
- Personal accounts, email accounts and payment accounts
- Firebase project ownership unless separately transferred and accepted
- API keys, service credentials, signing keys and secret environment values
- Non-transferable third-party services or licences
- Any asset whose creator, licence or ownership cannot be verified
- Regulatory approvals, compliance certifications or production guarantees
- Ongoing development support unless separately agreed in writing
Current asking price
USD 2,400
Serious, reasonable offers may be considered. The sale is for a pre-revenue software asset and is subject to written terms, buyer due diligence and verified transfer scope.
$2,400asking price in USDRequest acquisition details
Buyer FAQ
Direct answers before due diligence.
No verified revenue evidence was found in the supplied archive. It is presented as a pre-revenue software asset.
The archive includes private-beta and alpha-stage language, but no verified public store listing or active public service. Public launch should not be assumed.
No. The product is positioned as a family-care coordination and organisational tool, not a diagnosis, treatment or emergency service.
That claim is not made. The archive includes meaningful code, rules, functions and tests, but production deployment, security, device behaviour and release readiness require buyer verification.
The intended package includes project source, transferable owned assets, documentation, tests and this acquisition/demo site. The final transfer scope must be defined in a written agreement.
Not automatically. Personal accounts, private credentials and non-transferable third-party services are excluded. Any Firebase project transfer requires separate verification and platform procedures.
Only if a signed acquisition agreement assigns the verified transferable rights. This website is not itself an assignment of intellectual property.
No support commitment is assumed. Any transition help, warranty or post-sale work must be separately agreed.
Yes, technically. CarePilot is treated as a current working product name; branding, identifiers and public assets can be migrated after the buyer completes clearance.
Production configuration, device and platform testing, final legal review, localisation, release signing, operational monitoring, compliance work and market validation are among the open buyer tasks.
Yes. The included browser demo uses local sample data and does not connect to a production backend.
Email pssmaysara@gmail.com with the buyer or company name, intended use and the materials you would like to review.
Acquisition enquiry
Review the product foundation in detail.
Request the source inventory, technical due-diligence summary and available transfer information. No fake lead form is used; the enquiry opens your email client directly.