Synthesis · sample
Will mid-market ops teams switch to per-seat pricing?
Executive summary
The proposed per-seat model is read as a penalty on exactly the teams you want to expand. Willingness-to-pay holds for the core workflow but collapses when pricing scales with headcount rather than value. A usage- or outcome-anchored tier survives the council; per-seat does not.
Key findings
Per-seat reads as an expansion tax
Personas managing growing teams flagged that cost rises fastest exactly when they add the people the tool is meant to help.
The core job clears the price
For the reschedule/handover workflow, the acceptable range sat comfortably above the proposed base — value is not the problem.
“AI-powered” triggers a security review
Procurement personas mapped the AI framing to risk; leading with local-first shortened the imagined review.
Sentiment across the council
01Anatomy
The synthesis is the answer.
The council is the log; the synthesis is what you act on. Every claim traces back to a quote, and you can see who disagreed and what moved them.
- Executive summary you can forward as-is
- Findings tied to evidence quotes
- Persona verdicts with stance and tags
- Sentiment and dissent across the council
02The receipts
The quotes behind the verdict.
“The new tier removes the one feature my team actually pays for. That’s a churn trigger, not an upsell.”
“Per-seat pricing punishes exactly the teams you want expanding. I’d cap it.”
““AI-powered” reads as risk to my security team. Lead with local-first or you lose us at review.”
The deliverable
One page you can defend in the room.
Every council resolves into a single synthesis: the question, an executive summary, findings tied to evidence, and the verdicts behind them.
Export to PDF · query it over MCP
03More study types
One engine, many questions.
What price makes them hesitate?
A van-Westendorp sweep finds the acceptable band and the two objections that cap it.
See the solutionDoes the new homepage land?
The council reports what it misread, the competing frame, and the one rewrite that fixes it.
See the solutionWhy did they really switch?
Push, pull, anxiety and habit — reconstructed from a remembered switch, with the timeline.
See the solution04Get your own
Two ways to a report like this.
Run it yourself
Install the MCP server on your own AI agent and produce this in minutes — free and local.
Install MCP — freeHave us deliver it
No time, no team? Send a brief and we’ll run the full study, QC it, and hand you the finished report plus a portal you can query.
Request a studyIllustrative sample — figures are representative, not from a real client engagement.