Feature Request Router · SaaS & Startups
See which roadmap items carry real customer demand and ARR
Every customer request posted in Slack #feedback is matched to your Notion roadmap with the customer's plan and ARR from HubSpot, and the thread gets the link.
Free account to start. Buying and running live need a paid plan.
- Starts from an event in a connected app
- 2 AI steps
- About 20 min to set up
Sound familiar?
The job, before and after this agent.
What it feels like today
- “Feature requests disappear into Slack and the PM never sees half of them.”
- “We can't tell which requests come from big accounts and which from free users.”
- “Sales keeps asking whether anyone logged their customer's ask.”
What you get with the agent
- The request, the problem behind it, the customer and urgency pulled from each #feedback message.
- The customer's plan and ARR looked up on their HubSpot company.
- Matched against up to 100 items on your Notion roadmap.
- The customer, their words, plan and ARR added to the matching item, or a new Triage item created for the PM.
- A reply in the Slack thread with the roadmap link. It never promises dates, and bug reports are skipped.
Before
An account manager posts a renewal-risk customer's request in Slack. It gets two emoji reactions and is never seen again.
After
Seconds later, the request is added to the existing export roadmap item with the customer's plan and ARR, and the thread shows the link so the account manager knows it's logged.
How it works
The whole workflow, step by step.
When a teammate posts a customer request in your Slack #feedback channel, AI pulls out the request, the problem behind it, the customer and urgency, treating the customer's words as untrusted text. The agent looks the company up in HubSpot for plan and ARR and reads up to 100 items of your Notion roadmap. If an item already covers the same need, it adds the customer, their words, plan and ARR to it. Otherwise it creates a new item with Status Triage for the PM. It replies in the Slack thread with the link. It never promises dates or that something will be built, doesn't reply to customers and skips bug reports.
- TriggerNew message in #feedback
- AI stepPull out the request
- LogicA feature request?
- Not a request:Not a feature request
- No customer:Read your roadmap
- Customer named:Find the company in HubSpot
- OutputNot a feature request
- App callFind the company in HubSpot
- App callRead your roadmap
- AI stepMatch it to the roadmap
- LogicExisting item or new?
- Existing item:Add the customer to the item
- New:Create a Triage item
- App callAdd the customer to the item
- App callReply in the thread
- OutputAdded to the roadmap item
- App callCreate a Triage item
- App callReply in the thread
- OutputNew item for triage
This is the workflow that opens in your workspace when you set the agent up. Every step can be edited.
- Step 1New message in #feedbackStarts within seconds of a top-level message in your feedback channel (where sales, success and support post what customers ask for). The app's own messages never start it.
- Step 2Pull out the requestAI pulls out the request, the problem behind it, the customer (company, domain or email), how urgent it is and the customer's own words.
- Step 3A feature request?Chatter and bug reports are left alone; requests without a named customer skip the HubSpot lookup.
- Step 4Not a feature requestThe run history keeps the message and why it was skipped.
- Step 5Find the company in HubSpotLooks up the customer's company in HubSpot by domain (or name) for its plan and ARR.
- Step 6Read your roadmapReads up to 100 items from your Notion roadmap database.
- Step 7Match it to the roadmapAI compares the request with your roadmap items' titles and summaries: it adds to an existing item when it's the same need, or proposes a new one for triage.
- Step 8Existing item or new?Matches add the customer to that roadmap item; new needs get a Triage page for the PM.
- Step 9Add the customer to the itemAppends the customer, plan, ARR, urgency and their words to the matching roadmap item.
- Step 10Reply in the threadReplies under the #feedback message with the roadmap item's link.
- Step 11Added to the roadmap itemThe run history keeps the match and the reply.
- Step 12Create a Triage itemAdds a new item to your roadmap database with Status Triage, the need, the customer and their words.
- Step 13Reply in the threadReplies under the #feedback message with the new Triage item's link.
- Step 14New item for triageThe PM triages it in Notion.
Example run
What goes in, and what comes out.
Example with fictional data
Comes in
Slack #feedback: Acme Studio wants a direct export to their accounting software, saying it would save their bookkeeper a day a month; renewal next month.
The agent produces
Matched to the roadmap item Accounting exports. Added: Acme Studio, their words, plan Growth and ARR from HubSpot, urgency high (renewal). Thread reply with the Notion link.
What you need
Everything it takes to run it.
About 20 minutes from purchase to live. A checklist above the canvas takes you through each step.
Plan
Included in Enterprise; on other paid plans it's $99 once. Agents run live on paid plans, from Basic ($39/mo).
Your AI key
Connect any of 14 AI providers on your own key. Your provider bills usage directly, at cost; we add no markup.
Checklist
- A paid plan (agents run live on paid plans).
- An AI provider key (Settings → AI Providers).
- Slack, HubSpot and Notion, connected in Settings → Integrations, and a Notion roadmap database.
Setup, about 20 minutes
- Connect your AI provider. The AI steps run on your own key (OpenAI, Anthropic, Google and more). Add one in Settings → AI Providers.
- Connect Slack. Connect the Slack workspace with your feedback channel (Settings → Integrations → Slack).
- Connect HubSpot. Connect your HubSpot account (Settings → Integrations → HubSpot).
- Connect Notion. Connect Notion and share your roadmap database with the Fluxo Flow integration (Settings → Integrations → Notion).
- Pick the feedback channel. Open the trigger and pick your Slack account and #feedback channel.
- Describe your product and roadmap. Open “Pull out the request” and “Match it to the roadmap” and replace the placeholder in each with the same rules.
- Pick HubSpot and the properties. Open “Find the company in HubSpot”, pick your account and list the company properties to read.
- Pick the roadmap database. Open “Read your roadmap”, “Add the customer to the item” and “Create a Triage item” and pick your Notion account and roadmap database.
- Pick Slack for the thread replies. Open both “Reply in the thread” steps and pick your Slack account.
- Test it with Dry Run. Press Dry Run: the agent runs on sample data with no messages sent and nothing written to your apps.
- Switch the trigger on. Open the trigger and press “Activate app trigger”: from then on each new #feedback message is routed.
Is it a fit?
Who it's for, and what it won't do.
Built for
- SaaS product managers
- Customer success and account management teams
- Startup founders prioritizing the roadmap
What it doesn't do
- It never promises dates, priority or that something will be built.
- It matches against the titles and properties of up to 100 roadmap items; the PM triages new items and merges duplicates.
- It doesn't reply to customers, only to your teammate in the thread. Bug reports are skipped.
We list the limits up front so you can decide before you buy.
Price
$99 one-time
Per workspace. It never renews.
- Included at no extra cost on Enterprise.
- Buying and running it live need a paid plan, from Basic ($39/mo).
- Dry Run costs nothing: simulated AI and app calls, nothing sent.
- AI usage is billed by your own provider, at cost. No AI credits to buy from us.
One-time agent purchases aren't covered by the 30-day money-back guarantee. Refund policy
FAQ
Questions about Feature Request Router.
What if it matches the wrong roadmap item?
It only matches the same underlying need; anything else becomes a Triage item, so nothing is lost. The PM triages new items and merges duplicates.
Will it tell customers something's coming?
No. It never promises dates, priority or that something will be built, and it only replies to your teammate in the thread, never to customers.
What do I need?
Slack, HubSpot and Notion with a roadmap database. Setup takes about 20 minutes.
Is it worth the price?
A one-time price that never renews, against a PM manually logging and sizing every request. Live runs need a paid plan and your own AI provider key.
How does it match?
It compares the request with the titles and properties of up to 100 roadmap items and only matches the same underlying need. Everything else becomes a Triage item, so nothing is lost; the PM merges duplicates.
Where do plan and ARR come from?
From your HubSpot company record, found by the customer's domain or name. List the property names (e.g. ["name", "domain", "plan_tier", "arr"]) in “Find the company in HubSpot”.
Will it tell customers when something ships?
No. It never promises dates or that something will be built; it only logs demand and replies to your teammate in the thread.
Is this a subscription?
No. Feature Request Router is a one-time purchase of $99 per workspace and never renews. The Enterprise plan includes it at no extra cost. Running it live needs a paid plan (from Basic ($39/mo)), and your AI provider bills you directly for usage.
Can I test it before it touches real data?
Yes. Once it's set up in your workspace, Dry Run plays every step on sample data with simulated AI and app calls: nothing is sent and nothing in your apps changes. Switch the trigger on only when you're happy.
Put Feature Request Router to work.
Free account, no credit card. Your Agents page opens with Feature Request Router ready to buy and set up, then Dry Run it before it goes live.