SuperDuperCo sells a sharp product with a blurry name. The proof is there; the position isn't — and the AI engines are filling the gap with the wrong category.
- Customer proof is dense — named logos, quoted outcomes, hard numbers on the homepage and case studies.
- The voice is consistent across the site and the founder's writing — confident, plainspoken, specific.
- Strong organic footprint on bottom-funnel comparison and integration queries.
- Three of five AI engines describe you as "a reporting tool," not a revenue-operations platform.
- The homepage H1 leads with a feature, not a category — buyers can't repeat what you do.
- No llms.txt, and JSON-LD is missing the Product and Organization types the engines lean on.
Rewrite the homepage H1 and intro to name the category once, plainly — "the revenue-operations platform for B2B finance teams" — then ship llms.txt and Product/Organization JSON-LD so the engines have a source to cite.
Positioning snapshot
- 01One ledger for revenue, billing, and forecast — no exports
- 02Close in days, not the last week of the quarter
- 03Audit-ready by default, with every number traceable to source
Positioning health check
The product is clear once you scroll; the H1 makes a buyer work for it.
Pain points map tightly to the RevOps/finance buyer's quarter-end reality.
The "one ledger" wedge is buried below three feature tiles that read like every rival.
Proof density is high — named customers, quoted numbers, traceable claims.
Site and founder voice align; the sales deck still leads with the old analytics framing.
Positioning scorecard
- Positioning54
- Messaging67
- Discoverability39
- Reputation71
- Distribution49
- Narrative Drift46
Detailed findings
54Positioning4 factors gradedExpand
““Real-time revenue reporting and analytics for modern teams.””
RecommendName the category buyers actually use — revenue-operations automation — in the H1, once, plainly.
“No /vs page; the homepage never names an alternative or the status quo.”
RecommendAdd a single explicit contrast (the spreadsheet-and-CSV close) so the wedge has something to push against.
““Built for finance and operations teams who move fast.””
RecommendTighten “fast-moving teams” to the named buyer: RevOps and finance leaders at scaling B2B SaaS.
““Close your books faster.” — a comparative, not a position.”
RecommendMake the claim defensible and owned: close and forecast from one ledger, no exports.
67Messaging4 factors gradedExpand
“Claim → proof → offer holds from hero to case study.”
RecommendKeep the spine; move the “one ledger” proof point up to sit directly under the H1.
“The strongest proof (a named 6-day close) sits in the third section.”
RecommendPromote the 6-day-close stat into the hero — it's the most repeatable line on the page.
“Site and founder essays share one confident, specific register.”
RecommendBring the sales deck into the same register; it still reads like the old analytics era.
““Powerful insights at your fingertips.” — filler among otherwise specific copy.”
RecommendCut the two remaining vendor-speak lines; replace with the concrete numbers you already own.
39Discoverability4 factors gradedExpand
“Ranks for “revenue reporting tool,” not “revenue operations platform.””
RecommendBuild the category page and interlink it so you rank for the position you want, not the one you have.
“ChatGPT, Gemini, and Perplexity all return “a reporting/analytics tool.””
RecommendShip llms.txt and a citation-ready category definition so the engines have a source to quote.
“Paid spend bids on “BI dashboards,” reinforcing the wrong category.”
RecommendReallocate paid toward category and contrast terms that match the position you're claiming.
“No llms.txt; JSON-LD missing Product and Organization types.”
RecommendAdd llms.txt and Product/Organization JSON-LD — the AI Visibility Kit generates both.
71Reputation4 factors gradedExpand
“Listed in two vendor databases under “Analytics,” absent from RevOps maps.”
RecommendSubmit to the RevOps and finance-automation categories where your buyers actually look.
“Eight named logos, four quoted outcomes with hard numbers.”
RecommendKeep it — this is your strongest asset; repackage the numbers into the hero.
“Founder publishes sharp RevOps essays; they don't link back to the site.”
RecommendWire the founder's essays into the category page so the influence compounds on-site.
“Steady employee reshares; two integration partners co-market.”
RecommendGive partners a co-branded one-pager from the Comparison Kit to amplify the wedge.
49Distribution4 factors gradedExpand
“Blog posts roughly monthly, with two quarter-long gaps last year.”
RecommendSet a sustainable cadence the Brief can feed; consistency matters more than volume.
“Almost entirely owned; little earned coverage in RevOps communities.”
RecommendSeed the founder's strongest take into two RevOps newsletters to start the earned flywheel.
“One CTA (“Book a demo”); no lower-commitment path for early-stage buyers.”
RecommendAdd the free audit / ROI calculator as a no-call entry point above the demo CTA.
“No newsletter; LinkedIn is the only active distribution surface.”
RecommendStand up a monthly RevOps newsletter — your proof and founder voice are built for it.
46Narrative Drift4 factors gradedExpand
“Homepage still leads with the 2023 “analytics” framing.”
RecommendMove the public story to the revenue-operations position the product has already grown into.
“Two rivals repositioned to “revenue operations” in the last two quarters.”
RecommendReclaim the wedge now — “one ledger” is sharper than either rival's framing, if you say it.
“Recent releases and hiring show momentum, but the homepage doesn't.”
RecommendSurface a “what shipped” line on the homepage so the brand reads as alive.
“No single coherent story you'd put on one slide for a board.”
RecommendGenerate the Synthesis once the queue clears its first wave — it becomes the board slide.
Strengths
Proof you can stand on
Eight named customers, four quoted outcomes, and a traceable 6-day-close stat. This is the rare B2B site where the evidence outruns the adjectives.
A real wedge hiding in plain sight
The "one ledger, no exports" mechanism is genuinely differentiated. It just needs to move from the third section into the H1.
A voice that holds
The site and the founder's published writing read like one person wrote them — confident, specific, free of filler. Most companies can't hold that line.
Priority issues
The AI engines have categorized you wrong
highThree of five engines describe SuperDuperCo as "a reporting tool." With no llms.txt and incomplete schema, they have nothing better to cite — so the wrong category compounds with every query.
The H1 leads with a feature, not a category
highBuyers can't repeat what they can't name. The homepage opens on “real-time reporting and analytics,” which buries the revenue-operations position the product actually owns.
Rivals are claiming your wedge
mediumTwo competitors repositioned to “revenue operations” last quarter. The “one ledger” story is sharper than either — but only if you say it before they finish taking the category.
Recommendations
Rewrite the homepage H1 and intro around the category, once, plainly.
Do nowThis single change moves Positioning, Messaging, and Discoverability at once — the engines, the buyer, and search all read the same first line.
Ship llms.txt and Product/Organization JSON-LD.
Do nowGive the AI engines a citable source for the right category. The AI Visibility Kit generates all of it from this audit.
Promote the 6-day-close proof into the hero.
Near termYour most repeatable, defensible number is sitting three sections down. In the hero it does the work the filler line is doing now.
Stand up a monthly RevOps newsletter.
StrategicYour proof density and founder voice are built for it, and it opens an earned channel you don't currently have.
Recommended Kit
AI Visibility Kit
Generates the llms.txt, robots diff, JSON-LD, homepage H1+intro rewrite, and citation-gap briefs that close the Discoverability gap above — ready to hand to a developer.