Product management

The board that knows who's paying.

Every tracker shows you the task. This one shows you the customer behind it — their account, their revenue, the feedback that asked for it, and the goal it serves. Drag-and-drop board, deep task detail, releases, OKRs — and views that morph to your methodology, not the other way round.

Example data

The board

Built like the trackers you've used. Joined like none of them.

A drag-and-drop board that does the table stakes properly — then puts a customer record behind every card.

    Drag and drop

    Move cards between columns; group by status or your own custom grouping.

    Filters that match how you triage

    Slice the board by priority, type, assignee, or tags — in any combination.

    WIP limits per column

    Set a limit on any column and see when a stage is overloaded.

    Custom fields

    Add the fields your team actually needs on the task, not a plugin away.

    Multiple assignees

    Tasks and subtasks each take several owners — pairing isn't an edge case.

    Subtasks

    Break work down; every subtask has its own status and assignees.

Inside a task

Open a card. Everything's already there.

The task detail is a full work surface — not a modal with a description box. Conversation, files, blockers, and time all live on the card.

  • Comments. Threaded team discussion on the task itself — decisions stay next to the work.
  • Attachments. Drop files straight onto the task.
  • Dependencies. Mark what this task blocks and what blocks it — blockers are visible, not tribal knowledge.
  • Time tracking. Start a timer on the task — one running timer per person — and tracked time fills against the estimate.
  • Estimates. Story points, t-shirt sizes, hours, or ideal days — whichever your product is configured for.
  • Activity feed. Every change on the task, logged as it happens.

The Spine Strip

Every task carries its why.

Below the description, each task wears a strip no other tracker has: the customer account and what they pay, the piece of feedback that asked for this, and the objective it advances. That's the strip on the card at the top of this page — Fernwood & Co · $5,000/mo.

    Account + MRR

    Assign the task to a customer and it carries their plan and revenue. Cutting it means knowing exactly whose money walks.

    Insight

    The customer feedback that asked for this work, linked — verbatim, not paraphrased into a ticket.

    Objective

    The goal this task advances, so the board reads as strategy — not just a queue.

Run it your way

One board. It speaks your methodology.

Pick a methodology per product and the board grows the views that method actually needs — no plugins, no add-ons, no second tool.

    Scrum

    Sprint planning with burndown charts and velocity — plan the sprint, watch it burn down.

    Shape Up

    A real hill chart: watch work move from figuring-it-out to getting-it-done.

    Waterfall

    A Gantt timeline with phases — for the work that genuinely is sequential.

    Experimental

    An experiment board: hypothesis in, verdict out — validated or not.

Watch: four methodologies, one product OS · Example data

Kanban and Scrum boards included too — Kanban is where those WIP limits earn their keep.

Releases

A shipping log, not a guessing game.

Cut a release — upcoming or already shipped — and point tasks at it from the task detail. Each release shows the work targeting it and how much of it is done.

  • Cut releases by hand — name them, date them, mark them shipped.
  • Tasks target a release from their detail view — the release page lists them with live status.
  • Done-vs-total per release, so "can we ship?" has a number.

Goals & OKRs

Objectives wired to the work — not a quarterly spreadsheet.

Create objectives for a period, add key results, and track them with live progress bars. The same objectives appear on task Spine Strips, so strategy and execution read from one record.

  • Objectives scoped to a period — quarters, halves, whatever you run.
  • Key results in any unit: percentages, dollars, or a unit you type yourself.
  • Live progress bars per key result and per objective — update the number, the bar moves.

Configured per product

Each product picks its own way of working.

Methodology, estimation style, and prioritization framework are set per product in settings — run Scrum on the platform and Shape Up on the new bet, side by side in one org.

    Methodology

    Scrum, Kanban, Shape Up, Waterfall, or Experimental — the board's views follow.

    Estimation

    Story points, t-shirt sizes, hours, ideal days — or none at all.

    Prioritization

    RICE, WSJF, Value-Effort, MoSCoW, or Kano — scoring real demand over in Insights.

Honest edges: Shape Up pitches and a betting table are built but not exposed in the board yet — the hill chart is what ships today. ProductOS is a web app; figures shown on this page are example data.

Early access

See your work carry its customers.

Connect Stripe and GitHub in minutes and watch your own tasks pick up accounts, revenue, and feedback — on a walkthrough with us.