A calmer starting point
We did not start Orgo by listing every feature a planning tool could possibly contain. We started with a smaller question: what would it take to make an ordinary week feel more legible?
Most of us already have calendars, notes, reminders, and loose documents. The problem is rarely that nothing exists. The problem is that context splinters. A meeting lives in one tool, the reasoning behind it sits in another, and the next action ends up in a third place with no memory attached to it.
Orgo is our attempt to bring those fragments back into one calm workspace. We want planning to feel deliberate again: not frantic, not over-optimized, and not packed with features that punish you for having a messy day.
What we chose for the first release
The first public version of Orgo focuses on three surfaces that belong together:
- a weekly planning layer that keeps time visible
- a notes layer that captures decisions while they are fresh
- a task layer that turns reflection into follow-through
That meant saying no to a lot. We did not try to become a full collaboration suite on day one. We did not chase automation for its own sake. We did not fill the product with decorative urgency just to make it feel busy.
The principle underneath the product
Calm is not a visual mood we add at the end. It is a product principle. It changes what deserves prominence, how much motion is acceptable, and how often the interface should ask for attention.
The same principle shapes this journal. We want each post to explain not just what shipped, but why it deserved to exist in the first place. If the product is about helping people remember what matters, the writing should do the same.
