Fundraising

How a Technical Founder Raises a First $500K Pre-Seed With No Finance Background

You can code the product. Here is how to run the raise, in the same plain, sequential way you would ship a feature.

A focused founder working at a laptop in a small startup workspace, whiteboard with a simple plan behind them
The short answer

A technical founder raises a first $500K pre-seed by treating it as a process, not a finance exam. Size the round to 18 months of runway and one milestone, raise on a post-money SAFE, build a list of 40 to 60 fit investors, and run outreach in a tight two to four week window.

A technical founder with no fundraising experience can raise a first $500K pre-seed by running it as a process, not passing a finance exam. Size the round to roughly 18 months of runway and one milestone, raise on a standard post-money SAFE, build a list of 40 to 60 well-fit investors, and run outreach in a tight window. The finance is light on purpose at this stage.

If you can ship software, you can run a pre-seed. The reason it feels impossible is that most fundraising content is written in the language of finance and treats you as if you already know what a cap, a discount, and a pro rata are. You do not need that vocabulary to start. You need a sequence. This is the same raise broken into concrete steps, in the order you actually do them, written for someone who understands systems but has never sat across from an angel. For the full seven-step version of the process, see the pre-seed fundraising process step by step. This piece is the technical-founder cut of it.

Step one: size the round to a milestone, not a vibe

The number is not $500K because $500K sounds right. It is whatever buys you enough time to hit the one proof point that earns your seed round. Work it backward. Decide the milestone, decide the team and months required to reach it, and price that.

A useful rule of thumb from Y Combinator: an engineer costs all-in roughly $15,000 per month once you include salary, benefits, and overhead. So a plan to run a small team for 18 months is straightforward arithmetic.

Input Example Notes
All-in cost per engineer/month $15,000 YC rule of thumb, salary plus overhead
Team size (incl. you) 2 Founder plus one engineer
Months of runway 18 Enough to reach a real milestone
People cost $540,000 2 x $15,000 x 18
Trim to a clean target ~$500,000 Round down, keep it lean

That is the entire logic. You are not raising $500K, you are buying 18 months and one milestone, and $500K is what that costs. If you want the deeper version of this math and the tradeoffs at different round sizes, how much to raise at pre-seed works through it in detail. The milestone itself matters as much as the money, so pair this with sizing your runway and the milestones that earn the next round.

Step two: pick the structure (and why it is a SAFE)

At $500K in the US, you will almost certainly raise on a post-money SAFE. You do not need to master venture finance to make this choice, because the choice is nearly made for you by convention. A SAFE is standard, cheap to execute, and lets you close investors one at a time as they say yes, instead of holding everything until a full priced round comes together.

The one concept to understand is the valuation cap: it sets the price at which your SAFE converts to equity later. You do not need to model the conversion by hand today, but you should know it determines how much of the company the SAFE holders end up owning. Keep the terms plain, set one cap if you can, and avoid stacking many different caps that complicate your table. If you want to understand why a SAFE beats the alternatives at this stage, the comparison of SAFE vs convertible note vs priced round lays out each option in plain numbers.

Step three: write the capital plan you were dreading

Here is the relief: the "financial model" investors expect at pre-seed is not a spreadsheet with five years of projections. It is a simple, honest plan for how $500K becomes a milestone. Think of it as a README for your raise.

A pre-seed capital plan answers three questions:

  • Who and what does the money buy? The hires, the tools, the runway.
  • What does it get you to? The specific milestone that makes your seed round fundable.
  • How long does it last? The months of runway, stated plainly.

That is it. A rough allocation of a $500K round might look like this:

Use of funds Share Why
Engineering (you plus one) ~70% The build is the point
Tools, infra, hosting ~10% Keep it lean
Go-to-market experiments ~10% Enough to test, not scale
Buffer ~10% Runway rarely goes to plan

Investors read this to judge whether you are a responsible steward of capital, not to check your accounting. Clear thinking beats false precision every time.

Step four: build the list before you send a word

The most common technical-founder mistake is starting outreach before building the list. Reverse it. Spend the first block of time assembling 40 to 60 investors who actually fit your stage, sector, and check size. A pre-seed investor writes small, early, high-risk checks and is comfortable backing an unproven idea. A Series A fund is not your customer, and pitching them wastes both of your time.

Sort your list into three tiers:

  1. Warm intros. People who can introduce you to an investor. Highest hit rate.
  2. Strong fit, cold. Investors who back your exact stage and space but do not know you.
  3. Reach. Nice-to-haves you contact last, once your pitch is sharp.

Build this in a simple sheet: name, firm, why they fit, how you reach them, status. You already track work in systems. Track the raise the same way.

Step five: run outreach in a tight window

Do not trickle out emails over three months. Batch your outreach so meetings cluster into a two to four week window. Concentrated conversations build momentum: when several investors are looking at once, interest compounds, and a yes from one becomes a signal to others. A raise spread thin over months loses that effect and reads as stalled.

Reach out to your warm intros first, then your strong-fit cold list. Keep the first message short: what you are building, why you, the round size, and one line of traction or insight. Your goal in the message is a meeting, not a commitment. When investors pass, ask why, and listen for a pattern. If the same objection keeps coming back, your story or your fit has a fixable problem, which the diagnostic for why a pre-seed keeps getting passed helps you pinpoint.

Step six: close on paper, one yes at a time

The advantage of the SAFE is that you do not need everyone to agree at once. As each investor commits, you send the SAFE, they sign, they wire, and that money is in. You are not waiting to assemble a full round before anything closes. This is why a first raise can build: your first $100K committed makes the next $100K easier, because progress is visible.

Keep your closing simple. Use a standard SAFE document, keep your cap consistent, and track who has signed and who has funded in the same sheet you built in step four. When you have enough committed to fund the plan, you can keep the round open a little longer for a strong late investor or close it and get back to building. Both are fine.

You do not need a 400-page finance text to do this. You need the sequence above, executed. The Funding Framework exists to give first-time and technical founders exactly that: a founder-to-founder playbook for the pre-seed raise, in plain numbers, from sizing the round to closing it. If you want the shortest path from "I have never done this" to running a real raise, start at The Funding Framework and work the steps in order.

Sources and further reading

Frequently asked questions

How much should a technical founder raise at pre-seed?
Size the round to about 18 months of runway plus one clear milestone, not to a round number. A common approach is to price the team you need, use a rough all-in cost of about $15,000 per engineer per month, add overhead, and multiply by 18. For many first-time technical founders that lands near $500K, enough to build and reach a proof point without over-diluting.
Do I need a finance background to raise a pre-seed round?
No. Pre-seed investors are backing the founder, the problem, and early product progress, not a financial model. You need a simple capital plan that shows how the money reaches a milestone, a standard SAFE, and a clear story. The finance is deliberately light at this stage, which is why a technical founder can run the process without formal training.
What structure should a first-time founder use for a $500K pre-seed?
A post-money SAFE is the default for a US pre-seed of this size. It is standard, well understood by investors, cheap to execute, and lets you close investors one at a time as they commit rather than waiting for a full priced round. Set a valuation cap, avoid stacking too many different caps, and keep the terms plain.
How long should a pre-seed raise take?
Aim to run the active raise in a concentrated two to four week window rather than an open-ended process. Build your investor list first, then reach out in a batch so meetings cluster and momentum builds. A raise that drags for months usually signals a list, story, or fit problem, not a patience problem.
From the book

Run your raise with a system, not a guess.

This is the kind of thinking The Funding Framework walks through, step by step, from story to close.

Get the book
All articles