Most calendars are happy to let you book 11 hours of meetings on a Tuesday and say nothing. Timeweaver is the opposite. It treats your work week as a fixed budget of hours and makes you allocate it across the things that actually matter — deep work, delivery, stakeholder time, learning — then continuously grades the plan for overbooking, fragmentation and cognitive overload before the week even starts.
It started as a personal itch: I wanted to see whether my intentions for the week were physically possible, not just whether they fit on a grid.
What it does
Budgets, not just events
Each category gets targets, soft caps, hard caps and minimums — Timeweaver flags when you’re near a cap, over it, or under a minimum you said mattered.
A governance layer that scores your week
An evaluation engine computes capacity, meeting density, context switches, deep-work integrity and overbooking, then rolls them into a cognitive-load score per day.
Guardrails with an override trail
Blow through a hard cap and you can’t just sail past it — you confirm and record why, so exceptions stay deliberate and logged.
Smart suggestions
Give categories a percentage of your week and it greedily fills the remaining capacity, steering deep-work toward your lowest-load days.
Why it’s interesting
The fun part wasn’t the CRUD — it was the evaluation model. Turning fuzzy ideas like “this week feels too chaotic” into a weighted score (meeting density, switch rate, fragmentation, deep-work integrity, overbooking) forced me to be explicit about what a good week actually looks like. It’s opinionated software, and that’s the point.
Labs noteAn unpublished side project — a sandbox for thinking about time, attention and how much an app should push back on its user. Rough edges included, on purpose.