July 23, 2026
5 min read
2 views
Most advice on how to start a software consulting company stops at "get clients and write good code." That's true but useless. What you actually want to know is what the calendar looks like month by month, where the money comes from, and when the panic sets in. This post walks through a realistic first year with concrete numbers — not to predict your exact results, but to give you a mental model to plan against and adjust.
A quick caveat: the figures below are illustrative examples built from common patterns among solo and small consultancies, not survey data. Your market, rates, and network will move every number. Use them as scaffolding, not gospel.
To make numbers mean anything, we need a baseline. Let's model a single founder — an experienced developer — going independent, working from home, targeting small-to-midsize businesses.
That 25-billable-hours figure is the single most important assumption. New consultants routinely plan for 40 billable hours and are shocked when they hit 15. Selling, invoicing, and unpaid discovery calls eat the rest.
Expect the first three months to produce little income. If you started with warm leads from your network, you might land one small project. If you started cold, you likely earned nothing billable yet.
The emotional reality matters here. You'll feel like you're doing everything except the work you're good at. That's normal — you're building a pipeline, and pipelines have lag. The mistake to avoid is going quiet on outreach the moment you land your first small gig, which creates a feast-then-famine cycle you'll pay for in Q2.
If you keep prospecting consistently, month four or five usually brings your first repeatable rhythm. One project referral leads to another. You start to see what kind of work you attract.
This is where most first-year founders make their most expensive mistake: underpricing and under-scoping. You quote a "two-week project," it takes five weeks, and you effectively earned $40/hour. Track your actual hours against every estimate from day one. That data is the difference between a business and an expensive hobby.
By the end of Q2, aim to have at least one client who has hired you twice. Repeat clients are worth far more than their invoices — they're proof your delivery is trustworthy, and they're your best referral source.
Around month seven to nine, revenue tends to stabilize as referrals compound. This is also when the invisible enemy shows up: cash flow timing.
You can be "profitable" on paper and still be unable to pay yourself, because a $10,000 invoice sent in August might not land in your account until October. Two defenses help: require a deposit (25–50%) before starting work, and bill in milestones rather than one lump sum at the end. This single habit prevents more consulting failures than any amount of technical skill.
By months ten through twelve, if things went reasonably well, you have a small stable of clients and a rough sense of your monthly floor.
Rolling those quarterly ranges together:
Read that last line carefully. Year one usually pays worse than a job. You're trading short-term income for ownership, flexibility, and a much higher ceiling in years two and three, when your rate rises and your pipeline runs on referrals instead of cold effort. Founders who expect to match their old salary immediately tend to quit right before the compounding kicks in.
If you track only a few things in year one, track these:
Learning how to start a software consulting company isn't really about the launch. It's about surviving the lag between effort and income long enough for referrals and repeat clients to carry the load. Budget your runway for that gap, protect your cash flow, and treat year one as tuition for a business that pays off later.
A practical small business website checklist for 2026 — 25 must-haves covering speed, trust, local SEO, and conversions to turn visitors into customers.
Learn marketing fundamentals in plain language: what marketing is, the 4 Ps and 7 Ps, the funnel, positioning, and how to start with a $0 budget.
How do AI receptionists work? An engineer's plain-language teardown of the call pipeline — from routing to booking — for small business owners wary of AI.