How-to · Research ops · Stack inventory · Oct 2026
Stack map for research ops (Oct 2026): inventory AI seats across research, feedback, and surveys
How-to inventory — research and feedback jobs, tools, owners, and overlaps. Overlap is the point: most teams find three tools theming the same feedback, two summarizing the same sessions, and a chat assistant re-synthesizing interviews the repository already tagged. Pair with Stack map for product ops and Stack map for support ops.
What this how-to covers
Research and product teams add AI one surface at a time: the research repository gets chat and agents, the testing tool adds AI moderation and summaries, in-product surveys theme open text, feedback capture dedupes ideas, a feedback analytics tool builds a taxonomy, the in-app guidance tool adds an agent, and everyone already has a chat assistant. A year later, four tools theme the same NPS comments. This how-to builds one table — Job | Tool | Owner | Cost/mo | Overlap | Decision — for seven jobs where overlap is common: research repository, user testing, surveys, feedback capture, feedback analytics, in-app guides, and the chat assistant.
It is an inventory, not a ranking. Fill Cost/mo from your own invoices, write overlaps in plain sentences, and add who approves: study launches, survey sends, idea merges and status changes, roadmap changes, and anything that contacts participants or customers. AI suggests; a named person approves. No participant or customer PII goes into a general chat tool, and an AI-written quote is never presented as a participant’s words.
How to inventory research-ops AI seats
Examples at a glance: each feature has a concrete example from a real job plus a short Try this you can run this week.
1. Build the blank table (primary)
What it is: Start with seven rows and six columns. Leave cells blank until you have a source. The seven jobs: research repository (Dovetail or similar), user testing (Maze, UserTesting), surveys (Sprig or your in-app tool’s surveys), feedback capture (Canny or a feedback board), feedback analytics (Enterpret, or Dovetail Channels), in-app guides (Userpilot, Appcues, Pendo), and the chat assistant (Claude, ChatGPT, or Gemini seats used for guides, screeners, and synthesis — see Claude for research ops and ChatGPT for research ops).
Primary workflow:
Build Job | Tool | Owner | Cost/mo | Overlap | Decision blank for: research repo, user testing, surveys, feedback capture, feedback analytics, in-app guides, chat assistant.
2. Owners and Cost/mo from invoices
What it is: For each tool, write one owner — the person who can cancel it — and the monthly cost from the invoice or card statement. If you can’t find it, write "Unknown — check bill". Don’t fill costs from list prices: many tools in this stack publish no prices at all, some list only a free tier and a custom enterprise plan, and the ones that do publish prices price by tracked users, monthly active users, seats, studies, or credits. Our dated reviews note what each vendor published on 9 October 2026 — Dovetail, Maze, UserTesting, Sprig, Canny, Enterpret, Userpilot — but contract prices differ from list prices.
Costs from invoices only:
For each of the seven jobs, name the owner and Cost/mo from invoices only. If missing, write Unknown — check bill. Do not invent prices, user counts, or seat numbers.
3. Mark overlaps in plain language
What it is: For each row with two or more tools, write one sentence about what both do — for example, "Sprig and our feedback analytics tool both theme NPS comments." Common overlaps: the repository and feedback analytics both build themes from support tickets; the survey tool and the in-app guidance tool both send in-product surveys; the testing tool and the repository both summarize interview videos; and the chat assistant re-synthesizes notes that already sit, tagged, in the repository.
One sentence per overlap:
For each row with two or more tools, write one plain sentence about what both do on that job. No scores or labels. Flag any job with no paid AI as blank.
4. Add who approves studies, surveys, and idea changes
What it is: Add two short columns for tools that can act: Who approves (study launch, survey send, screener, idea merge or status change, roadmap change, close-the-loop message to customers) and Data rules (no participant or customer PII in general chat; consent limits on recordings; redaction settings in the repository; which API keys or MCP connections can write). If a tool can launch, send, merge, or message on its own, write whether that setting is on, its scope, and who approved it.
Name who approves:
For every tool that can launch a study, send a survey, merge or close feedback, or message customers, add Who approves and Data rules columns. Write whether any automatic action is on.
5. Write a Decision in one sentence
What it is: For each overlap row, write a Decision in one sentence: keep both (and why they do different jobs), consolidate onto one tool, or pause one for 30 days. Name who owns the follow-up and the date. Don’t use scores or labels. If a contract is annual, write the renewal date so the decision happens before it renews.
One sentence, one owner:
For the feedback analytics and chat assistant rows only, write a Decision in one sentence each (keep both, consolidate, or pause). Name who owns the follow-up date and note any renewal date.
6. Run a 30-day check
What it is: After 30 days, check each paused or consolidated tool: did anyone ask for it back, did any research or feedback job stop getting done, and did approvals still happen where they should? Update the table and keep it next to your research budget. For September vendor changes, see What’s new in Dovetail (Sep 2026) and What’s new in Userpilot (Sep 2026).
Check after 30 days:
Thirty days after a pause or consolidation, ask the owners three questions: did anyone ask for the tool back, did any research or feedback job stop getting done, and did approvals still happen. Update the table.
Pricing context (October 2026)
This how-to is dated 9 October 2026 and is not a price sheet. Research and feedback tools price per tracked user, monthly active user, seat, study, credit, or quote, and several publish no prices at all. Our dated reviews record what each vendor listed on 9 October 2026: Dovetail, Maze, UserTesting, Sprig, Canny, Enterpret, Userpilot, and Appcues. Fill Cost/mo from your invoices.
Optional structured help: $9 toolkit spreadsheet or $19 toolkit audit.
Uncertainty: Plan names, AI add-ons, credit models, panel fees, and bundled pricing change often, and several vendors in this stack quote every deal. Consent and redaction rules for research participants differ by organization and region. Always verify on the vendor's live page and your bill before budgeting. This is product education, not legal or privacy advice for your environment.
When it’s useful (honest take)
Useful when research, product, or CX pays for more than one AI surface and you suspect several tools theme the same feedback or summarize the same sessions.
Useful when you need to show who approves every AI-suggested study launch, survey send, idea merge, or customer message.
Less useful when you have one repository, one testing tool, and one chat habit with clear jobs. Soft $19/$9 only if overlaps are real.
Comparing several AI tools for the same job? The $9 AI toolkit spreadsheet puts each one you pay for on one page with cost, usage, and payback, so overlaps are easy to spot.
Want someone to do it for you? AI toolkit audit — $19
Related options (educational)
| Need | Better home | Why |
|---|---|---|
| Inventory seats by research-ops job | This stack map | Jobs · tools · owners · overlaps · decision |
| Product and support inventory | Product ops · Support ops | Same table pattern, different jobs |
| September vendor notes | Dovetail · Userpilot | Dated changes |
| Research hub vs feedback analytics | Dovetail vs Enterpret | Compare by main input |
| Testing tools side by side | Maze vs UserTesting | Study type and panel |
FAQ
What is a research-ops stack map?
One table that lists each research and feedback job (research repository, user testing, surveys, feedback capture, feedback analytics, in-app guides, chat assistant), the tool that does it, its owner, its monthly cost from your invoices, overlaps with other tools, and a one-sentence decision.
Which jobs should we inventory first?
Feedback analytics and the chat assistant, then surveys. They overlap most often because several tools theme the same open-text feedback and assistants re-synthesize notes the repository already tagged.
Should we use list prices for Cost/mo?
No. Use invoices or card statements. Many research and feedback tools are quote-only or bundle AI into a platform deal, and contract prices differ. Write Unknown — check bill when you can’t find it.
Why add who approves?
Because several tools can now launch AI-moderated studies, send surveys, merge or close feedback, or draft messages to customers. A named person should approve those actions, and participant data should stay out of general chat tools.
When do the $9 / $19 toolkit offers help?
Only when overlaps are real and you want a structured sheet ($9 spreadsheet) or a second pair of eyes on the table ($19 audit).
Optional next step (if seats overlap)
If research and product already pay for overlapping AI seats across the repository, testing, surveys, feedback tools, and chat, map that before you buy another assistant. Map the overlap with the $19 AI toolkit audit or the $9 AI toolkit spreadsheet. Email Audit $19 or Toolkit spreadsheet $9.
Checkout is live via Stripe. After you pay, we email delivery (spreadsheet) or intake next steps (audit).