Run the project, not the project-management software.

Ro Projects are first-class contexts for outcomes whose work, knowledge, relationships, authority, and decisions benefit from one explicit boundary. Not every durable record needs to belong to a Project.

A project should explain the work, not create more of it.

Personal project management becomes expensive when maintaining the system competes with delivering the outcome. Ro starts with meaningful records and relationships, so a Project can stay legible without constructing a bespoke database first.

Tasks show responsibility, blockers, waiting, review, and history. Notes hold current knowledge. Discussions retain deliberation and conclusions. People and Organizations keep the business context nearby. Attention returns only the matters that genuinely need consideration.

Project workspaceOutcome, work, knowledge, and relationships
Projects / Northstar launchActive
PROJECT

Northstar launch

Prepare the new service for its first customer rollout.

Owner
Alex
Open Tasks
8
Waiting
2
Needs attention
3

Work now

Finish onboarding checklistAlex · In progress
Review import behaviorSam · Review
Confirm rollout groupWaiting for two replies

Knowledge and decisions

Release approachNote · Updated yesterday
Scope the first releaseDiscussion · Concluded
Acceptance scenariosNote · 4 related Tasks
Northstar launch / 18 related recordsHistory available

One project surface, several kinds of truth.

The Project is an operational and collaboration boundary, not merely a folder around a task list.

Outcome

Keep the purpose and current state visible.

The Project carries the intended result, its active work, relevant knowledge, audience, and attributable history without requiring a status meeting to reconstruct them.

Work

Move Tasks through responsibility and waiting.

Plan parent and subtask relationships where they are real, record blockers, and let reviews or returned commitments surface through Attention.

Knowledge

Keep Notes and conclusions beside execution.

A specification, playbook, meeting note, or resolved Discussion remains linked to the work it informed instead of becoming detached documentation.

Participation

Add people or agents against the same records.

A person can own the entire Project. When an Agent Actor is useful, delegation happens through explicit Tasks and bounded authority, not through a parallel AI workspace.

Serious project context without portfolio bureaucracy.

Ro can support an individual's projects, a team scope, client engagements, or an owner-operated company. It is not trying to recreate enterprise resource planning, timesheets, or a wall of portfolio dashboards.

The local-only product is designed to be complete and offline-capable. Synchronization is added when people, devices, or remote workers need one shared authority. Ro is under active development.

Projects
A real boundary
Tasks
Accountable work
Knowledge
Linked and current
Agents
Optional participants

Run projects as one connected record.

Join early access and help shape Ro’s project workflow.

Tell us about your work Optional

Only Ro product and early-access updates. Unsubscribe whenever you like.