About DevTune
Why we built DevTune
Buyers now ask AI which products to trust. DevTune records the answers they get, helps your team improve them, and checks whether the work made a difference.
What DevTune records
- 01
AI answers
What buyers were told and which pages were cited
- 02
Site activity
The pages AI systems fetched and the visits they sent
- 03
Work shipped
What your team approved and changed
- 04
Results
What moved after the change
Why DevTune exists
One prompt tells you almost nothing.
A screenshot shows one answer on one day. It can't tell you how often your product appears, why another company was cited instead, or whether your work changed anything.
We kept seeing teams told to publish more content or chase an opaque score. DevTune replaces that guesswork with a simple loop. See what is happening, choose the work, then check the result.
How DevTune works
One job, four parts
The same project data runs through the whole product. You can follow a finding into the fix and back to the result.
- 01
Visibility
Record the answers, mentions, and citations buyers see.
- 02
AI Demand
See which pages AI systems crawl or fetch, and the visits they send.
- 03
Act
Turn a finding into a ranked action and a brief your team can edit.
- 04
Outcomes
Compare what happened before and after the work shipped.
How we work
Show your working.
You shouldn't have to trust a score you can't inspect. DevTune keeps the source data, dates, and coverage with the result so you can check the claim yourself.
Start with the source
Open the answer, citation, and page behind a result.
Don't blur the signals
A citation is not a mention. A crawl is not an answer fetch or a visit.
People decide what ships
Agents investigate and draft. Your team approves the work.
Put dates on the comparison
Show the period being compared and say when the source coverage is incomplete.
From product growth to AI search
Ben spent his career building and growing products for developers. At CloudBees, he led Product and Growth with a team of more than 40 product managers and designers. At Snyk, he led the teams responsible for growth, education, and developer experience during a period of more than 160% year-on-year ARR growth.
He then moved into advising, working with founders and product and growth leaders at B2B developer-tool companies on product-led growth, product-led sales, growth teams, and experimentation.
When AI started changing how buyers discover and judge software, he saw teams trying to manage the channel with prompt screenshots, opaque scores, and generic content advice. He turned his focus to that growing problem. DevTune brings the habits that made product growth more scientific to AI search. Measure what buyers see, make a change, check the impact, repeat.
Who we build for
For the people who have to fix it
We started with developer-tool and infrastructure companies, where a stale technical claim can cost a sale. DevRel, growth, content, docs, and product teams use DevTune to work from the same facts. It also works for any company whose buyers ask AI for advice.
Our research
We publish what we learn.
The State of AI Search for Dev Tools tracks the answers buyers see, the pages AI platforms cite, and the companies that appear most often. The report and its method are public.
Read the State of AI SearchWhat does AI say about your product?
Start with the answers your buyers see.