Key findings
What we found
- Homepages know what matters. 94 of 100 make at least one of the four promises engineering leaders are hired to own somewhere on the page.
- Most don’t lead with it. Only 35 of 100 put one of the four promises in the headline. The other 59 have the line further down and lead with something else.
- Only 6 of 100 headlines give the buyer a concrete promise: a number, a time frame, or another metric the buyer could hold the company to.
- All four promises get buried the same way. Architecture and stack fit is on 82 homepages and in 9 headlines.
- It depends on the category. When the product solves the buyer’s problem directly, the headline says so: 9 of 12 observability homepages and 9 of 12 testing homepages lead with one of the four promises. Auth (0 of 12) and application security (0 of 13) never do; they lead with security, which we didn’t score as one of the four.
The four promises: on the page vs in the headline
| Promise | Job posts that list it | On the homepage | In the headline |
|---|---|---|---|
| Architecture and stack fit The tool fits the architecture they own and the stack they already run. | 86% | 82% | 9% |
| Reliability The tool helps keep production up: fewer incidents, faster recovery. | 78% | 50% | 11% |
| Quality The tool helps hold the quality bar: fewer bugs reach production. | 78% | 43% | 9% |
| Delivery speed The tool helps the team ship faster, through a named step like builds or deploys. | 66% | 33% | 6% |
Percentages of 50 job posts and of 100 homepages. Job posts: 50 US engineering-leader roles at B2B tech companies. Homepages: 100 dev-tool companies, seed to Series C. A homepage can make several promises but leads with one.
Why we ran it
The headline is the first impression
When a company buys a dev tool, an engineering leader is usually in the decision. Your homepage headline is often the first thing they read. If it doesn’t speak to what they are accountable for, you’ve lost the first impression, even when the proof sits a few scrolls down.
Why engineering leaders buy dev tools
Engineering leaders buy dev tools to hit the goals they’re measured on. Their job posts spell out what those goals are. Four of the responsibilities that came up most are ones a tool can directly help with. When a homepage says it will help with one of them, that is what we call a promise.
They’re accountable for
Technical strategy and architecture
In 86% of job posts (43 of 50)
So a tool can promise
It fits the architecture you own and the stack you already run. (architecture and stack fit)
They’re accountable for
Reliability and production operations
In 78% of job posts (39 of 50)
So a tool can promise
Production stays up: fewer incidents, faster recovery. (reliability)
They’re accountable for
Engineering quality and practices
In 78% of job posts (39 of 50)
So a tool can promise
Fewer bugs reach production. (quality)
They’re accountable for
Shipping predictably
In 66% of job posts (33 of 50)
So a tool can promise
Your team ships faster and hits its dates. (delivery speed)
We started with the buyer, not the homepages
Instead of guessing what engineering leaders care about, we read what their own job posts hold them accountable for, and built the four promises from that.
Then we checked the homepages against that list
For each of the 100 homepages we asked two questions. Does the page make any of the four promises? And does the headline lead with one?
94/100
Make one of the four promises
Somewhere on the homepage, in the company’s own words.
35/100
Lead with one in the headline
The headline and the line directly under it.
6/100
Headlines with a concrete promise
A number or a time frame on what the buyer gets.
What concrete looks like
Could a buyer hold you to it?
Most headlines led with a general claim, a security promise or a plain product description. A few gave the buyer something to verify. We turned real headlines into patterns, so no company can be identified; the bracketed parts are what each company filled in.
Concrete: a buyer could hold you to these
6 of 100 headlines did this.
- “[N]x cheaper than [a named competitor]”
- “[A feature] in minutes instead of months”
- “[A feature] in days, not quarters”
- “Recover from [an outage] in minutes, not weeks”
Generic: a buyer can’t verify these
The kind of line most headlines led with.
- “The [category] platform built for the speed of AI”
- “The [noun] layer for agents and apps”
- “Ship software [a feeling]”
By category
Some categories lead with the buyer’s problem
Observability and testing tools sell the outcome engineering leaders own, and their headlines say so. Most auth and application-security homepages make a promise on the page, but none leads with one of the four. They lead with security, which we didn’t score as one of the four, or with a product description.
| Category | Homepages | Lead with a promise | Make one on the page |
|---|---|---|---|
| Observability and incident response | 12 | 9 of 12 | 12 of 12 |
| Testing and QA | 12 | 9 of 12 | 12 of 12 |
| CI/CD and deployment | 13 | 6 of 13 | 13 of 13 |
| APIs and integration | 12 | 5 of 12 | 12 of 12 |
| Internal developer platforms and infrastructure | 13 | 4 of 13 | 13 of 13 |
| Databases and data infrastructure | 13 | 2 of 13 | 12 of 13 |
| Application and supply-chain security | 13 | 0 of 13 | 11 of 13 |
| Auth, identity and secrets | 12 | 0 of 12 | 9 of 12 |
8 dev-tool categories, 12 or 13 homepages each. Results are reported by category only.
The rubric
Run it on your own homepage
“Does our homepage speak to the buyer?” usually gets answered by gut feel. This is the rubric we used, so you can apply it the same way every time.
- Start with what your buyer is accountable for. For engineering leaders, four things a tool can help with: architecture and stack fit, reliability, quality and delivery speed. Each is a promise your homepage can make.
- Read only your headline and the line under it. Which of the four promises does it lead with, if any?
- Test that line. “Deploys go from 30 minutes to 3” passes. “Ship 10x faster” doesn’t: faster than what? A multiplier needs a baseline the buyer can check, like a named competitor or a before-and-after.
- Read the whole page and mark every promise it makes. Customer quotes and case-study stats don’t count; only your own claims do.
- If a stronger promise sits further down the page, that’s the line to test in your headline.
Could a buyer hold you to the promise? If not, it isn’t specific enough.Generic AI lines (“[X] at the speed of AI”) don’t pass on their own. Use them as context, not as the promise.
Two scoring rules that settled the edge cases
- “Set up in 5 minutes” is about installing the product, so it isn’t delivery speed.
- Only the company’s own claims count: a vendor-stated number passes, a case-study or testimonial number doesn’t.
Free content audit
Want a second read on your homepage headline?
We’ll run this rubric on your homepage, show you which of the four promises you already make, and point to the line we’d test in your headline.
How we ran it
Method and limitations
- Job posts. 50 public LinkedIn job posts for engineering-leadership roles at B2B tech companies, US, posted 17 September to 16 October 2026: VP Engineering (16), Head or Director of Engineering (12), Head of Platform or Infrastructure (11) and Engineering Manager (11). We grouped every responsibility in them into themes, with no preset list.
- The four promises. Of the themes that came up most, four are promises a dev tool can make: technical strategy and architecture (43 of 50 posts), reliability (39), engineering quality (39) and shipping predictably (33). Hiring and growing the team (48) and partnering with the business (46) came up more often, but no tool can promise those, so they are not scored. Security and compliance (33 of 50 posts) is a promise a tool can make too, but it wasn’t one of the promises we scored; 20 of the 100 headlines led with a security promise.
- Homepages. 100 dev-tool companies, seed to Series C, 12 or 13 in each of 8 categories. The list was drafted by our team and cross-checked against YC and G2.
- Definitions. “In the headline” means the headline and the line directly under it. “On the homepage” means anywhere on the homepage. Only claims in the company’s own voice count; customer quotes, testimonials and case-study stats don’t.
- Concrete promise. A headline counts as concrete when it puts a number or a time frame on what the buyer gets. Aspiration (“the next [N] years”), social proof (“[N]+ teams”), scope (“24/7”) and setup time (“live in minutes”) don’t count.
- Scoring. Every homepage was scored with Claude against the same written rules, so every page was judged the same way.
- Limitations. One snapshot of each homepage on one day, US job posts only, a company list we drafted ourselves, and some judgment even with written rules. Results are reported by category, not by company.