A practical one-page business plan template for solo developers. Track revenue goals, client mix, and quarterly forecasts without the spreadsheet chaos.
You didn't become a programmer to write business plans. You became a programmer to build things, solve problems, and ideally get paid well for it. Yet somewhere between landing your first client and juggling three retainers, you realized you have no idea if you're actually on track.
That's the gap a one-page business plan fills.
Most business planning advice assumes you're running a traditional company with a board, a five-year roadmap, and quarterly earnings calls. That's not you. You're a solo developer—maybe you have a couple of contractors, maybe you work alone. You need to know two things: How much should I be making this quarter? and How's the business actually doing right now? Everything else is noise.
A proper one-page plan answers both questions without turning into a binder of spreadsheets. It's a living document you'll actually look at, update monthly, and use to catch problems before they become crises. Think of it less as a business plan and more as a revenue and health dashboard that fits on a single page.
The solo developers who thrive aren't the ones with the most clients or the biggest retainers. They're the ones who know their numbers, understand their revenue concentration risk, and adjust course before the quarter falls apart. This guide walks you through building that plan—and the tools that make maintaining it painless.
Before you write anything down, you need clarity on what actually matters. Strip away the business jargon and focus on what keeps you up at night.
Question One: How Much Should I Make This Quarter?
This isn't about greed or ambition. It's about survival and intentionality. Your quarterly revenue target is the number that tells you whether you're on pace to hit your annual income goal, whether you need to raise rates, and whether you should be hunting new clients or focused on delivery.
Most solo developers wing this. They take whatever work comes in, hope it adds up to enough, and panic in November when they realize they're short. A one-page plan forces you to decide upfront: What's the minimum I need to earn per quarter to hit my annual target? Then you work backward from there.
Let's say your annual income goal is $120,000. That's $30,000 per quarter. Now you have a number to chase instead of a vague hope. You can look at your current client roster and ask: Will these clients generate $30k this quarter? If not, you know you need to either land new clients, increase rates, or adjust your goal.
Question Two: How's the Business Actually Doing Right Now?
This is the health check. It's not just about revenue—it's about whether your revenue is stable or fragile. A solo developer with three clients generating $10k each looks healthier than one with a single client generating $30k, even though they're bringing in the same money. The first one loses 33% of revenue if one client leaves. The second one loses 100%.
Your one-page plan needs to show:
Question Three: What's the Gap Between Where I Am and Where I Want to Be?
This is where the plan becomes actionable. You have a quarterly target. You have a current revenue projection. The gap between them is your work for the next 90 days.
If your target is $30k and your current clients are projected to deliver $18k, you have a $12k gap. That gap tells you exactly how much new revenue you need to land—or how much you need to upsell existing clients—to hit your number. It's concrete. It's measurable. It's not "I should probably find more clients sometime."
Without this clarity, you're flying blind. With it, you have a plan.
Let's build this thing. A one-page plan for a solo developer has five core sections, each designed to be scanned quickly but contain enough detail to actually guide decisions.
Start at the top with your numbers. This is the anchor for everything else.
Format it like this:
Annual Income Goal: $[your target] Quarterly Target: $[annual goal ÷ 4] Current Quarter: Q[X] 20XX
That's it. Two numbers that frame everything below. If your annual goal is $150,000, your quarterly target is $37,500. If you're in Q2, you know you need to generate $37,500 between April and June to stay on pace.
Why start here? Because every decision that follows—whether to take a new client, whether to raise rates, whether to focus on delivery or sales—flows from this number. It's your north star.
Many solo developers have never written their annual income goal down. They have a vague sense of "I should make more" but no actual target. Writing it forces you to be honest about what you actually need and want to earn. That clarity is the foundation of everything else.
Now list your active clients and their projected contribution to this quarter. This is where you move from abstract targets to concrete reality.
For each client, you need:
| Client | Monthly Retainer | Projects | Q2 Total | % of Target | |--------|-----------------|----------|----------|-------------| | Acme Corp | $8,000 | $2,000 | $26,000 | 69% | | Startup XYZ | $3,500 | $0 | $10,500 | 28% | | Freelance Project | $0 | $1,500 | $1,500 | 4% | | Total Projected | — | — | $38,000 | 101% |
This table tells you everything:
Without this breakdown, you're guessing.
This is the health check. It directly answers How fragile is my business?
Break it down:
For example:
Risk Assessment:
That's actionable. That's a plan.
Now compare your target to your projection and identify what needs to happen.
Quarterly Target: $37,500 Projected Revenue: $38,000 Gap: -$500 (you're slightly ahead)
If you were behind, this is where you'd list what needs to happen:
Below the gap, list your top three priorities for the quarter:
Your one-page plan is useless if you don't update it. This section lists the metrics you'll check every month to see if you're still on track.
When you see a metric moving in the wrong direction, you adjust. Maybe you accelerate your client hunt. Maybe you talk to a client about upselling. Maybe you realize you need to raise rates. But you're making decisions based on data, not panic.
Let's build a complete one-page plan from scratch. You're a solo developer with three clients, and you want to make $100,000 this year.
Step One: Set Your Target
Annual goal: $100,000 Quarterly target: $25,000 Current quarter: Q3
Step Two: List Your Clients
You have three clients:
Client A: $6,000 × 3 months = $18,000 Client B: $3,000 × 3 months = $9,000 Client C: $2,000 × 3 months + $4,000 = $10,000
Total projected: $37,000
Step Four: Assess Concentration
Top client (A): $18,000 / $37,000 = 49% (acceptable, but watch it) Top three clients: 100% (all your revenue is concentrated)
Retainer split: $33,000 / $37,000 = 89% (healthy, predictable)
Step Five: Identify the Gap
Target: $25,000 Projected: $37,000 Gap: -$12,000 (you're ahead!)
But wait—you're ahead of your quarterly target, but all your revenue comes from three clients. Your priorities should be:
You've got the framework. Now let's talk about where people go wrong.
You think, "I'd like to make $100k this year," but you don't actually know if you need that or if it's realistic. You haven't thought about your actual living expenses, taxes, or business costs.
Fix: Work backward from your real number. Calculate your annual expenses (personal + business), add 30% for taxes, then add your desired profit. That's your real target. If you need $60k to live comfortably and cover business costs, and you want $20k in profit, your target is $80k. Not $100k because it sounds good.
You build a beautiful one-page plan in January, then never look at it again. By June, your client situation has changed completely, but you're still working off outdated numbers.
Fix: Schedule a monthly 15-minute review. First Friday of every month, you spend 15 minutes updating your plan with actual numbers. Did a client reduce their retainer? Update it. Did you land a new client? Add them. Did a project scope expand? Revise the revenue. This keeps your plan living and useful instead of a static document.
You know one client is 60% of your revenue, but they've been stable for two years, so you stop worrying about it. Then they get acquired, restructure, or just decide to bring work in-house. Suddenly you've lost half your income.
Fix: Treat concentration risk as an active project, not something you'll "eventually" address. If your top client is above 40% of revenue, make it a quarterly goal to land a new client. Not "someday." This quarter. Even if you're busy. Especially if you're busy—that's when you can afford to invest in diversification.
You decide you want to make $80k this year and set that as your revenue target. But you haven't accounted for contractor costs, software subscriptions, or the fact that you'll spend 20% of your time on non-billable work (sales, admin, learning).
Fix: Your revenue target should be 1.5 to 2x your profit target, depending on your business structure. If you want $50k in profit, your revenue target should be $75k to $100k. This accounts for business costs and the reality that you can't bill 100% of your time.
You identify a $10k gap, but you don't actually do anything about it. You don't reach out to prospects, you don't talk to existing clients about upselling, you just... hope.
Fix: Your quarterly priorities aren't suggestions—they're commitments. If your plan says you need to land $10k in new retainer work, that means you're spending time on sales every single week. Maybe it's five hours. Maybe it's ten. But it's scheduled, it's non-negotiable, and you're tracking progress against it.
You can build your one-page plan in Google Docs, Excel, or even on paper. But some tools make it easier to maintain and act on.
Spreadsheet-Based: Google Sheets is free and works well for tracking clients and revenue. You can build your entire plan in one sheet—clients on the left, monthly projections across the top, key metrics at the bottom. It's simple, it's visual, and you can share it with an accountant if needed.
Purpose-Built Tools: If you want something designed specifically for solo developers and freelancers, Cashierr is built exactly for this. It handles revenue planning, quarterly forecasting, client tracking, and gap-to-goal analysis with AI agents that flag problems before they become crises. Instead of maintaining a spreadsheet, you input your clients and targets, and it automatically projects your revenue, tracks your progress, and alerts you when you're off pace. It's built by people who understand the solo developer mindset—no corporate jargon, no 50-page feature list, just the two questions you actually care about: How much should I make? and How's the business doing?
Simple Dashboards: Tools like Carrd and other one-page website builders can also serve as simple personal dashboards if you're comfortable with that format, though they're primarily designed for website creation rather than financial planning. For actual business planning and forecasting, a spreadsheet or dedicated tool like Cashierr is more appropriate.
The tool doesn't matter as much as the discipline of using it. Pick something you'll actually open every month, and stick with it.
Let's walk through what this looks like in practice. Meet Jordan, a solo developer who builds custom integrations for e-commerce platforms.
Jordan's One-Page Plan (Q3 Start)
Annual target: $90,000 Quarterly target: $22,500
Clients:
Concentration: BigShop is 62% of revenue (high risk)
Priorities:
Jordan checks his metrics:
Action: Jordan reaches out to BigShop to understand the payment delay. Turns out they're in a cash flow crunch themselves. Jordan offers to break their retainer into two smaller payments instead of one large one. Crisis averted, and Jordan learned something about his biggest client.
End of Quarter (Week 12)
Actual Q3 revenue: $25,200
What happened:
Q4 Plan Update
Jordan exceeded his quarterly target, so he's on pace for his annual goal. But he's learned that:
That's the power of a one-page plan.
Your one-page plan works when you're solo. But what if you start bringing on contractors or considering a part-time hire?
The framework stays the same—you still need a quarterly revenue target, you still need to understand your client mix, you still need to identify gaps. But some elements change.
When You Have Contractors:
You need to add a line item for contractor costs. If you're bringing in $50k in revenue but paying $15k to contractors, your actual profit is $35k. Your revenue target needs to account for this. Maybe you adjust your target from $50k to $70k to maintain the same profit.
You also need to think about utilization differently. If you're doing some of the work and contractors are doing some, you need to project how much you can bill versus how much you're paying them to bill.
When You're Considering Hiring:
This is where your one-page plan becomes critical. Before you hire anyone, you need to know: What revenue do I need to generate to make hiring worthwhile?
If you're paying someone $40k/year, you need to generate enough additional revenue to cover that salary plus overhead plus your own profit. That's probably $80k to $100k in additional revenue. Your plan tells you whether you're on pace to hit that or if you need to wait.
When You're Running Multiple Clients:
Your one-page plan scales. Instead of five rows (one per client), you might have fifteen. The structure stays the same. You still track concentration, you still identify gaps, you still set quarterly priorities. The difference is that as you grow, these metrics become even more important because a single client leaving has less impact on your overall business.
The one-page plan isn't a temporary tool for solo developers. It's a foundational document that grows with you.
Here's a trick that separates developers who use their plans from developers who build them and forget them: print it out.
Yes, really. Print your one-page plan and stick it somewhere you see it daily. Your desk, your monitor, your notebook. Something about having a physical copy makes it real in a way that a Google Doc never does.
Every time you see it, you're reminded of your quarterly target, your client concentration, and your priorities. When you're deciding whether to take on a new project, you can glance at your plan and ask: Does this move me toward my quarterly target? Does it help with concentration risk? Is it one of my top three priorities?
If the answer is no to all three, you probably shouldn't do it. That's how a one-page plan actually changes your behavior.
You can also use your plan as a conversation starter. When you're talking to a potential new client, you can reference your plan internally: I'm looking for a retainer client generating $3k+/month to diversify my client base. That specificity helps you evaluate opportunities faster.
When you're talking to an existing client about expanding their work, you can be honest: I'm at capacity right now, but I could make room for this project if we restructured your retainer. You're not just winging it—you're making decisions based on a real understanding of your business.
Every 90 days, you do a full review of your plan. This is different from your monthly check-in. It's a deeper dive that informs your next quarter's plan.
The Review Covers:
Without it, you're just going through the motions. With it, you're actually learning and improving.
You now have everything you need to build a one-page business plan that actually works for a solo developer. Here's your checklist:
Core Sections:
For solo developers, that clarity is worth more than any fancy planning tool. It's the difference between wondering if you're on track and knowing it. It's the difference between panic when a client goes quiet and a calm understanding that you've got a plan to handle it.
Your one-page plan is your business compass. It doesn't tell you every step to take, but it tells you which direction you're heading. And for a solo developer trying to balance code, clients, and sanity, that's everything.
Start building yours this week. You'll be amazed at how much clearer your business becomes when you can see it all on one page.
Master the 3-bucket system for solo developers: operating, tax, and profit accounts. Stop leaving money on the table and make tax season painless.
Master your solo dev finances in 30 minutes every Friday. Track revenue, expenses, goals, and cash flow with this step-by-step ritual.
Master revenue forecasting by tracking just 5 metrics. Learn which data points drive 80% of forecast accuracy for freelance developers.