The Rolling 90-Day Forecast: A Lighter-Weight Alternative to Annual Plans

You know the feeling. January rolls around, you sit down with a spreadsheet, and you try to predict what your freelance business will do for the next twelve months. By March, half those assumptions are wrong. By summer, you've stopped looking at it entirely.

Then October hits, you're scrambling to figure out if you're on track for your income goals, and you realize you have no idea what "on track" even means anymore.

This is why annual plans fail for solo programmers. The world moves too fast. Client projects change scope. New opportunities appear. Your rate goes up. A retainer ends unexpectedly. A twelve-month forecast can't breathe with reality.

There's a better way: the rolling 90-day forecast. Instead of locking yourself into a rigid annual plan, you plan the next quarter in detail, execute for three months, and then roll forward. Every ninety days, you're looking ahead with fresh data and real context. You're not guessing about next October; you're planning next October when you're actually in July and can see what's actually happening.

This is how agile teams ship products faster, how product managers stay responsive, and how solo developers can finally answer the two questions that matter: How much should I be making this quarter? and How's the business actually doing right now?

Why Annual Plans Die (And Why That's Not Your Fault)

Let's start with the obvious: annual planning is a relic of a slower era. It assumes your business environment stays relatively stable for twelve months. For a solo programmer, that assumption breaks down by week two.

Consider what actually changes in ninety days:

• A major client might reduce their retainer hours
• You land a new project that shifts your revenue mix entirely
• Your rates go up (or you realize they should)
• A tool you rely on doubles in price
• You get burned out and decide to work fewer hours
• A competitor undercuts your pricing
• You ship a new product that brings in unexpected passive revenue

None of these are rare events. They're the normal texture of running a freelance business. An annual plan that doesn't account for this fluidity isn't a plan—it's fiction.

There's also a psychological component. When you create an annual budget in January, you're operating on hope. You haven't shipped anything yet. You don't know if last year's assumptions still hold. By the time you're deep enough into the year to have real data, the plan is stale, and updating it feels like admitting you were wrong. So you ignore it instead.

A rolling 90-day forecast flips this. You're always planning from a position of real information. You just finished a quarter; you know what actually happened. You can see the next quarter clearly enough to make smart decisions. Anything beyond that is genuinely uncertain, so you don't pretend to know it.

What Is a Rolling 90-Day Forecast, Exactly?

A rolling 90-day forecast is a forward-looking financial plan that covers the next thirteen weeks, updated continuously as time passes. Here's how it works in practice:

The Structure:

You define your next quarter in detail: projected revenue from each client, known expenses, goals you're chasing, and risks you're watching. You execute against that plan for ninety days. At the end of the quarter, you look back at what actually happened, then roll forward and create a new 90-day forecast that includes the next quarter.

So if you're in Q1 (January–March), your rolling forecast covers January through March. In April, your rolling forecast covers April through June. In July, it covers July through September. You're always looking ninety days ahead, and you're always updating based on reality.

This is fundamentally different from an annual plan, which tries to predict all twelve months at once and then stays static. As research on agile planning practices from McKinsey shows, rolling quarterly forecasts allow organizations to adapt faster to market changes than fixed annual budgeting.

Why Ninety Days?

Ninety days is the sweet spot. It's long enough to plan meaningful work—you can't ship anything real in two weeks, and three-month cycles let you see patterns. But it's short enough that your assumptions probably won't be destroyed by reality. You can forecast client revenue with reasonable confidence. You can see which expenses are locked in. You can make decisions about hiring, tools, or new projects.

Anything longer than ninety days, and you're guessing. Anything shorter, and you're in reactive mode, never stepping back to plan.

The Core Components of Your Rolling Forecast

A useful rolling 90-day forecast isn't complicated, but it needs to answer specific questions. Let's walk through what goes into one.

Revenue Projections by Client

Start with the easiest part: money coming in. For each client, you need:

• Retainer revenue: If you have clients on retainers, you know roughly what they'll pay each month. (Or you should—if a retainer is unpredictable, that's a separate problem.)
• Project revenue: Any fixed-price projects you've already sold. If you've quoted a project at $15,000 and you're planning to deliver it in Q2, that's $15,000 in Q2 revenue.
• Likely-but-not-certain revenue: This is where it gets real. You have a prospect you're pretty confident will sign in the next month. You've had preliminary talks about scope. You're 70% sure it'll happen, and if it does, it's worth $8,000. Do you include it? Yes—but you label it as a forecast, not a locked-in number. Some forecasters use a confidence percentage; others use a separate column.
• Upside: What would happen if you landed that stretch project? If a client expanded their retainer? Keep this separate so you can see your conservative case vs. your optimistic case.

The key insight here is client concentration risk. If 80% of your revenue comes from one client, your forecast should highlight that. If that client cuts their retainer in half, your whole business changes. A rolling forecast makes this visible every quarter.

As discussed in rolling forecast best practices, emphasizing quarterly models over annual planning helps you catch concentration risk early rather than discovering it mid-year when it's too late to respond.

Expense Tracking and Projections

Now for the money going out. Break this into categories:

• Fixed monthly expenses: Rent, internet, software subscriptions, insurance. These are predictable.
• Variable expenses: Contractor costs, freelance help, hosting that scales with usage. These fluctuate with your workload.
• Quarterly or annual expenses: Tax payments, conference fees, equipment upgrades. These don't happen every month, but they'll hit in your ninety-day window.
• Discretionary spending: New tools you're considering, education, marketing. These are the first things you can cut if revenue dips.

The discipline here is being honest. Not "what would be ideal" but "what will I actually spend?" If you always upgrade your laptop in Q3, put it in the forecast. If you always hire a bookkeeper in Q4 to prep taxes, include it.

Revenue Goals and Targets

This is where the forecast becomes a planning tool, not just a prediction. What do you want to achieve this quarter?

• Revenue target: What's your MRR (monthly recurring revenue) target? If you want to hit $30,000 in quarterly revenue, and your current forecast shows $26,000, you have a $4,000 gap. Now you can ask: Do I need to land a new client? Raise my rates? Expand an existing retainer?
• Profitability target: After expenses, what do you want to keep? If you're forecasting $30,000 in revenue and $8,000 in expenses, you're left with $22,000. Is that enough? Do you need to cut costs or increase revenue?
• Growth target: How much do you want to grow compared to last quarter? If last quarter was $25,000 and this quarter is $30,000, that's 20% growth. Is that the pace you want?

These targets give you a north star. They're not rigid—you can adjust them—but they let you see if you're on track or if you need to take action.

Risk Flagging

The most valuable part of a rolling forecast is what it reveals about risks. As you build your forecast, ask:

• What if a client cuts their retainer? How much revenue would you lose? Can you absorb it?
• What if a project slips? If you're counting on $10,000 from a project in March but it slips to April, does your March forecast still work?
• What if you don't land that prospect? You're 70% confident about an $8,000 deal. What happens if it falls through?
• What if expenses spike? You're planning for $7,000 in hosting costs, but what if usage doubles?

A good rolling forecast doesn't just project the most likely scenario. It surfaces the risks so you can think about them. "If client X cuts their retainer, I drop below my target by $6,000. I should start prospecting now." That's a forecast working for you.

Building Your First Rolling Forecast

Let's make this concrete. Say you're a solo developer, and it's January 1st. Here's how you'd build your first rolling forecast for Q1.

Step 1: List Your Revenue

Retainer clients:

• Client A: $4,000/month (locked in for 6 more months)
• Client B: $2,500/month (up for renewal in April—likely to renew, but not 100% certain)
• Client C: $1,500/month (new retainer, just started)

Projects:

• Website redesign for Client D: $8,000 (scheduled to deliver in March)
• API integration for Client A: $3,000 (scheduled for February)

Prospects:

• Warm lead on a $12,000 project (60% confidence, would close in February)
• Exploratory conversation about a $6,000 retainer (40% confidence, would start in March)

Conservative Q1 Revenue:

• Retainers: $8,000/month × 3 months = $24,000
• Confirmed projects: $8,000 + $3,000 = $11,000
• Total: $35,000

With Upside:

• Conservative + 60% of warm lead ($12,000 × 0.6 = $7,200) + 40% of retainer opportunity ($6,000 × 0.4 × 3 months = $7,200)
• Total: $49,400

Now you have a range. Conservative case is $35,000. Optimistic case is $49,400. Reality will probably be somewhere in between.

Step 2: List Your Expenses

Monthly fixed costs:

• Laptop/equipment lease: $200
• Internet: $60
• Software subscriptions: $150
• Accounting software: $30
• Total: $440/month

Quarterly costs:

• Tax payment (estimated): $3,000
• Insurance renewal: $400
• Conference ticket (one in March): $800
• Total: $4,200

Variable costs:

• Contractor help (estimated): $1,500 for the quarter

Q1 Total Expenses: ($440 × 3) + $4,200 + $1,500 = $6,620

Step 3: Calculate Your Net and Compare to Goals

Conservative case:

• Revenue: $35,000
• Expenses: $6,620
• Net: $28,380

Optimistic case:

• Revenue: $49,400
• Expenses: $6,620
• Net: $42,780

Now ask: Is this on track for my goals? If your annual target is $120,000 in net revenue, you need $30,000/quarter on average. Your conservative case ($28,380) is slightly below that. Your optimistic case is well above it.

This tells you something important: You need to focus on closing that warm lead and the retainer opportunity. Those two deals get you from "below target" to "crushing it." That's actionable.

Step 4: Identify Risks

Looking at your forecast, what could go wrong?

• Client B's retainer is up for renewal in April, but it's in your Q1 forecast. If they don't renew, you lose $2,500/month starting in May. That's worth watching.
• The warm lead is only 60% confident. If it doesn't close, you drop $7,200 in revenue. That's a big swing.
• You're counting on landing that $6,000 retainer. If it doesn't happen, you lose $7,200 of upside.
• The website redesign is scheduled for March delivery. If it slips to April, your Q1 revenue drops by $8,000.

These aren't catastrophes, but they're worth flagging. You might decide to start prospecting for a backup project in case the warm lead falls through. Or you might reach out to Client B early to make sure they're planning to renew.

The Rolling Part: Executing and Updating

Building the forecast is one thing. Keeping it alive is another.

Here's what happens in practice:

January–March: Execute Against Your Plan

You've got your forecast. Now you work. You deliver projects, manage clients, handle invoicing. Every week or two, you update your forecast with new information:

• The warm lead closes in week 2? Update your revenue. You're now in the "optimistic" scenario.
• A client asks to delay a project? Shift the revenue to Q2.
• You realize you're spending more on contractors than expected? Increase your expense forecast.
• A new prospect appears? Add it with a confidence percentage.

The forecast isn't static. It's a living document that reflects reality as it unfolds.

End of March: Look Back and Roll Forward

At the end of Q1, you review:

• What actually happened? Did you hit your revenue target? Were expenses in line? Which assumptions were right, and which were wrong?
• What did you learn? If a client's retainer was higher than expected, that's valuable. If a project took longer than planned, that matters for future forecasts.
• What's locked in for Q2? You know which clients will renew. You know which projects are scheduled. You know which retainers are at risk.

Then you build your Q2 forecast using the same structure, but with better data. You've now got actual numbers from Q1 to inform your assumptions.

As research on 90-day rolling plans from Harvard Business Review demonstrates, this rolling approach keeps plans relevant because you're always updating based on actual performance, not stale assumptions.

Why Rolling Forecasts Beat Annual Plans for Solo Developers

Let's be direct about the advantages:

You Stay Responsive to Reality

An annual plan assumes the world stays stable. A rolling forecast assumes it changes. When your biggest client cuts their retainer, you find out in your quarterly review and can adjust. You're not stuck with a plan that's already broken.

You Catch Problems Early

If your Q2 forecast shows you're going to miss your revenue target, you know that in March, not in September. You have three months to fix it: land a new client, raise your rates, cut expenses, or adjust your goals. That's real time to act.

You Can Actually Forecast Accurately

Forecasting three months out is hard but possible. Forecasting twelve months out is guessing. A rolling forecast focuses on what you can reasonably predict, which means your forecasts are actually useful instead of laughably wrong.

You Avoid the Planning Trap

Many solo developers skip planning entirely because annual plans feel pointless. A rolling forecast is lightweight enough to maintain but structured enough to be useful. You're not spending hours on a spreadsheet that dies in February. You're spending an hour every quarter updating something that actually guides decisions.

You Can See Patterns

After a few rolling forecasts, you start seeing patterns. Maybe Q4 is always higher revenue because clients budget before year-end. Maybe you always underestimate contractor costs. Maybe certain types of projects are more profitable than others. That pattern recognition makes future forecasts better.

Making Rolling Forecasts Part of Your Routine

The hardest part of a rolling forecast isn't building it once. It's keeping it alive. Here's how to make it stick:

Schedule a Quarterly Review

Every ninety days, block off two hours. Look at your actual results, compare them to your forecast, and build the next quarter's plan. Put it on your calendar now. Treat it like a client meeting—non-negotiable.

Keep It Simple

Your first rolling forecast should be a spreadsheet with five columns: client name, revenue type, amount, confidence, and notes. That's it. Don't build an elaborate financial model. The goal is a tool you'll actually use, not a masterpiece that intimidates you.

Update It Monthly

Don't wait until the end of the quarter to update your forecast. Spend fifteen minutes every month reviewing what actually happened and adjusting your projections. This keeps the forecast honest and catches surprises early.

Share It With Someone

If you have an accountability partner, a mentor, or a fellow freelancer, share your rolling forecast with them. "Here's what I'm planning for Q3. Here's where I'm at risk." External eyes catch blind spots. Plus, saying your goals out loud makes them more real.

Use Tools That Support Rolling Forecasts

You can build a rolling forecast in a spreadsheet, but purpose-built tools make it easier. Platforms designed for revenue planning and forecasting—like Cashierr, which uses AI agents to track goals and flag gaps—can automate the tracking, update your projections as invoices come in, and highlight risks without you having to manually update a sheet every week.

The right tool turns a quarterly ritual into something that stays current with minimal effort. As product teams have discovered, using rolling 90-day approaches with proper tooling helps teams ship faster and stay aligned.

Common Mistakes (And How to Avoid Them)

Mistake 1: Being Too Optimistic

When you're building your first forecast, it's tempting to assume everything goes perfectly. All prospects close. No projects slip. No clients cut retainers. Reality is messier.

Fix: Build a conservative case, a likely case, and an optimistic case. Use the likely case for planning. Use the conservative case to stress-test your business.

Mistake 2: Treating the Forecast Like a Prediction

A forecast isn't a prediction. It's a plan. It's what you're aiming for, informed by your best guess about the future. It will be wrong. That's fine. The point is to have a plan you can adjust, not a prophecy.

Fix: Review your forecast monthly. Update it as reality changes. Use it to guide decisions, not to judge yourself.

Mistake 3: Ignoring the Risks

You build a forecast, everything looks good, and you stop thinking about it. Then a client cuts their retainer, and you're blindsided.

Fix: Every time you build a forecast, explicitly list the top three risks and what you'd do if they happened. "If Client A cuts their retainer, I'll have $4,000 less revenue. I'd cut discretionary spending and focus on landing a new prospect."

Mistake 4: Forecasting Too Far Ahead

Some solo developers try to forecast six months or a year ahead. The further out you go, the less accurate you are. You're just making up numbers.

Fix: Stick to ninety days. Anything beyond that is genuinely uncertain. You can have rough thoughts about it, but don't pretend to forecast it.

Mistake 5: Never Looking Back

You build a forecast, execute for three months, then immediately build the next one without reviewing what actually happened.

Fix: Always spend time comparing your forecast to reality. What did you get right? What surprised you? Use that to improve your next forecast.

Rolling Forecasts in Action: A Real Example

Let's follow a solo developer through a year of rolling forecasts to see how this actually works.

Q1 (January–March):

Sarah builds her first rolling forecast. She has three retainer clients ($8,000/month), one confirmed project ($5,000), and a prospect she's 50% confident about ($10,000). Conservative forecast: $29,000. Optimistic: $34,000. She's targeting $30,000, so she's close but not quite there. She decides to focus on closing that prospect.

By March, the prospect falls through (happens), but a retainer client adds 10 more hours per month. She ends up at $31,000 in revenue—slightly above her target. Her actual expenses are $6,200, slightly less than forecasted. Net: $24,800.

Q2 (April–June):

Sarah builds her Q2 forecast with real Q1 data. She knows her retainers are more stable than she thought. She has two new projects queued up ($8,000 total). One retainer is up for renewal, and she's 80% confident it will renew (up from 70% last quarter—she's had good conversations). Conservative: $32,000. Optimistic: $37,000. Target: $32,000.

She focuses on closing that renewal and delivering the projects well so clients ask for more work. By June, the retainer renews, both projects deliver on time, and a client asks her to scope a larger engagement. Actual revenue: $34,500. Expenses: $6,800. Net: $27,700.

Q3 (July–September):

Sarah's now in a rhythm. Her Q3 forecast is built on solid data. She has four retainers ($10,500/month), a confirmed project ($12,000), and that larger engagement she's scoping (70% confident, $15,000). Conservative: $33,500. Optimistic: $40,500. Target: $35,000.

She's also noticed that Q3 is usually slower (summer vacations, budget freezes), so she's being cautious. She lands the larger engagement in August. By September, actual revenue is $39,200. Expenses are $7,100 (she hired a contractor to help). Net: $32,100.

Q4 (October–December):

Sarah's now confident in her forecasting. She knows her retainers are solid. She knows projects take longer than she estimates. She knows Q4 is strong. Her forecast: $40,000 conservative, $50,000 optimistic. She's targeting $40,000 to hit her annual goal of $120,000.

She lands a new retainer in October (not forecasted—upside). By December, actual revenue is $48,000. Expenses are $7,500 (year-end tax payment, plus contractor help). Net: $40,500.

The Year:

Sarah's total net revenue for the year: $125,100. Her original annual target: $120,000. She beat it by $5,100—not because she nailed every forecast, but because she stayed responsive to reality and adjusted quarterly.

More importantly, she knows exactly how her business is doing at any point. She's not surprised by numbers. She's caught problems early. She's made decisions based on data, not hope.

That's what a rolling forecast does.

Building Your Rolling Forecast System

If you're ready to start, here's a simple framework:

The Spreadsheet Version

Create a sheet with these columns:

• Client/Project Name
• Revenue Type (retainer, project, prospect)
• Monthly Amount (for retainers) or Total Amount (for projects)
• Confidence % (100% for locked-in, lower for prospects)
• Month (Jan, Feb, Mar, etc.)
• Notes

Add a summary section that calculates:

• Total Conservative Revenue (locked-in items only)
• Total Likely Revenue (conservative + 75% of prospects)
• Total Optimistic Revenue (conservative + 100% of prospects)
• Total Expenses
• Net for Each Scenario
• Gap to Goal (target minus likely revenue)

Update it monthly. Review it quarterly. Done.

The Tool Version

If spreadsheets feel tedious, consider a platform built for this. Cashierr is designed specifically for solo developers and small agencies. It tracks your revenue by client, projects your quarterly numbers, flags risks (like client concentration), and uses AI agents to monitor your business health. Instead of manually updating a spreadsheet, your actual invoices and expenses feed the forecast automatically. It answers the two questions every solo developer worries about: "How much should I make this quarter?" and "How's the business actually doing?"

The tool handles the math and the updates. You focus on the decisions.

The Mindset Shift

Moving from annual plans to rolling forecasts is as much a mindset shift as a practical one.

Annual planning assumes you can predict the future. Rolling forecasting assumes you can't—but you can plan for the next ninety days and adjust as you learn.

Annual planning is about locking in a number and hitting it. Rolling forecasting is about setting a direction, executing, learning, and adjusting.

Annual planning feels serious and official. Rolling forecasting feels flexible and adaptive. For solo developers, that flexibility is a feature, not a bug. Your business changes. Your forecast should too.

As research on agile organizations highlights, companies that embrace rolling planning cycles adapt faster to market changes and make better decisions than those locked into annual cycles.

Starting Today

You don't need to be perfect. You don't need elaborate financial models. You just need to answer three questions for the next ninety days:

1. How much revenue am I forecasting? (Conservative, likely, optimistic)
2. How much will I spend? (Fixed, variable, one-time)
3. Where am I at risk? (Client concentration, project delays, prospect dependency)

Take an hour this week. Build your first rolling forecast. Put your next quarterly review on your calendar. Update it monthly.

That's enough to get started. The rest is just staying curious about what actually happens and adjusting your plan accordingly.

Rolling forecasts won't make your business perfect. But they'll make it less surprising. And for a solo developer juggling clients, projects, and the constant question of "how much should I actually be making?", that's worth a lot.