Skip to main content
Case studies
Reef & RangeApparel · AU + NZ
213%new-customer acquisition lift

Reef & Range wanted growth that didn't come at the cost of margin. Self-calibrating thresholds anchored to their own data — not someone else's playbook — drove new-customer acquisition 213% above plan.

// the deltas

NCA vs. plan

+213%
Q1

Negative terms written

1,940
auto

Winner floor

self-set
per-store

Wasted-spend terms

-38%
QoQ

Growth rules that weren't theirs

Reef & Range had been running on inherited rules of thumb — a fixed ROAS floor, a generic negative-keyword list, a scaling cadence copied from a course. The rules were someone else's distribution, applied to a very different business.

The result was predictable: winners scaled too slowly and waste accumulated in the long tail of search terms no one had time to prune.

Self-calibrating, channel-aware

The Campaign Specialist built a winner floor from Reef's own contribution-margin and new-customer distribution, then ran an anomaly responder across Google and Meta. It writes NEGATIVE_TERMS on wasteful queries, scales winners that clear the floor, and pauses losers — all under per-action rate limits.

Because the floor is theirs, the system scales acquisition campaigns that an inherited 2.0 rule would have starved.

Triple-digit acquisition, less waste

First quarter on the new floors, new-customer acquisition came in 213% above plan, while wasted-spend search terms dropped 38% quarter over quarter. The growth and the discipline came from the same source: thresholds that describe Reef's store, not the internet's.

We stopped importing someone else's ROAS rule and let the system find ours. The anomaly responder writes negative terms while we sleep. First quarter, new-customer acquisition came in 213% over plan.
Priya Nadar
Growth Lead · Reef & Range

// your story next

See your own case study in 90 days.

The fastest path to a numbers-driven story is to connect a read-only token. We'll show you exactly what the agents would have done over your last 30 days — before anything writes.

Dry-run by default · Append-only logs · One-click rollback