Product and strategy · 4 min read
The two readers
The person who signs and the person who evaluates want opposite things from the same page. Writing for one loses the other, usually silently.
Two people read a technology company's website, and they want opposite things.
The **executive or owner** wants the outcome. What changed, what it was worth, what the risk is, in plain language, quickly. They have limited technical fluency and no appetite for acquiring more.
The **technology leader** wants the architecture. The constraints, the trade-offs, what broke and what it cost. They have been pitched by many firms and trust almost none of them, and marketing language actively repels them.
The buyer cannot evaluate. The evaluator cannot buy.
How this usually goes wrong
Most firms write for the buyer, because the buyer signs. The site is outcome-led, plain, and slightly thin.
The technology leader arrives, reads for ninety seconds, finds no evidence anyone has done anything difficult, and forms a private opinion. They do not complain. They do not send an email saying the site lacked technical depth. They tell their executive it looks fine and quietly suggest a different firm, or they do not push back when someone else does.
You never learn this happened. There is no analytics event for a CTO deciding you are not serious. It is the most expensive thing your website does and it is invisible.
The opposite failure is rarer and just as real: a site written entirely for engineers, which the person with the budget cannot parse and does not feel spoken to by.
Two depths, one page
We resolve it structurally. Every substantial page has two reading depths.
**The surface** is outcome, plain language, what changed and what it was worth. It is complete on its own. An executive can read only this and have everything they need to make a decision.
**The depth** is architecture, constraints, decisions, rejected alternatives, what did not work. It extends the surface rather than repeating it, and it is reached by one deliberate action.
Applied to a case study, the split follows the structure: situation, problem, objective, result and lesson at the surface; thinking, solution, technology and experience underneath.
Three rules that make it work
**The depth layer is never gated.** No form, no email address, no "download the technical brief". The moment you gate it you have converted the most valuable trust signal you own into a lead-capture mechanism, and the person you were trying to impress closes the tab.
**It is real content on the same URL.** Progressively disclosed, not a separate page and not loaded behind an interaction that hides it from search engines or screen readers. It is indexable, linkable and keyboard-reachable. A technology leader who arrives on a technical article from a search result is a common path, and it has to work.
**Some things are depth-native.** An engineering article written for a CTO does not need a simplified layer bolted on top. Forcing every piece into the same shape produces two mediocre halves.
The measurement that falls out of it
Because the depth layer requires a deliberate action, engaging with it is a **behavioural signal that someone is evaluating rather than browsing** — and it is the only pre-contact signal of a serious buyer that you can actually observe.
That is the real argument against gating it. Gate it and you convert a clean signal into a form fill, and lose the trust that would have produced the contact.
The part that cannot be faked
The depth layer is the only content a competitor cannot copy, because it requires having done the work.
Anyone can write that they care about architecture. Only someone who shipped the thing can say which approach they rejected and why, what the constraint actually was, and what it cost when they got it wrong. That specificity is the entire signal, and it is why the temptation to write a plausible-sounding technical section is worse than writing none at all — a technology leader can tell the difference immediately, and now they know something about you.
One body of work, two outcomes
There is a second return on this, which we did not design for and would not have predicted.
The depth layer is also the strongest recruiting asset a small firm has. Engineers judge a company by the quality of its technical writing, not by a careers page. The same content that convinces a CTO you can be trusted convinces an engineer they would learn something working with you.
One body of work, two strategic outcomes, and neither of them possible if you had written for the buyer alone.