The tidy version of founding a company is that you raise some money, quit everything else, and pour yourself into one thing. The real version, for many of the founders we meet, is messier. They are building a startup while doing client work, letting paid projects fund the product, and hoping the two do not pull each other apart before the balance tips. At Bluka we build apps for exactly these founders, so the balancing act comes up in almost every early conversation. This piece is that conversation written down: the trade-offs to weigh, the tension to expect, and the questions worth answering honestly before you commit.
Why consider client revenue instead of raising
Client revenue buys the one thing outside money cannot: the freedom to be wrong slowly. When your runway is a spreadsheet of invoices you control rather than a countdown to the next round, you can change your mind about the product without a board meeting, and you can say no to a bad-fit client because you are not desperate for the logo.
There is a quieter benefit worth weighing too. Client work keeps you close to a real market. Every project brief that lands in your inbox is a live sample of what people actually struggle with and pay for, which is a kind of market research you cannot buy. It walks in the door and pays you to learn from it. If you are weighing what fair pricing looks like from the client side of that equation, we wrote about it in the £25k MVP myth.
The trade is obvious and worth stating plainly. Client-funded means slower. The product gets the hours that are left over, and some weeks there are not many. Anyone choosing this route is choosing patience over speed, and it only works if you want the thing badly enough to build it in the margins.
The tension nobody warns you about
The hard part is rarely the workload, it is the context switching. A morning spent deep in a client’s problem, thinking in their domain, using their constraints, is a morning your brain is not in your own product. Switching back is not free. There is a real cost to picking up your own roadmap after eight hours of holding someone else’s, and on a bad week that cost is the whole evening you meant to spend building.
What makes it genuinely difficult is that client work is legible and the product is not. A client has a deadline, an invoice, a person who will be unhappy if you slip. Your own product has none of that. It has no one chasing it except you, which means it is always the thing that can wait, and if you are not careful it waits forever. The urgency gradient runs entirely the wrong way. The work that pays shouts, and the work that matters most to your future whispers.
We have watched this sink good founders, and the failure mode is never dramatic. Nobody decides to abandon the product. They just keep choosing the urgent thing, week after week, each choice reasonable on its own, until a year has gone by and the product is exactly where it was. Building a startup while doing client work fails quietly, by a thousand sensible decisions to deal with the client first.
Rules worth putting in place before you start
The founders who make this model work tend to run a few rules, and the rules are boring on purpose, because boring is what survives a busy week.
The first is that product time gets booked like a client meeting, not left to whatever is spare. Spare time does not exist when clients are paying. If the product does not have a protected slot on the calendar with the same weight as a paid commitment, it gets nothing, so give it one and defend it.
The second is to think hard before taking client work that is far from your own product. Every project close to your product makes you sharper at building it. Every project far away is just money, and money you could earn does not justify the context-switching tax if it teaches you nothing. That means being willing to turn down work that would pay well and pull you off course, which is a harder discipline than it reads. It helps enormously when clients arrive with a clear brief, which is why we wrote a note on how to write an app developer brief.
The third is honesty with clients about what you are. A studio or a founder with a product of their own should not hide it. Most clients like it, because it means the people building their app are also shipping something of their own and feeling every decision from the inside. What erodes trust is not the split attention, it is discovering the split attention later.
Questions to ask before building a startup while doing client work
Before committing to this route, there are a handful of questions worth answering honestly, ideally on paper:
- Do you want the product badly enough to build it in the margins for years rather than months?
- Can you protect product hours on your calendar even in a week when a client is unhappy?
- Is the client work close enough to your product that it teaches you something, or is it only money?
- Do you have a clear line for the work you will not take, however well it pays?
- What does “the balance has tipped” look like for you, and how will you know when it is time to go all in on the product?
If the answers are honest and you still want it, this is a legitimate way to start a company, not a lesser one. The stories that make it sound like everyone quit and raised are survivorship bias with good PR. Plenty of durable companies were funded by paid client work rather than investors, and there is no medal deducted for patience.
The discipline is the whole game
Whichever rules you choose, the shape of the challenge stays the same. Client work will always try to expand to fill the time, because it has deadlines and people and money attached, and the product will always try to shrink, because it has none of those pressing on it. The job is to hold that line, week after week, and give the quiet work a fair share of your best hours rather than your leftover ones.
If you are weighing this route for your own idea and want a partner who understands the balance you are trying to strike, tell us what you are working on and we will give you an honest read.
.webp)
.webp)
