Harvestr is built around five building blocks. Once you see how they connect, the rest of the product makes sense: feedback comes in from your customers, you group it into discoveries organized by component, and the discoveries you commit to end up on your roadmap.
Feedback
Everything your customers and teammates tell you about the product: a support ticket, a sales call, a Slack thread, an interview note. Feedback arrives in your inbox from every connected tool, or is added by hand.
You process it there: HAI suggests where each piece belongs, you link it to discoveries, then mark it as processed. One piece of feedback can feed several discoveries: link the whole thing, or just the passage that matters.
Customers
The users and companies behind the feedback. Each piece of feedback has a requester, so you always know who asked for what.
Sync your CRM or import a file to add attributes such as plan, ARR or industry, and group customers into segments. That's what lets you weigh a discovery by who is asking, not just by how many.
Discoveries
A discovery is a product opportunity: a problem to solve or an idea to explore. Every piece of feedback you link to it adds evidence, and the customers behind that feedback come with it.
Discoveries carry a state (for example Backlog, In progress, Shipped), fields to score them, and links to engineering issues. A discovery can have sub-discoveries, for the solutions you consider.
Components
The areas of your product, such as Billing, Mobile or Integrations. Each discovery sits in one component, so your backlog is organized the way your product and your teams are.
Roadmap
What you've decided to build. Roadmap projects are high-level initiatives that group one or more discoveries, so you can share the plan internally, or publish it for your customers, without exposing your whole backlog.
Putting it together
A typical journey:
A customer mentions a problem in a support ticket. It lands in your inbox, linked to that customer.
HAI suggests the discovery it belongs to, in the right component. You accept.
Over weeks, more feedback piles up on that discovery. Its feedback count and the revenue of the customers behind it make it rise in your priorities.
You add it to a roadmap project, create the engineering issue from it, and move it to Shipped when it's done.
The teammate who sent the original ticket is notified, and can tell the customer.
Where to go next
Getting started with Harvestr: set up your workspace in five steps