Senior care apps

// The problem

A home care agency schedules caregivers by phone and group text, cannot confirm visits happened until timesheets arrive, and spends hours filling every sick call.

// What we would build

An iOS and Android app for caregivers and a web app for coordinators: schedules, visit check-in and check-out, tasks and notes from the care plan the team wrote, and open shifts offered to the right caregivers in one tap.

// What is in it

// Stack

• Next.js
• React Native
• PostgreSQL
• Scheduling interface
• AWS

// The problem

A retirement residence answers dozens of calls a day from families asking about meals, activities and how their parent is doing, and mails monthly invoices on paper.

// What we would build

A web and mobile portal for families: updates and photos the care team chooses to share, activities and menus, messages to the right staff member, and invoices and payments, with access set by the resident or their representative.

// What is in it

// Stack

• Next.js
• React Native
• PostgreSQL
• Stripe
• AWS

// The problem

A home care agency's supervisors read dozens of short notes a day, written in a hurry and often in a second language, to spot the clients who need a nurse's visit.

// What we would build

A tool that turns each caregiver's notes into a clear summary in the supervisor's language and flags notes that mention a fall, a missed meal or a change the care plan says to report, for a person to review. It runs on an open-source model in the agency's own cloud account, so client details never reach an outside provider, and it never suggests care.

// What is in it

// Stack

• Open-source model
• Next.js
• PostgreSQL with pgvector
• AWS

// The problem

The owner of a home care agency sees visits in the scheduler, hours in payroll and invoices in accounting, and finds missed visits and unbilled hours weeks later.

// What we would build

A dashboard that reads scheduling, visit check-ins, payroll and billing into one model, so the owner sees visits completed and missed, hours worked against hours billed, and open shifts by region, every day.

// What is in it

// Stack

• Next.js
• PostgreSQL
• dbt
• Scheduling and payroll interfaces
• AWS

// The problem

A care agency's office copies visit hours from the scheduler into payroll and into invoices for families and funders, by hand, every pay period.

// What we would build

An integration hub between scheduling, visit check-ins, payroll, billing and accounting, so a confirmed visit becomes payroll hours and an invoice line once, with every message logged.

// What is in it

// Stack

• Node.js
• PostgreSQL
• OpenAPI
• Scheduling, payroll and accounting interfaces
• AWS

// The problem

A home care agency, the families it serves and a public funder each keep their own record of which visits happened, and disputes over missed or shortened visits take weeks to settle.

// What we would build

Each visit's check-in and check-out recorded on a private permissioned ledger the agency and the funder run nodes of, with families able to see their own parent's visits, so nobody can quietly change a visit after the fact. If the agency's own records are trusted by everyone, a database with the same views is simpler, and we will say so.

// What is in it

// Stack

• Next.js
• PostgreSQL
• Hyperledger Besu (private, permissioned)
• Scheduling interface
• AWS