Product & engineering

Plan next to the customers
who asked for it.

Every planning tool can hold a backlog. What none of them can tell you is which customers are waiting on a feature, what those accounts are worth, or which support threads are still open against it — because a planning tool has no idea what a customer is. In RowFold your roadmap is a set of ordinary tables, one link away from all of it.

Start free See the roadmap template

01What you get

The roadmap template builds four linked tables and fills them:

  • Features — status, priority, team, sprint, an estimate in points, an owner, and a count of the customer requests behind it.
  • Sprints — start, end, goal, status, how many features are committed, and the total points across them.
  • Teams — who owns what, and who leads.
  • Customer requests — what people actually asked for, linked to the feature it became.

Those are tables, not a fixed app. Add a column, change the statuses, point a view at it, or throw one away — the same as any other table you build here.

02The link that matters

Features carry an Asked by count: a rollup across the customer requests linked to that feature. It is one column, and it changes the conversation in planning — “this one is asked for eleven times and two of them are on your biggest account” is a different sentence from “this one is a P2”.

Because everything is in one workspace, that link keeps going. A request can come from a support ticket, and a ticket sits one link from that customer’s orders and invoices. So “what is the revenue behind the top of our backlog” is a report, not a data export and a spreadsheet.

Plain English: the customer asking for a feature and the customer in your accounts are the same row. There is nothing to sync.

03Ordering the backlog

A backlog is ordered by judgement, not by a column. Sort any view by Manual order and rows get a grip you can drag — the order is saved against the record and everyone sees it.

Two things worth knowing. It works on a phone: the grip is its own small target, so a swipe anywhere else on the row still scrolls the grid as normal. And it works from the keyboard: focus a grip and use the arrow keys, which is also the fastest way to move something a long way.

Manual order is a platform feature, not a roadmap one — any table can be hand-ordered.

04Sprints and burndown

A sprint is a record with a start, an end and a goal. Features link to it, so the count of committed features and the total points come from rollups rather than from anyone keeping a tally.

Put a burndown tile on a dashboard and it plots what is still outstanding against the pace it would need — the line, and the line it should have followed. It totals a points field or counts records, steps by day, week or month, and reads whichever date means “finished” on your table.

05What it does not do

Checked against the code, not assumed:

  • No ceremonies. There is no planning poker, no retro board, no stand-up prompt.
  • No velocity forecasting. Past sprints total their points; nothing projects a finish date from them.
  • No git, PR or CI integration. Nothing moves a feature because a branch merged.
  • It is not trying to replace a tool your engineers like. If your team lives in a dedicated issue tracker and is happy, keep it. This is for the planning that has to sit beside customers, revenue and support — which is the part that usually ends up in a spreadsheet.

Next: the template, the helpdesk if the requests arrive as support threads, or what it costs. Everything here is part of RowFold, not an add-on with its own price.