Spreadsheets and group texts don't survive the week
A home-care structure — local association, small agency, independent caregivers — coordinates dozens of weekly visits: each client has their days, times and habits; each caregiver has availability and mileage. The shared spreadsheet and the group chat hold for a while, then come the misses this trade doesn't forgive: the forgotten visit, the double booking, the replacement agreed by phone and never written down.
Specialised platforms exist, but they're built for established agencies: electronic visit verification modules, integrated billing, per-caregiver pricing — disproportionate cost and complexity when you're starting out or deliberately staying small.
Your organisation, described then generated
Describe how you work: “We're a small home-care team with eight caregivers. Each client has planned visits during the week (day, time, duration, type of help), assigned to a caregiver. Absences trigger a replacement. I want each caregiver's day, each client's week, unassigned visits, and hours per caregiver for payroll.”
The generated application structures that register: clients and caregivers, visits with statuses (planned, done, cancelled, needs cover), and a dashboard answering the daily questions — the day per caregiver, uncovered visits, the month's hours.
- Client records: contacts, habits, planned visits
- Caregiver records with their visits
- Visits: day, time, duration, type, status
- Replacements traced (who covers which visit)
- Dashboard: today, uncovered, hours per caregiver
A reliable register beats a clever scheduler
A small structure's real need isn't a route-optimisation algorithm: it's a single, current register that the office and the caregivers read without ambiguity. A centralised web application guarantees it: the change made at the office is what the caregiver sees on her phone, and the visit history stays browsable — precious for families and for payroll hours alike.
The application ships with realistic demo data (clients, a typical week, varied statuses) to evaluate immediately, and three generation levels (Sketch, Craft, Masterpiece) to raise the polish.
Small-structure cost, owned tool
The Discovery plan (€0) generates the first application; Pro (€25/month) and Max (€149/month) are for iterating, with the cost shown before each generation — no per-caregiver pricing.
And the tool belongs to the structure: code ZIP export, GitHub push, free hosting or the included dedicated URL. The visit register — sensitive data if there ever was — stays with you, on infrastructure you choose.
Typical generated entities
- Client
- Caregiver
- Visit
- Replacement
- Worked hours
Generated screens
- Day per caregiver
- Week per client
- Visits needing cover
- Worked-hours entry
- Agency dashboard
Dashboard indicators
- Today's visits / uncovered
- Hours per caregiver
- Active clients
- Replacements this month
Frequently asked questions — home care
Does the application optimise routes automatically?
No — deliberately: automatic optimisation is specialised platforms' territory. The generated application keeps the reliable register (who, where, when, what status) that makes human coordination simple. Since the code is exportable and standard, a developer can add scheduling aids if the need is confirmed.
Does it cover regulatory visit verification or dedicated billing?
No: regulatory obligations keep their certified tools. The application covers operational tracking — visits, replacements, hours — and its structured data makes declarations that much easier.
Can caregivers check their schedule on a phone?
Yes: it's a responsive web application — each caregiver reads her day and visits from her phone's browser, with nothing to install.
Can we track different types of help (housekeeping, meals, companionship)?
Yes: describe your visit types and they structure the application — with filters and per-type hour counts if you need them.
Does client data live with a third-party vendor?
No: the application and its database are yours (ZIP export, GitHub, free hosting). You choose where the data lives — including on your own server.