A Focus Group panel report
Five voices on jibeworks.com.
The catalog hosting this page was placed in front of five AI personas. Each was given a mission, a budget, a level of patience. Each came back with notes. Below: the report, in full. The criticism is honest. That is the point.
- KR Karen
- DR Dev Raj
- MG Mia
- TM Tom
- ZA Zara
The catalog reads as craft; that comes through across all five voices. What does not come through is price, proof, and readiness. Three of five panelists exit without a clear next step they could take alone. The fix is surface-level — status pills, a price range, one customer line — not structural. The bones are good.
Verbatim, lightly edited.
- KR
- Patience
- low
- Literacy
- low
- Budget sens.
- high
I scrolled. The pictures are nice. I have no idea what any of this costs. I see ‘custom work — email me’ and I think, that means expensive, and I leave. I don't know what I'd be emailing about. I don't know which thing is for me.
- DR
- Patience
- high
- Literacy
- high
- Budget sens.
- medium
The MCP Contract page is a beautiful thesis defense. I read every line. I want to see two more reference implementations before I'd recommend it to a teammate. Synth Ops is the only one — and it's the author's own. I'd want a third party to vouch.
- MG
- Patience
- medium
- Literacy
- medium
- Budget sens.
- high
‘Free core, paid customization’ is fine — but the customization quote lives in an email. I can't tell my finance team ‘I want this’ without a number. Even a range would unblock me. The nudge to email is also the friction.
- TM
- Patience
- medium
- Literacy
- low
- Budget sens.
- low
Where are the case studies? I see craft. I do not see customers. I do not see ‘Acme Corp uses StratBrief weekly, results below.’ My VP would ask. I would have no answer. The catalog is one person's portfolio — that may be the point — but for me to bring it in, I need a logo wall.
- ZA
- Patience
- low
- Literacy
- high
- Budget sens.
- medium
Cool catalog. Show me the receipts. Three of these say ‘forthcoming.’ Two are public artifacts I could try right now. I want a clearer signal of which is which on the homepage so I don't click into a beautiful detail page just to find out it's not real yet.
Patterns across the panel.
- F-01
Pricing is opaque across every SKU. Two of five panelists explicitly mention it as friction.
- F-02
Social proof is absent. No customer logos, case studies, or third-party reference implementations beyond the author's own.
- F-03
Status (shipped vs. forthcoming) reads on the detail pages but blurs on the home/collection surfaces — three of five panelists noted the gap.
- F-04
Customization quoting requires an email even to scope, which is itself the friction the ‘in-context’ nudge is meant to remove.
Prioritized.
- high
Surface a customization price range on the home page, even if quoted firmly only by email.
- high
Add a small status pill (shipped / building / planned) to every SKU card on `/` and `/collection`.
- medium
Recruit one external reference implementation of MCP Contract beyond Synth Ops — even a small one.
- medium
Replace the catalog's About paragraph with one customer or one shipped engagement, when one exists.
- low
Consider an excerpt or screenshot from a real Focus Group report on a real product, on this very page, when one is shippable.
The same five voices — or a custom set tuned to your audience — can be aimed at any web product. The deliverable is a report in this shape, with screenshots and a friction map.
Request a panel