Most pre-seed companies do not have a budgeting problem. They have a runway problem wearing a budgeting costume. With a handful of people, little or no revenue, and a bank balance that sets a hard deadline, the question is rarely "what is the ideal process?" It is "how do we decide what to spend, quickly, and get it right often enough?" Two approaches dominate. Top-down starts with the money you have and divides it. Bottom-up starts with the work you plan to do and adds it up. Founders argue about which is correct, but at this stage you usually need a piece of each, in a specific order.
Top-down budgeting means the founder decides the total spend first, then splits it. You might say: we can spend $300,000 over the next 18 months, so engineering and product get 60%, go-to-market gets 20%, tooling and infrastructure get 10%, and legal, accounting and everything else gets 10%. Every new expense has to fit inside its bucket.
Its strengths are speed and coherence. One person can build it in an afternoon, and it cannot exceed what the company actually has. It also forces a real conversation about trade-offs before anyone gets attached to a plan.
The weakness is that the numbers are guesses. A target like "$15,000 for marketing this year" says nothing about what a conference ticket, a designer, and a paid test will actually cost. When reality arrives, the bucket either gets quietly overspent or the work stops. And when a team member is told their budget without being asked what the work requires, they tend to treat it as an annoyance rather than a plan.
Bottom-up means you list the expenses you expect and total them. Salaries and contractor rates, cloud and hosting, the design tool, the CRM, incorporation and filings, bookkeeping, a recruiting fee, a conference, a laptop replacement. Each line has an owner and a reason.
This version is grounded in reality and surfaces things founders forget. It also creates natural accountability: the person who asked for the line understands what it buys.
It is also slow and optimistic. In a four-person team, a careful bottom-up pass takes days, not hours. People underestimate one-off costs and forget recurring ones, while each owner tends to ask for the comfortable version of their plan. Nobody enforces a ceiling, so the total often lands above what you raised. Bottom-up is a good description of intent and a bad description of constraint.
The failure modes are predictable, and they show up fast:
The workable model for a tiny team is a two-layer budget. The founder sets the outer layer: a hard spending ceiling for the next 18 to 24 months, based on cash in the bank plus revenue you have actually collected, minus a buffer you will not touch. That ceiling is non-negotiable and belongs to one person.
Inside that ceiling sit three or four buckets, no more. Team, product and infrastructure, go-to-market, and admin. Then the people closest to the work build the next 90 days line by line — bottom-up — inside their bucket. They are not setting the total; they are deciding how to spend a number they did not choose. That is a much easier job than defending a wish list, and it produces far better detail.
The point of the split is that the two layers answer different questions. The ceiling answers "how long do we have?" The line items answer "what are we buying?" Mixing them into one spreadsheet is what makes budgeting feel like a fight.
Your pre-seed budget has one job: to tell you how many months you have left and what you would cut first if the answer changed. Everything else is detail. Keep it on a single page, give it one owner, and revisit it on a fixed date each month. If you cannot explain the whole thing in five minutes to a new advisor, it is too complicated to be useful.
One caveat worth stating plainly: budgeting is not tax, accounting, or legal advice. Once you have a plan you believe in, have an accountant glance at the categories — particularly anything touching payroll, equity, or cross-border payments — before you commit to it.
Photo: Altnet / Pixabay
