Why most relaunches lose revenue for a quarter
Redirect maps, template parity and crawl budget decide the first 90 days. Design decides the next 900.
A crystal is formed by pressure and time. A result is formed by sprints and audits. Everything below is the mechanism, the console and the proof.
Templates ship under a performance budget and report their own conversion.
Every template ships under 1.2 s LCP and reports its own conversion.
Rankings, content and crawl data in one foundation, refreshed before traffic slips.
Organic revenue reported against a quarterly hypothesis.
Native apps and internal tools on architecture built for retention and audit.
Retention and crash-free rate on the board report, not launch-day screenshots.
Four stages, one number per sprint. The sequence is fixed because the order is the control: nothing is built before the hypothesis is signed, and nothing continues before it is measured.
2 weeks
Analytics, search, codebase and funnel audit. We read the data you already have before we ask for new data.
Output: a ranked list of revenue hypotheses.
1 week
One hypothesis, one number, one sprint plan. The board signs the number, not a backlog.
Output: a signed sprint plan with the target figure.
2-week sprints
Shipped to production every sprint. Performance and quality gates run in CI, so nothing slow or broken reaches a customer.
Output: production releases, every sprint.
End of every sprint
The number is measured against the hypothesis in writing. Continue, pivot or stop is a decision, not a drift.
Output: continue, pivot or stop.
We stop work that does not move the number.
Most agencies bill for activity. We bill against a hypothesis, which means a stopped sprint is a result, and a continued one is earned.
Site performance, rankings and release health in one view. The team reads the same numbers the board reads, and every action in the log carries its reason.
Illustrative console, example figures.Every client gets one. It is where the audit is read.
Each figure is the single metric an engagement was scoped against, measured at the audit, not at launch.
Organic revenue in two quarters
+38%
Nordic retailer. Search programme across 412 refreshed pages, revenue attributed per cluster.
Median largest contentful paint across 38 templates
1.1s
Insurance comparison site. Field data, 75th percentile, after the image and font pipeline shipped.
Crash-free sessions after re-platforming
99.3%
Field logistics app, iOS and Android. 30-day window, measured in the stores' own tooling.
Checkout completion lift from one change
+11%
One-tap wallet on checkout step three. A/B tested over four weeks, design system untouched.
Example engagements, figures illustrative.
Three engagements written up to the number they were scoped against. Names are fictional.
Relaunch on a shared design system with a performance budget in CI. Checkout rebuilt as a web app on the same components.
1.1 s LCP, +24% conversion in the first quarter.
412 pages refreshed in priority order, crawl budget fixed first, every cluster attributed to revenue rather than sessions.
+38% organic revenue in two quarters.
Native iOS and Android for drivers and dispatch, offline first, with crash and retention gates on every release.
99.3% crash-free sessions, 4.7 store rating.
2 weeks, fixed fee
Scoped after a 30-minute call.
Ongoing 2-week sprints
Scoped after the audit.
Defined product, milestone billing
Scoped after the audit.
No prices on this page. A price before a diagnosis is a guess, and we do not sell guesses.
Short notes from engagements. Written for the person who has to defend the budget.
Redirect maps, template parity and crawl budget decide the first 90 days. Design decides the next 900.
One page, one number per channel, one agreed method. Everything else is an appendix.
Downloads and launch traffic measure the campaign. Retention at day 30 measures the product.
Two weeks, fixed fee, and a ranked list of the numbers worth moving. If nothing on the list is worth it, you will know that too.
Prefer email?hello@fancyfroggy.ai