The problem no one could solve.
Two ways to fail, no way to win.
Warrior Rising helps veterans and military families start and grow businesses, and Warrior Academy is where that starts online — courses, enrollment, a student dashboard. Except signups were misbehaving in a way nobody could pin down.
Configure it one way: the veteran got registered and enrolled, but their signup information vanished. Configure it the other way: the information saved, but they were never enrolled. Staff were blind either way, the problem had outlived everyone who'd tried to fix it, and then their Director of Programs sent a text.
The site had been accumulating for years. We started digging.
The site didn't need more code. It needed less.
Two root causes, once the layers came off. A signup form with another form nested inside it — invalid HTML, which browsers handle about as well as you'd expect: they quietly close the first form and let the two systems fight over the submission. And injected JavaScript hijacking the enrollment process with hardcoded URLs and half-second timing delays — so enrollment worked whenever the timing worked, and failed silently whenever it didn't.
Nobody had broken the site on purpose. It had been patched into fragility, one injection at a time.
Hundreds of lines of fragile code, retired by one small plugin.
We removed the nested form, moved the agreement into the page itself, and rebuilt enrollment on the LMS's own supported hooks — deliberate, server-side, no timing gods required. Then we packaged it as a proper WordPress plugin: a settings panel staff can actually use, CSRF protection, no open redirects, no loops.
Small enough to read in one sitting. Boring in all the ways infrastructure should be.
“What would you need to bring hosting over?”
Ten days after the fix, that was Warrior Rising's question. One simple text. Our honest answer: we normally host only what we build — the rule protects every client on our infrastructure — so Warrior Rising would need its own dedicated server while we rebuilt the environment properly. They said yes.
Modern PHP, real memory, daily backups, security scanning, the plugin graveyard cleared out, old admin accounts retired. Better hosting than they had, for less than they'd been paying. And the support changed shape entirely: issues that used to sit in a ticket queue now get resolved over a text — occasionally before we've even seen the message.
Came for a fix. Stayed for the infrastructure.
The right diagnosis is the cheapest fix.
Months of symptoms traced to two root causes and solved with less code than the workarounds had accumulated. Infrastructure is customer-ing too — the quietest kind.
When it's done right, nobody notices, and everybody gets through the door.