Skip to main content

Feature requests

Know who wants it, before you build it.

Productmind turns your agentic interviews, feedback widget conversations and the customer meetings its AI notetaker records into feature requests automatically. Each ask joins the request with the same intent, with who asked and what they said. When the evidence meets your rules, promote it into a feature or a task, or hand it to a coding session.

Read the user guide

How requests fill up

The same ask joins the same request,
with who asked and what they said.

When Productmind summarizes a customer meeting, an agentic interview or a feedback widget conversation, it picks out what the customer asked for. Each ask joins the request you already have with the same intent, or starts a new one, linked back to the conversation, the customer and their account.

Meet Software Inc, a fictional company that sells invoicing software. Every name in these pictures is sample data.

  • Your team's voice too.

    Add a teammate's input with their role and position: supporting, neutral, opposing or conditional, with the condition written down.

  • Tell the PM agent.

    Name who asked, such as Jane Doe at Acme wants this, and it finds the contact and adds their interest, or files a new request with it attached.

  • From your coding assistant.

    Connected over MCP, Claude Code, Codex or GitHub Copilot can file a request for you, from where you already work.

  • Notes, bug reports and screenshots.

    Convert a note or a bug report that is really a request. Attach a screenshot, and Productmind drafts the description from it.

Demand

See who wants it,
not just how many.

Every interest is someone, or something, with a reason: a customer with their sentiment and what they said, a teammate with their role and position, or a market signal, a strategic directive, a support pattern or what a competitor does.

Read moreFeature requestsContacts and accounts

Sample data

What it becomes

Promote it.
Keeping sight on next steps.

A request is promoted once, into a feature or a task, and its row shows where it went. Merge the ones that ask for the same thing, and reject the ones you won't build.

  • A feature, described for you.

    When a request describes a capability of its own, promote it into a new feature or an existing one. Productmind drafts the new feature's description from the request for you to review, and several requests can go into one feature.

  • A task, or a coding session.

    Promote a piece of work into a task, or launch a coding session: the request becomes its task in the same step, and the session works in the repositories of the applications it is linked to. You check it, then draft its plan.

  • Duplicates merged.

    Merge requests that ask for the same thing. Every interest is copied to the one you keep, and Productmind rewrites its description to cover them all.

  • Followed to the release.

    Open a request's lineage to see the customers behind it, the feature or task it became, and the session and release that followed. On plans that include lineage.

Read moreLineage

Sample data

Just build it.

An idea or a backlog. Either way, you're not building alone.

Get started