Case study · Blue OwlE-commerce
2020 to 2022Frontend development for agency clients04 / 04

Blue Owl

Turning a paid-traffic store into an organic one

A blog and content section the client never asked for. We pitched it, built it on a headless CMS and shipped it.

E-commerce2020 to 2022

What changedMeasured before
and after3 outcomes
in production02

(01)Monthly visitors125,853 → ~150,000

(02)New entry pages beyond product listings

(03)Developer time per published article

The processWhat we walked into
and what we didFrontend development for agency clients03

What we
walked into

A client store depended almost entirely on paid traffic, with monthly visitors flat at 125,853.
The site had no blog or guides, so only product pages ranked in search.
Editors had no way to publish without a developer.

(01)Proposed the blog and content section to the client unprompted, with the SEO and traffic case behind it.
(02)Built it on Gatsby and GraphQL with WordPress as a headless CMS, so editors publish without engineering.
(03)Structured templates, metadata and internal linking around product categories.
(04)Handed over documentation and trained the client's team on publishing.

StackGatsbyGraphQLWordPressJavaScriptjQuery

Now an agentThis playbook runs
on every commit1 agent
in the fleet04

The agents below now run the checks, measurements and fixes from this engagement on every repository they connect to.

Next stepGains Audit
Fixed price, fixed scopeTwo weeks
One repository05

Fixed priceYour CI, your codeBook the audit

We connect the fleet to one repository for two weeks. You get a ranked list of gains in euros and the first pull requests, already open.