In partnership with

Hiring in 8 countries shouldn't require 8 different processes

This guide from Deel breaks down how to build one global hiring system. You’ll learn about assessment frameworks that scale, how to do headcount planning across regions, and even intake processes that work everywhere. As HR pros know, hiring in one country is hard enough. So let this free global hiring guide give you the tools you need to avoid global hiring headaches.

The most dangerous document in any small business is the annual plan.

I say this with love because I used to be obsessed with them. Every December I would block out two or three days, set up a whiteboard, and build a beautiful 12-month plan. Goals by quarter. Key initiatives. Revenue targets by product line. Hiring milestones. The whole thing was a masterwork of strategic intent.

And by April, most of it was already irrelevant. The market had shifted. A big client had churned. An unexpected opportunity had appeared. Priorities I had set in December no longer mapped to the reality I was living in four months later. By July, the plan was collecting dust. By October, I had quietly abandoned it and was operating on instinct again.

This is not a personal failure. This is what happens to annual plans in small, service-based businesses. The planning horizon is too long, the environment is too dynamic, and the feedback loop is too slow to correct course before you have wasted a quarter or two chasing something that no longer matters.

What actually works is a 90-day operating rhythm. Short enough that you can hold the whole thing in your head. Long enough to produce meaningful results. Tight enough to force real prioritization. And when it ends, you reset. You do not extend. You start over, armed with what you learned, and you build the next 90 days from scratch.

Why Ninety Days Is The Magic Number

Ninety days has three properties that make it uniquely powerful as a planning unit.

First, it is long enough to produce a meaningful outcome. Almost nothing useful happens in 30 days. You can launch something small. You can run an experiment. But building a new offer, hiring and onboarding a team member, or meaningfully improving a business process generally takes longer than a month. Ninety days gives you room for the work to actually land.

Second, it is short enough to stay focused. Twelve months is an abstraction. Your brain cannot meaningfully track that far out in a small business. Ninety days is concrete. You can see the finish line from the start. You can feel the pressure of the calendar. You know if you are on track or behind by about week six, which leaves you enough time to adjust.

Third, it forces prioritization. You cannot do 15 major initiatives in 90 days. You cannot even do five well. If you are honest with yourself, you can do two, maybe three major things in a quarter if the team is small. That constraint is a feature, not a bug. It forces you to name the things that actually matter and ignore everything else.

The Structure Of A Growth Sprint

Every 90-day sprint I run in my own business follows the same structure. There are three major sections and a handful of recurring rhythms.

Section one is the outcome. One sentence that defines what is different about the business at the end of 90 days compared to the start. This is not a goal with metrics attached. It is a state description. By June 30, we have a self-sustaining referral pipeline producing at least two qualified leads per week without any outbound effort. That is an outcome. It is specific, observable, and either achieved or not.

Section two is the set of initiatives. Two or three concrete projects that, if executed, will produce the outcome. Each initiative has a named owner, a defined scope, a weekly check-in cadence, and a completion definition. If an initiative cannot be fully described in three sentences, it is probably actually two initiatives and needs to be split.

Section three is the metrics. Not dozens. Two or three leading indicators that tell you whether the initiatives are working. Leading indicators, not lagging ones. Not revenue, which is a lagging indicator. Something more upstream like calls booked, or proposals sent, or activations completed. If the leading indicator is moving, the lagging one will follow. If the leading indicator is flat, no amount of hoping will change the outcome.

The Weekly Rhythm That Powers The Sprint

A sprint plan is worthless without a weekly operating rhythm to enforce it. I run a single weekly meeting, Monday morning, 45 minutes maximum, with three sections.

Section one is the leading indicator review. We look at the two or three metrics we committed to at the start of the sprint and ask: are they moving in the right direction. Yes means we stay the course. No means we dig into why. We do not slot in new initiatives. We fix the existing ones.

Section two is the initiative update. Each owner gives a 90-second update on their initiative. Not a narrative. Not a story. What did you complete last week. What are you completing this week. What is in your way. If something is stuck, we surface it and assign the clear next action. No lengthy problem-solving in the meeting itself.

Section three is the reset question. Given what we learned this week, does the sprint plan still make sense. Most weeks the answer is yes and we move on. Occasionally the answer is no, and we adjust. The important thing is we ask the question every week, so that when the answer is no, we catch it early rather than stumbling forward for another month before noticing.

The Mid-Sprint Checkpoint

At the 45-day mark of every sprint, I do a focused checkpoint review. Not a meeting. A document. I sit with the sprint plan and ask four questions.

One. Are the leading indicators actually leading to the outcome. Sometimes you set a metric at the start of the sprint that sounded right and, 45 days in, it turns out it is not actually correlated with the outcome you want. Better to catch that at day 45 than day 90.

Two. Are the initiatives still the right initiatives. The world has moved. New information has surfaced. Sometimes the thing you started building in week two is genuinely no longer the highest priority by week six. It is okay to kill initiatives mid-sprint. It is not okay to finish them out of stubbornness when they no longer serve the outcome.

Three. Is the team capacity still matching the plan. Did someone leave. Did an unexpected opportunity eat 20 percent of someone’s week. Is the scope of an initiative bigger than it looked at the start. Adjust scope, not timeline.

Four. What have we learned that the next sprint needs to know. Start building the list now, while it is fresh, rather than trying to reconstruct it at day 90 when the next planning session begins.

The Close-Out Ritual

The last week of the sprint is not for finishing. It is for closing out. I separate these on purpose. If you use the last week of the sprint to scramble toward completion, you will never have the space to actually look at what happened.

The close-out ritual has three parts.

First, the outcome check. Did we produce the state we said we would produce. Not a partial credit exercise. Yes or no. If no, why not. If yes, what produced the success and how do we institutionalize it.

Second, the retrospective. What worked. What did not. What would we do differently. This is a team exercise if you have a team, a solo one if you do not. Written down. Not a meeting that ends with nothing recorded.

Third, the clean slate. The next sprint is designed from scratch based on what we know now, not as an extension of the previous one. This is the discipline that keeps 90-day sprints from becoming rolling 12-month plans with different colored paint.

Tools That Keep The Sprint Running

The administrative overhead of running a sprint well is not trivial. You are tracking initiatives, metrics, weekly check-ins, and a mid-sprint review. Without a system, it turns into another thing on your plate that gets crowded out. I run the entire sprint on a single dashboard built inside Go High Level with the leading indicators pulled automatically from the CRM. I can see at a glance whether the sprint is on track without opening five different tools.

For the initiatives themselves, which often involve workflows that span multiple tools, I use Make.com to connect the pieces. An initiative like launching a new referral program might involve a form on the website, a CRM update, an email sequence, and a Slack notification. Make stitches it all together so the whole initiative runs without me babysitting it.

The weekly meeting itself gets recorded and transcribed by Fathom which means I can scan the transcript later if I forgot what someone committed to, and the action items feed automatically into the sprint dashboard. No one takes notes. Everyone is actually present in the meeting instead of typing.

For my own focus time during the sprint, Rize tracks where my hours are actually going. At the end of each week I can see whether I spent my time on the sprint initiatives I committed to, or whether it drifted into everything else. The data does not lie. And it is uncomfortable in a useful way.

The Mistake Most Operators Make

The most common failure mode with 90-day sprints is trying to fit a 12-month plan into a 90-day container. You cannot. And if you try, you will end up with a sprint that is technically planned but practically meaningless because it has so many initiatives nothing actually moves.

The discipline of the sprint is in what you cut. Two or three initiatives means two or three initiatives. Not two or three plus a little side project. Not two or three plus some other stuff that came up. The whole point is that the constraint forces you to decide what matters most this quarter, and everything else waits.

This is uncomfortable. There will always be something that feels urgent and important that did not make the sprint. That is exactly the feeling you should want. If nothing feels left out, your sprint is not focused enough. Say no to enough things that you feel the discomfort, then hold the line for 90 days, and you will be astonished at what actually gets done.

What Compounds Over Multiple Sprints

The magic of 90-day sprints is not in any individual sprint. It is in what compounds over four of them in a row.

A single sprint produces one meaningful outcome. Four sprints produce four meaningful outcomes, plus a business that has gotten dramatically better at running the sprint process itself. The second sprint is better than the first because you have learned how to scope initiatives realistically. The third is better because you have learned how to pick leading indicators that actually lead. The fourth is better because the team has internalized the rhythm.

A year of 90-day sprints will produce more real progress than three years of annual planning, because the feedback loops are tight, the prioritization is forced, and the learning compounds sprint over sprint. This is the operating rhythm that separates service businesses that grow predictably from the ones that rely on heroic bursts of effort followed by long, quiet stretches of wondering what happened to the plan.

How To Choose The Sprint Outcome

Choosing the right sprint outcome is where most operators either win or lose the whole quarter. Pick the wrong outcome and the 90 days can be perfectly executed and still not move your business forward. Pick the right one and even a sloppy sprint produces real progress.

The filter I use is the compounding question. Of the things that could be true at the end of 90 days, which one would produce the most downstream leverage for everything that comes after. Not which one has the biggest dollar impact in the next quarter. Which one would make the next two quarters dramatically easier.

Last year, I had a sprint where I had to choose between two outcomes. One was launching a new service tier that projected to add 30,000 dollars of monthly recurring revenue. The other was rebuilding our client onboarding system so it ran without my involvement. The revenue one was sexier. The onboarding one had bigger downstream leverage, because once I was out of the onboarding loop, I could double client capacity without doubling my hours. I picked onboarding. Three quarters later, the service tier got launched easily because the operational capacity to deliver it was already in place. The reverse order would have buried me.

Compounding outcomes are almost always operational before they are strategic. Systems before offers. Infrastructure before expansion. The temptation is always to chase the revenue gain directly, and sometimes that is the right call. But if you keep asking the compounding question, you will consistently end up investing 90 days in the things that make every future 90 days more productive.

When A Sprint Should Be Killed

Not every sprint should run to completion. This is a hard truth that sprint evangelists rarely talk about.

If the mid-sprint checkpoint reveals that the outcome you set is no longer the right outcome, you should kill the sprint. Not pause it. Not modify it. Kill it, write down what you learned, and start a new sprint with a new outcome. The calendar time is already spent. The question is whether the remaining 45 days go toward a misaligned outcome or a corrected one.

The reasons to kill a sprint are specific. The market has shifted in a way that invalidates the original assumption. A bigger opportunity has surfaced that would be a mistake to ignore. The work revealed that the outcome you set was built on a bad premise. A team member departure has gutted the capacity needed to finish. Any of these is a legitimate reason to stop.

The reasons that are not legitimate are just as specific. The work is harder than expected. You are not making progress fast enough. You lost motivation halfway through. Those are reasons to push through, not reasons to kill. Distinguishing between the two requires brutal honesty, which is why the mid-sprint checkpoint document matters. Written analysis is harder to bullshit than spoken analysis.

Want the shortcut?

If you want the complete 90 Day Growth Sprint template, including the planning doc, weekly meeting agenda, and checkpoint review worksheet, Just reply to this email with the word SPRINT and I will send it straight to your inbox.

Talk Soon,

Dan

Dan Kaufman, Founder, Dead Simple Growth and Pinnacle Masters

83 Ways to Stay in Control

When margins tighten, every move matters.

BELAY’s Small Business Survival Guide gives you 83 practical ways to cut costs, improve cash flow, and keep operations running smoothly without overextending your team.

Keep Reading