Skip to main content
Pitch Audits are a pre-sales workflow for agencies. They help you qualify prospects, prepare sales conversations, and show AI visibility opportunities before creating a full client workspace. Enter a prospect domain, choose the market, language, prompts, and AI engines, then launch the audit and share the report. Use Pitch Audits when you need to:
  • show a prospect how AI assistants answer buyer questions in their category
  • compare the prospect against competitors detected in those answers
  • surface cited sources, content gaps, and available-to-buy opportunities
  • share a sales-ready report before a full client onboarding
To create an audit, you must be an Owner or Manager of an active agency team. Your balance must cover the estimated cost when you create the audit, even if you choose to review the prompts before launching.

Create a pitch audit

1

Open Pitch audits

In Qwairy, open Pitch audits in the sidebar and select Create pitch audit.
2

Enter the prospect website, country, and language

Add the prospect website, then choose the country among the 24 supported countries and the language among the 46 language variants. The country controls which AI engines are available and the local results.
3

Choose the prompt source

Select Generate with AI and choose the number of prompts, from 20 to 100 in steps of 5 (30 by default), or select Use my prompts and paste 20 to 100 prompts, one per line. Duplicate prompts are ignored.
4

Select the AI engines

The default engines are ChatGPT, Gemini, and Copilot. Depending on country availability, you can also select AI Overview, Claude (Beta), AI Mode, Perplexity, and Grok. Select at least one engine.
5

Choose when answers run

With Automatically launch AI responses enabled, answers are generated right after the prompts are ready. When it is off, the prospect profile and prompts are prepared, then generation waits for your review before it spends credits.
6

Review prompts and launch

Review, edit, add, or remove prompts if needed, then launch answer generation.

Credits

Credits are charged only for generated answers. Prompt preparation and prompt review do not spend response credits. The creation dialog shows the estimated credits, your available balance, and an estimated response time. Each selected AI engine costs 1 credit per prompt:
For an audit of 30 prompts on the three default engines, you need the following balance to start preparing the prompts. Qwairy checks the balance again when you launch answer generation.

What the report includes

Pitch Audit reports are built for pre-sales conversations. A completed report includes:
  • an AI visibility score for the audited brand
  • the underlying prompts and answer evidence
  • cited source domains and source URLs
  • available-to-buy opportunities when sources can be targeted
  • Social, Shopping, Local, and Ads/Sponsored insights when detected
  • multi-competitor reports when competitors are found
  • public sharing options for client-facing delivery
Pitch Audit reports are snapshots. AI assistants can answer differently over time, so create a new audit when you want a fresh market read.

Share the report

Open the completed report and copy its public link to share it with a prospect or client. Public reports include the same sections as the dashboard report, including the detected insight sections when available. The report interface is displayed in the audit language when it is English, French, Spanish, German, or Portuguese, and in English otherwise. If your team uses white-label features, shared reports follow your agency branding settings.

Automate pitch audits through REST API

Agency teams on Business, Agency Business, or Enterprise can automate the core Pitch Audit lifecycle with an existing API key:
  • POST /api/v1/pitch-audits creates and queues the audit;
  • PATCH /api/v1/pitch-audits/{auditId}/prompts saves the reviewed prompt set;
  • POST /api/v1/pitch-audits/{auditId}/confirm starts answer collection;
  • the list and report endpoints follow progress and return the completed evidence.
Creation and confirmation require an Idempotency-Key. Saving prompts requires the If-Match value returned as the report ETag. Retry and server-generated export actions remain in the dashboard. See Create a Pitch Audit.

Read pitch audits through REST API and MCP

Reads list audits and return complete reports. The MCP read tools never change an audit. For an agency team on an active Business, Agency Business or Enterprise plan, separate MCP write tools can create, review and confirm an audit once you grant the write:pitch-audits scope; see Pitch Audit write tools. Retrying an audit stays in the dashboard.
  • REST API: GET /api/v1/pitch-audits and GET /api/v1/pitch-audits/{auditId}
  • MCP: list_pitch_audits and get_pitch_audit
Each detailed report returns availableSubjects and coCompetitors. To open a co-competitor’s derived report, reuse its subjectId with the same audit:
With REST API, use the nested report resource: /api/v1/pitch-audits/{auditId}/reports/{subjectId}. Add includeCoCompetitorScores=true to retrieve every co-competitor and its score summary in one request. Report summaries omit full answer text by default; pass includeAnswers=true only when evidence-level access is required. See Pitch Audit API and Pitch Audit MCP tools.