- Cookie3
- Posts
- you're flying blind babe
you're flying blind babe
5 Prompts to Run a Full Competitor Benchmark with Cookie AI

Hi there,
Not here to judge, most crypto projects are out here tracking their own numbers, seeing the line go up, and calling it a win.
Follower growth. Impressions. Engagement rate. Cool. Up compared to what, though? Growing compared to who?
Because in a market where attention is finite, and Mindshare is genuinely zero-sum, knowing your own metrics isn't the same as knowing where you actually stand. That's not a strategy. That's a vibe.
Benchmarking is what separates the teams operating with a map from the ones just... vibing into the void. And it's exactly what Cookie AI is built around. Every metric it surfaces is designed to be read against the field, not in isolation, not in a vacuum, not just to make you feel good about yourself.
Here's what a full benchmarking workflow actually looks like in practice.
The first thing you want to understand is how much of the total conversation in your category is yours. This is called - mindshare - it’s not follower count, not raw impressions, but your actual percentage of the attention being generated across your entire competitive set.
Getting this picture manually means tracking different projects across dozens of metrics and doing the math yourself. Cookie AI pulls this data across your entire competitive set and compresses that into a single prompt:
"Give me a ranked breakdown of Mindshare across [Project] and its top 5 competitors for the last 30 days. Include signal, impressions, and post volume for each. Highlight where we rank and how far we are from the project directly above us."

For a project like the one in our example, the answer is 9.9%. Without the competitive context, 8.8% is just a number. With it, you know exactly where you rank, how far you are from third place, and how dominant the category leader actually is.
This is the foundational insight that everything else builds on. You cannot set a realistic growth target, allocate budget intelligently, or evaluate whether a campaign worked without knowing your baseline share of voice relative to the field.
Step 2: understand what is driving the gap
Mindshare is step one: it tells you where you are in relation to your competition, and how much attention you are getting.
The next question to ask yourself is, ‘Why is my mindshare this particular percentage?’ To answer this, you need to break the mindshare into its individual components.
You can use this follow-up prompt to break it down: "[Project A] and [Project B] have similar post volumes this month, but different Mindshare scores. Break down the difference by signal per post, KOL quality, and impressions per tweet. Tell me specifically what is driving the gap."
When you run this prompt, Cookie AI breaks the Mindshare gap down into its components:
signal per post,
KOL quality
impressions per tweet
smart engagement
and more,
for each project in your competitive set. This matters because the root cause of a gap determines the fix. A volume problem and a quality problem look identical on a Mindshare chart but require completely different responses.
We ran this prompt for our example project with Cookie AI, and this is what came back: Cookie AI shows that our example project and project 4 produce similar numbers of posts, but project 4 generates more signal per post. The gap is not active. It is engagement quality, how many people are amplifying each piece of content, and how influential those people are. This distinction matters enormously for what you do next. If the gap were driven by volume, the answer would be to post more. Because it is driven by quality, the answer is to understand who is amplifying your competitor's content but not yours.

Once you know what is driving your gap, the next question is who is moving. A competitor whose signal efficiency is improving month over month is building momentum that compounds, and by the time it shows up clearly in Mindshare numbers, the gap is already harder to close. You want to catch it early.
Ask Cookie AI: "Rank all competitors by signal-per-post efficiency for the last 30 days. Flag any project whose efficiency has improved by more than 10% compared to the previous period and show what changed."
This kind of granular benchmarking tells you which competitors are building momentum you should be paying attention to before it compounds.
Step 3: Run a period-over-period comparison to separate project issues from market-wide shifts
A single 30-day snapshot tells you where everyone stands right now. But it cannot tell you whether you are gaining ground or losing it, whether a competitor's lead is growing or shrinking, or whether a dip in your numbers is something you caused or something the whole market experienced. For that, you need to compare two periods side by side, and that comparison is where the real strategic decisions get made.
Here is an example prompt we ran: "Compare signal for [Project] and its top 3 competitors across the last two 30-day periods. For each project, tell me whether the change is likely market-wide or project-specific, and flag any outlier that bucked the trend."

This is the kind of nuance that changes how you respond. A project-specific decline calls for a different set of actions than a market-wide one. Cookie AI gives you the context to tell the difference, and the action that follows looks completely different depending on the answer. If the decline is market-wide, you hold your strategy and wait for sentiment to recover. If it is project-specific, you go looking for what changed: a drop in KOL activity, a competitor that ran a campaign, a narrative shift your content did not respond to.
Step 4: go beyond pure signal to understand sentiment
Not everything that matters is captured in volume metrics. How people talk about you, the tone of the conversation your project generates, is a signal of a different kind. A project can be discussed frequently, but critically. Another can be discussed less, but with genuine conviction.
Run this example prompt in Cookie AI to check your signal: "Rank [Project] and its competitors by sentiment score for the last 30 days. For the top and bottom ranked projects, give me the main themes driving their sentiment in either direction."

For our example project, the answer to that prompt was actually a bright spot within an otherwise concerning picture: despite sitting fourth in Mindshare and declining in signal, the project has the most bullish sentiment in its competitive set.
Understanding this distinction changes where you put energy. If sentiment were the problem, you would focus on product narrative and community trust. Because it is not, you focus on distribution.
Step 5: benchmark your KOL coverage.
Mindshare is ultimately driven by conversation, and conversations in crypto are driven by people. A project does not gain attention because it posts more; it gains attention because the right accounts pick up its posts and amplify them to audiences that matter. KOLs are the engine behind that amplification, which is why benchmarking your KOL infrastructure against your competitors is just as important as benchmarking your signal or Mindshare.
You can follow up with Cookie AI with this prompt: "Compare the top 15 KOLs driving signal for [Project] versus [Competitor] over the last 30 days. For each list show total signal, Smart KOL count, average follower size, and average posts per KOL. Summarize the structural differences in one paragraph."
What Cookie AI surfaces is often the clearest explanation for why competitive gaps exist. The top project's signal is not driven by the official account posting more; it is driven by a small number of high-follower, high-frequency advocates who have built dedicated identities around the project.
You can take this prompt even further: "Find Smart KOLs who generated signal for any of our competitors in the last 30 days but have zero mentions of [Project] in the last 90 days. Rank by signal impact on competitors and exclude any accounts affiliated with those projects."
The answer should reveal hundreds of accounts generating signals for competitors without ever touching your project. These are not cold prospects. They are already engaged in your space, already interested in the category, already credible to the audience you want to reach. They are just not talking about you yet.
Step 6: audit your internal amplification
The final benchmark most projects never run is the one against themselves. Teams spend time analyzing competitors, tracking KOLs, and monitoring Mindshare, but rarely apply the same rigor to inward. How much signal is your own team actually generating? Are the people with the highest-quality audiences consistently posting about the project, or are they lost in the general market commentary? These are questions most teams answer with gut feel, if at all.
Cookie AI makes it measurable with this example prompt: "Pull signal, impressions, and post volume for these team accounts over the last 30 days: [list handles]. Rank them by signal generated and show what percentage of each person's tweets mentioned [Project] by name."
Cookie AI pulls the full picture: who is posting, at what frequency, generating how much signal, and how often they mention the project.
You dig into the highest-potential account: "Categorize @[handle]'s last 90 days of original posts by content theme. For each theme show tweet count, total signal, and average signal per tweet. Rank themes by signal efficiency and tell me which one is most underutilized relative to its performance."
The answer tells you exactly where to focus,not by intuition, but by what the audience has already proven it responds to.
TL;DR: The benchmarking workflow in six steps
Share of voice: rank your Mindshare against competitors to establish your true position in the category
Gap analysis: break down what is actually driving the difference: volume, signal quality, or KOL infrastructure
Trend reading: compare two periods side by side to separate market-wide shifts from project-specific problems
Sentiment: identify whether your challenge is reach or narrative before deciding where to put energy
KOL benchmarking: map who is amplifying competitors but not you, and build your activation list from there
Team audit: measure your own team's signal contribution and find the conversations you should have been inside
Got questions? Feedback? You know where to find us 📞, we’re here to help you get organized, even if we’re still figuring out our own lives.
Until next lesson,
stay cookish. 🍪