Closing Loops · Episode 1 — with Cortni Lawson, founder of InfraNet HR. Published July 2, 2026 · 20 min listen.
🎧 Listen to Episode 1 on Spotify
What looks like an ordinary text message can represent weeks of invisible work.
In the first episode of Closing Loops, InfraNet founder Cortni Lawson tells the story behind one of the most meaningful milestones in building the platform: the first text message sent from her own software. Getting there took a month — an AWS approval gauntlet, three rejections, and a lot of quiet persistence — to send a single message that read “InfraNet HR Production path test from app.infranet-hr.com.”
But the episode isn’t really about AWS, SMS, or code. It’s about the invisible work that founders, HR professionals, and so many others do every day — the work nobody notices until something goes wrong. It’s about the difference between productivity and capacity, and why the best infrastructure is the kind that disappears.
This morning, my phone buzzed. Normally I wouldn’t think twice about a text message — I probably receive twenty or thirty of them every day, and most disappear from my memory almost as quickly as they arrive. This one didn’t. It said, “InfraNet HR Production path test from app.infranet-hr.com.”
I stared at it for a second, and then I smiled. Not because it was particularly exciting to anyone else — it was just a text message. But to me, it represented an entire month of work.
Welcome to Closing Loops. I’m Cortni. I’ve spent nearly twenty years working in recruiting, human resources, safety, payroll, compliance, and now software. This show isn’t really about any one of those things. It’s about people. It’s about work. It’s about the invisible systems quietly shaping our lives every single day. And today, I wanted to tell you why one ordinary text message meant more to me than I ever expected.
At the end of May, AWS approved InfraNet to send email. That process wasn’t bad — I answered a few questions, told them about my business, explained what the platform did, and approval came pretty quickly. I remember thinking, well, that wasn’t so bad.
Then I had what felt like a perfectly reasonable thought. I’ve been recruiting for over fifteen years. People don’t really live in their inboxes anymore — they live on their phones. If someone is out on maternity leave, if they’re recovering from an injury, if they’re waiting to hear whether paperwork has been approved, a text message is often the fastest way to reach them. So I thought: if email was that straightforward, surely text messaging can’t be much different.
It turns out I was adorable, because that assumption cost me an entire month.
The first thing AWS tells me is that I need an originator phone number. Perfect — let’s request one. Except I can’t, because you need a campaign first. Okay, let’s make a campaign. Except you can’t create a campaign until you’ve registered your brand. Okay, let’s register the brand. I submit my business information, my FEIN, wait a couple of days — thankfully, approved. Now I can finally build the campaign.
Except building a campaign isn’t really building a campaign. It’s proving to every wireless carrier that you’re not a scammer — that you’re not selling miracle supplements, not promoting political candidates, not sending spam. You’re just trying to communicate with people who actually asked to hear from you. Which, ironically, is exactly what InfraNet exists to do.
InfraNet doesn’t send advertisements. It doesn’t send promotional blasts. It sends reminders. It tells someone their leave paperwork has been approved. It reminds an employee they have fifteen days left to submit documentation. It lets a supervisor know a return-to-work release has been received. It keeps stakeholders connected during moments when communication actually matters. Human communication, wrapped in technology.
So I filled everything out. I even had ChatGPT help me word the responses, submitted it, waited — denied. Reason? Incomplete. That’s it. No roadmap, no explanation. Just no.
Okay, maybe I misunderstood something. Second submission, denied again. At this point I’m frustrated — not angry, just mentally tired. Is it my wording? My screenshots? The opt-in flow? The opt-out language? Because AWS has a remarkable ability to make you wonder whether you’ve forgotten how to read English.
So I walked away — not forever, just long enough to stop staring at the same wall. I went back to building InfraNet: state overlays, workers’ compensation logic, jurisdictional configurations, unemployment mapping — things that reminded me why I started building in the first place.
A week later, I came back. Third submission, denied again. At this point I’m seriously considering whether text messaging is even worth the effort — not because employees don’t deserve it, but because every hour I’m spending arguing with AWS is an hour I’m not building something else. That’s the trade-off founders make every single day. You don’t choose between good ideas. You choose which good idea gets your attention today.
A few days ago, I decided to try one more time. This time, I copied every rejection, every note, every screenshot, every tiny clue AWS had given me, and dumped it into Cursor. Together we rewrote everything — the campaign description, the opt-in language, the opt-out flow, the screenshots, the examples. I submitted it, closed my laptop, and honestly tried not to think about it.
The next morning I had completely put it out of my mind. And then I had this little tug: hey, you need to check AWS. So I pulled up AWS, signed in, and — approval. I laughed out loud. Not because I’d beaten AWS, but because I could finally move on. Or so I thought — because approval was only the beginning. Now I had to request the originator phone number, hook everything up, write the code, configure the webhook, test, fail, test again. Eventually AWS sent me a test message. Success.
Then InfraNet sent me one. And I don’t know why, but that hit differently. The sender didn’t say AWS. It didn’t say Amazon. It didn’t say test script. It said InfraNet HR. For the first time, my platform spoke. It had its own voice. And I just sat there looking at my phone, smiling.
Then something unexpected happened. I texted people I love. They were excited for me. They said congratulations, they asked questions, they celebrated with me. But after those conversations, I realized something. One of the loneliest parts of building something is learning how to celebrate by yourself. Not because people don’t love you — they do — but they didn’t spend the last month living inside the problem with you. They didn’t get rejected three times. They couldn’t experience that victory the way I did, because they hadn’t carried the weight that came before it. And that’s okay. I think that’s just part of building.
The text message itself wasn’t important. It was what it represented: weeks of invisible work.
Nobody wakes up on a Tuesday morning and thinks, wow, payroll happened again. Nobody applauds because the OSHA log was completed correctly. Nobody sends flowers because somebody remembered to mail the FMLA packet on time. Nobody celebrates when a workers’ compensation carrier gets exactly the document they needed — because that’s the expectation. It’s supposed to work. And honestly, I think that’s beautiful. The best infrastructure is invisible. When it works, it disappears. The more I thought about it, the more I realized that’s exactly what HR feels like.
I don’t think most people understand what HR actually does. If you’ve never worked in it, you probably think recruiting, benefits, maybe onboarding, maybe firing people, Christmas parties, open enrollment. That’s usually where the list ends.
The reality is that HR is one of the most operationally complex functions inside an organization. Imagine it’s Tuesday morning and you’re the only HR manager supporting three hundred employees. At 8:15, someone slices their hand on a machine. At 8:40, a supervisor calls because two employees are accusing each other of harassment. At 9:00, payroll has a garnishment question. At 9:30, a workers’ compensation adjuster is waiting on medical documentation. At 10:00, someone walks into your office because their spouse was just diagnosed with cancer, and they don’t know where to start.
Meanwhile, open enrollment is next month. ACA reporting is due. An unemployment hearing is Thursday. You have three interviews this afternoon, a safety committee meeting in thirty minutes, and OSHA has reporting deadlines that don’t particularly care how busy you are. That’s Tuesday. Not a bad Tuesday — just Tuesday.
None of those tasks are individually impossible. It’s the accumulation. It’s death by a thousand paper cuts. Eventually you stop having seconds. And that’s where organizations get themselves into trouble — not because people don’t care, but because people run out of capacity. There’s a difference. I’ve never met an HR professional who wanted to forget to follow up with an injured employee. It happens because one person is trying to carry the administrative weight of hundreds. Eventually something slips — and then everyone notices. Now there’s an audit, a lawsuit, a fine, an appeal, an investigation. Sometimes the better question is: how many things went right before this one thing went wrong? Because no one was counting those.
When people ask what InfraNet does, they usually expect a feature list: leave management, safety, OSHA, workers’ compensation, regulatory workflows, employee relations, AI, dashboards, text messaging. Sure, it does those things. But that’s not why I built it.
I built it because I spent nearly two decades watching good people drown in administrative work, and I kept asking the same question: why? Why are we still copying information from one form into another? Why are we manually tracking deadlines on spreadsheets? Why does an injury have to be documented three different times before it’s complete? Why does HR spend so much time remembering things that computers are incredibly good at remembering?
Technology has transformed accounting, manufacturing, logistics, finance, healthcare. But HR, in so many organizations, still lives in email inboxes and Excel spreadsheets. And the cost isn’t measured in paperwork. It’s measured in attention.
That was probably the biggest lesson recruiting ever taught me. When I interviewed people, I didn’t want my face buried in a laptop. I wanted to look at them, hear them, notice when they smiled talking about a previous job. People tell you so much when you actually pay attention. I always documented the interview afterward, never during, because for that hour, that person deserved my attention. Not half of it. All of it.
Somewhere along the way, I think we’ve confused productivity with capacity. They’re not the same thing. Productivity asks: how much can you get done? Capacity asks: how much of yourself is still available when the work is finished? Those are very different questions.
There was a time when I thought progress had to look dramatic — a launch, an announcement, funding, applause, fireworks. Now progress looks different. It looks like a deployment succeeding, a webhook finally behaving, an employee receiving the right reminder at exactly the right time, a text message arriving from my own platform. Those aren’t dramatic moments. They’re quiet, steady, almost invisible — but they move the work forward.
I keep thinking about that first text message. Someday it won’t come to me. It’ll go to an employee wondering if their leave paperwork was received, or someone recovering from an injury, or an HR manager juggling a hundred responsibilities who just needs one less thing to remember. They’ll never think about AWS or webhooks or the month I spent getting rejected. And honestly, I hope they never do — because if I did my job well, the technology will disappear and the communication will remain. And maybe, just maybe, someone in HR will get thirty extra minutes that day. Thirty minutes to walk the floor, to check in on an employee, to coach a supervisor, to listen — not because software replaced them, but because software remembered the things they shouldn’t have to.
That’s the future I’m trying to build. Not one where technology becomes more human — one where technology creates more room for humans to be human.
Thank you for spending some time with me today. I know your time matters. Until next time — keep closing loops.
InfraNet HR is compliance software that connects workforce events — workers’ compensation, OSHA, FMLA, and workplace incidents — in one platform, so overwhelmed HR teams see patterns before they become problems. Request access →