Your verdict
Your page is half shared.
About half of what your page says, Cribl also says. You're less same than 300 of the 366 SaaS sites scored (SaaS avg 56).
Each named site is scored the same way, against the other 3 in this set, so its tick means the same as your marker. The dashed line is the frozen benchmark average.
Less same than average
The average SaaS site scores 56; you scored 46.
You are 10 points less same than the average SaaS site.
Closest overlap: Cribl
Of the 3 sites you named, Cribl echoes the most of what your page says. Scored the same way against the rest of the set, Cribl sits at 48.
Cribl is the competitor you sound most like.
Room to own more
17% of your claim space is ownable: unique, relevant, and hard to copy.
17% is ownable, and every claim you own already leads.
Three changes worth testing first.
Chosen by rule from the comparison with Cribl, ClickHouse and Scanner: the shared claim taking your most prominent space, then the claims only you make that sit too low on the page to be read. Each one links to its claim card.
- “Build a Security Data Lake without changing how your SOC works”
Cribl and Scanner say it too (67% of the set). Buyers may still need it, but shared ground cannot carry your hero — move it lower and give that space to something only you can say.
Table stakesMost of the set says this too. - “Search unstructured logs directly in object storage”
Keep the fact, lose the position: cribl and Scanner say it too (67% of the set), and your hero is spending its first impression on the same territory as theirs.
Table stakesMost of the set says this too.
Try these changes, then test them with real buyers.
This measures overlap. Whether buyers notice is a different question, and only they can answer it.
What you can own
Claims only you make, that buyers weigh, and that competitors can’t easily copy.
17% of your page’s claim space is yours to keep.
Why this is not 100 minus the Sameness Index
The index is a weighted composite across six categories, including page structure and visuals. This bar is measured on your claims alone, weighted by where each one sits on the page. Different denominators, so the two never add to 100 and are not meant to.
Already leading with · 2
- Build a security data lake without changing SOC workflows
“Build a Security Data Lake without changing how your SOC works”
- Acts as federated search provider for existing SIEM
“Federated provider for your SIEM”
Buried in body copy · 0
Nothing buried. Every claim you own is already above body copy.
Where you blend in
Territory you spend prominent space on that the set also occupies. Not every line is one to delete — the question is whether it has earned the space, or whether something only you can say should be there instead.
- Commodity · 67%Table stakesHerosearch data in place across your data lake
- “Build a Security Data Lake without changing how your SOC works”
- “Search unstructured logs directly in object storage”
- “Federated provider for your SIEM”
You say this 3 different ways.
Cribl and Scanner cover this territory. Buyers may need to hear it, but in your hero it spends the first impression on shared ground.
They say- Cribl“Consolidate pipelines, cut noise, tier 'just-in-case' data to low-cost storage, and search it in place when you need it”
- Scanner“Schemaless indexing for object storage across all clouds, SaaS tools, and lake and warehouse streams.”
- Commodity · 100%Table stakesSectioncuts data/SIEM cost, predictable bills
- “70%+ Savings - Put data in Lumi instead of your SIEM backend to lower costs”
Common ground with Cribl, ClickHouse and Scanner. Say it if buyers need it — lower on the page, where it is not the thing they read first.
They say- Cribl“The first problem Cribl solved for us was optimizing our firewall log consumption, we saw a reduction of about 50%”
- ClickHouse“Cost effective: Best-in-class compression ratios that reduce storage and accelerate performance”
- Scanner“Fast and economical for AI to freely iterate”
- Commodity · 100%KeepSectionone platform for ingest, storage, analysis
- “AI usage is generating more data than ever. Agentic workflows require more history and context. Lumi is the SIEM platform for the AI age.”
Cribl, ClickHouse and Scanner all say what they are and who they are for, as every page in a category must. Keep it — it is orientation, not differentiation.
They say- Cribl“Your AI Platform for Telemetry”
- ClickHouse“The leading database for AI”
- Scanner“Built for the AI Security Era”
- Commodity · 100%Table stakesSectionqueries and investigations are much faster
- “15x+ Faster searches - Accelerate investigations across real-time & historical data”
Cribl, ClickHouse and Scanner make the same claim. It cannot set you apart, so it should not carry the section.
They say- Cribl“Search faster. Investigate smarter.”
- ClickHouse“Powering agentic systems with millisecond queries at petabyte scale”
- Scanner“100x faster than traditional SIEMs and data lakes.”
- Commodity · 100%Table stakesSectionworks with existing tools and query languages
- “A Security Data Lake needs a search layer that makes all of your data usable through the tools your analysts already know”
A buyer comparing tabs sees this on Cribl, ClickHouse and Scanner. Yours earns nothing by repeating it up top; it can live lower down. Nobody else uses your exact words, but everyone is on the ground. Nobody else makes this exact claim, but everyone occupies the territory — lead with the specific, not the generic.
They say- Cribl“Shape and move data to any tool - no new agents or infrastructure”
- ClickHouse“Developer friendly: Built to ensure that even the most sophisticated data analysis can be done intuitively, using simple SQL”
- Scanner“Built for integrations, automation, and custom workflows. Connect Scanner to your existing tools and security stack.”
- Commodity · 67%Table stakesSectioncustomer proof of quantified results
- “With Imply Lumi, we can ingest more data, retain it longer, pull in telemetry from platforms beyond Splunk, and still understand what our costs will look like…”
Cribl and Scanner got here first as far as a buyer can tell. Keep the fact for readers who need it; move the position to a claim only your page can make. Nobody else uses your exact words, but everyone is on the ground. Nobody else makes this exact claim, but everyone occupies the territory — lead with the specific, not the generic.
They say- Cribl“Cribl Search has optimized our operations teams' time and efficiency. They're able to troubleshoot and find issues for our customers in a minimal amount of…”
- Scanner“We can search through a full year of logs in seconds, giving us visibility into an order of magnitude more data than before.”
- Contested · 33%SharpenHerolegacy tools force cost/coverage tradeoffs
- “Your data is trapped inside your SIEM”
- “Moving your logs to your data lake is easy. Accessing it is hard.”
- “Legacy SIEMs require compromises”
You say this 3 different ways.
Scanner is on this territory too (33% of the set). It narrows the field without winning it — make it specific enough that it cannot be said of them.
They say- Scanner“Traditional SIEMs cause vendor lock-in”
- Contested · 33%SharpenSectionfast, easy migration and deployment
- “Imply is the fastest, most efficient way to decouple your stack”
Cribl is on this territory too (33% of the set). It narrows the field without winning it — make it specific enough that it cannot be said of them. Nobody else uses your exact words, but everyone is on the ground. Nobody else makes this exact claim, but everyone occupies the territory — lead with the specific, not the generic.
They say- Cribl“Make SIEM migrations seamless”
- Contested · 33%SharpenSectionorder-of-magnitude better efficiency than legacy
- “Best-in-class efficiency - Lumi is more than an order of magnitude more efficient than legacy SIEMs”
Shared with ClickHouse. Sharpen it to the thing only you do here, or it reads as a claim any of you could make.
They say- ClickHouse“ClickHouse is the fastest and most resource efficient real-time data warehouse and open-source database”
Claim-by-claim evidence
Every claim on your page (15)
What the columns mean
- Claim
- The grouped claim, then your exact line beneath it.
- Type
- What kind of claim it is: category, segment, outcome, capability, quality or proof.
- Placement
- Where it sits on your page: hero, section or body copy. Hero claims weigh most in the index.
- Same claim
- Share of the competitors making this exact claim. Drives ownership and ownable share.
- Same territory
- Share of the competitors with any claim in the same buyer-facing territory. This is what the index is scored on.
- Sayability
- Whether a competitor could truthfully make the same claim: anyone could, copyable with effort, or hard to copy.
- Relevant
- Whether buyers decide on this. A unique claim nobody buys on is not ownable.
- Ownership
- Commodity: 60% or more of the set says it. Contested: 20–59%. Unique: under 20%, owned when it is also hard to copy.
Tap a column to sort by it; tap again to reverse. Sorted by Same claim, highest first.
Search logs in place in object storage / data lake “Search unstructured logs directly in object storage” | capability | Hero | 67% | 67% | Copyable with effort | Yes | Commodity |
Purpose-built as the SIEM platform for the AI age “AI usage is generating more data than ever. Agentic workflows require more history and context. Lumi is the SIEM platform for the AI age.” | category | Section | 67% | 100% | Anyone could say it | Yes | Commodity |
Data is trapped/locked into your SIEM vendor “Your data is trapped inside your SIEM” | outcome | Hero | 33% | 33% | Anyone could say it | Yes | Contested |
Cuts telemetry/SIEM costs dramatically (quantified) “70%+ Savings - Put data in Lumi instead of your SIEM backend to lower costs” | outcome | Section | 33% | 100% | Copyable with effort | Yes | Contested |
Data lakes are cheap to fill but hard to query “Moving your logs to your data lake is easy. Accessing it is hard.” | outcome | Section | 33% | 33% | Anyone could say it | Yes | Contested |
Legacy SIEMs force compromises “Legacy SIEMs require compromises” | outcome | Section | 33% | 33% | Anyone could say it | Yes | Contested |
Order-of-magnitude better efficiency than legacy tools “Best-in-class efficiency - Lumi is more than an order of magnitude more efficient than legacy SIEMs” | quality | Section | 33% | 33% | Copyable with effort | Yes | Contested |
Searches/investigations are dramatically faster (multiplier) “15x+ Faster searches - Accelerate investigations across real-time & historical data” | outcome | Section | 33% | 100% | Copyable with effort | Yes | Contested |
Query using existing languages (SPL and SQL)grouping uncertain “Query Lumi using SPL and SQL” | capability | Body | 33% | 100% | Copyable with effort | Yes | Contested |
Build a security data lake without changing SOC workflows “Build a Security Data Lake without changing how your SOC works” | outcome | Hero | 0% | 67% | Copyable with effort | Yes | Unique and owned |
Acts as federated search provider for existing SIEM “Federated provider for your SIEM” | category | Section | 0% | 67% | Copyable with effort | Yes | Unique and owned |
Customer: ingest more data, retain longer, predictable costs “With Imply Lumi, we can ingest more data, retain it longer, pull in telemetry from platforms beyond Splunk, and still understand what our costs will look like…” | proof | Section | 0% | 67% | Anyone could say it | Yes | Unique for now |
Data lake needs a search layer analysts already know “A Security Data Lake needs a search layer that makes all of your data usable through the tools your analysts already know” | capability | Section | 0% | 100% | Anyone could say it | Yes | Unique for now |
Fastest, most efficient way to decouple the stack “Imply is the fastest, most efficient way to decouple your stack” | quality | Section | 0% | 33% | Anyone could say it | Yes | Unique for now |
Legacy approach means a separate search experience “Separate search experience (legacy SIEM compromise)” | capability | Body | 0% | 100% | Anyone could say it | No | Unique for now |
- Search logs in place in object storage / data lake“Search unstructured logs directly in object storage”capabilityHerosame claim 67%same territory 67%Copyable with effortCommodityAlso on Cribl, Scanner
- Purpose-built as the SIEM platform for the AI age“AI usage is generating more data than ever. Agentic workflows require more history and context. Lumi is the SIEM platform for the AI age.”categorySectionsame claim 67%same territory 100%Anyone could say itCommodityAlso on Cribl, Scanner
- Data is trapped/locked into your SIEM vendor“Your data is trapped inside your SIEM”outcomeHerosame claim 33%same territory 33%Anyone could say itContestedAlso on Scanner
- Cuts telemetry/SIEM costs dramatically (quantified)“70%+ Savings - Put data in Lumi instead of your SIEM backend to lower costs”outcomeSectionsame claim 33%same territory 100%Copyable with effortContestedAlso on Cribl
- Data lakes are cheap to fill but hard to query“Moving your logs to your data lake is easy. Accessing it is hard.”outcomeSectionsame claim 33%same territory 33%Anyone could say itContestedAlso on Scanner
- Legacy SIEMs force compromises“Legacy SIEMs require compromises”outcomeSectionsame claim 33%same territory 33%Anyone could say itContestedAlso on Scanner
- Order-of-magnitude better efficiency than legacy tools“Best-in-class efficiency - Lumi is more than an order of magnitude more efficient than legacy SIEMs”qualitySectionsame claim 33%same territory 33%Copyable with effortContestedAlso on ClickHouse
- Searches/investigations are dramatically faster (multiplier)“15x+ Faster searches - Accelerate investigations across real-time & historical data”outcomeSectionsame claim 33%same territory 100%Copyable with effortContestedAlso on Scanner
- Query using existing languages (SPL and SQL)grouping uncertain“Query Lumi using SPL and SQL”capabilityBodysame claim 33%same territory 100%Copyable with effortContestedAlso on ClickHouse
- Build a security data lake without changing SOC workflows“Build a Security Data Lake without changing how your SOC works”outcomeHerosame claim 0%same territory 67%Copyable with effortUnique and owned
- Acts as federated search provider for existing SIEM“Federated provider for your SIEM”categorySectionsame claim 0%same territory 67%Copyable with effortUnique and owned
- Customer: ingest more data, retain longer, predictable costs“With Imply Lumi, we can ingest more data, retain it longer, pull in telemetry from platforms beyond Splunk, and still understand what our costs will look like…”proofSectionsame claim 0%same territory 67%Anyone could say itUnique for now
- Data lake needs a search layer analysts already know“A Security Data Lake needs a search layer that makes all of your data usable through the tools your analysts already know”capabilitySectionsame claim 0%same territory 100%Anyone could say itUnique for now
- Fastest, most efficient way to decouple the stack“Imply is the fastest, most efficient way to decouple your stack”qualitySectionsame claim 0%same territory 33%Anyone could say itUnique for now
- Legacy approach means a separate search experience“Separate search experience (legacy SIEM compromise)”capabilityBodysame claim 0%same territory 100%Anyone could say itnot a buying criterionUnique for now
How this was calculated
Sameness measures how much your claims overlap with the sites compared. It does not measure message quality or whether buyers prefer you.
AI-analyzed: an AI read each page on its own and grouped the claims that say the same thing. No score here was written by a model — every number is computed from those groupings in our own code, with the weights below.
How the score is built
| Category | Weight | Yours | What a high score means |
|---|---|---|---|
Messaging Category framing, who it is for, and the outcome promised | 30% | 64 | The most expensive kind of sameness. A buyer cannot tell what job you do that the others do not. |
Claims Attribute and benefit claims — speed, ease, quality, ROI | 30% | 33 | Every shared claim is a line already read on another tab. Cut the ones nobody owns and spend the space on something they cannot. |
Features Capabilities and functions the page lists | 15% | 83 | Expected in a mature category, and the least alarming of the six. Feature parity is normal; leading with it is the mistake. |
Proof The kinds of evidence offered: customer logos, numbers, testimonials, case studies, badges | 10% | 15 | Same kinds of proof as everyone means the proof stops working as proof. It is scored on the kind of evidence, not on which customers are named. |
Structure Section order, navigation, CTA language and placement | 10% | 0 | The generic SaaS template — hero, logos, three-feature grid, testimonial, CTA. Familiar is not the same as memorable. |
Visual Palette family, imagery style, layout patterns | 5% | 60 | Weighted lowest on purpose: buyers rarely decide on this. Worth knowing, rarely worth fixing first. |
Each site was read on its own first, with no knowledge of the others, so your page gets no benefit of the doubt a competitor’s does not. A category nothing could be measured for drops out and the rest are re-weighted, rather than counted as zero.
What we compared (4 pages read)
What it cannot tell you
The index can find where two pages converge. It cannot say whether a buyer would notice, or which of your reasons to buy actually land. A single check also moves several points between runs, so read the band and the ranking, not the last digit.
Your highest-impact changes
- 1Table stakesYour hero copy says “Build a Security Data Lake without changing how your SOC works”.
Cribl and Scanner say it too (67% of the set). Buyers may still need it, but shared ground cannot carry your hero — move it lower and give that space to something only you can say.
- 2Table stakesYour hero copy says “Search unstructured logs directly in object storage”.
Keep the fact, lose the position: cribl and Scanner say it too (67% of the set), and your hero is spending its first impression on the same territory as theirs.
- 3Table stakesYour section copy says “70%+ Savings - Put data in Lumi instead of your SIEM backend to lower costs”.
This is the set's common ground — Cribl, ClickHouse and Scanner all say it too. It will not set you apart wherever it sits, and in the section it costs you the one place a distinctive claim would be read.
- 4Table stakesYour section copy says “A Security Data Lake needs a search layer that makes all of your data usable through the tools your analysts…”.
A buyer with three tabs open reads a version of this on every one of them. Say it further down for the readers who need it; the section should carry a claim they will only find here.
- 5Table stakesYour section copy says “15x+ Faster searches - Accelerate investigations across real-time & historical data”.
True of you and true of them: Cribl, ClickHouse and Scanner all say it too. That is why it decides nothing, and why the section is the wrong place to spend it.
- 6Table stakesYour section copy says “With Imply Lumi, we can ingest more data, retain it longer, pull in telemetry from platforms beyond Splunk, a…”.
In the section: True of you and true of them: Cribl and Scanner say it too (67% of the set). That is why it decides nothing, and why the section is the wrong place to spend it.
- 7Table stakesYour body copy says “Separate search experience (legacy SIEM compromise)”.
In the body: Keep the fact, lose the position: cribl, ClickHouse and Scanner all say it too, and your body is spending its first impression on the same territory as theirs.
The only way to know if it matters.
This report can tell you where your messaging overlaps. It cannot tell you whether a buyer would care, or which of your reasons to buy actually land. Put the page in front of real B2B buyers in your target market and ask them.
