Looping

Software doesn't stand still—it evolves. But the tools we use to manage that evolution are often disconnected, fragmented, or missing entirely.

I've spent years thinking about how teams build and run software, how decisions are made, how system health is maintained, and how context is passed forward over time. What's missing is a platform that ties it all together.

That's what I'm building with Looping.

A Suite for Managing Software Over Time

Looping will be a suite of integrated products designed to help teams build, operate, and iterate on software in a structured, intentional way. It provides a clear framework for managing development, experimenting with new ideas, and maintaining operational health—all in one place.

The suite will support planning, execution, learning, and coordination—helping teams stay aligned not just on what they’re building, but how it changes over time.

This is Just the Beginning

Looping is still in development, but I'm starting to share now because I want to start the conversation early. Future products will help teams manage the entire software lifecycle:

• Development – Plan, document, and track product changes with roadmaps and changelogs.
• Experiments – Run A/B tests, feature flagging, and cohort analysis to refine ideas before fully committing.
• Operations – Monitor service health, track incidents, and keep teams aligned on responsibilities.

I don't expect to get everything right from day one—Looping will evolve just like the software it's designed to support. If this vision resonates with you, I'd love to hear your thoughts.