sales-skills/sales-askable

Askable Platform Help

Askable (askable.com) is an all-in-one AI research platform — the research-ops / real-participant class, a panel-first peer of Great Question. It does the whole loop on real people:

• Recruit — from its own verified participant panel (triple-verified, fraud/voice-clip/LinkedIn checks, a high self-reported show rate) or bring your own (BYO) via a share link.
• Run any method — AI-moderated interviews (the Askable AI moderator runs multilingual interviews at scale), remote/live interviews, unmoderated prototype & usability tests, surveys, card sort / tree test, five-second, first-click, website & mobile testing, diary studies.
• Analyze — AI theme/pattern analysis, heatmaps/path flows, and Insight Streams (continuous weekly insights with video evidence), with findings linked back to quotes and clips.
• Project Delivery (its differentiator) — hand a whole study to Certified Askable Researchers who recruit, run, and deliver findings for you in ~48h. A done-for-you service layered on the self-serve tool.

Australia-founded; the panel is strongest in AU / NZ / UK / APAC. Compliance: SOC 2, ISO 27001, GDPR.

Two things to say almost every time:

• It's real people, but a study "I'd pay" is still not a purchase. Real interviews and panel research beat synthetic signal (genuine reasoning, objections, language) — but the willingness-to-pay go/no-go belongs to a real behavior test (pre-sale, smoke test), not a study transcript. Route that to /sales-idea-validation.
• It's UI-only — no public REST API, webhooks, or MCP surfaced. Native integrations are with UX research tools (Lookback, Optimal Workshop, Loop11, UserZoom) plus SSO; data-out is manual export. "Call the Askable API / fire a webhook on study completion" is the wrong mental model — for an API/webhook-native research pipeline, route to /sales-great-question (REST API + webhooks + MCP).

Step 1 — Gather context

If references/learnings.md exists, read it first for accumulated platform knowledge.

Ask only what you can't infer:

1. What do you want from Askable?
   • A) Recruit participants — from the Askable panel, or BYO (your own users via a share link)
   • B) Run a study/method — AI-moderated interview, unmoderated prototype/usability test, survey, card sort/tree test
   • C) Managed research — Project Delivery (Certified Askable Researchers run + deliver it for you)
   • D) Analyze / Insight Streams — themes, heatmaps, continuous weekly insights
   • E) Get data out / automate — export, or an integration (there is no public API/webhooks)
   • F) Pricing / plan gates — credits, the Pro vs Enterprise split, the recent pricing change
   • G) Choose — Askable vs Great Question / Respondent / User Interviews / Chikka
2. Is this discovery (strangers off the panel) or feedback from your own users (BYO)? That changes whether you pay for recruitment and how honest the signal is.
3. Where are your participants? Panel depth is strongest in AU/NZ/UK — niche or non-APAC B2B audiences are where reach/screener limits bite.

Skip-ahead: if the user wants to compare research tools across the market or the validate-before-building method, that's a /sales-idea-validation question — route in Step 2.

Step 2 — Route or answer directly

| If the user's question is about… | Route to | |---|---| | Comparing research/recruit/idea tools across the market, or the validate-before-building method | /sales-idea-validation {question} | | A REST API / webhook / MCP-native research pipeline (Askable has none — it's UI-only) | /sales-great-question {question} | | Running a real behavior demand test (smoke-test page, waitlist, pre-sale) after research | /sales-idea-validation or /sales-funnel {question} | | Analyzing existing NPS/CSAT/VoC/review feedback into themes (post-launch, not new studies) | /sales-customer-feedback {question} | | Card sort / tree test / IA as the core job across tools | /sales-uxtweak {question} | | A recruit-only marketplace (recruit + screen + pay, you run the session elsewhere) | /sales-respondent {question} |

When routing, give the exact command: "This is a {domain} question — run: /sales-idea-validation {original question}"

Otherwise, answer Askable-specific questions using Step 3.

Step 3 — Askable reference

Read references/platform-guide.md for the full reference — the module / automation-surface table (what's UI-only vs export vs native integration), best-effort credit-based pricing and the Pro vs Enterprise split, the panel + BYO recruiting workflow, the Study → Participant/Session → Insight data model, the AI-moderator and Project Delivery workflows, and the export/handoff recipes. Read references/askable-api-reference.md for the automation surface — it documents that there is no public API/webhooks/MCP and inventories the actual data-out and integration options.

Answer using only the relevant section — don't dump the full reference.

Step 4 — Actionable guidance

• Say the caveat: research is not a purchase. Whatever the user asks, make explicit that Askable studies real people (a big step up from synthetic personas — genuine reasoning, objections, language), but a stated "I'd pay" in a study is not observed demand. Keep the why/objections/ language and take the go/no-go from a real behavior test (pre-sale, smoke test) — route that to /sales-idea-validation.
• Treat automation as UI-only, and don't invent endpoints. When any automation/export/integration comes up, state that Askable has no public REST API, webhooks, or MCP server — the native integrations are with UX research tools (Lookback, Optimal Workshop, Loop11, UserZoom) plus SSO, and the only data-out is manual export. Don't design a REST/webhook pipeline or guess endpoints; if a programmatic pipeline is a hard requirement, route to /sales-great-question (REST API + webhooks + MCP).
• Present pricing as best-effort, credit-based, and quote-gated — and flag the recent change. Tell the user pricing is credit-based (incentives baked into credits) with a Pro self-serve tier and a custom Enterprise tier, both currently demo/quote-gated with no public list price, and that Askable recently moved off the old flexible credit model (a top complaint — reviewers say the new pricing limits flexibility and study volume). Point to askable.com/pricing to confirm, and note the 30-day new-user credit program as the low-friction way to try it.
• Push BYO when they already have users. If the user has a waitlist or existing customers, bring your own participants (share the study link to your own audience) avoids panel recruitment cost and is the cheaper, faster path — recommend it over paying to recruit from the panel.
• Name the panel/screener limits before recommending recruitment. Panel depth is strongest in AU/NZ/UK; for niche B2B or non-APAC audiences, warn that reach is thinner and screener logic is limited, so over-recruit, tighten screeners, and consider a B2B-strong recruit peer (/sales-respondent).
• Match the job to the mode. The AI moderator runs interviews at scale; Project Delivery is the done-for-you option (Certified Researchers deliver in ~48h) when the team lacks research time; Insight Streams is for continuous discovery, not a one-off study. Pick the mode to the need.

If you discover a gotcha or tip not in references/learnings.md, append it there with today's date.

Gotchas

Best-effort from research (2026-07) — pricing (credit model, Pro/Enterprise split, the recent pricing change), panel size/coverage numbers, the method list, the integration list, and compliance certs all move; verify at askable.com and askable.com/pricing.

• Real ≠ demand. Panel and interview research reveal the why better than any synthetic tool, but a stated intent to pay is not a purchase — the go/no-go still belongs to a real behavior test.
• No public API/webhooks/MCP — automation is manual export + UX-tool integrations. Don't design a webhook-on-completion pipeline or invent endpoints; a REST/webhook pipeline is a /sales-great-question job.
• Pricing is credit-based and quote-gated — and recently changed. Incentives are baked into credits; Pro/Enterprise are demo-first with no public list price; the move off the old flexible credit model is a live complaint (flexibility + study-volume limits). All best-effort — confirm at askable.com/pricing.
• Panel is APAC/AU/UK-weighted. Reach and demographic filtering are thinner for niche B2B or non-APAC audiences — over-recruit and consider /sales-respondent for B2B/hard-to-reach professionals.
• Screener logic is limited. Complex qualification for niche projects can be hard to express — design behavior-based screeners, use disqualifiers/quotas, and expect to over-recruit against no-shows.
• BYO is free and often the right call. If you already have users, bring your own participants via the share link instead of paying to recruit from the panel.
• Project Delivery is a managed service, not a feature toggle. Certified Researchers run the study for you (~48h) — great when you lack research time, but it's a different cost/engagement model than self-serve.

Related skills

• /sales-idea-validation — The tool-agnostic validate-before-building method + the full research/recruit/persona/validator tool landscape (use this to decide build-or-not; a study "yes" is not demand). Install: npx skills add sales-skills/sales --skill sales-idea-validation -a claude-code
• /sales-great-question — The API-native research-ops peer (recruit + run + repository) with a REST API + HMAC webhooks + MCP — the pick when you need a programmatic pipeline Askable's UI-only surface can't offer. Install: npx skills add sales-skills/sales --skill sales-great-question -a claude-code
• /sales-respondent — The recruit-only marketplace strong in B2B / hard-to-reach professional panels — reach for it when Askable's APAC-weighted panel is too thin. Install: npx skills add sales-skills/sales --skill sales-respondent -a claude-code
• /sales-chikka — The self-serve, voice-first AI-moderated-interview peer (BYO, marketing-asset pipeline); pick by panel need and format. Install: npx skills add sales-skills/sales --skill sales-chikka -a claude-code
• /sales-customer-feedback — Real-customer NPS/CSAT/VoC strategy across tools (use to analyze existing feedback; Askable proactively recruits and runs new studies). Install: npx skills add sales-skills/sales --skill sales-customer-feedback -a claude-code
• /sales-do — Not sure which skill to use? The router matches any sales objective to the right skill. Install: npx skills add sales-skills/sales --skill sales-do -a claude-code

Examples

Example 1: "The Askable study loved my idea — should I build it?"

User says: "I ran an Askable panel study and unmoderated test, and most people said they'd use and pay for it. Green light?" Skill does: Credits the signal as real (actual recruited people, genuine reasoning — far better than a synthetic tool), then draws the line: a stated "I'd pay" in a study is not a purchase. Tells the user to mine the transcripts, clips, and Insight Streams for objections, hesitation, and pricing language (the real value), then take the go/no-go from a real behavior test (pre-sale or a "buy" click) via /sales-idea-validation. Notes pricing/panel figures are best-effort. Result: The founder keeps the qualitative depth and runs a pre-sale before committing to build.

Example 2: "How do I pipe Askable results into my CRM/warehouse via the API?" (developer/automation)

User says: "I want a webhook to fire when a study finishes and push the transcript to BigQuery." Skill does: States plainly that Askable has no public REST API, webhooks, or MCP server — there is no endpoint or key to build against, and it does not invent one. Explains the native integrations are with UX research tools (Lookback, Optimal Workshop, Loop11, UserZoom) plus SSO, and the only data-out is manual export of transcripts/results. For a webhook-on-completion pipeline into a CRM or warehouse, routes to /sales-great-question (REST API + HMAC-signed webhooks + MCP). Result: The user stops hunting for an API that doesn't exist and either exports manually or moves the pipeline to an API-native research-ops tool.

Example 3: "Askable is quoting me a lot and I already have users — is there a cheaper way?"

User says: "The pricing feels high and inflexible now. I have a waitlist — do I have to pay to recruit?" Skill does: Explains pricing is credit-based and quote-gated (Pro/Enterprise, demo-first, no public list price) and that the recent move off the old flexible credit model is a common complaint — all best-effort, confirm at askable.com/pricing, and mention the 30-day new-user credit program. Then points out that bringing your own participants (BYO) — sharing the study link to the existing waitlist — avoids panel recruitment cost entirely and is faster. If they still need strangers at B2B scale, notes the panel is APAC-weighted and suggests /sales-respondent. Result: The user runs the study against their own list for free instead of over-paying to recruit.

Troubleshooting

"Where's the Askable REST API / webhook to sync studies?"

Symptom: You're looking for an API key and a webhook to fire on study completion. Cause: Askable is UI-only — no public REST API, webhooks, or MCP server surfaced. Its native integrations are with UX research tools (Lookback, Optimal Workshop, Loop11, UserZoom) plus SSO, and data-out is manual export. Solution: Export transcripts/results from the UI, or use the UX-tool integrations for your testing stack. If a programmatic pipeline into a CRM/warehouse is a hard requirement, use an API-native research-ops tool instead — route to /sales-great-question (REST API + HMAC-signed webhooks + MCP).

"The new pricing feels expensive and inflexible / I keep hitting study-volume limits"

Symptom: Costs went up and the old per-study flexibility is gone; you can't run as many studies. Cause: Askable moved off its older flexible credit model to a credit/track model with Pro and Enterprise tiers (best-effort — a top user complaint is lost flexibility and study-volume limits). Pricing is quote-gated with no public list price. Solution: Treat pricing as best-effort and confirm at askable.com/pricing; use the 30-day new-user credit program to trial it; and where you already have an audience, bring your own participants (BYO) to avoid recruitment credits. If flexibility and B2B reach matter more, compare against /sales-respondent (recruit-only, PAYG) and the API-native /sales-great-question.

"Recruitment is slow / participants don't fit / panel is too thin for my audience"

Symptom: Slow fills, off-brief participants, or you can't reach a niche/non-APAC B2B segment. Cause: The panel is strongest in AU/NZ/UK/APAC and screener logic is limited, so niche or non-APAC B2B recruiting is where reach and qualification bite — and "off-brief participants" is usually a screener-design problem, not a bad panel. Solution: Tighten screeners (behavior-based questions, hidden disqualifiers, quotas), over-recruit against no-shows, and for B2B / hard-to-reach professionals consider a B2B-strong recruit peer (/sales-respondent). Where you have your own users, BYO sidesteps panel reach entirely.