Research is complete and the draft is ready.
Commitment · approval still needs AlexKeep your work from living in your head.
Ro is a native, async workspace where work, relationships, responsibilities, and decisions stay coherent over time. It brings back what needs you and lets the rest stay quiet.
Under active development · Concept product shown
Two things need you.
Everything else is handled or healthy.
Requires judgment 1
Recovery exhausted 1
Automated recovery was attempted. A bounded fix is ready.
Responsibility · release authority requiredTwo things need you.
Everything else can stay out of view.
The few things that need you. Nothing more.
Attention is a durable reason something deserves your awareness, judgment, or action now. A promise nearing its due date or a waiting threshold passing can qualify without any autonomous attempt.
Three things need you.
Friday, 19 September
Draft is ready; promised outcome needs approval
Review proposalRecovery exhausted; release authority required
Decide on fixFollow-up threshold passed; no automatic authority
Approve follow-upAttention precision matters more than coverage. An empty surface and “Nothing needs you right now” are successful product outcomes.
Who does the work is not the point.
You, another person, an automation, or an agent can carry it out. Ro keeps the responsibility, authority, waiting, decision, and accepted outcome coherent.
What must remain true?
Responsibility · Commitment if validated · Waiting · Decision · Authority
Ro · email · browser
Their chosen tools
Schedules · provider systems
External execution state
Agents increase the leverage. They do not create the need.
Ro should already earn its place for work you do yourself or with other people. Delegation makes the same durable record more valuable. A Workspace can hold your own scope, a team, a client engagement, or a company; the first commercial focus is owner-operated and small businesses.
Keep specialist work in specialist tools.
Ro can own the ordinary work while code, mail, accounting, payments, and execution details remain authoritative in their natural systems.
Tasks, notes, discussions, relationships
Code, issues, changes, checks
Messages, delivery, appointments
Accounting, payments, workflows, agent execution
Ro references external truth and reconciles relevant outcomes. It does not aggregate a full copy of every provider or demand that specialist work move into Ro.
Ro can be where the ordinary work happens.
Tasks, Notes, Projects, Discussions, People, Organizations, and Interactions are first-class native surfaces. Specialist artifacts can remain elsewhere without losing their meaning in Ro.
Can you send the revised proposal by Friday?
The conversation and delivery state remain in the mail provider.
- Beneficiary
- Customer
- Outcome
- Proposal delivered
- Due
- Friday
- Responsible
- Alex
- Source
- Email reference
Responsibilities, authority, decisions, outcomes, risk, and provenance remain durable across tools and handoffs.
Ro Tasks give ordinary work a durable address; specialist work can retain its own canonical artifact.
Notes, Projects, Discussions, Tasks, and relationship records form a complete workspace when that is the simplest home.
Stable references lead back to source control, mail, accounting, files, workflows, and execution systems when authoritative detail matters.
Ro organizes responsibility and attention around the work.
It does not need to organize every artifact, replace every specialist tool, or become another screen you supervise.
Native and local-first from the beginning.
The complete local authority lives on your computer, needs no Ro account or server, and remains useful through the GUI, CLI, capture surfaces, agents, and integrations. Add synchronization only when the work needs it.
The complete local authority lives here.
- Authority
- This Mac
- Account
- Not required
- Availability
- Offline
- Access
- Native app · CLI · local API
- Capture
- Global shortcut · links · files
Organizational state and any first-party records remain available without a Ro server.
Add synchronization without changing what the work means.
Use Ro Cloud or a self-hosted Ro Server when people, devices, or remote workers need one shared authority. Native clients keep authorized work locally available.
A complete native workspace, with clear boundaries.
Tasks, planning, Projects, Notes, and relationship records are first-class Ro surfaces. Specialist systems remain authoritative where they are the better home.
Writing from development
All writing →What part of your work still depends on your memory?
Join early access if commitments, waiting, decisions, or follow-up still require you to keep checking several tools by hand.