Nodes, arrows, a layer-cake architecture graphic, an animation of data moving through a pipeline. Somewhere above the fold, the phrase “How it works.”
The standard critique is this is a complexity problem: too much jargon, too many acronyms, simplify until your mum gets it.
But most deep-tech copy is often perfectly well written. The problem is what it’s written about.
The mechanism gets the whole page, and the consequence, the thing the buyer actually came for, is buried somewhere inside it if it shows up at all.
A visitor arrives wondering what world this thing produces. They leave without an answer, because everyone was busy explaining how the engine runs.
The mechanism is the founder’s story
Founders lead with the mechanism because it’s the achievement. Five years in a lab, the patent, the thing three other teams tried to build and couldn’t.
So the homepage has to become a proof of existence, with an architecture diagram, benchmark table, evidence that this is not vapourware.
This means the mechanism does get its moment. It gets properly examined in the sales call, the security review, the pilot.
The homepage’s job comes earlier, and it’s smaller: it has to work before anyone agrees to a call.
Simplifying makes it worse
The usual fix tends to produce something worse: category language.
Strip the detail out of your ML-driven anomaly detection, and you sound like every other company doing anomaly detection.
Somewhere along the way, simplification got confused with minimalism: fewer words, cleaner pages, delete anything that looks technical.
But the detail is where the differentiation sits. Delete it, and you keep the generic frame, which is why so much simplified deep-tech copy reads like it was written by the category rather than the company. “We use advanced AI to secure your infrastructure” could run on forty homepages without anyone noticing the swap.
Good simplification chooses which detail carries the point. Bad simplification removes weight until nothing is left to disagree with.
What the good ones actually did
Stripe’s technology is complex: card networks, acquiring banks, reconciliation, compliance across a hundred jurisdictions.
All of it is explained somewhere, and the docs go as deep as any engineer wants. None of it leads. What leads is the consequence: a developer ships payments this afternoon instead of this quarter.
Even the famous seven lines of code were never really an explanation of how Stripe works. It was a picture of what your Tuesday looks like once it does. Above it all sat a consequence so large it doubled as a mission: grow the GDP of the internet.
Cloudflare runs one of the more technical networks on earth: anycast routing, edge compute, DDoS mitigation at a scale most engineers will never touch.
It publishes obsessively about all of it; the homepage just doesn’t make you read any of it first. What the homepage sells is the world where your site stays up, loads fast everywhere, and attacks bounce off before you notice them. The network sits behind that as proof.
Neither of them dumbed anything down. The technology stayed exactly as complex as it was. They moved it behind the consequence instead of in front of it.
In practice
Run your homepage copy through these before it ships:
Write down what the customer does differently after deployment. If the sentence contains your architecture, rewrite it. The output should be concrete: a shipped feature, a closed threat, a faster decision.
Paste your headline onto a competitor’s homepage. If it still works there, it’s category language. Rewrite until it could only be yours.
Check where the mechanism lives. One click deep, not on the front door. If a technical buyer can’t find it at all, you’ve overcorrected.
Ask whether the copy feels safe. Consequence copy makes a claim someone could challenge. Mechanism copy describes what you built, and safe usually means nothing is being claimed at all.
Pony Studio is the Emerging-Tech Brand Studio — a London-based branding and creative design agency specialising in strategic brand development for tech companies worldwide. If you’re building something bold and want a brand that moves at the same speed as your ambition, let’s talk.