The tools behind the platform… (Don’t forget to read part 1, part 2, and part 3!)
***
Building Innovation from Ideas is a new series where I’ll document the process of building a brand-new platform for nurses.
🏗️Part 4: The Platform Itself
I officially started building this “opportunities platform for nurses” on August 1, at the time of this drafting, I was 9 weeks in. I’m still not an engineer, and I’m still asking Claude a lot of questions.
I’m hoping these articles will give you insight on what it means to build technology or software solutions using AI as a partner.
And feel free to leave a comment or reach out with questions on my process at any time.
The Bossy Nurse is a reader-supported publication. To receive new posts and support my work, consider becoming a free or paid subscriber.
Last week I covered what I had to put in place before building anything: choosing a name, buying a web address, picking a password manager, and getting email working.
This week is about the part nurses will actually use, which is where their profiles and information are stored and protected.
It’s eleven tools, and every one of them is free at with the size (0) of the platform right now. Eleven sounds like a lot, so I sort them into five groups.
1. The filing cabinet
Every nurse who joins will have a profile with information. All of that information needs a home, and that home is the database.
A database is basically a very serious spreadsheet that a lot of people can use at the same time. For that, I use a tool called Supabase.
It also handles signing people in, so I didn’t have to go find and set up a second product for that.
Why I picked it
The usual way to protect private information is to write code that remembers to hide it.
Supabase lets you put the rule inside the database itself. (If you want to ask your AI about it, it’s called row level security.)
So when a search is performed on the platform, the database only hands back what the person searching is allowed to see.
My code doesn’t have to remember to filter anything, because the database refuses to give up the rest, as long as I’ve written the rules correctly.
It works a lot like a Pyxis.
The machine only opens the drawers you’re cleared for, so it doesn’t matter if someone tries to open the wrong one. The protection is in the machine itself, not in each person remembering the rules.
I also changed two settings on day one. Every new section of the database starts locked, and nothing new can be reached from the internet until I deliberately allow it.
Those are two separate locks.
So, the trust is built in at the very beginning, because it’s much harder to add after nurses have already handed you their information.
Other options aside from Supabase:
- Firebase has a database option that fits connected information like a nurse’s profile, but it isn’t free.
- PlanetScale doesn’t have a free version, so it was out for a project my size.
- Neon was a close call. It’s a good database, but Supabase gave me everything I needed in one place.
- Amazon has an option too, but it takes a lot more setup, and I wanted my time going into the parts nurses will actually use.
Supabase is also open source, which means the code behind it is public. If the company disappeared, I could run the same thing somewhere else. That’s the “what breaks if this company disappears?” question from part two.
Signing in without a password
Here’s how a nurse will sign in. She types her email, gets a link, clicks it, and she’s in.
In that instance, she won’t worry about creating a password.
There’s nothing for her to forget, and there’s no password sitting in my database for anyone to steal. The safest information is the information you never held.
This came bundled with Supabase. I didn’t build it and didn’t pay extra for it, which is part of why I chose it.
One more trust decision, about AI
I use a company called Cloudflare to connect my web address to my site, and it also lets me decide which kinds of automated visitors can come to my site.
I let search engines in, so nurses can find the platform. I also let in tools like ChatGPT and Claude when someone asks them a question and they search the web for the answer. That way, if a nurse asks one of them about career opportunities, my platform can show up in the answer.
I block the ones that collect content to train AI models.
My reason is specific to nurses.
A nurse who agrees to let my platform use her information is agreeing that my platform can use it. She’s not agreeing to have her details soaked into an AI company’s training data.
A search engine can drop you later. Once an AI model has learned from something, it can’t unlearn it.
2. What the site is made of
These next four are what the site itself is built with. Here’s what each one does.
- Next.js is the frame of the house. It decides how pages get built and how they show up on someone’s phone or laptop.
- React lets you build a piece once and reuse it everywhere, like a form you build once and roll out to forty units.
- TypeScript catches mistakes while the code is being written. Think of a hard stop in the eMAR, where the error gets caught before it ever reaches the bedside.
- Tailwind handles how the pages look: colors, spacing, and size.
I couldn’t write any of these four from scratch.
I tell Claude Code what I want, and it writes the code using them. That’s what I meant in part two about directing the AI instead of learning to code first.
3. Where it lives
Hosting is someone else’s computer that stays on all day so yours doesn’t have to.
My platform lives on Vercel.
I also looked at Netlify, which is a fair option. Vercel won because it’s made by the same company that makes Next.js, so it understood my project right away and there was very little to set up.
4. The undo button
Git is track changes for a whole project instead of one document. It saves every version forever, with a note about why each change was made.
GitHub is the website that keeps a copy of all that history somewhere other than my laptop.
The easiest way I’ve found to think about it is that Git is track changes and GitHub is Google Drive.
Track changes works whether or not you ever upload the document anywhere. That’s why I count them as two tools. One runs on my laptop and works without the internet, and the other is a website that keeps a copy of my project’s history online.
My project on GitHub is private.
Automated programs scan public projects around the clock looking for passwords and keys that people posted by accident. Keeping the project private means that mistake is fixable instead of instantly public.
(Same reason I set up the password manager first last week. 🔐*)*
Because of Git and Github, I can look at any day of the build and see exactly what changed.
When something breaks, I go read what I did instead of guessing.
5. The paper trail
These two are the least impressive tools on the list, and I’d keep them before almost anything else.
Google Docs is my build log. The days that I “code,” I write down what I set out to do, what got done, what I decided, and why.
Google Sheets is my field dictionary.It’s where I define each thing the platform asks nurses for and write down why it’s needed. I filled it out before I built anything. If I can’t explain why I’m asking a nurse for something, I don’t ask for it.
In week three, I went back and undid one of my own good decisions. My notes said what I’d done but never said why. So it looked like a mistake, and I “fixed” it.
Write down why you made a decision, along with what you decided. A decision without its reason is easy to overrule later, even by you.
What all of this cost
Nothing extra. All 10 are free at my size currently (zero folks on the platform), so everything I’ve set up so far, last week’s pieces included, still comes to less than $20 a year total.
“Free at my size” also means the bill grows as the platform does, so I’m keeping an eye on where each one starts charging.
Stack or tool?
It’s the same test as the last two weeks: if this disappeared tomorrow, would my platform stop working? (Get your primer on the nurse’s “tech stack” here.)
- Stack: Supabase, Next.js, React, TypeScript, Tailwind, and Vercel. Take any one of them away and the platform or my simpler site goes down.
- Tools: Git, GitHub, Google Docs, and Google Sheets. The platform keeps running without them. But, without these tools I’d just be building blind and forgetting everything I’d decided, which is why they’re still on the list.
Refresher… and before the next part in this series
If you want the shortest possible list for starting your own idea, it’s five things:
- A name you’ve checked on the trademark register.
- A domain from a registrar with an honest renewal price.
- A password manager.
- A way to send email.
- An AI you can direct, and the willingness to make it explain itself.
Everything else can wait until somebody is actually using what you built.
The tools are the easy part to find.
What you bring as a nurse is knowing which information is sensitive, who should see it, and what happens to a real person when it leaks. That’s what shaped almost every decision in this post.
Three questions for you.
- What’s the one piece of information your idea would hold that you’d be embarrassed to have leak? Consider designing your technology or tool around that one first.
- Where are you writing down why you made a decision?
- What’s the smallest version of your idea that five real people could use next month?
Tell me in the comments.
Next week: the last tech stack part. It covers four tools that get people to the thing you built.
I’ll chat soon,
—Marsha 🧡
