Capture and structure
Turn rough text or voice into connected projects, goals, plans, tasks, documents, and context.
PUBLIC ROADMAP · UPDATED JULY 10, 2026
BuildOS is becoming a thinking environment where rough input becomes structured work, project memory compounds, and people and agents operate from the same context.
SHIPPED
These are current product capabilities, not future promises.
Turn rough text or voice into connected projects, goals, plans, tasks, documents, and context.
Keep activity, source context, document history, relationships, and daily briefs attached to the work.
Explore, update, audit, and forecast work with the relevant project, task, document, brief, and calendar context.
Delegate bounded work to background Agent Runs that can be watched, steered, scheduled, and reviewed before commit.
Visualize how work connects, invite project members with scoped roles, and publish selected documents to the web.
Sync with Google Calendar, search across structured work, repeat tasks, and connect outside agents through MCP.
NOW
The immediate work is activation, verification, reliability, and a clear business model.
Show the messy-input-to-structure transformation, prove that project memory persists, and make the first brief immediately useful.
Finish production verification for AI Inbox, project review loops, and evidence-backed Complete Project Audits.
Complete live UI and calendar verification for Agent Runs and scheduled Operatives, then tighten reliability and safety.
Billing is not active. We will define the paid experience and communicate it clearly before any account can be charged.
NEXT
The next layer compounds public work, recurring workflows, connected agents, and review controls.
Build on public document pages with a showcase, cloneable project structures, and stronger creator attribution.
Edit schedules, regenerate future instances, and create the next occurrence without maintaining a large batch.
Package the local MCP bridge, improve connector setup, and make scoped BuildOS context easier to use from outside tools.
Give people clearer control over audit history, review appetite, notifications, and when proactive suggestions appear.
EXPLORING
These ideas need stronger user evidence before they become commitments.
Notice meaningful drift or blocked work early, then offer a grounded next move without creating notification noise.
Help people see competing commitments and shared context across projects without turning BuildOS into enterprise portfolio software.
Let trusted agents act on recurring project work with explicit scope, observable runs, and review when the stakes require it.
The responsive web app comes first. Native iOS and Android remain an option when mobile usage justifies a second client.
DELIBERATE BOUNDARIES
BuildOS is not trying to become heavyweight portfolio software, fabricate a percentage chance of success, or silently rewrite your schedule. We prefer evidence-backed project health, lightweight dependencies, visible agent work, and user-controlled changes.
HELP SHAPE THE ROADMAP
The most useful feedback starts with a real project: what you tried, what stayed scattered, and what would have helped you move forward.