Skip to content

Product, from plan to task.

Whoever builds the product writes the plan, keeps the roadmap in a table, moves tasks and collects feedback. Everything is in the same place, and it connects.

A wiki that knows when it ages.

Pages worth knowing have someone who looks after them and a date until when they hold. Expired ones rise to the top, with the question: is it still right?

A week

An example, with made-up names and data. Every feature it names has its own page.

  1. Monday

    Write the product plan.

    A block document, with the roadmap table inside and links to the pages you need. You write it together, and the history can be rewound.

  2. Tuesday

    Look at the roadmap the way you need.

    The same table as a board, a timeline or a calendar: the view changes, the data does not.

  3. Wednesday

    Move the tasks.

    Tasks from every table live in one place, by space and by team, with due dates. Board by status and workload are behind Other views.

  4. Thursday

    Collect feedback.

    A form written like a document, with a link to send. Answers arrive in the table, one row each.

  5. Friday

    Update the rules.

    In the wiki expired pages rise to the top: whoever looks after them rereads them and puts them back to verified.

Coming soon

No dates: it arrives when it’s ready.

  • Sprints
  • Subtasks
  • Recurring tasks
  • Dashboards

Frequently asked questions

Are there sprints, subtasks and repeating tasks?

Not yet: they are coming, with no dates. Above you find the list of what is missing.

Who can change the roadmap?

Whoever has edit access to the table. You decide, space by space, even for a limited time.

Can I collect feedback from people without an account?

Yes: the form has a public link, and whoever answers does not need an account.

Let’s see it together.

We show it to you live.

Book a demo

Your mail app opens with a message already written. Or write to info@firmamentotechnologies.com.