Project management · checked 2026-10-13

Can I vibecode Productboard?

KINDA· weekend project

For one product manager, the core of Productboard is small: gather notes, link the useful sentences to feature ideas, score the ideas and lay them out on a roadmap. An agent can build that, plus a public voting page, in a session or two. What stays a gap is what turns it into a team system: feedback flowing in from Intercom, Zendesk, Slack and Gong, a Jira hand-off in both directions, shared workspaces and the Spark AI layer. Productboard now sells to teams of five makers and up, so the DIY version mostly suits founders and solo PMs who were never its customer.

variesprice per seat

—you'd save a year

weekendbuild time

—people replaced it

Before you start

What you need on hand.

DifficultyIntermediate · Some system setup or keys.

TimeAn afternoon for the core; the public portal adds an evening

Claude Code, Codex or CursorAny of them can run the prompt.
Node.js 22better-sqlite3 compiles a native module, so build tools must be installed.
Your Productboard notes and features exportsTwo CSV files, requested from export URLs while signed in; the links arrive by email.
An SMTP accountOnly for confirming votes on the public portal.

Before you buildThere is no free Productboard plan to fall back to. If all you need is a public board where users vote, self-hosting Fider is quicker than building.

1. Install one agent: Claude Code, Codex, Cursor.
2. Make an empty folder and open it in the agent.
3. Paste the prompt below, press enter, and answer its questions as it builds.

The prompt

Build me a feedback-to-roadmap tool to replace Productboard. Requirements:

- Node.js 22 + TypeScript: a Fastify API and a React front end built with Vite,
  served on http://localhost:4610. Data in better-sqlite3 at ./data/product.db,
  copied to ./data/backups/ once a day.
- Notes inbox: paste text, POST to /api/notes, or upload a CSV (including
  Productboard's notes export) with a column-mapping preview. Each note has
  source, customer, company, tags and processed/unprocessed state; FTS5 search.
- Select a passage in a note and link it to a feature as nice-to-have,
  important or critical. Each feature lists every passage linked to it.
- Hierarchy: product > component > feature > subfeature, drag to reorder, with
  statuses I can rename. Import Productboard's features CSV export.
- Scoring: RICE fields plus one custom formula that can use any number field and
  the weighted count of linked feedback. Sort and filter by score.
- Roadmap: Now / Next / Later columns and a quarter timeline by release, each
  exportable as PNG and CSV.
- Public portal: only when PORTAL_PORT is set in .env, serve /portal on that
  port alone, with chosen features, one vote per email (confirmed by a link
  sent over SMTP) and an optional comment that arrives as a new note.
- If ANTHROPIC_API_KEY is in .env, add a "Summarize feedback" button per
  feature; everything else works without it. Single user, no accounts, no
  telemetry, local-first.
- Out of scope: Jira, Slack, Intercom and Zendesk integrations; multi-user
  editing.
- README: setup, backups, and the Productboard export URLs for notes and features.

Opens your agent with the prompt filled in, you press enter. Or copy it and paste it into an empty folder.

Share on X

Max MiskowSponsoredAI agents, automations and MVPs, built for your company.Visit site ›

Then keep going

Next prompts, same folder.

The first prompt builds the core. Run these one at a time in the same folder to grow it into your own Productboard.

Add an email intake to the feedback tool in this folder. Requirements:

- Watch one IMAP folder (credentials in .env) with `imapflow` every 5 minutes.
- Each new message becomes a note: sender as customer, sender domain as company,
  subject as title, body as text, attachments saved to ./data/files/.
- Mark processed messages with an IMAP flag; never delete mail.
- Skip mailing lists and auto-replies (List-Id, Auto-Submitted headers).
- Update the README with how to set up a forwarding rule into that folder.

Add GitHub Issues sync to the feedback tool in this folder. Requirements:

- GITHUB_TOKEN and the repo name come from .env.
- "Send to GitHub" on a feature creates an issue with its description and links
  to the top five feedback passages; store the issue number on the feature.
- Every 10 minutes, pull issue state: closed issues move the feature to a
  status I map in settings.
- Never edit issues other than the ones this tool created.
- Update the README with the token scopes needed.

Add feedback themes to the tool in this folder. Requirements:

- Embed every note with nomic-embed-text through Ollama and keep the vectors
  in the existing SQLite database; re-embed a note when it changes.
- Cluster the vectors with agglomerative clustering (cosine, threshold set in
  settings) and show each theme with its note count and three examples.
- If ANTHROPIC_API_KEY is set, name each theme in five words or fewer.
- One click links all notes in a theme to a chosen feature.
- Update the README with the Ollama install and model pull steps.

Add release emails to the feedback tool in this folder. Requirements:

- When a feature moves to the status I mark as "released", queue one email to
  every confirmed portal voter and every note author with an email address.
- Let me edit the message before it goes; send over the SMTP settings in .env,
  at most 30 per minute.
- Each email has an unsubscribe link, and nobody gets the same feature twice.
- Log sends in SQLite and show them on the feature page.
- Update the README.

What you lose

Feedback piped in automatically from Intercom, Zendesk, Slack, Gong and email
Two-way links between features and Jira or Azure DevOps
A shared workspace where PMs, support and sales all add insights
Spark AI summaries, themes and generated specs
Polished roadmap views that stakeholders browse on their own

Why people still pay

Product teams pay to keep every customer request in one searchable place tied to the roadmap, so prioritization starts from evidence rather than the loudest voice in the room. The connectors that feed it from support and sales tools, the Jira hand-off and roadmaps that executives can open themselves are the parts a home-made tool would have to keep alive.

Moatintegrations collaboration switching costs

Leaving Productboard

Take your data, then cancel.

1 · Take your data out of Productboard

1Feedback: while signed in, open https://<workspace>.productboard.com/api/notes/export; a link to the CSV arrives by email. Add ?export_type=with_features to keep the links between notes and features.
2Features, components and subfeatures: open https://<workspace>.productboard.com/api/features/export (makers and admins only).
3Roadmaps download only as PNG images from the board's export option; companies and users export from a grid board.
4Notes that came from Slack, Zendesk or Intercom export without their text, and there is no full-workspace backup; the public API is the fallback for anything else.

2 · Cancel Productboard

1Monthly plans: tell Productboard before the next renewal date, through in-app chat or support@productboard.com.
2Yearly and multi-year plans: give notice of non-renewal at least 30 days before the term ends, or it renews.
3Contract customers follow their subscription agreement or write to billing@productboard.com.

The billing article routes cancellation through Productboard's team, so keep the written confirmation.
Data stays for up to 60 days after the subscription ends and is then deleted for good; exporting it is your job.
Run the notes export with features before the end date: it is the only file that keeps feedback tied to features.
Removing makers or downgrading mid-cycle does not refund the rest of the period.

Checked 2026-10-13 against Productboard's docs: 1, 2, 3, 4, 5

The escape hatch

Don't feel like building it? These are already free.

FiderOpen sourcePublic portal where customers post and vote on ideas, with statuses and email updates.★ 4.6k · active Oct 2026 · docker to self-host
WebVisit ↗QuackbackOpen sourceFeedback boards, public roadmap and changelog, plus a support inbox, in one self-hosted app; a young project.★ 314 · active Oct 2026 · docker to self-host
WebVisit ↗ClearFlaskOpen sourceFeedback portal with voting, a roadmap and announcements, under Apache 2.0.★ 450 · active Oct 2026 · docker to self-host
WebVisit ↗

All 5 free alternatives to Productboard ›

The numbers

Productboard pricing

Plan	Monthly	Annual, per month	What you get
Business	custom	—	5-maker minimum, 25 contributors, 2 product portals, up to 5 Jira or Azure DevOps connections, 500 AI credits per maker a month.
Enterprise	custom	—	5-maker minimum, unlimited contributors, SAML SSO and SCIM, custom roles, Salesforce integration, 1,500 AI credits plus 800 per extra maker a month.

Free tier: No free plan on the current pricing page.
Billing: Priced per maker (contributors are free), monthly or yearly; yearly plans renew unless you give notice at least 30 days before the end.
Hidden costs: Prices are no longer published; earlier price lists showed $59 per maker a month on the yearly Pro plan, but the page now routes Business through a demo. AI credits beyond the allowance cost $5 per 50 (monthly plans) or $60 a year per 600 (yearly). Removing makers mid-cycle refunds nothing.
Source: www.productboard.com

Also on the list

Linear$10/mo · Project managementKINDA

Trello$6/mo · Project managementYES

Notion$12/mo · Notes & knowledgeKINDA

Questions

Productboard, briefly

Not answered here? Tell us and we'll add it.

Ask a question ›

Kinda. The core is a weekend build with the prompt on this page, but real gaps remain: Feedback piped in automatically from Intercom, Zendesk, Slack, Gong and email, Two-way links between features and Jira or Azure DevOps.

Productboard's pricing is usage-based or varies by plan.

Feedback piped in automatically from Intercom, Zendesk, Slack, Gong and email; Two-way links between features and Jira or Azure DevOps; A shared workspace where PMs, support and sales all add insights; Spark AI summaries, themes and generated specs; Polished roadmap views that stakeholders browse on their own. If any of those matter to you, keep paying.