A nurse I know finishes her ward shift at 7am. The 15 minutes before that are the most important of her night — handover. She tells the day shift what happened overnight, what to watch, what the on-call doctor said, which patient's family is coming in upset, which IV pump is about to alarm.
The hospital has a multi-million-pound EHR. None of it captures any of that.
So she does what every nurse on every ward does: she scribbles on a piece of paper. Her own format. Her own shorthand. "Bay 3 — K+ recheck 8am — bloods chased — daughter v anxious." Then she hands the paper to the day shift, who bins it by lunch.
Last week she opened Shelf and typed:
> "Shift handover notes. Add patients by bay number with name, key issues, tasks to do, things to watch overnight. Tick off tasks. One button to clear everything at end of shift."
About 30 seconds later Boom! she had it. Running on her laptop. Data storage under the hood. No login. No cloud. No PHI on anyone's server because there is no server.
## Why no SaaS was ever going to build this
Indie hackers know this math cold. To build a "handover notes app for nurses" as a real product you need:
- HIPAA / GDPR compliance, audit logging, encryption at rest and in transit
- EHR integration (Epic, Cerner — either will eat you alive for a year)
- A procurement motion into hospital trusts (18 months, minimum)
- Liability insurance to sign the contract
- A team large enough that the unit economics demand £40k/seat/year
So the only software that exists for nurses is the multi-million-pound EHR — which doesn't have a "things to tell the next nurse" field, because that field has zero billable value.
The actual need — I want private notes, on my own device, in my own format, that wipe at end of shift — has been sitting in the long tail since 1990. Worth nobody's time to build. Worth one nurse's time to describe in a sentence.
## What changed
The cost of building one personal tool used to be "learn to code, spin up a server, host it, maintain it forever." Now it's one sentence in plain English.
That's what Shelf is. A free desktop app that takes that sentence, generates a working HTML app, and runs it locally with persistent storage. No account. No cloud. The SQLite file lives on her laptop. If the ward wifi drops (it does), the app keeps working. If she switches hospitals next year, the app and every note she's ever taken come with her.
This is the long tail of software finally getting a tail. The market for a generic nurse-handover app was always 1.5 million nurses × zero willingness to onboard to yet another tool. Multiply by zero, you get nothing — which is exactly what's been built. The market for each nurse's own tool is one person, and the cost per build is now lower than the cost of complaining about the EHR.
The same mechanism that built her handover app also builds:
- A patient-bay round timer for a hospice nurse
- A daily P&L tracker for a corner shop
- A revision quiz scoped to one chapter of one textbook
- A pit-stop trainer for a sim racer
None of these are startups. All of them are 30 seconds of typing.
## Try it
- Download Shelf: [getmyshelf.app](https://getmyshelf.app)
- The exact prompt: "Shift handover notes. Add patients by bay number with name, key issues, tasks to do, things to watch overnight. Tick off tasks. One button to clear everything at end of shift."
- Or skip the build: import [shift-handover-notes-add-pa.shelf](https://raw.githubusercontent.com/soyu-apps/getmyshelf.app/refs/heads/main/samples/shift-handover-notes-add-pa.shelf) — drag it into the sidebar, her exact app appears on your machine.
Show it to a nurse you know. See how long it takes them to ask if they can keep it.
The answer is yes. That's the whole point.
---
Shelf is a free desktop app. Apps you make in it stay on your machine forever. The point isn't to compete with big software — it's to fill the gap big software was never going to fill.
Love the story of building this at 3am. What’s been the biggest challenge so far as a solo founder?
Making people believe that our product simply works!
This app is simply awesome. it further create custom apps which run on your machine for free..i liked the idea i would certainly try it..
Lovely to hear those words. Could you please leave some feedback after trying it. You can join our discord group.
Love this story. For healthcare apps GDPR + HIPAA compliance is such a real barrier — many indie founders underestimate the documentation burden (DPA templates, consent flows, data subject request procedures).
I just built a 50-point GDPR self-audit checklist specifically for indie SaaS founders to self-assess before paying for a formal audit. Free Google Sheet:
https://www.indiehackers.com/post/50-point-gdpr-self-audit-checklist-for-saas-founders-free-google-sheet-anyone-want-it-fef7364c43
Would love to know if something like this would have helped you in the early days.
The thing that really lands for me is how small the need is on paper and how totally invisible it is to a normal SaaS roadmap… but it’s literally the sharp end of patient care for the people actually doing the work.
The “one nurse, one sentence, one local app” framing is powerful. Feels like we’re finally getting tools that respect individual workflows rather than trying to drag everyone into yet another centralized system just so it fits procurement and billing.
Also really appreciate the no-login, no-cloud, no-PHI stance. For this kind of use case, “stays on my machine forever” isn’t a nice-to-have — it’s the only reason it can exist at all.
Super inspiring example of what this new “long tail of personal software” can look like in the real world.
Thanks — the "stays on my machine" point is the one I keep coming back to. The reason no SaaS exists here isn't that nobody thought of it; it's that the moment a server enters the picture, the use case dies under compliance weight. Local-only isn't a privacy stance — it's the only architecture that lets the tool exist at all.
The thing I'm watching for now is how many other roles have the same shape: small need, sharp end of the work, invisible to procurement. Nurses are the cleanest example I've found, but I suspect teachers, social workers, and lab techs all have their own version of the paper-that-gets-binned-by-lunch.