Agree on it before anyone writes code.

A product requirements document laid out as a board: goals, user stories, requirements, wireframes and tasks side by side, a line from every requirement to its work.

Futur3 Board is in private beta. Invited accounts get every Subscriber feature free during the beta. No limits on your free boards, saved anywhere.

A product requirements document as a board: goals, user stories, numbered requirements, wireframes and build tasks, linked.

Why engineers and pms put it on a board

Product requirements document: notes, links and wireframes gathered by the goals

Out of the chat threads

The customer calls, the edge case from standup, the design file, the half-written ticket. Pull them onto one board, and stop rebuilding the spec from memory every time someone asks what’s in scope.

The board zoomed out: goals, requirements, wireframes, tasks

Scope, design and tasks together

Goals, the requirements table, the wireframes and the build to-do, side by side. Zoom out and you spot the missing screen, for pausing a schedule, before QA does.

A requirement row with lines to its task and wireframe

No line out means a gap

Draw a line from REQ-03 to the task that builds it and the wireframe that shows it. A requirement with no line out is a gap. A task with no line in is scope creep.

The build to-do: must, should or could and the effort on each task

Cut scope with everything in view

Must, should and could, side by side with the effort on each task. When the date won’t move, you choose what waits for v2 in one meeting, and everyone sees why.

REQ-05 with the engineer’s sticky note and the decision beside it

Review it with design and eng

Invite the team to edit and everyone works on the spec at once, pointers named. An arrowed comment lands on the exact requirement row, with the decision beside it. Only the board’s owner needs Subscriber.

How it works

  1. Write the goals. Goals, non-goals and user stories in one list.
  2. Number the requirements. One table row each: ID, priority, acceptance criteria, status.
  3. Wire them to the work. A line from each requirement to its task and wireframe.

What goes on the board

Pick a block to see where it sits on Billowrey’s board.

GoalsRequirements and buildWireframesData modelBillowrey — Recurring Invoices, v1 SpecProduct: Tamsin Reyes · engineering: Ivo Marsh · design: Joon Park · ship target Feb 2, 2027Goals and storiesGoal: no more retyping th…Goal: paid on time, witho…Non-goal: billing by usageStory: a bookkeeper sets…Story: an owner pauses a…Customer call“I retype thesame 14 invoicesevery month.”Ostrelle BakeryStandupWhat if the cardis declined onthe 1st?BuildREQ-01 Picker · Must · 3dREQ-02 Send · Must · 2dREQ-03 Preview · Must · 2dREQ-04 Pause · Should · 3dREQ-05 Email · Could · 1dPreviewQuestionDoes a pausedmonth counttoward theyearlydiscount?Blocks REQ-04.SendSet up scheduleIvo · engWhat if thecard expiresmid-cycle?RequirementsIDCriteriaStatusPriorityREQ-01Bills mont…DoneMustREQ-02Sends 9 a.…DoneMustREQ-03Preview fi…BuildingMustREQ-04Pause, res…To doShouldREQ-05Expiry ema…ReviewCouldSaveDesign fileRecurring, v4DecisionEmail the client 7days before. Noretry on an expiredcard. Tamsin, Oct21Pause scheduleNo screen yet. Neededfor REQ-04.Data modeltype RecurringSchedule = {clientId: stringevery: “week” | “month”sendAt: “09:00”pausedUntil?: Date}SchedulesClient’s emailNewPayscreen

Questions

Does it replace our issue tracker?

No. The board is where you shape the feature and agree on it. The requirements table exports to CSV, so you can bring the rows into whatever tracker you use.

Can I show the prototype next to the requirements?

Add a Link block to it beside the stories it covers, with screenshots as images, so the board still reads well when nobody clicks through.

Can we run the kickoff from it?

Yes. Set camera views from problem to stories to requirements to plan, and present full screen, the user stories revealed one click at a time (Subscriber), so nobody reads ahead.

Is it really free?

Yes. No limits on your free boards, saved anywhere: make as many as you like, with as many pictures and blocks as you like. They save on your computer, in your browser, or in your own Google Drive or OneDrive. The $5 Subscriber plan adds share links to view, comment, present or edit together live.

Who keeps my boards?

You do. Every board is a file you own: on your computer, in your browser, or in your own Google Drive or OneDrive. If you stop subscribing, your boards stay right where they are.

Does it work offline?

Yes. Install it from your browser in one click and it opens and saves like any app, with no connection.

Build the right thing the first time.

More boards like this