A founder posted a simple number, €200 a month in burn, and got sixty comments about servers, cloud cost, and architecture. The thread had a different problem hiding in plain sight. The business had zero paying users, and the real budget debate was not the infra bill. It was distribution.
That distinction matters. At zero revenue, the usual advice, spend 10 to 20 percent of revenue on marketing, is circular. There is no revenue yet. So the question is not how much of revenue to spend. The question is what scarce resources you are actually allocating before revenue exists.
For pre-revenue founders, the answer is usually founder hours first, euros second. If you do not budget time for conversations, outreach, and proof creation, the product can look disciplined while the business remains invisible.
The thread problem
The live case was blunt. The founder had built a product, paid for infrastructure, and still had no customers two months after launch. He had done some outbound work, 20 cold calls in three days, and turned that into 3 demos. The break-even math was clear, 21 customers at €9.90 or 3 agencies at €79. The comments, however, mostly fixated on the stack, the servers, and whether the hosting was sensible.
That is a familiar trap. Infrastructure cost is visible, numeric, and easy to optimize. Distribution effort is diffuse, harder to measure, and more uncomfortable to confront. Yet the latter is usually the real bottleneck.
The visible number is rarely the decisive one. Founders often optimize the bill they can see, while underfunding the work that creates demand.
Why revenue rules fail
Budget frameworks built on revenue percentage are useful once the business has a repeatable motion. Before that, they are placeholders. A rule like 10 to 20 percent of revenue sounds disciplined, but at zero revenue it is mathematically empty.
It also creates false comfort. If you write down a percentage, you feel like you have a budget. In reality, you have only deferred the hard decision about how much time, energy, and cash to commit to getting the first customers.
That is why the question, how much should a pre revenue startup spend on marketing, is often the wrong question. The useful question is simpler, and less flattering, how many founder hours will you spend making demand appear?
Hours come first
Before revenue exists, marketing is not a department. It is a set of founder actions that create contact, trust, and evidence. That includes cold outreach, direct conversations, useful content, partnerships, and follow-up.
In the thread, the fastest signal came from calls, not code. Twenty calls produced three demos. That is not a complete growth system, but it is a real data point. It shows that the founder already had one channel with movement, and likely needed more time there, not more debate about hosting.
So the first budget should be written in hours. Not vaguely, in a calendar slot. If you do not assign hours to distribution, product work will consume them all. The calendar will fill itself with work that feels productive and keeps the business safe from uncomfortable feedback.
A usable split
For a pre-revenue software founder, a practical starting point is a 60/30/10 hour split.
- 60 percent, conversations and outreach, direct contact with prospects, customer interviews, follow-up, demo booking, and channel testing.
- 30 percent, distribution assets, writing, case studies, landing pages, demo scripts, short videos, and other assets that make outreach easier.
- 10 percent, everything else, tooling, analytics, housekeeping, and experiments that support the first two buckets.
This is not a law. It is a corrective to the common bias toward building and polishing. When a founder is pre-revenue, the business is usually not short on features. It is short on attention from the right people.
What the money covers
Pre-revenue money is not primarily for ads. It is for small, practical leverage.
- CRM or sequencing tools
- Email sending and domain setup
- Landing page software
- Call recording and scheduling
- Light design or editing help
- Small experiments, not broad spend
Most founders do not need a large media budget before the first customers. They need enough cash to keep the outreach machine running and enough discipline not to mistake software spend for demand generation.
That is the gap the thread exposed. The founder had already spent on infrastructure, yet the more important line item, founder effort on distribution, was still underpriced.
When percentages work
Percent-of-revenue rules do matter, eventually. They become useful when three things are true, the business has revenue, the channel is repeatable, and the economics are visible enough to forecast.
That is when budget can be anchored to a known base. At that point, you are no longer guessing whether outreach works. You are deciding how much to scale what already works.
Until then, percentage rules can mislead. They make the budget look mature before the business is mature.
If you want a cleaner transition, use this sequence, first budget time, then validate a channel, then convert that channel into a spending plan. That is the order. Not the reverse.
What anxiety hides
Cost anxiety often displaces attention. Founders can stare at a monthly bill because it feels controllable. The real fear is usually less tidy, maybe the product is not needed, maybe the positioning is weak, maybe no one wants to talk.
So the bill becomes the object of scrutiny. It is easier to argue about €150 Azure, €45 Hetzner, and a few dollars of AWS than to ask whether the last ten hours created any new demand.
That pattern matters because it wastes scarce early energy. A founder can spend days tuning infrastructure while the business waits for a first meaningful conversation.
What he got right
The Live24h founder did several things well.
- He was honest about the state of the business.
- He had a clear integration wedge, which can matter in B2B.
- He tested direct outreach instead of waiting for inbound.
- He priced the product simply, which makes the break-even math visible.
The main reallocation is not dramatic. It is to move attention from infra optimization to distribution work. Keep the stack lean enough to function, then spend the scarce hours on conversations, customer discovery, and proof.
That is also where content fits. Useful public work is not a branding ornament. It is a distribution asset. Better exists because distribution, not product polish, decides early survival.
How to budget
If you are pre-revenue, write next week’s budget in two columns.
- Hours, how many hours will go to outreach, calls, follow-up, and asset creation.
- Cash, what you need to keep the tools and tests moving.
Then ask three questions.
- Which activities create real conversations?
- Which activities support those conversations?
- Which costs are merely visible?
If a line item does not improve access to customers, shorten the line item or cut it.
What to stop measuring
Stop measuring yourself against percent-of-revenue advice before revenue exists. It will not help. You do not yet have the denominator.
Also stop using infrastructure spend as a proxy for seriousness. A lean stack is sensible. A low bill is not a strategy. Nor is a clean architecture if nobody knows the product exists.
The useful metric in the early stage is simpler, conversations created per week. If that number is flat, the budget, meaning time and cash, is probably pointed at the wrong work.
Takeaway
At zero revenue, the right marketing budget is not a percentage. It is a weekly allocation of founder hours, supported by a small amount of cash for tools and tests.
Start with outreach and customer conversations, build the assets that make those conversations easier, and keep overhead low enough to stay alive. Only after a repeatable channel appears should you translate performance into a percentage-of-revenue plan.
In other words, before you ask how much to spend on marketing, ask what you are spending your time on. That is the number that decides whether the first customer arrives.