Productboard

Promptfree, for everyone, and the only version there is

Copy the prompt for Claude CodeCopy the prompt for CodexCopy the prompt for Cursor

Copy

Build the product feedback tooling I actually need instead of Productboard — and know which half is the value.

**It is the link from a feature to the customers who asked for it.** A list of ideas is a spreadsheet. A list where each line carries the six accounts that raised it, and what they pay, is an argument. That link is the build.

STACK
- Node 20+ with Fastify, server-rendered HTML with a little vanilla JS
- SQLite through better-sqlite3, WAL mode, with FTS5
- Caddy in front

THE DATA MODEL
- notes: id, source, external_ref, body, author_name, company_id, received_at, processed_at — a raw piece of feedback, from anywhere
- companies: id, name, domain, plan, mrr_cents, traits_json — because a request from an account paying a lot is a different fact from one that is not
- features: id, title, description_md, status, area_id, effort, created_at, shipped_at
- links: id, note_id, feature_id, at, actor_id — the join that is the whole product
- scores: id, feature_id, framework, inputs_json, value, computed_at
- releases, and a public roadmap view over features by status
- Nothing is scored automatically. A person reads a note and links it, and that reading is the work

GETTING FEEDBACK IN
- A shared inbox address, a form, and adapters for the support tool and the chat where it actually arrives
- **A browser extension or a keyboard shortcut to capture a sentence in one action**, because feedback is heard in the middle of doing something else and anything slower is lost
- Every note keeps its source and a link back to the original conversation. A request with no context is a request nobody can act on
- Deduplicate on arrival by similarity, offering the existing note rather than creating a second

THE LINK, DONE PROPERLY
- One note can support several features and one feature many notes
- When a feature ships, **everybody who asked for it is a list you can email.** That single action — telling the twelve people who requested it that it exists — is worth more than the entire rest of the tool, and almost nobody does it
- The count of linked notes and the total revenue behind them, shown on every feature, computed at query time

PRIORITISATION, HONESTLY
- Implement one framework, not four. Reach times impact divided by effort, with each input recorded and the formula written on the page
- **Every input is a guess and the output is a guess with arithmetic on it.** Show the inputs beside the score, always, so the conversation is about the estimate rather than about the number
- Never sort the roadmap by score alone and call it a plan. The score orders a discussion; it does not replace one

THE PUBLIC ROADMAP
- Three columns and no dates: exploring, building, shipped. Dates on a public roadmap are promises, and they are the reason most public roadmaps are eventually taken down
- A subscriber can follow a feature and is told when it moves, which closes the loop the feedback opened
- Server-rendered, fast, with its own permanent URLs

WHAT MATTERS MOST
The note-to-feature link, and emailing everybody who asked when it ships. The first makes prioritisation defensible; the second is the only part customers ever see.