Welcome to PromptSpark.ai

What PromptSpark.ai does

PromptSpark.ai monitors the questions that matter to your market across supported AI platforms. It records the answer, finds brand mentions and cited sources, and turns that evidence into comparable visibility, sentiment, position, and source metrics.

The product is designed for evidence-led decisions. A score tells you where to look; the underlying answer, brand mention, and source record tells you why the score moved.

How to use these docs

• Start with Quickstart if you are creating your first project or waiting for your first results.
• Use the setup guides when you need to change prompts, brands, competitors, markets, topics, or tags.
• Use the results guides when you need to interpret a metric, verify an answer, or understand a source opportunity.
• Use the action guides when you are ready to turn evidence into website, content, or outreach work.

From prompt to decision

1. Ask A tracked prompt is sent to each enabled AI provider in the project.
2. Capture PromptSpark.ai stores the answer and the web sources used or cited by the provider.
3. Analyze The answer is checked for tracked and discovered brands, position, sentiment, recommendations, and source evidence.
4. Compare The Overview and detail pages aggregate completed answers across the selected project, period, provider, market, topic, and tag filters.
5. Act Source gaps, brand findings, audits, and generated actions help you decide what to improve next.

What makes the evidence useful

PromptSpark.ai is most useful when the monitoring setup stays stable long enough to create a comparable history. The same question can produce different wording from one run to another, so the product looks for patterns across completed answers rather than treating one response as the whole market.

{"Begin every analysis by confirming the scope" => "project, date range, providers, markets, topics, tags, and completed response count. Then move from the summary metric to the exact answers and sources that contributed to it. This keeps a small sample, provider outage, or changed prompt set from becoming an unsupported conclusion."}

• Use summary metrics to locate meaningful movement.
• Use answer evidence to understand the language and competitive context.
• Use source evidence to identify websites and pages your team can influence.
• Record the action you take so later runs can be read against a clear change date.