Everything here happens before you build a single screen. (Don’t forget to read part 1, part 2, and part 4!)
***
Building Innovation From Ideas is a new series where I’ll document the process of building a brand-new platform for nurses.
🏠Part 3: The Boring Foundation
I’m four weeks into building an opportunities platform for nurses, and I’m still not an engineer.
In part two we covered what a tech stack is. This week I’m showing you the first pieces of mine, plus the tools I used to set them up.
I think of it like moving into a house. Before anything else, you need a name on the mailbox, an address, a set of keys, and a way to get your mail.
It’s the dull part, and it all has to be in place before anyone can visit.
1. The name
There’s a free government list of every business name somebody has already legally claimed.
It’s the trademark search on the United States Patent and Trademark Office (USPTO) website.
I had a name I liked well enough. I’d already been using it in my notes and in every conversation with Claude and ChatGPT.
Then I searched the trademark register and found four companies using that exact name.
All four were in healthcare. One of them described, almost word for word, one of the things my platform will do.
So I dropped it.
A lawsuit wasn’t really what worried me.
What worried me was how big the mess would get later. Right now the only places that name lived were my notes and my AI chats, so changing it didn’t cost a thing right now.
Changing it after nurses have joined is a different story.
They’d have a profile link in their email signature, on their resume, and sent to recruiters (possibly).
A rename at that point breaks things for them. Redirects exist, but I didn’t want to spend my early users’ trust explaining why their link changed.
Make sure you search the trademark register before you fall in love with a name.
Then I needed a .com that was actually available, and this is where I lost the most time.
I asked Claude to check a long list of names, close to 200. It came back, confidently, saying a bunch of them were available.
I’d go to buy one and it was taken. It found another. Also taken.
A domain name (check out this post for all relevant definitions and tech stuff) can be bought and just sit there with nothing on it. It looks empty, so a quick check says it’s open when it isn’t.
Once I pushed Claude on why its answers kept being wrong, we switched to checking the official registry.
(Sometimes you have to give Claude or ChatGPT a good nudge. 😉)
For .com names that’s Verisign, the company that keeps the master list. The search bar on a domain seller’s site, like GoDaddy, and the official registry are two different sources. When you need a definite answer, trust the registry.
We checked over 300 names after that. Mythology, Latin, all kinds of directions.
I spent hours trying to get the name perfect. What I settled on isn’t what I pictured at first. It sounds good, it makes sense, and a nurse would be comfortable saying it out loud. Don’t let naming stall your whole project.
2. The address
Your domain name is your address on the internet, like thebossynurse.com. You rent it, usually a year at a time, from a company called a registrar.
I’ve used GoDaddy for years. This time I asked Claude whether there were other options I should look at, and it suggested Porkbun. I’d never heard of it. But I went with it for three reasons:
- The renewal price is honest. A lot of registrars are cheap the first year and cost more every year after. Year two and beyond is the price that matters.
- Privacy protection is included free. More on that below.
- Checkout was simple. It didn’t pile add-ons into my cart before I could pay. That’s not the main reason to pick a registrar, but I noticed it.
Other options include GoDaddy and Namecheap, which is fine but a little more at renewal. There’s also Cloudflare, which is the cheapest of all.
I turned Cloudflare down for this on purpose, and I’ll explain why in the next section.
About privacy protection. When you register a domain, your name, home address, phone number, and email can end up in a public directory, and spammers pull from it. Privacy protection hides that information. Some registrars include it and some sell it as an extra. Check before you pay, and look at what it costs at renewal too.
3. The phone book
In part two, I called DNS the internet’s phone book, or the unit directory.
You know the charge nurse’s name, and the directory tells you which extension actually rings. DNS takes the name someone types in and points it at the computer where your site actually lives.
I use Cloudflare for this. It’s free at the size of my platform (no users) right now.
Cloudflare also sells domains cheaper than Porkbun, and I could’ve had my address and my phone book at the same company on one bill. But, I split them on purpose.
If one company locks my account, has a billing problem, or goes down, I don’t lose both the name and the ability to point it anywhere. I’d still have one and could move the other.
That’s the “too many eggs in one basket” question from part two. I pay a little more for the separation, and I’m fine with that.
4. The keys
I use Bitwarden, a password manager.
It’s one lockbox that holds every password and every key, and you only memorize the one password that opens the box.
It has a free version, and it works for your personal life too. Families use it to share logins without texting passwords back and forth.
If you’ve pulled meds from a Pyxis, you already get the idea. You log in once and it opens only what you’re cleared for.
Bitwarden was scheduled as the last thing on my setup day. I moved it to first.
The very next thing I was building was the database, where every nurse’s profile will live.
When you create a database, it hands you a key.
That key needs a safe place the moment you get it. And if you’re scrambling for somewhere to put it after it’s already on your screen, it ends up pasted in a note, a chat, or a file on your desktop. That’s how secrets leak.
Set up the lockbox before anything hands you a key. It takes a few minutes.
5. The mailroom
Your platform will need to send email and receive email. I didn’t realize those are two separate jobs, usually handled by two separate tools, until I started to build out this platform
Sending email: Resend
Think about every automatic email you’ve gotten after signing up for something: a sign-in link, a password reset, a reminder, a “you’re confirmed.” Your platform has to send those, and Resend sends mine.
The free tier covers 3,000 emails a month, with a limit of 100 a day. For something small, like a tool 100 nurses or 100 businesses use, that can carry you a long time. It was also the cleanest setup of the email tools I looked at.
Other options are Postmark, SendGrid, Amazon SES, and Mailgun.
I wrote down why I didn’t pick each one and what would make me switch. Your future self won’t remember why you said no. Six months from now, one of those will look like the better choice for reasons you already thought through.
So remember to track these decisions…
Receiving email: Cloudflare Email Routing
This one’s free and it’s part of Cloudflare, which I already use.
It forwards anything sent to an address at your domain into an inbox you already check. It works like call forwarding, but for email.
That means I can put contact@[myplatform].com everywhere as a placeholder, and it lands in my regular personal inbox. It only handles incoming mail, so I can’t send from that address.
The alternative is Google Workspace, which gives you a real mailbox at your domain for about $7 to $8.40 a month per person. I pay for it at thebossynurse.com because that site has been live for years and real people email me there.
For the new platform I said no for now.
Forwarding does the job for free while it’s just me and nothing is live. I’ll likely move to Workspace once there’s a team or the platform launches.
6. Proof your mail is really from you
Three invisible settings keep your emails out of spam, and they have names you’ll likely not remember: SPF, DKIM, and DMARC. You don’t need to memorize them.
They’re three small notes you publish in your phone book (DNS) that let someone’s email inbox check whether an email claiming to come from you really did.
Think of two patient identifiers before a med. The receiving inbox checks the email against what you published before it lets it through.
Without them, anyone can send an email that looks like it came from your platform. It might say “Your license verification failed, click here to re-enter your license number,” or “Your Social Security number doesn’t match our records.”
If it it shows up looking like me, and it actually isn’t, my platform becomes a phishing platform aimed at the exact nurses who should trust it.
I had seen DMARC before I started building, but wasn’t too familiar with its purpose. SPF and DKIM either.
Claude Code flagged them because it could tell what I was building, and other tools like it (e.g., Codex by OpenAI, makers of ChatGPT) will do the same.
Still, good to know the names so you can ask for them if your AI doesn’t bring them up.
Claude also taught me something about DMARC. It has a strict setting that tells the world to throw away anything suspicious, and Claude told me not to start there. If one of your own tools isn’t set up right yet, strict mode throws away your real emails too.
So I started on ‘watch’ mode. For a while, I’ll just read the reports. Once they show my real emails getting through clean, I’ll tighten it to the more stricter setting.
These settings stop someone from sending as your exact address.
They can’t stop someone from buying a lookalike address, so it still helps to tell your users what your real emails look like.
What all of this cost
The name check, the address, the phone book, the lockbox, sending mail, receiving mail, and the proof that mail is really from me cost less than $20 a year total. Everything besides the domain is free at my size.
What it actually cost me was time. I’d budgeted an hour or two for the name and domain. I lost hours because Claude and I were checking domains the wrong way, and because I kept chasing a perfect name.
Oh, and I also pay for Claude and ChatGPT. I like the freedom of building without a limit. And since I already use these two tools in my personal life. I’m not counting the costs of these tools at this time.
Stack or tool?
Last week’s test asks one question: if this disappeared tomorrow, does my platform stop working? And that will let you know if it’s part of your “tech stack” or simply a tools you use.
- Stack: Porkbun (the address), Cloudflare DNS (the phone book), and Resend (no sign-in links without it)
- Tools: the USPTO trademark search, the Verisign lookup, Bitwarden, and, for now, Cloudflare Email Routing
SPF, DKIM, and DMARC aren’t software at all. They’re settings that live inside the phone book.
Refresher… and before the next part in this series.
Two rules to keep:
- Check the trademark register before you fall in love with a name.
- Set up your password manager before anything hands you a key.
You don’t have to know all of this going in.
Claude Code and Codex will often catch these pieces on their own.
Your job is knowing what you’re building well enough to give good directions, and noticing when the AI is confidently wrong. (It was wrong about my domains for hours. 🥴)
Three questions for you.
- Have you already named your idea? Search it on the USPTO trademark site this week and tell me what came up.
- Where do your passwords live right now?
- Which of these pieces did you not know existed before today?
Tell me in the comments.
I’ll chat soon!
Marsha
