Paso

I built Paso out of frustration with how planning tools break down over time. Even when I worked with structured systems at work, I still kept a private list on the side just to know what I actually needed to do next. Over the years I tried many tools: Jira at work, and personally Superlist, Notion, ClickUp, Asana, Obsidian, Microsoft To Do, and TickTick. They all worked well at the beginning, but over time they became noisy, fragmented, or too rigid for real life. What worked best for me was surprisingly simple: one very long document. New things at the top, days separated by dates. It gave me perspective and continuity, but it clearly lacked structure and started to hit its limits. That’s where Paso started. The core idea was to combine that long-term perspective with just enough structure to make it sustainable. A single, infinite timeline where every day is a space for notes and actions. Ideas can live freely in a draft state and only move into time when they’re real. As time passes, finished work fades instead of piling up. During development, the biggest shift was realizing that planning shouldn’t optimize your day. It should help you stay oriented over weeks and months. Motivation comes and goes, but direction is what keeps things moving. Paso is the result of that process - calmer, slower, and built for long-term use without rotting over time.