Documentation
Qivo is a product development tool: work orchestration for people and AI agents. You turn the work of building a product — hardware or software — into tasks and hand each one to whoever will do it — a teammate, or an AI agent (§13). Creating the work is the point; the planning is what keeps it honest: each task carries the hours of work left on it, the roadmap knows how much time each person actually has, and each is colored by whether it will really be ready in time — not by which folder it happens to live in. A plan that tells the truth, so the work you hand out is a commitment rather than a wish.
Qivo in one minute
The planner's browser tab is titled Qivo.
How work is organized
Organization → Project → Sub-project → Task. Projects and sub-projects are accountable to a named lead; teams are sharing groups.
Finding your way around
On desktop, the left navigation panel is 273.6px wide, giving project names more room. Projects use text names without identity icons or icon pickers.
The Overview — project health at a glance
A dashboard, scoped to the current project, sub-project, or all of them. In Blue and Dark, primary headings, names and values use near-white text; supporting…
The Board
Five status columns — pinned headers that stay put as you scroll, live counts, and a + on each column that opens the New-task dialog and creates into that…
The Roadmap
The Task, week and milestone header stays above the task scroll area. The vertical scrollbar starts below that header; task rows and dependency lines stay…
"Will it be ready in time?" — the delay status
This is Qivo's headline answer to the question every status meeting circles around. For every task that isn't done, Qivo projects the week the work will…
Planning against real capacity
"Plan on roadmap" jumps to the timeline with the task's whole row highlighted, from its name across the timeline. The blue tint, thin edges, marker beside…
The task window
Opening a task floats one window over a blurred backdrop. Its first line is a breadcrumb — project → sub-project, saying where the task lives. Each name is a…
Organization and team settings
Every settings page is a title over outlined boxes, one per section, each named on its border. Inside a box, a hairline and a name mark a further group, so…
Working together
A person in Qivo is a name and an email address. Nothing else — there is no job title to keep current, because a title nobody could edit after the seat was…
Who sees what — the access model
Projects can be shared with teams and individual users. Access inherits to sub-projects and tasks, with one read-only ceiling over all grants.
Automation & AI — the REST API and the MCP server
Two surfaces, one credential model: whoever calls is a user.
Administration, guard rails and the demo
Organization → Users lists everyone, and each row carries one control that answers what they are to you. The email address beneath a person's name, or the…
What sets Qivo apart — the marketing summary
The public homepage introduces Qivo through the Airspace design: a spacious blue page with a board overview, roadmap and dependencies, weekly capacity, and…