Commercial model
Start with a visible, honest next step.
The Visibility Sprint is a fixed-scope answer-engine review: real collection through paid provider APIs, real observation by hand where no API exists, and a named reviewer on every record. It is delivered inside the software as a verified evidence ledger, a prioritised backlog and one client-ready report. There is no subscription tier today. Everything on this page is either a limit the product enforces or a commitment we hold ourselves to, and each one says which it is.
Available now · one-time engagement
Visibility Sprint
Your client’s priority questions are asked on a schedule through the Perplexity Sonar API and the OpenAI Responses API with web search, and by hand in the consumer interfaces where no API exists. Every answer is stored with its cited sources, its model and its timestamp, and a person signs each record off. You get the ledger, a prioritised backlog, and one link you can hand your client.
Every record is human-verified
A named reviewer signs off each observation. Unverified records cannot reach your client’s report.
No number is presented as a measurement
There is no estimated score anywhere in the product. Every figure counts observations that actually happened. Read the method.
- Kickoff
- Within five business days of your purchase
- Delivery window
- 20 business days from kickoff
- Prompts observed and recorded
- At least 10, up to the 50 per audit the product enforces — the working set is agreed at kickoff
- Scheduled calls included
- Two: a kickoff call and a findings readout
- Work performed by
- AnswerLift — the same reviewer runs the observations and signs off every record before it can reach your client
- Provider API usage costs
- Included in the fee — collection runs on AnswerLift's own Perplexity and OpenAI API keys, and provider usage is never billed on to you
Kickoff, delivery, calls and the reviewer are engagement commitments. The 50-prompt ceiling and the provider-cost position follow from what the product does, not from a promise on this page. None of these is a commitment about rankings, citations, traffic or what an answer engine will say — nothing in this product can deliver one.
What the Sprint produces, counted
Each row below is enforced by the product itself, not by a promise on this page.
| Deliverable | How many | What it is |
|---|---|---|
| Brands and markets | 1 brand · 1 market | An audit records one brand, one domain and one target market. A second brand or a second market is a second engagement. |
| Collected automatically | 2 provider APIs | Perplexity Sonar API and OpenAI Responses API (web search). Both are official paid APIs. Each answer is stored verbatim with its cited sources, the model, and the timestamp. These are not the consumer ChatGPT or Perplexity products and are never labelled as if they were. |
| Recorded by hand | 3 consumer surfaces | ChatGPT, Google AI Overviews, Perplexity. A person asks the question in the interface and records what they saw. Nothing is scraped. |
| Collection cadence | From every 6h | Set per prompt, up to 50 tracked prompts per audit. A run that could not reach a provider is stored and shown as a failed run — never quietly dropped. |
| Priority questions in the brief | 3–5 | The intake will not accept fewer than three or more than five. These frame the work; they are not the full prompt set. |
| Evidence ledger | Unlimited records | Each record carries the prompt, its version, the engine, the source label and URL, the capture and observation times, the mention-versus-citation call, confidence, volatility and a written note. |
| Human QA sign-off | Every record | A named reviewer verifies each observation. Unverified records are excluded from the client report by the query itself, not by the page. |
| Remediation backlog | Written from findings | Every task is written by the person who decided it was worth doing, with owner, priority, due date and status. Nothing is seeded from a template. |
| AI-crawler log ingestion | Up to 5,000 rows | Import your own server or CDN log summary for GPTBot, PerplexityBot, ClaudeBot, Google-Extended and the rest. A crawler hit is a fetch, not a citation, and the product says so wherever it shows one. |
| Client-facing report | 1 shareable link | Read-only, excluded from search engines, carrying no AnswerLift analytics, and expiring 30 days after it is issued. It shows verified observations and nothing else — there is no score on it, because there is no score anywhere in the product. |
Done by a person
- Choosing the prompts worth asking, and the cadence for each.
- Asking questions in the consumer interfaces, where no API exists.
- Reading every collected answer and confirming or correcting its classification.
- Signing off every record — collected or hand-entered — before a client can see it.
- Writing the interpretation and the prioritised remediation work.
- Exporting and supplying the AI-crawler logs from the client's own servers.
Done by the software
- Asking tracked prompts on schedule through the two paid provider APIs.
- Storing each answer verbatim with its cited sources, provider, model and timestamp.
- Making a provisional cited / mentioned / absent call for a reviewer to check.
- Deriving volatility only from repeated observations of the same prompt.
- Enforcing the human-QA gate on what can reach a client report.
- Rendering, exporting and expiring the client report.
Important boundaries
- Does not guarantee rankings, citations, traffic, revenue, or answer-engine behavior.
- Does not scrape the consumer ChatGPT, Perplexity or Google interfaces, and does not cover Google AI Overviews.
- Does not treat a provider API answer as identical to what the consumer product would say — each record names its provider and model.
- Does not establish that any change you make caused any change in an answer.
- Does not produce an estimated or computed score of any kind. If nothing was observed, nothing is reported.
- Does not automatically publish content or make changes to a client site.
- Does not replace your agency's client approvals, editorial judgment, or publishing control.
Decision guide
Snapshot, Sprint, or platform rollout.
Choose the step that matches your current need. The comparison deliberately separates what can happen now from a future platform access conversation.
| Path | Free Snapshot | Visibility Sprint | Platform rollout |
|---|---|---|---|
| Availability | Available now | Available now | Sales-led rollout |
| Commercial model | Free diagnostic request | $3,500 one-time engagement | Discussed with sales |
| What you receive | A written fit assessment and a recommended path | A verified evidence ledger, a prioritised remediation backlog, and one shareable client report | Discussed with sales |
| Best for | Clarifying the visibility question | Getting defensible evidence in front of one client | Agencies evaluating platform access |
| Measurement | None | Provider-API collection plus human observation, every record reviewed | Discussed with sales |
Buyer responsibilities
Bring the client context.
To keep the Sprint focused, your team provides the client domain, three to five priority questions, the target market, and the agency owner who approves scope and client-facing wording.
After purchase
- 01
Kickoff: confirm the agency, client context, questions, and working scope.
- 02
Collection and QA: tracked prompts run on schedule through the provider APIs, gaps are filled by hand, and a named reviewer reads and signs off every record.
- 03
Handoff: you receive the verified evidence ledger, the prioritised remediation backlog, and one expiring client-report link you can hand to your client under your own branding.
Not sure where to start?