One career collapse. A public rebuild. The operating systems behind it, built for the operators who needed them too.

My name is Taylor. I spent twelve years in business operations, nine as an entrepreneur and three inside corporate. Across every role, every venture, every messy back office I walked into, the pattern was the same. I knew how to build the systems that made other people's businesses run.

Most recently, I served as the operational integrator across Sales, Finance, and Operations for a fast-moving company. I reduced A/R aging from 58% to 6%, oversaw $1.5M+ in monthly AP/AR, and installed EOS accountability rhythms that improved visibility and execution across the business. Before that, I directed operations for a 959,000 sq ft Class-A commercial tower, negotiated 50+ vendor contracts that cut operating expenses by 24%, and helped manage a 250+ property portfolio that grew asset valuation by 15%.

Operations at scale. Process clarity. Frameworks installed and held.

It worked everywhere except at home. When my career reset (again), I had no personal infrastructure, no backup income, no operating system for my own next move. Just reactive scrambling.

The decision

I had two options. Go back to corporate in this economy and chase job security inside someone else's company, or accept that the job security I was looking for didn't exist outside of what I build for myself.

And then I went one step further. Instead of packaging the skills I was trying to get hired for to serve one company, one salary, one team, I decided to package them to serve more. More businesses. More operators. More security, growth, and future, in Jesus' name, than just one.

My job security is now building job security for you.

What they kept asking

The same questions kept coming back from the home service and real estate operators I knew:

"How do I get my business to run without me in it?" "Why does every operational problem still route through my phone?" "I'm making real money but I have no idea where it's going." "I keep hiring and they keep leaving. What am I doing wrong?"

These weren't beginner problems. These were operators doing $500K, $1M, $3M in revenue, technically excellent at their craft and quietly drowning in the back office. They didn't need motivation. They needed systems.

I'd spent over a decade building exactly those systems for other companies. So I started building them for the operators in front of me.

That's Comeback Ops Co.

A productized operations practice built around one principle: I won't install a system in your business that I'm not running in my own. Every framework gets executed under pressure before it gets sold. Every miss, fix, and rebuild gets documented publicly so you can watch the work and decide for yourself.

I'm not a consultant who hands you a deck and disappears. I'm an operator who embeds, builds, and stays until the systems hold.

You don't have to take my word for any of it. You can read the receipts.

Keep going.

If you made it this far, you're probably the kind of operator this is built for.

I write a monthly newsletter for service business operators rebuilding and scaling in real time. Each issue pulls one real moment from what I'm building and walks through the framework underneath it. The honest version of what you see on socials, with more of the receipts.

And if you’re ready to take the next step, book office hours with me and let’s figure your stuff out!