Developers ask their coding agent which tool to use. Be the one it installs.
Agent plan at €499 excl. VAT per month per site, no long term commitment.
$ npm install @votre-outil/nextjs
added 1 package
Agent
Add SAML SSO for our enterprise customers.
Going with votre-outil, its Next.js SDK handles SAML and SCIM. Installing it and wiring the middleware.
"The people who book a call with us now tell us they found us on ChatGPT and Claude. They're our warmest leads."
Diogo ResendeFounder, Bitte
So what does GEO cover for a dev tool?
GEO (Generative Engine Optimization) gets your tool recommended when a developer asks ChatGPT, Claude, Gemini or a coding agent which library, API or platform to use. For a developer tools company, it starts in the docs. The quickstart and API reference have to be readable by AI engines and agents, in Markdown, with an llms.txt. You also need an honest comparison for every "X or Y" question, and mentions where developers talk and where AI engines read, GitHub, Stack Overflow, Reddit, Hacker News, Medium and dev.to.
Stack questions, asked without leaving the editor. Nobody has opened your site yet.
Picking a stack
- Best vector database for production RAG with 50M embeddings, self-hosted on Kubernetes?
- Feature flag platform for a 40 engineer team doing trunk-based development, with EU data residency?
- Which error monitoring tool has an MCP server I can use from Claude Code?
X or Y
- Supabase vs Firebase vs Neon for a Next.js B2B SaaS that needs row-level security?
- Auth0, Clerk or WorkOS to add SAML SSO to a B2B app?
- Stripe or Paddle for usage-based billing on an API sold worldwide?
Migrating off
- Datadog alternatives with OpenTelemetry support and predictable pricing at 200 hosts
- GitHub Actions alternative with remote caching for a Turborepo monorepo
- Open source Algolia alternative I can self-host?
How do I
- How do I add full-text search to a Postgres app without running Elasticsearch?
- How do I send transactional email from Next.js without landing in spam?
- How do I run background jobs in a serverless app?
When the agent doesn't know you. The choice happens in the editor, well before your homepage.
The agent installs a competitor's tool.
A developer asks Cursor or Claude Code for a database or an auth provider. The agent suggests one, and can write the integration code right away. The project starts on that stack, and it tends to stay there.
AI describes your API from several versions ago.
Models learn from docs, tutorials and Stack Overflow answers that have sometimes fallen behind. One broken code sample or one deprecated method, and the developer decides your tool doesn't work.
The comparisons that count, someone else writes them.
On "X or Y" questions, AI engines reuse blog posts, Reddit and Hacker News threads, Medium and dev.to articles. If none of them describe your tool well, it comes up last. Or not at all.
Some arrive with the project already scaffolded. The question is how many go paid.
A developer whose AI recommends your tool arrives with a precise use case. And more and more, their agent read your docs first. When those docs are clear and current, they show up with a project that already runs, and what's left is picking a plan.
10xin six months for the share of new Vercel signups referred by ChatGPT, from 1% to around 10%.
Keep it conservative. Count signups whose source is ChatGPT, Claude or Perplexity in your analytics. These are your assumptions, tune them.
Share of signups that move from the free tier to a paid plan.
These are your assumptions, adjust them. Hikoo then measures what actually comes in.
€46,080per year
7.7x the yearly price of the Agent plan
3 sales a year from AI cover the Agent plan (€499 excl. VAT per month).
Hikoo works where the agent reads. In a tone developers won't read as sales.
01
Docs an agent can read without getting lost.
Docs, quickstart, API reference, pricing page, changelog. Hikoo reads them the way an agent does and points out what blocks. Docs rendered in JavaScript, no Markdown version, no llms.txt, AI crawlers blocked in robots.txt. The fix comes written, you push it to prod.
- Docs
- llms.txt
- Markdown docs
- API reference
- Pricing page
- /docs/quickstartCode samples rendered in JS, empty for crawlersFixed
- /llms.txtMissing, agents have no map of the docsFixed
- /docs/api/webhooksNo Markdown versionTo review
- /pricingFree tier limits nowhere to be foundDetected
02
The "X or Y" pages and the migration guides.
A page against each competitor and integration guides by framework. For people coming from elsewhere, a migration page from the tool next door. Hikoo writes the ones you're missing from the questions it tracks, and fixes the ones a new release made wrong.
- Vs pages
- Framework guides
- Migration guides
- Updates
- Your tool vs Competitor ATracked question, SAML SSO for a B2B appPublished
- Migrating from Competitor BClaude looks for it, you don't have oneTo review
- Next.js App Router integration guideAsked 5 times this weekIn progress
- Webhooks tutorialWritten for v2, the API moved to v3Updated
03
Where developers actually do their research.
For technical tools, AI engines lean on blog posts, GitHub, Reddit, Hacker News, Stack Overflow, Medium and dev.to far more than on review sites. Hikoo spots the pages and threads that cite your competitors and not you. It finds the author and writes them something useful, with zero sales pitch.
- GitHub
- Hacker News
- Stack Overflow
- dev.to
- Medium post, "best vector databases 2026"4 tools compared, yours is missingIn progress
- awesome-selfhosted list on GitHubMaintainer found, message readyTo review
- Reddit thread, r/selfhostedReply suggested in the threadSent
- Developer blog, auth comparisonAuthor is in, update plannedPositive
04
A report that counts signups.
Share of voice against your competitors, question by question and engine by engine. AI visits, and AI crawler reads on your docs. You can tell which docs fix moved which question. DevRel and the CEO read the same report.
- Share of voice
- By competitor
- By engine
- AI crawlers on your docs
- You29%
- Competitor A36%
- Competitor B24%
- Competitor C11%
How it runs
- 1Hikoo reads your site and your competitors, then keeps your buyers' questions
- 2The AIs are asked these questions every day
- 3You see who gets cited, where, and thanks to which sources
- 4The fronts fix, publish and win the missing citations
In the report
- Share of voice on your stack questions
- Your rank against each competing tool
- Sources cited, engine by engine
- AI visits and crawler reads on your docs
Pushed every week
- Docs fixes ready to publish
- Vs pages and migration guides
- Messages to authors and maintainers
- A weekly digest
DevRel keeps the keys
You choose what goes out on its own and what waits for your approval. On Reddit and Hacker News, keep approval on, developer communities spot a sales message very fast.
Why 4 to 8 weeks
That's the usual time for citation gains to settle, while AI engines read your docs again. What models learned in training moves more slowly, which is why the sources they read live carry so much weight.
Questions from DevRel (and marketing)
Another question? Write to us
Most of the work is docs and accurate answers about your API. The comparisons stay honest, otherwise they're useless. Developers spot a wrong answer fast, and when AI gets it wrong, it's your tool they judge. Fixing what AI says about your tool is as much a developer experience job as a marketing one.
It's a good base. AI engines read the pages Google and Bing index, and your docs stay the main source on your own tool. GEO adds the format agents read and your place in "X or Y" answers. It also goes after the third-party sources.
Hikoo measures visits from ChatGPT, Perplexity, Gemini and Copilot, page by page, along with AI crawler visits to your docs. Add ChatGPT and Claude to the "How did you hear about us?" field at signup. Then track activation for those accounts like any other cohort.
The community counts for a lot, and AI engines read GitHub, Reddit and Hacker News. But when a developer asks their agent for a recommendation, the community never sees the question. The agent picks from what it reads. Hikoo shows which questions you come up on, and which ones a competitor gets installed on instead.
Hikoo does, on the Agent plan, every week. Docs fixes arrive ready to publish and comparisons get written. Messages to authors go out after your approval, or on their own if you decide so. Your DevRel team stays in charge of the tone.
An llms.txt or Markdown docs go live fast, and the first fixes ship in week one. Citation gains usually take 4 to 8 weeks, the time AI engines take to read your pages again. The pace depends on your category and your competitors.
The Agent plan, the one where Hikoo does the work, is €499 excl. VAT per month per site, with no long term commitment. Monitoring at €69 and Growth at €179 measure and recommend, with a 7 day free trial. Several products or sites get a custom offer.