Skip to content
Waitlist

Project Brain: the global knowledge store for your project.

Keyword research delivers topics. A competitor analysis shows the search market. Earlier decisions change what makes sense next. The Project Brain holds this information together as one context.

One context per project 142 notes · 318 connections
Visibility in AI answers ok
The brand is mentioned in 9 of 24 prompts. Measured 11 Sep 2026.
Content gap “GEO strategy” new
No dedicated page type exists for 312 assigned keywords.
Target audience Enterprise conflict
Profile confirms “no Enterprise”. New conclusion contradicts it – the confirmed value takes precedence.
Every note has Ask AI

When every analysis only knows itself.

Individual tools can deliver good results and still not add up to a shared picture. Keyword research doesn't know about the competitor analysis, content creation knows nothing about AI visibility – and the user carries the connections across by copy and paste.

The Project Brain keeps the connections inside the project itself. The results of each area stay distinguishable but become available in the shared context.

Separate tools
Keywords
Competition
AI visibility
Content
Four results, four contexts. The user carries the connections.
One project context
Keywords→ Topic
Competition→ Topic
AI visibility→ Topic
The same subject connects the areas – traceable and distinguishable.

One context with source and version.

The Brain keeps confirmed facts separate from AI conclusions. Every piece of information comes with its source, the time it was observed and a confidence level.

Confirmed values from the profile always take precedence. If two pieces of information contradict each other, BrandZaps does not resolve the conflict silently – the contradiction becomes visible as a conflict.

INFORMATION SOURCE OBSERVED CONFIDENCE STATUS
Target audience: agencies, 5–30 staff Profile, confirmed 04.09.2026 high ok
Market: DACH Website snapshot 08.09.2026 medium new
Target audience: enterprise IT AI conclusion 11.09.2026 low conflict
A plausible new statement does not replace a confirmed decision

This is essential for a system that works with company knowledge. The confirmed value stays valid until someone changes it – the contradiction remains visible alongside it.

Changes become new history
Version 3 · currentMarket DACH, language de
Version 2Market DE
Version 1First draft from snapshot

This way you can trace which state a finding was based on and what has changed since.

Findings instead of loose summaries.

Each area of the project publishes a limited number of findings. These sentences come from queries over the measured data – not from text that was read. The numbers follow the same calculations as the area views, so the Brain never creates a second version of the truth.

01Titlewhat it is about
02Specific statementone sentence, not a paragraph
03Reference setwhat it was calculated on
04Measurement datewhen it was measured
05Statusok · new · conflict
Finding · AI visibility ok
Competitor dominates topic “GEO audit”

The same provider is cited in 14 of 24 prompts on the topic, your own domain in 3 of 24.

Reference set24 prompts · 1 topic
Measurement date11.09.2026
Calculationsame as area view
Ask AI

Connections with a traceable reason.

The findings sit as note cards on a canvas. Two cards are connected when they name the same thing – the same topic, the same page or the same competitor. When you zoom out, the cards become simpler but stay readable.

Content gap Page /services/geo lacks depth Topic “GEO audit”
Shared entity Topic “GEO audit” Reason for the connection: the same confirmed topic
AI visibility Competitor cited in 14 of 24 prompts Topic “GEO audit”
Bridges between the areas

A page flagged in the content gap analysis can be connected to the topic in which a competitor is cited in AI answers.

From finding to the next question

Every note has “Ask AI”. One click opens Project Chat with that question – you don't have to copy the finding and describe it again.

View Project Chat →

What comes together in the Project Brain.

These areas don't sit side by side as separate lists. They are connected through their shared entities, topics and findings.

01Company and brand
02Offers and services
03Website
04Target groups
05Keywords and topics
06Competitors
07Performance data
08AI visibility
09Historical analyses
10Actions and decisions

One Brain per project.

The Project Brain does not collect third-party body text in its context: no competitor pages verbatim, no AI answer texts, no full page texts. This limit protects against injected instructions.

The project boundary is also anchored in the database. A Brain only sees its own project – important when one account manages several websites.

No third-party body text

The context stays focused on structured, project-specific information.

Project boundary in the database

A Brain only sees its own project – even with several websites in the account.

Separate projects, separate truths

Projects stay separate, even when they are managed under the same account.

The next step doesn't start from zero, but from everything the project knows.

Facts with a source Confirmed values, observation time and confidence on every piece of information.
Measurements with calculation Findings adopt the measurement logic of their area.
Observation with a question Every note leads straight into a conversation with Gauss.