Hev meets Jev
Building your own SOTA reranker is now highly achievable. I pointed TypeSafe's new structured-output model at three BEIR datasets, untuned, and it landed next to the purpose-built rerankers on quality, price, and latency.
adam hevenor
One guy,
many agents.
AI, search, and agentic engineering consulting.
I help CTOs turn their engineering org into a technical staff that directs agents toward outcomes. I run my own practice that way — hev factory, hev layer, and hev ask are what it ships.
launching — hev factory
The many-agents part, packaged.
"One guy, many agents" isn't just a slogan, it's how I build. You can try it out yourself. hev factory runs a crew of coding agents on a Mac you own: a front desk that takes the work, a loop that breaks an approved plan into tasks, and a worker per task in its own session you can attach to and take over by typing.
$ brew install hev/tap/factory
$ factorythe lead bet — hev layer
Focus on results, not infra.
The search engineering layer: a transparent, turbopuffer-shaped proxy that makes an existing vector store better without changing client code. Query routing reads the shape of a request and picks vector, lexical, or hybrid with RRF fusion. Typo-tolerant surfacing returns near-misses with a badge saying why. It takes on the jobs your search team never asked for — caching, transforms, embedding, cost, and ops.
case studies & r&d
case studies -> r&d ->I help teams align strategically, then move with them to help elevate the pace. Client engagements fund my R&D, allowing my clients to benefit directly from my research. -> about Adam
case study · Trio Health A search api that became an agentic platform 
case study A two-week CLI sprint for an LLM evals platform 
case study · Taffrail An MCP server for a wealth-advisory rules engine 
r&d · active hev factory 
r&d · active hev layer 
r&d · experiment hev ask 
showcase
travels with charlie
A travel publication, built whole — destination guides, illustrated art direction, search, accounts. Next up: an agentic trip app builder.
-> travels-with-charlie.com
the client workspace
Every engagement ships an agent.
Built around weekly updates I write myself — what landed, what's next, what's blocked. The agent answers on top of them, grounded in the plan, the hours, and everything we produce. Yours to keep. Shown: an example week.
-> book a timeservices
view services ->
Workshops A hands-on half day with your team: operating an agent factory, evals from zero, KPIs that drive behavior, or one shared vocabulary across your leadership. Your team leaves with something working. 
Research Plan A hosted plan for the question you're actually trying to answer — what to learn, from whom, in what order, and what would change your mind. Your team marks progress against it and interrogates it with an agent. 
Research Program The plan, and I run it. Six interviews with people who can answer the question, then the insight analysis: what the market said, where it contradicts your roadmap, and what to do about that. 
Search & Retrieval POV A proof of value on your own corpus. Evals first, so "better" is a number you can defend, then hybrid, reranking, chunking, and the vector database call, argued from your data. You keep the eval set and the system. 
Fractional CTO I run a factory on your codebase. Agents do the volume, I own the review gate. Around that: architecture, vendor selection, hiring judgment, and delivery rhythm. 
Hourly Data engineering, ML, and strategy work billed by the hour — for a bounded problem, a second opinion, or ad-hoc help when you don't need a standing engagement. recent writing
view all ->How to choose a vector database
Talk abstract. Reading the vector pricing calculators, linking features to outcomes, and what else decides it anyway — existing search systems, AWS credits, and how fast your data grows.
Dope tech: TopK
First entry in a series on the search tech I actually reach for. TopK gets the 2026 architecture right — multi-vector late interaction, object-store-native plus NVMe, LSN read-after-write consistency, and Postgres-compatible SQL. Not enterprise-ready yet, and I say where.
A new role for SWE, managing outcomes not outputs
I haven't reviewed a line of code in over a decade — not because I can't read it, but because I learned in 2008 that trust comes from outcomes, not from meddling in output. That's the same lesson every engineer handing work to an agent is about to learn.