How does growth-driven design contribute to faster ROI?

Return on investment compares what a project gained with what it cost over a set period. Payback is a different measure. The Corporate Finance Institute's explanation of payback period defines it as the time a project takes to recover its initial cost from the cash it produces, and it separates that from how profitable the project is. Simple payback ignores everything earned after the recovery point. It also ignores risk and the fact that money received later is worth less.

So two projects can trade places depending on which question you ask. One recovers its cost sooner, and the other earns more over three years. The question here is about speed, so this answer looks mainly at payback.

The method's first release is called a launchpad. The method describes the launchpad as a foundation for collecting user data and improving, and not as the finished product. It sets a goal of 60 to 90 days, shows examples that took between 40 and 120, and says speed shouldn't come at the cost of value to the user. Lean Labs' growth-driven design program has the same shape: a strategy phase of 10 to 14 days, a launchpad in 60 to 90 days, then improvement sprints of 30 days.

The benefit of a new site starts when buyers begin using it. If the launchpad performs better than the current site on the pages buyers use, each month it's live ahead of a larger build is a month of added benefit. If it goes live quickly and performs no better than the old site, the earlier date adds no contribution. We cover what belongs in that first release in what a launchpad website is.

After launch, the work continues in cycles. Lean Labs describes choosing changes from page behavior, form results, CRM lifecycle data and sales feedback. It ranks them by expected pipeline impact, by buyer relevance and confidence, and by effort.

Ranking decides what each sprint works on first, and some of the chosen changes won't produce a gain. That work is paid for all the same, and its cost belongs in the calculation with the changes that worked.

A new lead, a closed deal and money received are three different dates. Payback is counted in cash, so in a business with a long sales cycle it can trail the improvement on the page by months.

Suppose a B2B company compares three ways to replace its site. Every number here is assumed. "Contribution" means the revenue from added customers minus the cost of serving them, measured against what the old site would have produced. To keep the arithmetic simple, assume the contribution arrives as cash in the month shown and each fee is paid in the month it's incurred.

The first path is a single release. It costs $60,000 over six months, goes live at the start of month 7 and adds $10,000 a month in contribution. We've assumed it has the largest initial lift of the three. A fuller site isn't certain to perform better.

The second path is a launchpad with no further work. It costs $30,000 over three months, goes live at the start of month 4 and adds $6,000 a month.

The third path is the same launchpad followed by improvement work at $4,000 a month from month 4 through month 12. Assume each month of that work raises monthly contribution by $1,000 from the following month, as an average across the changes that worked and the ones that didn't. Real fees vary, and we cover them in how much growth-driven design costs.

Under these inputs, both launchpad paths recover their spending before the single release does. Their benefit started three months earlier, on half the initial outlay.

The improvement work moved recovery from the end of month 8 to the end of month 10, because each month added a fee before it added a gain. Through month 12 it brought in what it cost: $36,000 in fees and $36,000 in added contribution. In month 12 that site contributes $14,000. The launchpad alone contributes $6,000, and the single release contributes $10,000. Whether that gap holds in the second year is one more assumption, and the example doesn't test it.

Launching earlier and continuing to pay for improvement are separate decisions, and the second has its own costs and gains. The gain from a single cycle is hard to isolate, because other things change in the same month. We'd judge the improvement work across several cycles against what those cycles cost.

Change one input and the order changes. Suppose the improvement work adds nothing and continues at the same fee. The site contributes $6,000 a month against a $4,000 fee. That leaves $2,000 a month toward the $30,000 launchpad, and recovery moves to the end of month 18. The single release got there six months sooner.

Lean Labs' account of its redesign for Integrate says the rate at which visits became contacts rose 271% within 60 days of launch. That's the agency's own report of a change in one conversion rate over a stated window.

To compute a return from it, you'd need what the project cost, how many of those contacts became customers and what those customers contributed. You'd also need what the old site would have done in the same 60 days. The account doesn't supply those figures. We look at what such cases can teach in growth-driven design case studies.

The calculation is easier when the measuring is set up before the work starts. Record how the current site performs on the number you care about, using the approach in what metrics to track in growth-driven design. Agree with finance on what a new customer contributes after delivery costs, and on when that money is received. Count every fee, including the fees for work that produced nothing.

Those records give you spending and results by month. They don't show what the old site would have produced without the project. So the payback date you calculate is an estimate that rests on your baseline, and the baseline should be stated beside the date when you report it.