"Find the answer your keyword search keeps missing."
A code-search startup whose retrieval was genuinely better than grep — behind a page that led with the model instead of the answer.
Specimen record
Field
Developer tools · code search
Engagement
Workshop, then landing page
Timeline
21 days, kickoff to live
Baseline → after
+212%demo requests, sixty days after launch
Where the walk began
Enterprise-grade embeddings at scale
That sentence sat above the fold for a year. It named the architecture, and the architecture was real — but every visitor who could evaluate embeddings already had them. Sales calls kept circling a different moment: an engineer typing the same question three ways and giving up. The page never mentioned it.
The walk, retraced
The same four lanterns — what happened at each one.
01
Discover
We read the docs, sat in on nine sales calls, and interviewed each founder separately. The deck said infrastructure; the buyers kept describing a moment.
"We know it's in the codebase somewhere. We just can't type the right words for it."Engineering lead · demo call
"I typed the same question three ways, then gave up and asked in Slack."Senior engineer · user interview
"Grep finds the word. We need the thing the word means."CTO · lost-deal review
Three of nine calls — the evidence brief, page one
02
Frame
Two days, whole team. Three founders arrived with three products — a vector database, a developer platform, an IDE plugin. One sentence left the room, signed.
Day two — the wall narrowing to one sentence
The sentence, signed"For engineers who know the answer lives somewhere in the codebase, we find what keyword search keeps missing — no query language required."
03
Design
The page opens with the question, not the stack — one claim at three times the comfortable size, the product's real output above the fold. Two review rounds, decisions made in the file.
What it said
◦ beforeEnterprise-grade embeddings at scaleRequest access
What it says
◦ shippedFind the answer your keyword search keeps missing.See it find yours
Same product, same traffic — the fold, before and after04
Ship
Production code handed to their repo, analytics wired in, baseline set at launch. The one measured iteration moved the proof above the call to action.
