Announcements

Introducing Feedock: from feedback to shipped, in one workspace

2 min read
Oleh Husiev

Founder at Feedock

Every small team building in public runs the same broken relay. Requests pile up in a feedback tool. The real work happens somewhere else: a task board, a repo, your own head. And when something finally ships, the people who asked are the last to hear about it, if they hear at all.

Feedock closes that gap. It's a lightweight product workspace for tiny teams where feedback becomes roadmap, roadmap becomes tasks, and shipped work becomes a changelog that notifies the people who asked, automatically.

The gap nobody owns

Featurebase and Canny are good at feedback, roadmap, and changelog, but they don't execute. Linear and Jira execute, but they aren't public feedback hubs. So you end up hand-carrying the work across the gap: pasting requests into tickets, remembering which customer wanted what, and announcing changes one by one.

That hand-off is where momentum leaks. Feedock's bet: the integration between feedback and execution is the product. Not a feedback board bolted to a task tracker, but the loop that runs between them.

What you get

Feedock is the loop, made real:

  • A feedback board where users submit, vote, and comment, with no account required.
  • A public roadmap in Now / Next / Later / Shipped that stays in sync as you work.
  • Tasks and milestones linked to the roadmap, with GitHub activity moving them forward.
  • A changelog that ships the update and tells everyone who asked for it.
  • An embeddable widget, a React SDK, and a hosted portal, so it lives wherever your users are.
The Feedock public roadmap with Now, Next, Later, and Shipped columns
The public roadmap in Now / Next / Later / Shipped, kept in sync as you work.
Know what to build, why it matters, what's in progress, and what changed, without another heavy PM tool to maintain.

Who it's for

Feedock is for solo founders, micro-SaaS builders, and 2-5 person teams shipping in public. If you run a dedicated PM org deep in Jira, it isn't for you. If you're one to five people turning scattered requests into shipped features without drowning in process, it is.

This is the first of many posts. We're building Feedock in public and writing up the decisions as we make them. If that's your kind of thing, start free and build with us.