Cool-downs when the client is paying

In the book, the cool-down is a stretch of about two weeks between cycles. Nobody is assigned to a project. People fix bugs, try ideas and follow up on whatever the last cycle left behind. The betting table meets during it.

For a client paying by the week, two weeks of “nothing” looks like waste. The answer is to be specific about what the time is for and who benefits.

What the time is for

Four jobs come out of a cool-down.

• Clean-up. The bugs and loose ends from the last bet, fixed without needing a new pitch.
• Shaping. Work on pitches for the next betting table, so the next cycle starts with a shaped problem and not a conversation.
• Handover. Documentation, training and the things the client needs to run what you built.
• Rest and recovery. A team that has worked six weeks at full tilt makes better bets afterward.

AngelHack DevLabs, in its write-up, lists cool-down weeks as the time for bug fixes, maintenance and preparing the next pitch. That matches the first two jobs.

Three ways to bill for it

The right answer depends on your contract. These are the options to weigh.

1. Price it into the cycle. Quote the cycle and cool-down as one block. The client sees a single figure and a single calendar, and nothing looks unbilled.
2. Bill clean-up and shaping separately. The cool-down becomes a short paid engagement: fixing what shipped and writing the next pitch. The client pays for something concrete, and can end the relationship at the end of it.
3. Treat it as the agency’s time. You absorb it as the cost of running a healthier team. This works if your margins allow it and it can make you look more reliable than shops that bill for every week.

Whichever you pick, put it on the calendar from the first day. A client who sees the cool-down in the original plan will treat it as part of the process. A client who discovers it in week seven will treat it as a delay.

Keeping it short when the client is impatient

The book describes two weeks, but nothing says a cool-down must be that long for every team. A small team on short cycles can run a week. What matters is that each cool-down has a list: the bugs to fix, the pitches to write, the handover to finish. If there is no list, shorten it.

The client’s part in it

Cool-down is where the client can be most useful. They can review pitches for the next cycle, test what shipped and raise the issues they spotted. Ask them to bring a list of problems, not features, and use it to shape the next bets.

Do not let cool-down become a place where the previous cycle’s scope quietly resumes. The circuit breaker only works if the end of a cycle is a real end.

Questions people ask

Do you bill clients for the cool-down?

It depends on the contract. Options include pricing it into the cycle, using it for client-specific bug fixes and shaping the next bet, or treating it as the agency’s own time. Whichever you pick, say so before the first cycle.

How long should a cool-down be?

The book describes two weeks. You can shorten it for small cycles. It should exist and have a purpose.