What happens when the positioning is right.
Three case studies. Different sectors, same shape: a technically strong product, a market that wasn't responding, and the strategic decision that changed the commercial outcome.
Most of our work is anonymous by request — positioning is a strategic asset and clients don't always want the language they paid for to be public. Where attribution makes sense, we use it. Where it doesn't, we use sector descriptors. The work is the same either way.
Naming the problem the market couldn't articulate.
Context
UnlikelyAI was building neurosymbolic AI for regulated industries — interpretable, auditable AI for sectors where the cost of an LLM hallucination is regulatory, not just reputational. The technology was genuinely differentiated. The team was strong. The product was being adopted by serious buyers in financial services. But the market conversation was being dominated by general-purpose LLM providers, and "trust" and "safety" had become category clichés that meant whatever the speaker wanted them to mean.
The problem with the positioning
The existing language was about the technology — neurosymbolic, hybrid AI, deterministic logic. Architecturally accurate, commercially inert. The senior buyers in regulated sectors didn't care about how the AI worked. They cared about a problem they hadn't yet found the words for: the people inside their organisations responsible for AI decisions had no defensible position to take when something went wrong. The category was being written for engineers, but the buyers were compliance officers, general counsel, risk leads and executive sponsors who needed to be able to explain their AI deployment to a regulator.
What we did
We commissioned primary research with 1,000 senior leaders across financial services, government, healthcare and legal. The survey wasn't about AI capability — it was about the executives sitting on top of AI deployment and how they were thinking about responsibility, defensibility and oversight. We built the narrative around what we called the trust gap — the distance between what the technology could do and what the buyer could defensibly do with it in a regulated context. We launched it through a tier-one press strategy and a London event with senior leaders from J.P. Morgan, UBS, PwC, Cabinet Office and Deloitte in the room.
What happened
Coverage in The Times, BBC and The Daily Telegraph in the first week. The report became reference material in the sector — quoted in industry events, used internally by financial services compliance teams, and within six months the founder of Starling Bank was using the language to brief the FCA on AI in banking. UnlikelyAI moved from "interesting deep tech AI company" to "the firm with a defensible position on AI trust in regulated markets" — a category position that doesn't compete with the LLM providers because it answers a different question.
What changes when you stop treating every buyer like they're ready to buy.
Context
A B2B travel tech company with a strong product and a long sales cycle. The product solved real operational problems for hotels and travel platforms — the kind of problem that compounds revenue if you fix it and quietly drains margin if you don't. But pipeline conversion was sticking. New business felt slow, and the team couldn't tell whether the issue was lead volume, lead quality, message-market fit or sales execution.
The problem with the positioning
All marketing materials were optimised for buyers who already understood the category and were comparing options. The website, the sales decks, the content — everything assumed the buyer was at the "comparing solutions" stage. In reality, most of the addressable market didn't yet recognise the operational problem the product solved as a problem worth solving. So content was pulling in self-selected late-stage buyers — a small pool, highly contested by direct competitors — and ignoring the much larger pool of buyers who were feeling the problem without yet having words for it.
What we did
We mapped the buyer journey by awareness stage: problem aware, solution aware, product aware. We re-wrote the language for each. The problem-aware content stopped talking about the product entirely and started talking about the operational symptoms hotels were already feeling — the daily friction that made their teams want to throw a laptop. Solution-aware content reframed the category itself, separating the work the product did from the work competitors did. Product-aware content kept the existing technical depth but with sharper differentiators that worked in head-to-head comparisons.
What happened
£612,640 in identified revenue opportunity surfaced in the first cycle — a +206% lift against the previous comparable period. The pipeline broadened at the top, which counter-intuitively made the bottom convert faster, because buyers arrived having self-educated through the problem-aware content. Sales conversations got shorter. The team stopped having to convince buyers that the problem was real before they could start selling the solution.
Seven launches, one content architecture.
Context
A high-growth B2C edtech business launching personal development products at pace. The challenge: each launch had to feel like an event but they were happening multiple times a year to overlapping audiences. The same buyers were seeing different messaging for products that shared an underlying philosophy, and the brand felt less coherent the more product was released into the market.
The problem with the positioning
Each launch was being written in isolation. Different teams owned different launches. Each launch reinvented the company's worldview from scratch to justify its specific product. The result was a brand that read as inconsistent even though every individual launch was strong, because the underlying philosophy was being re-litigated every time instead of inherited.
What we did
We built a content architecture for the whole launch programme rather than per launch. We defined which buyer-stage messages stayed consistent across launches — the philosophy, the worldview, the way the company talked about transformation — and which moved: product specifics, instructor positioning, the particular promise of each release. Each launch sat inside the architecture rather than reinventing it. Launches stopped competing with each other for the same audience's attention and started compounding.
What happened
$3M in revenue across seven product launches in the period. 42% MoM traffic growth from the surrounding content strategy. The brand became more coherent, not less, as launch frequency increased — which was the original strategic bet. The architecture remained in use for several launch cycles after the original engagement ended.
Want to see what this looks like for your market?
Book a free 45-minute discovery call. We'll tell you exactly where the gap is — whether you work with us or not.
Book your call→ Two new Sprint clients per month.