Monthly Growth Optimisation

The situation

A website is sharpest on the day it launches and drifts from there. Copy goes stale, a page that used to convert quietly stops, a competitor changes their offer and nobody on your side notices for months. Nothing breaks in a way that trips an alarm; the business just slowly performs a little worse than it did on day one.

Most businesses have already paid for a diagnosis of this. A consultant or an agency delivered a list of recommendations, and the list is still sitting in an inbox because nobody had the hours to build any of it. Advice without a hand attached to build it becomes a report, not a result.

What changes

Every month, the site gets reviewed against real numbers, three to five specific changes get proposed, and the ones you approve get built and measured. None of it depends on a single big swing landing perfectly; the value comes from the string of smaller ones that keep landing. Nothing waits for a big relaunch that might never get scheduled; the next change ships as soon as it is approved, whether that takes a week or a month.

Compounding works in a growth programme the way it works in a bank account: small, repeated gains outrun one large leap that never comes again.

Six months in, the site is not the one that launched. Every change is dated, every result is recorded, and a leader can trace exactly which decision moved which number, with the evidence sitting in the data itself.

How it runs

1. 01

   Review all sources against last month

2. 02

   Propose three to five changes with expected effect

3. 03

   Ship approved changes and set up experiments

4. 04

   Report what moved and what did not

The review comes first every month, run against the full data set rather than a sample, so a recommendation is grounded in what actually happened last month and a hunch about what usually works never gets the final say.

Approved changes ship the same month, each one set up as a measurable experiment rather than a change made on faith. What moved and what did not both get written into the report, so a change that failed to help is recorded as clearly as one that worked. The same experiment framework applies whether the change is a headline rewrite or a full page redesign, so results stay comparable month over month.

What you receive

The changes themselves, shipped and live rather than sitting in a backlog, each one tied to the number it was meant to move. Every experiment's result is recorded, win, loss or inconclusive, so the record of what was tried is as complete as the record of what worked.

And the report itself: one page, written for a leader who has two minutes, showing what shipped, what moved, and what is queued for next month. Read across a year, the reports become a written history of how the site actually improved, one decision at a time, with nobody having to remember what happened last quarter from memory alone.