Founder & Developer · 2026 — Now
In active development
Lubble.
A planning system built for the long horizon — one that connects what you do today to where you intend to be in five years, and does the coordination in between.
Most productivity tools optimise the next 24 hours. They are very good at clearing a list and very bad at telling you whether the list was worth clearing. Lubble is built the other way round: it starts from long-term outcomes — financial position, career trajectory, health, relationships — and works backwards into what this quarter, this week and this afternoon should actually contain.
The problem
Being busy is not the same as making progress.
School, work, money, health, relationships and long-term ambitions all compete for the same finite attention. The default failure isn't laziness — it's drift. You spend years responding to whatever is loudest, and the things that actually compound never get scheduled at all.
The fix isn't another list. It's a system that holds the long view for you, and keeps applying it to the small decisions where it's easy to lose.
Reactive
Strategic
The model
Four horizons, one plan.
Every item Lubble tracks is attached to a horizon, and every horizon inherits from the one above it. A task exists because a week needs it; a week exists because a quarter needs it. Anything that can't trace a line upward is a candidate to be cut — which is how the system stays efficient without you auditing it.
Execution
The short list, already filtered. You see what to do now, not everything you could do.
Momentum
Concrete targets with a deadline close enough to feel real — the unit where habits either hold or break.
Trajectory
Savings and investment position, skills acquired, career steps taken. Slow-moving numbers that only respond to consistency.
Direction
The outcome everything else is reverse-engineered from. Rarely changes, and quietly decides everything below it.
The principle
Autonomous, not automatic.
Lubble runs the routine coordination on its own — rescheduling, sequencing, protecting the blocks that matter. But anything consequential stops and asks, with its reasoning shown. A system that plans your next five years has to be one you can audit and overrule, or it isn't trustworthy enough to hand the long view to.
That's an architectural commitment, not a setting: permissions are enforced server-side, so an approval gate can't be talked around.
What it optimises for
Compounding, not completion.
Growth
Progress you can see
Long-range targets broken into units small enough to act on and visible enough to stay motivating.
Efficiency
Less deciding
The cost of organising your life should fall as the system learns. Planning overhead is a bug, not a feature.
Durability
Rest is protected
Sleep, social life and recovery are inputs to long-term output, so they're scheduled, not sacrificed.
The three pillars
Signal from noise
School, work, money and relationships resolved into one picture, ranked by what actually moves the long-term outcome.
Autonomous, not automatic
It handles the routine work itself and holds anything major for approval, with its reasoning on show. You stay in control.
Built for the long game
Daily choices stay tied to multi-year goals — savings rate, investment targets, career direction — because that's where the compounding happens.
Not a to-do list. A system for making the next five years deliberate.
Building this is the most interesting problem I've worked on. If it's something that piques your interest, check out trylubble.com.