Case study · Growth
Unified commerce and growth system
Bloom’s site, ads and analytics told three different stories. We rebuilt the growth stack as a single system so creative, engineering and performance could operate on shared truth.
Bloom Retail10 min read
- Client
- Bloom Retail
- Industry
- Retail & ecommerce
- Category
- Growth
- Engagement
- Growth systems
- Duration
- 16 weeks
- Published
- Apr 1, 2026
One growth stack where creative, engineering and performance share definitions — and experiments become measurable.
Context
Bloom Retail was growing acquisition spend while the website, analytics and creative process drifted apart. Campaigns launched faster than landing pages could support. Tracking definitions differed by team. Leadership received three stories about the same week of performance.
The commercial cost was not only wasted media. It was slow learning. Experiments could not be compared cleanly, so the organization argued about dashboards instead of deciding what to ship next.
The challenge
Growth was being treated as a campaign function layered on top of a fragile web and measurement stack. Engineering optimized for releases. Marketing optimized for launches. Analytics tried to reconcile both after the fact.
We reframed the brief: build one commercial product where acquisition, site experience and measurement share ownership and definitions.
Approach
How we worked the problem
01
Unify definitions
We forced agreement on events, conversion states and channel ownership before spending another week on campaign tactics.
02
Treat the site as product
Landing pages, technical SEO and page performance entered the same backlog as acquisition — not a separate agency lane.
03
Instrument for decisions
Measurement was designed to answer commercial questions, not to produce more dashboards nobody trusted.
04
Run one rhythm
Creative, engineering and performance operated on a shared weekly cadence with shared experiment criteria.
Approach
We started with taxonomy. Events, funnels and channel ownership were agreed in writing before we rebuilt pages or media structure.
Technical SEO, landing-page engineering and performance marketing then entered one delivery rhythm. Attribution and experiment design were treated as product work with acceptance criteria — not as reporting chores.
The operating cadence mattered as much as the stack. Weekly reviews used shared KPIs. Backlog items had owners across marketing and engineering so “the site” and “the campaign” stopped being separate realities.
What we delivered
Bloom received a growth system: shared measurement, a site delivery path that could absorb campaign demand, and an experiment framework that made learning visible.
Creative briefs now referenced the same conversion states engineering instrumented. Performance teams could trust comparisons. Leadership stopped choosing between conflicting weekly reports.
Outcome
Marketing and engineering share one backlog. Experiments are measurable. Growth decisions are no longer based on competing dashboards.
The organization can still move quickly — but speed now compounds because the system remembers what worked and why.
Deliverables
- Shared event and conversion taxonomy
- Landing-page and SEO delivery system
- Performance measurement aligned to commercial KPIs
- Experiment framework across web and paid
- Technical performance baselines for key journeys
- Operating cadence for marketing and engineering
- Focus
- Growth stack
- Surface
- Web + paid
- Metric
- Shared KPIs
- Engagement
- 16 weeks
Related service: Digital marketing
