Projects

What a project represents

A project is the reporting boundary for one brand and its competitive market. It owns the prompts, tracked brands, markets, topics, tags, monitoring runs, answers, sources, audits, actions, and exports shown together in the product.

Create separate projects when brands, countries, languages, product categories, or reporting owners need independent baselines. Combining unrelated markets produces averages that are hard to act on.

On the Projects table, Brands is the number of brand records attached to the project and Queries is the number of query records attached to it. These are configuration totals, including records regardless of whether they produced a completed answer; they are not mentions, completed responses, or active-provider obligations. Status is the stored active, paused, or archived project state.

Complete onboarding

1. Describe the brand Enter the public brand name and website. PromptSpark.ai uses this context to enrich the profile and suggest competitors and prompts.
2. Review competitors Keep direct alternatives that a buyer could realistically compare. Remove suggestions that are publishers, partners, or unrelated names.
3. Confirm providers Choose the AI providers used by the account. Provider availability determines where project prompts can run.
4. Build the first prompt set Review generated suggestions, add questions manually, or upload a CSV before completing onboarding.

Maintain the project profile

• Profile holds the project name, primary brand context, website, and scheduling state.
• Brands contains the tracked brand record and its aliases; competitors sit under that brand.
• Markets define country, city, and language context that prompts can use.
• Topics and tags organize reporting without changing the wording of a prompt.

Decide when to split a project

Keep work in one project when the same decision-makers need one combined view and the prompts share a brand, competitive set, language, and market logic. Use filters, topics, and tags for meaningful segments that still belong to the same measurement system.

Create a separate project when combining the data would hide an important difference. Common reasons include a separate brand, a country with different competitors, a language requiring its own prompt wording, a product category with a distinct buying journey, or an agency client that needs separate access and reporting.

• Do not duplicate the same prompts across projects unless the market or ownership boundary genuinely differs.
• Name projects so a new team member can identify the brand and scope without opening settings.
• Document the date of major profile or prompt-set changes in the reporting notes shared with stakeholders.
• Archive obsolete work only after the team has exported any history it must retain.