Everything was chaotic. Nothing was documented. And everything was on fire.

When I first joined my federal agency, we were still using emails to get anything done. It was madness. You had to know what you needed, who to send it to, exactly what to ask for, exactly what to provide, and the next step in the process. New employees would take months to figure it out -some just left.

It was institutional knowledge at its worst. Critical processes trapped in people's heads, creating bottlenecks, mistakes, and frustration.

But it was this chaos that shaped me and this product.

Twelve years ago, I built the first version of LoopyList to solve our operational chaos. Instead of relying on institutional knowledge, teams could simply follow clear, repeatable checklists. No more guessing who handled what or what came next.

The system handled thousands of these processes for over a decade. Everyone loved it because it was simple, flexible, and actually helped them get work done -not fighting with the software.

Avoid institutional knowledge at all costs. Users shouldn't need to know which team handles what. They just need to know what they're trying to accomplish.

Trust people, not rules. Everyone knows their job better than the person building the workflow. Instead of baking in rigid logic and protocols, I chose flexibility with accountability. Less maintenance for admins, more usability for teams.

Assign to teams, not users. Even if it's a team of 1, the assignment will allow you to scale easier later. It's easier to change 1 team than 50 lists.

Orchestration, not automation. LoopyList doesn't automate your processes -it orchestrates them. It guides people through the right steps while capturing what actually happened.

I spent over 20 years in federal IT building applications, managing security audits, and leading technical teams. In early 2025 I was faced with a choice: either I could stay with the government and risk losing my job and pension, or I could retire early and pursue this project I'd been developing since 2012.

Retiring early meant losing part of my pension, and my wife and I would barely break even each month. But I took the risk and left on my own terms to build the next version of the system that transformed our chaotic agency into a well-oiled machine.

I had an umbrella, although a small one, to shelter me enough to work on this project full time.

Most process orchestration software tries to be everything to everyone. They're bloated, expensive, and require months of implementation.

When I left government, I hit the ground running. I started adding every feature I'd ever wanted. The problem? I was building for everyone, which meant building for no one. I realized I'd have to become a big company to support a big product. This was exactly the problem I was trying to avoid.

So I pivoted. I stripped out the enterprise complexity and focused on what made the original great: simplicity, flexibility, and results. LoopyList became a tool for people who want to get things done without fighting their software.

LoopyList is: A lightweight checklist orchestration tool for repeatable processes. Whether you're onboarding customers, managing property turnovers, or handling team workflows, it helps you execute consistently while capturing what actually happened in the process.

LoopyList isn't: A bloated enterprise tool that connects to everything else. It doesn't bait you in to automate processes that really can't (or shouldn't) be automated. Or force you into rigid workflows that costs time and money to maintain. It's simply flexible enough to work for your team from day one.

LoopyList works great for people tired of missing steps, losing details, or reinventing processes every time. It worked for our 300-person government agency for over a decade. It will work for you.

Premium access is almost ready. It's free to try and designed to grow with you. Got questions? Curious how it could fit your workflow?

Reach out. I'd love to hear from you.

You're exactly who I built this for.