DEV Community: Spencer Claydon

When to Quit Your Job to Start a Startup

Spencer Claydon — Sun, 24 May 2026 15:09:53 +0000

When to Quit Your Job to Start a Startup

If you're reading this, you've probably already pictured the email. The one where you tell your manager you're leaving to go build the thing you've been tinkering with at nights and weekends. You've also probably closed that draft 14 times because you can't tell whether you're being brave or reckless.

Both are possible. The difference between them isn't your gut. It's a handful of measurable thresholds you can check before you walk into that meeting. This piece lays out exactly what those thresholds are, what "enough traction" actually means, and how to think about runway, risk, and the part nobody talks about: what happens if it doesn't work.

When should you quit your job to start a startup?

You should quit when your startup either has paying customers, signed letters of intent, or funding that buys you at least 12 months of personal runway, and the next leap requires more time than nights and weekends can give. Quitting before any of those three is true is usually a vibes decision dressed up as conviction.

Most successful founders don't quit on day one. Pieter Levels built Nomad List on the side while traveling. Mark Zuckerberg ran Facebook from a dorm before going full-time. Drew Houston built the first Dropbox prototype while still at his previous job. The pattern is consistent: validate, build a wedge, then leave when staying employed is the thing slowing you down.

The trigger isn't "I have an idea." The trigger is "I have proof, and I'm leaving real progress on the table by being part-time."

What does "enough traction" actually look like?

Enough traction is whatever level of validation makes your odds of survival materially higher than zero. The specific number depends on your business model, but the bar is concrete, not vibes.

For B2B SaaS, a reasonable bar is 3 to 5 paying customers at your target price point, or signed letters of intent from 5 to 10 design partners. If you're charging $200 a month and you have five customers, that's $1,000 MRR. Not a business yet, but proof that your wedge cuts.

For consumer products, look for 1,000 active users, retention curves that flatten instead of trending to zero, and at least one engagement metric (sessions per week, posts created, songs added) growing without paid acquisition.

For marketplaces, you need both sides showing up. One side is easy. Two sides, in the same week, on the same transaction, is the unlock. Even 10 closed two-sided transactions per week is a strong signal at the start.

For content businesses or creator products, look for 5,000 to 10,000 engaged followers or 1,000 email subscribers with open rates above 35%. That's a small audience, but it's an audience that listens.

If you're not at any of these numbers yet, your job isn't slowing you down. Your validation is. Quitting won't fix that.

How much runway do you need before quitting?

You need at least 12 months of personal runway in the bank, and 18 to 24 is safer. Personal runway means your monthly burn (rent, food, insurance, debt minimums, business costs) multiplied by the number of months you can sustain it without income.

Run the math like this. Add up the bare-bones version of your monthly expenses. Not your current lifestyle. The version where you've cut everything that isn't survival or business-critical. For most people in a US metro that's $3,500 to $5,500 a month. Outside expensive cities or in lower-cost countries, it can drop to $1,500 to $2,500. Multiply that by 12. That's your minimum.

Then add an emergency cushion of three months on top of that. Startups always cost more and take longer than the founder thinks. The cushion isn't pessimism. It's the price of not having to take a survival contract gig six months in that pulls you off your real work for four weeks.

If you've raised pre-seed funding, the calculation shifts but doesn't disappear. Your startup pays your salary, but most pre-seed founders pay themselves $40k to $80k, well below market. Make sure your personal expenses fit the founder salary you're planning to take. Use a runway calculator to model both your startup runway and your personal runway side by side. Foundra has a free one at foundra.ai/tools/ if you want to skip the spreadsheet.

Quitting with three months of savings and a Stripe link that nobody has clicked yet is the textbook way to flame out in month four, take a desperate job, and have your startup wither while you're working 50 hours a week somewhere else.

Should you go full-time or stay part-time longer?

Stay part-time as long as your current job isn't the bottleneck. The right time to switch is when you can prove, with evidence, that more time would meaningfully accelerate progress.

Here's the test. Look at the last 60 days. What did you actually ship? What did you skip because you ran out of energy after a full workday? Now imagine those 60 days with 40 extra hours per week. What changes?

If the answer is "I'd talk to twice as many customers, I'd ship the v2 in three weeks instead of three months, and I'd start sales outreach I currently can't do during business hours," your job is the bottleneck. Quit.

If the answer is "I'd watch more YouTube videos about startups and reorganize my Notion," your job isn't the bottleneck. Your focus is. Quitting won't fix that either.

A lot of founders quit prematurely because part-time work feels slow. It is slow. But slow isn't the problem. Unfocused is the problem. You can validate a startup idea in 90 days while working full-time. You just need to be ruthless about what you spend your 10 to 15 weekly side hours on. (We have a 90-day validation framework on foundra.ai/key-reads/ that walks through exactly how to structure that time.)

What are the signs you're ready to quit?

The signs you're ready to quit are mostly about the business outpacing your bandwidth, not the other way around. Here are the five most reliable ones.

First, you're turning down customers or leads because you can't service them during business hours. If your sales pipeline has more demand than you can answer, your job is now actively costing you revenue.

Second, you have at least 12 months of personal runway, validated by an actual bank statement, not by mental math at 1am.

Third, you have signed paying customers or executed letters of intent that confirm someone will hand you money for what you're building, not just feedback.

Fourth, your weekends and evenings have produced shipped artifacts, not just plans. You have a working product, a real customer list, and a sales motion that's worked at least three times. The thing exists.

Fifth, you have a spouse, partner, or financial dependent who has actually heard the plan and agreed to the risk. Quitting your job affects people who didn't sign up for the startup. They need to be in the conversation.

If five out of five are true, you're ready. If three or four are true, you're close. If two or fewer, you have more work to do before you quit.

What are the signs you should NOT quit yet?

You should not quit yet if any of these are true, no matter how excited you are.

You haven't talked to 30 potential customers in the last 90 days. If you can't list them by name, you haven't done the customer discovery work yet, and your sense of what people want is based on imagination. Imagination is a great starting point. It's a terrible thing to bet your salary on.

You have less than 12 months of personal runway. The risk profile changes completely when you're under a year. Stress kills decision quality. You'll take a bad acquisition offer, a bad investor term sheet, or a bad customer contract because you need the cash.

You've never charged anyone for what you're building. Free users are a different species from paying users. Until money has changed hands, you don't know what you have. Side-project a payment link. Get one customer. Then talk about quitting.

You don't have a clear next milestone you're working toward. "I'll figure it out when I'm full-time" is the same energy as "I'll get in shape when I have more time." You won't. The structure you have now is the structure you'll bring with you.

Your spouse or partner doesn't know the plan or doesn't support it. This isn't romantic advice. This is operational. The single biggest predictor of founder burnout in the first year isn't traction. It's domestic friction. Get aligned before you quit.

How do you tell your boss you're leaving?

Tell your boss in person, with two weeks of notice minimum, and give them a clean exit story that doesn't burn the bridge. Most first-time founders overthink this conversation. Most managers have heard "I'm leaving to start something" before and have a script for it.

The format that works: schedule a 30-minute one-on-one, open with the news (don't bury it), share the headline (you're leaving to start a company), give the timeline (last day in two to three weeks), thank them for the opportunity, and offer a transition plan. Don't pitch them on your startup unless they ask. Don't badmouth the job. Don't oversell the new thing in case it fails and you need to come back.

Practical things to lock down before that meeting: your vesting schedule (any unvested equity you're walking away from), the IP assignment language in your employment contract (anything you built on company hardware or company time can become contested), your healthcare options (US founders, COBRA is expensive, look at marketplace plans early), and any non-compete or non-solicit language. Most non-competes are weakly enforceable, but you don't want to discover that mid-lawsuit.

If your startup is even tangentially in the same space as your employer, get an IP release in writing before you leave. Spend $500 with a startup lawyer to do this right. It will save you 50x that later.

What if you quit and it doesn't work?

If you quit and it doesn't work, you go back to a job. That's the part nobody says out loud, but it's also the calmest thing you can know going in.

The market for engineers, designers, PMs, and operators with 5+ years of experience and "founder of a startup that didn't make it" on their resume is strong. In many cases, ex-founders command higher salaries than they did before they left. The skills you build running your own thing (decision-making under uncertainty, prioritization, sales, hiring, financial modeling) translate directly to senior IC and management roles.

The mental side is harder than the financial side. Plan for both. Tell yourself, before you quit, what the off-ramp looks like. Specifically: at what point will you stop? Most founders set a hard runway floor (I will look for a job when I have 3 months of runway left) and a soft milestone floor (if I don't hit X by month 12, I'll reassess). Writing these down before you quit, while you're still calm, beats trying to make the call from inside a panic spiral 11 months in.

Quitting your job to start a startup isn't a one-way door. It's a decision that has costs and timelines and exits. Treat it like one.

Key takeaways

You should quit when paying customers, signed LOIs, or runway-securing funding make staying employed the thing slowing you down. Not before.

Personal runway under 12 months is the single most common reason founders fail in the first year. Get to 12+ before you quit, ideally 18 to 24.

"Enough traction" is concrete, not vibes. 3 to 5 paying B2B customers, 1,000 retaining consumer users, 10 weekly two-sided marketplace transactions, or 1,000 engaged email subscribers are reasonable bars by category.

The right time is when more hours would meaningfully accelerate progress, not when you're frustrated with how slow part-time feels. Slow and unfocused are different problems.

Set your off-ramp before you quit. A runway floor and a milestone floor, written down, in advance. This is the calmest decision you'll make all year. Make it now.

FAQ

How long should I work on my startup as a side project before quitting?
Most founders need 6 to 18 months of side work to validate the idea, build a wedge, and acquire enough early traction to justify going full-time. Less than 6 months and you usually haven't talked to enough customers. More than 24 months and the side project is probably either ready to go full-time or unlikely to ever get there.

Do I need to have raised money before I quit my job?
No. Plenty of founders quit on revenue or savings without raising. If you've got 12+ months of personal runway and paying customers, you don't need an investor's permission to leave. That said, raising a pre-seed round can be a clean way to extend your runway and signal commitment.

Can I start a startup while staying employed long-term?
Yes, if your business is a lifestyle business, a creator brand, or a small SaaS that runs without your full attention. The "quit your job" question only applies if you're trying to build a venture-scale company that requires your full time and focus.

What if my employment contract has an IP assignment clause?
Talk to a startup lawyer before you quit, ideally before you build anything on company hardware or company time. Most contracts assign IP that overlaps with company business or was built using company resources. A short legal review (typically $500 to $1,500) is much cheaper than litigation.

Is it better to quit and go full-time or raise pre-seed first?
Raising first is usually safer if you can do it. It gives you 12 to 18 months of runway and lets you pay yourself a modest salary. But raising while employed is hard because investors want to see commitment. Many founders quit, give themselves 3 to 6 months of savings, and raise during that window.

How do I know if I'm quitting too early?
You're quitting too early if you can't answer these three questions with specifics: who is your customer, what have they paid you, and what's the next milestone you're working toward. If any answer is vague, do more validation before you quit.

How to Build a Moat for Your Startup (Even Without a Patent)

Spencer Claydon — Sat, 23 May 2026 15:13:03 +0000

How to Build a Moat for Your Startup (Even Without a Patent)

The first time an investor asks "what's your moat?", most first-time founders freeze. You're nine months in. You have 40 paying users. You don't have patents or proprietary AI trained on a trillion tokens. What you do have is an idea that works and a customer list. Is that a moat?

Short answer: yes, but the kind of moat an early-stage startup builds looks nothing like the one a public company has. Investors already know that. They're not testing whether you have a finished castle. They're testing whether you have any idea what kind of castle you're building.

This guide breaks down how to build a moat for your startup as a first-time founder: the seven real categories of defensibility, which ones are achievable pre-Series A, which are theater, and how to pick the one that fits your business.

What is a startup moat?

A startup moat is any structural reason a competitor can't easily copy what you do, even if they have more money or more engineers. It's the thing that makes your customers harder to steal six months from now than they were yesterday.

The term came from Warren Buffett, who used it to describe public companies with durable competitive advantages. Coca-Cola has a brand moat. Visa has a network moat. Microsoft has a switching-cost moat baked into every IT department on earth. Those are decades-deep moats. You won't have one at seed stage. What you can have is the start of one, and a believable theory about how it gets wider every month you're alive.

The simplest test: imagine a well-funded competitor copies your product exactly tomorrow. What still gives you an edge a year from now? If the honest answer is "nothing", you don't have a moat yet. You have a feature. Investors care about that difference more than almost anything when they decide whether to write a check.

Do early-stage startups actually have moats?

Most early-stage startups don't have moats yet. They have moats under construction. That's a different thing, and it's fine: investors who back pre-seed and seed rounds expect this.

What they want to see is a plausible path from your current state to a defensible position within 24 to 36 months. They want to see that you've picked a category of moat, that the moat compounds with usage, and that you've already done one or two concrete things this quarter to start building it. If your answer is "we'll just out-execute everyone", you've failed the test. Execution is table stakes. It is not a moat.

Stewart Butterfield famously said Slack's only real moat in its early days was the rate at which it could ship. That's true, except shipping fast is what every well-run startup does. The actual moat Slack was building underneath the speed was the team-by-team switching cost: once a 30-person team moved all its in-jokes, integrations, and decision history into Slack, you couldn't pry them out with a crowbar. The speed was just the construction crew. The walls were switching costs.

So when you're answering the moat question at your stage, be honest: you don't have one yet. But you should be building one, and you should be able to point at the bricks.

What are the 7 types of startup moats?

There are seven categories of moat that show up across nearly every defensible company. Some take years to build. Some you can start in week one. The mix that's possible for you depends entirely on what kind of business you're in.

1. Network effects

Your product gets more valuable as more people use it. Marketplaces (Airbnb, Etsy), social networks (LinkedIn, Discord), and team tools like Slack live and die on this. It's the strongest moat that exists, but it's hard to start. You usually have to fake one side of the market for the first 12 months. Reddit seeded their early site with fake accounts posting to each other until real users showed up.

2. Switching costs

Once a customer is in, leaving hurts. They've trained their team, imported data, integrated other tools, or built workflows around your product. The cost of switching isn't the price difference. It's the workflow disruption.

This is probably the most underrated moat for SaaS startups. It starts small (one user, three settings) and grows fast (whole team trained, six integrations, 18 months of history). Notion, Linear, and Figma built quiet switching-cost moats while founders publicly worried about competitors who never landed a punch.

3. Brand

People buy because of how they feel about you, not features. They trust you. They'd be embarrassed using a competitor.

Brand is the slowest moat to build and the easiest to overestimate. Real ones take 5 to 10 years. What first-time founders often call "brand" is actually decent landing-page copy. Liquid Death built a real brand moat in 4 years by being the only canned-water company acting like a hardcore band. That's rare.

4. Proprietary data

You collect data nobody else can get, and your product improves the more you collect. Stripe's fraud models work because Stripe sees every transaction. ZoomInfo's database compounds because every customer correction makes it more accurate.

For first-time founders, this usually shows up as a feedback loop: users do something, that creates data, the data improves the product, which attracts more users. Pick a product where the loop is real, not theoretical.

5. Cost or scale advantages

You can produce something cheaper than anyone else because of how you're set up. Amazon's logistics. Wayfair's freight routing. A direct-to-consumer brand that owns its factory.

This rarely applies to early-stage software. If you're a service, hardware, or physical-world business, it absolutely can. Watch whether the underlying economics shift in your favor as you grow, or stay flat. If they stay flat, scale isn't your moat.

6. Regulatory or legal moats

Patents, licenses, exclusivity deals, certifications. Plaid took years to build relationships with every major US bank. Toast got compliance certifications that take 18 months and a legal team to replicate. A FedRAMP-approved startup has a moat against any competitor that isn't.

This isn't usually an early moat. It becomes one if you're in fintech, healthtech, govtech, or any regulated space, and the path starts with a single compliance milestone, not a patent.

7. Embedded distribution

Your customers find you through a channel competitors can't replicate. Shopify's app store. The Apple App Store. A category-defining piece of content (Ahrefs' blog, HubSpot's free CRM funneling into paid).

This is the moat first-time founders most often build without realizing it. If your top acquisition channel is something only you can run (you're a known voice in the space, you built a 30K X audience over four years), that's a moat. It just doesn't look like one until you try to hand it off.

Which moats are real and which are theater?

The moats most often faked in early-stage pitches are AI, brand, and "first-mover advantage." Investors have seen all three a thousand times.

"We use AI" is not a moat. Every team in the category is using the same model providers. What might be a moat is a proprietary fine-tuning dataset, a feedback loop on user corrections, or a domain-specific model nobody else can train because they don't have the data. If your AI moat is "better prompts", you don't have one.

"We have a great brand" almost never means what founders think it means at month nine. You probably have a nice logo and a tone of voice. That's positioning. Brand requires 50,000 customers to remember you in a commoditized category, and you're not there yet.

"First-mover advantage" is the most-mythologized non-moat in startup history. The first mover in search was AltaVista. The first mover in social was Friendster. The first mover in smartphones was BlackBerry. Being early helps a little. It is not a moat.

Real moats at your stage usually look like switching costs, embedded distribution, or the first thin layer of a network effect.

How do you start building a moat from day one?

Pick one moat category that fits your business, then design every product and go-to-market decision so it widens that moat. Don't try to build all seven. Pick one.

The exercise that works: list the seven moats above. For each, write a single sentence answering "could this realistically apply to my business in 24 months?" Most will be a hard no. You'll usually find one or two real possibilities. Pick the strongest, then ask: what would I do this month to start building it?

First moves you can do this quarter:

Switching costs: ship one integration with the tool your customers spend the most time in
Network effects: add an invite flow that pulls in three teammates per user, then design a feature that needs them active
Proprietary data: instrument every user action and feed clean signals back into your model or matching logic
Embedded distribution: write one piece of content per week in a channel where you have a personal edge, for 18 months, without quitting

The choice matters more than the speed. Most founders haven't actually picked one and end up defensible in zero ways instead of one.

This is where structured thinking helps. A spreadsheet, Notion doc, or planning tool like Foundra that walks first-time founders through positioning and competitive analysis can force you to write down which moat you're choosing. Once it's in writing, every weekly product decision gets a tiebreaker: does this widen the moat, or not?

How do you talk about your moat in a pitch?

When an investor asks about your moat, give them three things in order: which category you're building, what's already built, and what compounds from here.

Bad answer: "We're going to out-execute everyone in the space."

Slightly better answer: "We have a really strong team and we ship fast."

Good answer: "Our moat is switching costs. We're already integrated with the four tools our customers use daily, and we hold 18 months of their historical data in formats no competitor can read. Every month they stay, switching gets harder. Our churn dropped from 8 percent to 2 percent after we shipped the integrations. We expect that to keep dropping as we add the next four."

The good answer names the category, points at evidence, and shows the slope. That's all an investor needs from you at seed. They're not asking you to be Visa. They're asking you to prove you know what game you're playing.

If you can't currently answer like that, you have a different problem than your pitch. You have a strategy problem. Fix the strategy first, then the pitch fixes itself.

Common moat mistakes first-time founders make

The most common mistake is confusing a feature for a moat. The second is confusing speed for a moat. Both feel defensible from the inside. Neither survives a well-funded competitor showing up.

Other recurring mistakes:

Claiming network effects when you're a B2B vertical SaaS with no cross-customer value
Trying to build all seven moats at once, which means none of them compound
Mistaking lazy customers for a real switching-cost moat (one quarter of bad service and they're gone)
Calling your AI a moat when you're using the same APIs as every competitor
Ignoring the moat conversation until your seed pitch, then retrofitting strategy onto whatever you've built

A useful gut check: if you closed shop today and someone bought your company for $500K, what would they actually be buying? If the answer is "your codebase", you don't have a moat. If it's "your customers, data, distribution, or network position", you do.

Key takeaways

A startup moat is anything structural that makes your customers harder to steal six months from now than they are today
Early-stage startups don't have moats yet, they have moats under construction, and investors expect that
There are seven categories of moat: network effects, switching costs, brand, proprietary data, cost or scale, regulatory, and embedded distribution
Most first-time founders should pick one moat that fits their business and design every product decision around widening it
AI, brand, and first-mover advantage are the three most-faked moats and rarely count on their own at early stage
The pitch answer that works: name the category, show what's built, explain what compounds

FAQ

Does my startup actually need a moat to raise a seed round?

You need a believable theory of one, not a finished one. Investors at seed stage will accept "this is the moat we're building and here's the first evidence it's working." They will not accept "we don't think about moats."

What's the easiest moat to start building as a first-time founder?

Switching costs are usually the most accessible. Every SaaS startup can start building them on day one by integrating into customer workflows, capturing historical data, and making the product the place teams collaborate. The bricks are small but they stack fast.

Are network effects a realistic moat for B2B SaaS?

Sometimes. Single-player B2B tools don't have network effects no matter what the deck says. Multi-player tools (collaboration, marketplaces inside the product, cross-customer benchmarking data) sometimes do. Be honest about which kind you're building.

Is being first-to-market a moat?

Almost never. First-mover advantage is mythologized. The first mover in most categories lost to a second or third mover who learned from their mistakes.

Do patents count as a moat for software startups?

Rarely. Software patents are expensive to file, slow to enforce, and easy to design around. They might matter in deep tech, biotech, or hardware. For most consumer or SaaS software, the time and money are better spent on switching costs or distribution.

How long does it take to build a real moat?

A meaningful start can happen in 12 to 24 months. A moat that holds up against well-funded competitors usually takes 4 to 7 years of compounding. You don't need the finished version to raise. You need the start, the slope, and the conviction.

If you want to map out which moat actually fits your business model, the free tools at foundra.ai/tools/ include a startup positioning workspace that walks through competitive analysis and the moat exercise step by step.

Pre-Seed vs Seed Funding: What's the Actual Difference?

Spencer Claydon — Fri, 22 May 2026 15:10:15 +0000

Pre-Seed vs Seed Funding: What's the Actual Difference?

Two founders sit down at the same coffee shop. Both say they're raising $1.5M. One calls it a pre-seed. The other calls it a seed. They're pitching nearly identical decks. So what's the actual difference?

In reality, the line between pre-seed and seed funding has gotten blurry over the last five years. Round sizes have crept up. Stage labels have crept down. A 2010-era "seed" round looks a lot like a 2026 pre-seed. Founders who don't understand the distinction end up pitching the wrong investors, asking for the wrong amount, or worse, giving away too much equity for a round they could have skipped.

This guide breaks down pre-seed vs seed funding in plain language: how much you raise at each, what investors actually expect, how dilution works, and how to figure out which round you're really running. No buzzwords. No fluff. Just the stuff you wish someone had told you before you sent your first cold email to a VC.

What is pre-seed funding?

Pre-seed funding is the earliest round of institutional or semi-institutional capital a startup raises, usually before there's meaningful revenue or product-market fit. It typically ranges from $250K to $1.5M and gets a company from "idea plus founders" to "MVP plus early signals."

Pre-seed used to be friends-and-family money. Then around 2018, a wave of dedicated pre-seed funds opened up: Hustle Fund, Pear VC, Afore Capital, K9 Ventures, and dozens more. These funds write smaller checks ($100K to $750K), move faster than traditional VCs, and accept way more uncertainty.

A pre-seed round usually looks like this:

1 to 3 cofounders, often still partially employed
A prototype, MVP, or working demo
Some user interviews, maybe a waitlist
Little or no revenue
A clear hypothesis about the problem, not yet a proven solution

Investors at this stage are betting on the team and the wedge, not the numbers. You don't have numbers worth betting on. You're selling a credible plan to find them.

What is seed funding?

Seed funding is the round after pre-seed (or sometimes the first institutional round) where startups raise capital to find product-market fit and start scaling early growth. Seed rounds in 2026 typically range from $2M to $6M, with the median around $3M according to Carta's State of Private Markets data.

Seed is where the round actually starts to feel like "real" venture funding. The investors are bigger. The diligence is heavier. And the bar for what you need to show has climbed every year since 2018.

A modern seed round usually expects:

A working product with real users
$10K to $50K MRR (for SaaS), or equivalent traction in other models
Repeatable acquisition (even at small scale)
A team of 2 to 6 people, mostly full time
Clear evidence the product solves something people want

Here's the thing: a "seed" in 2015 needed almost none of that. You could raise $1M on a slide deck and a smile. Today, that same pitch gets you a pre-seed at best. So if you've been told "just raise a seed round," check what investors actually mean by it before you start sending emails.

Pre-seed vs seed funding: the 5 key differences

The cleanest way to compare them is across five dimensions: amount raised, valuation, traction expected, dilution, and investor type. Here's how they typically stack up in 2026.

Dimension	Pre-Seed	Seed
Typical amount	$250K to $1.5M	$2M to $6M
Valuation (post-money)	$4M to $10M	$10M to $25M
Stage	Idea to MVP	MVP to early traction
Revenue expected	$0 to ~$5K MRR	$10K to $50K MRR
Dilution	10% to 18%	15% to 25%
Lead investor	Pre-seed funds, angels	Seed VCs, micro VCs
Round timeline	4 to 12 weeks	3 to 6 months
Decision driver	Team and thesis	Traction and economics

A few things worth flagging here. First, the valuation ranges overlap. A "hot" pre-seed can price at $12M post and a slow seed can land at $9M. The label matters less than what you actually need and what investors expect of you.

Second, dilution math gets weird. Raising $1M at a $5M post means you give up 20%. Raising $3M at a $15M post means you give up 20% too. The percentage is similar, but the dollar value of what you're giving up is wildly different. Pre-seed dilution is cheap in absolute terms and expensive in percentage terms. Seed is the opposite.

Third, who leads the round matters more than the size. A pre-seed led by a respected pre-seed fund like Hustle Fund signals different things than a pre-seed cobbled together from 20 angels. Both work. They tell different stories.

How much should you raise at each stage?

The right amount at pre-seed is 12 to 18 months of runway to hit specific seed milestones. The right amount at seed is 18 to 24 months of runway to hit Series A milestones. Raising less leaves you stuck. Raising more dilutes you unnecessarily.

Let's make that concrete. Say you're a SaaS startup with two cofounders pre-seed.

Your monthly burn at pre-seed might look like:

2 founders at $5K/month each (well below market)
1 contractor or part-time hire: $4K
Tools, hosting, marketing: $3K
Total: ~$17K/month

To reach a credible seed pitch in 18 months ($30K MRR, retention proven, a small team in place), you need roughly $300K in operating cash, plus a $200K buffer for the next hire and unexpected costs. Call it $500K minimum, $1M comfortable. That's a pre-seed.

Now imagine you raised that, hit your milestones, and are 16 months in with $35K MRR and a team of four. Your burn is now $80K/month, and to get to Series A traction ($1.5M to $3M ARR) you probably need 24 months of fuel plus two engineering hires. That's $2.5M to $4M. That's a seed.

The math is more important than the label. Build a burn model. Define your milestones for the next stage. Subtract your current cash. The gap is what you raise. You can map this out in a spreadsheet, Notion, or a planning tool like Foundra that walks first-time founders through the runway and milestone math. The tool matters less than the discipline.

What do investors expect at each stage?

Pre-seed investors expect a credible team, a defensible insight, and a believable path to first traction. Seed investors expect early product-market fit signals, retention data, and a story about how their capital becomes 10x growth in 18 months.

Let's break that into the actual diligence questions you'll hear.

At pre-seed, expect:

"Why you? Why now? Why this problem?"
"What's your unfair advantage or insider knowledge?"
"Have you talked to customers? What did they say?"
"What does the first $1M of revenue look like?"
"Can you show me your MVP or prototype?"

At seed, expect:

"What's your MRR, growth rate, and churn?"
"What's your CAC, LTV, and payback period?"
"Show me cohort retention by month."
"What channels are working and what's the unit economics?"
"How does this become a $100M+ revenue business?"

You can see the shift. Pre-seed is about belief. Seed is about evidence. The same investor pitch deck that closes a pre-seed in two weeks will get politely declined at seed because there's no data to defend it.

If you've never seen the numbers seed investors care about, the basics are MRR, growth rate (week over week or month over month), gross margin, net revenue retention, CAC, LTV, and burn multiple. Carta and OpenVC both publish benchmarks. Read those before you build your seed deck.

Should you skip pre-seed and go straight to seed?

You can skip pre-seed if you have either personal capital, founder savings, or a previous exit funding the early build. You should skip it if your product is far enough along that seed investors will take you seriously without pre-seed milestones to point at.

Most first-time founders shouldn't skip pre-seed. Here's why.

Pre-seed money is cheap relative to what it buys you: the right to make mistakes. You'll need 6 to 12 months of unstructured exploration to find out whether your assumptions hold. Without pre-seed capital, you're doing that exploration while running out of personal savings, which warps your decisions. With pre-seed, you can run real experiments and kill the bad ones early.

There are three founder profiles who reasonably skip pre-seed:

Repeat founders with credibility. If you've returned capital before, seed investors will fund you on a slide deck. You don't need to prove the same things again.
Founders with deep personal runway. Two cofounders with $200K saved between them, no kids, low rent: that's 18 months of runway. Bootstrap to seed.
Companies with non-VC capital available. Revenue-based financing, grants, or strategic customer prepayments can substitute for pre-seed if your model supports it.

If none of those describe you, raise the pre-seed. The dilution cost is real but bearable. The optionality you buy is worth it.

How do you know when you're ready for each round?

You're ready for pre-seed when you have a working prototype, a clear founder story, and at least 30 customer interviews that point to a real problem. You're ready for seed when you have early product-market fit signals: consistent organic growth, retention curves that flatten, and unit economics that pencil out at scale.

A practical readiness checklist looks like this.

For pre-seed readiness:

You can describe your customer in one specific sentence
You've talked to 30+ potential users and have notes to prove it
You have an MVP or prototype people can actually click
You can name three things your product does and three it doesn't
You have a 12-month plan with milestones, not just a vision

For seed readiness:

You have $10K+ MRR (or $100K+ ARR for B2B) with clear growth
Your monthly cohort retention curves are flattening, not crashing
You can point to one acquisition channel that works repeatably
You can articulate your unit economics with real numbers
You have a 24-month plan and a Series A milestones target

If you're between these checkpoints, you're between rounds. Investors will either tell you "come back when you have X" or offer you a bridge. Bridge rounds (extending a previous round at the same terms) are common and not a sign of failure. They're a sign you need more time, which is normal.

For founders still figuring out where they sit, browsing free planning tools at foundra.ai/tools/ or running through a structured validation framework can help clarify which stage you're actually at, instead of optimizing for the round you wish you were ready for.

Key takeaways

Pre-seed funding is $250K to $1.5M, raised before traction, to build an MVP and find early signal. Investors bet on the team and thesis.
Seed funding is $2M to $6M, raised after early traction, to find product-market fit and prepare for Series A. Investors bet on the data.
Dilution at each stage typically runs 10% to 18% pre-seed and 15% to 25% seed. The percentages overlap; the dollar values don't.
Most first-time founders should raise pre-seed first. It buys the time you need to make mistakes without burning personal savings.
The label matters less than the milestones. Define what you need to prove in the next 18 months, calculate the burn, and that's your round size.
Bridge rounds are normal. If you're between stages, extending your existing round is often smarter than forcing a premature seed.

Frequently asked questions

How much equity do you give up in a pre-seed round?

Pre-seed founders typically give up 10% to 18% of their company. The lower end (10% to 12%) is common when you're raising under $500K from angels or a single pre-seed fund. The higher end (15% to 18%) shows up when multiple investors lead at a lower valuation.

Can you raise a pre-seed and a seed from the same investor?

Yes, but most pre-seed funds don't lead seed rounds. They'll participate in the seed (sometimes called "follow-on") to maintain ownership, but a different lead VC usually takes the seed. This is by design: pre-seed funds optimize for early-stage portfolio construction, not for writing $2M checks.

Do you need revenue to raise a pre-seed?

No. Most pre-seed rounds close before any revenue exists. What you do need is evidence that you understand the problem deeply, a working prototype or MVP, and a credible team. Some pre-seed investors will fund pure idea-stage companies, but it's getting rarer in 2026.

Is a pre-seed round dilutive?

Yes. Any equity round dilutes existing shareholders. Pre-seed typically dilutes founders by 10% to 18% in total. Convertible notes and SAFEs delay the dilution math until the next priced round, but the dilution still happens, often at a discount to the next round's price.

What's the difference between pre-seed and a friends-and-family round?

A friends-and-family round is usually $25K to $250K from people who know you personally and aren't professional investors. A pre-seed round is usually $250K to $1.5M and includes at least one institutional investor (an angel syndicate, a pre-seed fund, or a micro VC). The structures are similar; the participants and check sizes are not.

How long does it take to raise pre-seed vs seed funding?

A typical pre-seed round closes in 4 to 12 weeks once you start pitching seriously. A typical seed round takes 3 to 6 months, with more diligence, more meetings, and more references. If your fundraise is dragging past those windows, it's usually a sign your story or your numbers need work, not that the market is slow.

Can I raise both pre-seed and seed in the same year?

It's possible but unusual. Most founders raise pre-seed, spend 12 to 18 months hitting milestones, and then raise seed. Closing both rounds in the same year usually means either your pre-seed was too small (you ran out of runway faster than planned) or your traction took off so fast that you preempted the seed. The first is common. The second is rare.

How to Write a Monthly Investor Update (Founder's Guide)

Spencer Claydon — Thu, 21 May 2026 15:11:32 +0000

You raised. Congratulations. Now the part nobody warned you about: your investors expect a monthly update, and the first one is due in about three weeks.

Here's the thing. Most first-time founders treat the monthly investor update like a school report card. Wrong frame. The update is a tool. Used well, it gets you intros, hires, customer leads, and a smoother next round. Used badly, it makes your investors quietly downgrade you on their internal mental rankings.

This guide covers what to put in a monthly investor update, what to leave out, the exact structure that works, and how to use the update as leverage instead of just compliance.

What is a monthly investor update?

A monthly investor update is a short, structured email founders send to their investors every month, covering progress, metrics, asks, and lowlights. It's the most consistent communication channel between a founder and their cap table, and it's how investors decide whether to lean in, stay neutral, or quietly write you off.

Pre-seed and seed investors typically expect monthly cadence. Series A and later, monthly is still standard. Some founders try quarterly. Don't. Quarterly is what you send when you don't want to be helped.

The format runs 400 to 900 words, lives in an email body (not an attachment), and gets sent on the same day each month. Most founders pick the first business day of the month, covering the previous month.

Why do investors actually want monthly updates?

Investors want monthly updates for three reasons, and only one of them is the one they tell you about.

The stated reason: portfolio tracking. They have 20 to 60 companies and need a thin slice of signal to know which ones are alive, struggling, or breaking out.

The second reason: pattern matching. Seeing your numbers month over month, they spot patterns you can't. A flat CAC for three months while revenue grows means something. A founder who keeps moving the goalposts on what counts as a "win" means something else.

The third reason, and this is the one that matters for you: warm-loop fundraising. When you go to raise your next round, your existing investors get pinged by other VCs doing diligence. If your monthly updates have been sharp, clear, and consistent, your existing investors will pitch you to the new ones. If your updates have been late, vague, or absent, you'll be on your own. The seed-to-Series-A conversion rate sits around 27% in 2024 data from Carta. Updates don't fix a bad business. They absolutely move the needle for a borderline one.

What should you include in a monthly investor update?

A good monthly investor update has six sections, in this order: TLDR, metrics, highlights, lowlights, asks, and runway. Skip any of these and the update loses 80% of its usefulness.

Here's the rough word allocation: TLDR 30 words, metrics 100 words, highlights 200 words, lowlights 150 words, asks 100 words, runway 50 words. That's 630 words for a clean update. Add product news or hires if relevant.

TLDR (top of email)

Three sentences. State the month's headline, the headline metric, and whether things are tracking ahead, on, or behind plan. Example: "April was our strongest month: $42K MRR (up 18% MoM), broke even on paid acquisition for the first time, hired our second engineer. Tracking ahead on revenue, behind on enterprise pipeline."

Investors read the TLDR. Some only read the TLDR. Front-load.

Metrics

The same metrics every month. Same definitions. Same order. Pick five to eight numbers tied to your business model and stick with them. For B2B SaaS that's usually MRR, new MRR, churned MRR, net new logos, CAC, payback period, cash balance, months of runway. For consumer it might be weekly actives, retention curves, contribution margin per user, cash, runway.

The discipline of not changing the metric set is the point. Switching from MRR to "annualized run rate" the month MRR drops is a tell that investors clock immediately.

Highlights (what went well)

Two to four bullets. Specific. With numbers. "Closed Acme Corp, our largest contract to date ($28K ARR)" beats "had a great sales month." Name customers if you have permission. Name new hires by role and start date. Mention product launches with usage numbers, not feature lists.

Lowlights (what went wrong)

Two to four bullets. Specific. With your read on root cause and what you're doing about it. "Lost our second-largest customer (ChurnCo, $9K ARR). Root cause: we deprioritized their integration request for two quarters. Fix: hired an account exec starting May 15 and committed to a quarterly customer health review."

This is the section that separates real updates from theater. Investors trust founders who name lowlights specifically. Vague hedging ("some sales challenges this month") makes everyone uneasy. Naming the problem and the response, even if the response is incomplete, builds credibility.

Asks

Three asks maximum. Specific. Named. "Intros to: (1) Head of Eng at a Series B fintech for our open senior backend role, (2) anyone running RevOps at a 50-200 person SaaS company for our beta program, (3) lawyer recommendation for a UK entity setup."

Vague asks ("let us know if you have any intros") get nothing. Named asks get replies the same day.

Runway

One line. "$640K in the bank, 11 months of runway at current burn ($58K/month), starting next raise conversations in September." That's it. Don't bury this. Investors want to know how worried to be.

What should you leave out of an investor update?

Leave out: hedge language, screenshot collages, attached decks, generic startup quotes, "exciting milestones ahead," personal life updates, and any metric that you've never sent before and won't send next month.

The phrase "lots of exciting things in the pipeline" should be illegal. If something is exciting, it's either closed (highlight) or it's a specific ask (intros to close it). The pipeline is not progress.

Also leave out: every product feature. Investors don't care about feature lists. They care about whether the feature changed a number. "Shipped SSO in March: enterprise pipeline went from 2 to 7 deals" is signal. "Shipped SSO, dashboards, and CSV export" is noise.

How long should a monthly investor update be?

A monthly investor update should be 400 to 900 words in an email body, readable in under three minutes. Longer than that and investors skim. Shorter than 400 and you're probably hiding something.

Email body, not PDF. PDFs don't open on phones cleanly, can't be forwarded as easily, and signal more formality than the update warrants. The exception: include a single linked dashboard or a Google Doc if you want to give investors deeper-dive access for nerd-out sessions. Most won't click. The ones who do are your most engaged.

Don't use a tool that forces investors to log in to see your update. Visible.vc and similar tools are convenient for the founder, inconvenient for the investor. If it adds friction, it loses readership. The boring move (plain email) wins.

When should you send the update?

Send the update on the same calendar day every month. Most founders pick the 1st, 2nd, or 3rd business day, covering the previous full month. Consistency matters more than the specific date. Investors who get your update on the 1st of every month will subconsciously trust you more than founders whose update lands on the 12th, then the 4th, then the 19th.

If you miss a month, do not skip it. Send the missed month plus the current month together, with a short note at the top: "Combining March and April updates since I dropped the ball in early April. Here's both months."

Missing a month and then sending nothing is the worst signal in early-stage investing. It's how investors find out a company died: they realize they haven't gotten an update in four months.

How do you write the first investor update after a round closes?

Your first monthly investor update post-close should explain what the money is for, what milestones it's meant to hit, and the metric that will signal you've hit them. Frame it as a public commitment to the goals you pitched.

Example opener: "First update post-raise. We closed $1.4M on March 22. Plan: hire two engineers and one growth lead by end of Q2, ship the enterprise tier by July, double MRR to $80K by Q4. This update covers two weeks of post-close work, future updates will be monthly on the 1st."

This framing matters because it lets investors hold you accountable in a structured way, which they want. The founders who hide from accountability are the ones investors stop helping.

If you're early in the planning phase, you can map this out the same way you'd map a 90-day plan in a spreadsheet, Notion, or a structured planning tool like Foundra that walks first-time founders through milestones and the metrics that prove them out. The point is not the tool. It's that you've actually written down the plan in a form your investors can hold you to.

What's a good monthly investor update template?

Here's a stripped-down template you can copy. Sub in your own numbers and details.

Subject: [Company] Investor Update : April 2026

TLDR: April was [headline]. Hit [main metric], [tracking vs plan]. Top ask: [most important ask].

Metrics (vs March):

MRR: $X (+Y% MoM)

New MRR: $X

Churned MRR: $X

Net new logos: X

CAC: $X (payback Z months)

Cash: $X (Y months runway)

Highlights:

[Specific win with number]

[Customer or hire with name]

[Product launch with usage stat]

Lowlights:

[Specific problem, root cause, fix]

[Specific problem, root cause, fix]

Asks:

Intro to [specific role at specific company type]

[Specific operational ask]

[Specific advisor or hiring ask]

Runway: $X in bank, Y months at current burn ($Z/month). Next raise conversations starting [month].

That's the entire template. Use it for 24 months and you'll have one of the cleanest founder communication trails in your investors' inboxes.

Key takeaways

The monthly investor update isn't paperwork. It's the highest-leverage 30 minutes of your month if you treat it that way.

Send it the same day every month. Lead with a TLDR. Use the same metric set every time. Name specific lowlights and what you're doing about them. Ask for three specific things, not vague support. Tell people your runway without hedging.

Investors who get crisp monthly updates lean in. They make intros, share the update with co-investors, and tell other VCs you're a founder worth backing when your next round comes. Investors who get vague or absent updates do none of those things. The difference is 30 minutes a month and a willingness to be specific about your lowlights.

You can find structured templates for founder planning at foundra.ai/tools/ if you want a starting point, but the update itself should be in plain email. Don't outsource the writing. The voice in the update is part of what investors are evaluating.

FAQ

How often should I send investor updates?
Monthly, on the same calendar day every month. Pre-seed and seed investors expect monthly cadence. Quarterly is too infrequent for an early-stage company where situations change month to month.

Who do I send the update to?
All check writers plus any advisors or angels who explicitly asked to be included. Use BCC, not CC, so investors don't accidentally reply-all. Most founders also include a "forward freely" line so investors can share with relevant co-investors.

Should I include financials in every update?
Yes. At minimum: cash balance, months of runway, and your headline business metric (MRR, GMV, weekly actives, whatever fits your model). Investors who can't see those numbers will assume the worst.

What if I have a really bad month?
Send the update anyway, on time, with specifics. Frame the bad news directly: "April was our worst month in 8 months. Here's what happened, here's what we're changing." Investors respect direct framing. They don't respect silence or spin.

Should I use a tool like Visible.vc or just send email?
Email body, almost always. Tools that require login add friction and reduce open rates. The exception is if your cap table has 30+ investors and you need centralized read tracking, in which case Visible or DocSend can help.

Can I skip the lowlights section if everything went well?
No. Even in a great month there's something that didn't go well: a missed hire, a customer almost-churn, a slipped product date. Naming the small stuff builds the credibility you'll need when something big goes wrong.

How to Calculate Startup Valuation (Pre-Seed & Seed Guide)

Spencer Claydon — Wed, 20 May 2026 19:28:02 +0000

How to Calculate Startup Valuation (Pre-Seed & Seed Guide)

The first time someone asks what your startup is worth, your brain freezes. You haven't sold anything. You have a deck, a half-built MVP, maybe a few hundred signups from your landing page. There's no obvious answer. But you still need one, because the moment a check shows up, you'll be negotiating a number that affects your dilution, your runway, and how the next round prices.

This is how to calculate startup valuation when you're early, with no revenue or maybe a few thousand dollars of MRR. I'll walk through what valuation actually means, the five methods investors use at the seed and pre-seed stage, how to come up with a defensible number, and the negotiating dynamics that actually decide the final figure. You won't need a CFA. You will need to understand the math well enough to push back when a term sheet feels off.

What is startup valuation, and why is it different from a public company?

Startup valuation is the dollar value placed on your company at the moment of an investment. It's not a market-derived number. Public companies trade on quarterly earnings, comparable multiples, and millions of transactions a day. A pre-seed startup with no revenue has none of that, so the number gets negotiated between you and the investor based on traction, team, market, terms, and dealflow.

That's the part most first-time founders miss. Your valuation isn't an objective truth. It's a negotiated price that reflects how much an investor wants to own a piece of your future cash flows, and how much you're willing to dilute to get the capital. Two founders with identical companies can walk into the same fund and come out with different valuations because one of them ran a competitive process and the other didn't.

Worth knowing: at the pre-seed and seed stage, valuation is mostly about ownership percentage. An investor wanting 10% of a company will price the round so they get 10%, then back into the number. That's why "valuation" and "round size" are linked, and why you can't change one without the other.

What are the most common startup valuation methods?

The most common startup valuation methods at the early stage are the Berkus method, the Scorecard method, the Risk Factor Summation method, the Venture Capital method, and comparables (also called comps). Each one is a different lens on the same problem, which is how to put a price on a company that has more story than spreadsheet.

Here's the working version of each, in plain English.

Berkus method. Assign up to $500K of value across five categories: sound idea, prototype, quality management team, strategic relationships, product rollout. The cap under this method is $2.5M. It's a sanity check, not a real pricing tool, but it forces you to inventory what's actually there.

Scorecard method. Find recent local seed rounds (say, eight to ten) and average their pre-money valuations. Then adjust up or down based on how your team, market, product, competition, and traction compare. If the local average is $4M and your team is significantly stronger than average, you might end up at $5M to $5.5M. This is the method most angel groups actually use.

Risk Factor Summation. Start with a baseline (the local average pre-money), then adjust up or down by $250K for each of twelve risk categories: management, stage of business, legislation, manufacturing, sales, funding, competition, technology, litigation, international, reputation, and exit. Lower risk than average pushes the value up. Higher risk pulls it down.

Venture Capital method. Work backwards from a projected exit. If you think the company can exit for $200M in seven years, and the investor needs a 10x return on their seed check, they'll want their stake to be worth $50M at exit. That dictates the percentage they need now, which dictates the valuation.

Comparables. Look at recently-funded startups in your space, at your stage, and use their pre-money valuations as the anchor. Crunchbase, Pitchbook, and AngelList have enough public data to triangulate.

In practice, investors run two or three of these in parallel and triangulate. You should too, before you walk into any pitch meeting.

How do you value a pre-revenue startup?

To value a pre-revenue startup, you start with the comparables for your geography, sector, and stage, then adjust based on team quality, traction signals, and market size. There's no formula. There's a defensible range, and your job is to land at the high end of that range without breaking the deal.

Let me make this concrete. Say you're a pre-revenue B2B SaaS startup based in the US in 2026. Recent US seed-stage SaaS deals have been pricing around a $6M to $10M pre-money. If your team has one ex-FAANG engineer and one founder with domain experience, you have a working prototype, and 200 people signed up to your beta waitlist, you're probably in the $7M to $9M range. No traction beyond the waitlist? Closer to $6M. Letters of intent from three Fortune 500 companies? Closer to $10M, possibly above.

The traction signals that move the number, in rough order:

Paying customers (even one)
Signed letters of intent
A working product with active weekly users
A beta waitlist with verified emails
A previous exit by one of the founders
A pedigreed team (FAANG, top accelerator, prior startup operator)
Coverage in industry press

What doesn't move the number, despite what founders think: the size of your TAM in isolation, the cleverness of your idea, a 60-slide deck, or how long you've been thinking about the problem. Investors discount all of those to near zero.

For pre-revenue startups raising on SAFEs or convertible notes (which is most of them at pre-seed), you don't even set a true valuation. You set a valuation cap, which is the maximum valuation at which the SAFE converts into equity at the next priced round. That cap is the number you negotiate. A $5M cap on a SAFE means the investor's money converts as if the company were worth $5M, even if the next round prices at $15M.

What's the difference between pre-money and post-money valuation?

Pre-money valuation is the value of your company before the investor's money is added. Post-money valuation is the value after. The simple equation: post-money equals pre-money plus the amount raised.

Example. You raise $1M on a $4M pre-money valuation. Post-money is $5M. The investor's $1M divided by the $5M post-money equals 20% ownership. You and your team own the remaining 80%.

This matters because investors and founders sometimes talk past each other. An investor says "I'll do $1M at $5M" without specifying pre or post. Those are two different deals. If $5M is pre-money, the investor gets 16.7% ($1M / $6M post). If $5M is post-money, the investor gets 20% ($1M / $5M). On a $1M check, that's a 3.3% difference in ownership for you, which compounds painfully across future rounds.

A few notes worth memorizing:

Most US seed term sheets in 2026 quote pre-money by default.
Most YC-style post-money SAFEs do exactly what the name says: they cap the post-money, so the dilution is fixed regardless of how much else gets raised on the same note structure.
Always ask "is that pre or post?" the first time a number comes up. Founders who skip this end up signing surprise dilution.

How do investors actually decide your valuation?

Investors decide your valuation based on the percentage of your company they need to own to make the fund math work, the dealflow they're seeing this quarter, and how competitive your round is. The valuation methods are a justification layer on top of those three factors, not the deciding input.

Fund math first. A typical seed fund needs to return at least 3x to its LPs. If the fund is $100M and one home-run exit produces $50M of that, the fund needs to own enough of that company to write $50M out of an outcome. That math sets the minimum ownership a fund will push for, usually 8% to 12% at the seed stage. Below that, the fund can't move the needle even if your company is a winner.

Dealflow next. If a fund is seeing 200 deals a month and writing four checks, they have leverage on price. If you're a hot deal with three other term sheets in hand, the leverage flips. A real competitive process, three or four credible firms moving in parallel, can lift your valuation by 30% to 50% over the same round without competition.

Competitive dynamics third. This is the founder lever. You can't change fund math. You can build a process. The way to do that: line up first meetings with ten to fifteen firms in a two-week window, get them on the same decision timeline, and let the natural pressure of FOMO do the rest. Founders who pitch one firm at a time always take worse terms.

What investors say out loud is the methods. What they're actually doing is solving for ownership at a price the market will bear.

What's a realistic valuation for a first-time founder?

A realistic valuation for a first-time founder raising pre-seed in 2026 is $4M to $8M pre-money in the US, $3M to $6M in Europe, with significant variance by sector. For a priced seed round with a working product and some early revenue or strong design partners, the band is $8M to $15M pre-money.

The honest part: first-time founders take a discount versus repeat founders. A founder who exited their last company for $80M can raise at $12M pre-money on a deck and a vision. A first-time founder with the same deck and vision raises at $5M, if at all. The discount narrows as you build evidence. A working product narrows it. Paying customers narrow it more. A high-quality co-founder with relevant domain experience narrows it. Pre-seed valuations are mostly a function of perceived execution risk, and first-time founders carry more of that risk by default.

A few practical guardrails:

Don't anchor on the headline numbers you see on TechCrunch. Those are post-money totals from priced rounds, often after the company has $1M+ ARR. Your pre-seed reality is different.
Don't optimize for the highest possible valuation. Optimize for a price that lets you raise the next round at a step-up. A pre-seed at $15M sets a brutal bar for seed.
Don't agree to a number without modeling the cap table forward through Series A. You want to own enough at Series A to still have founder skin in the game for Series B and C.

A clean cap table at seed (founders 60-70%, ESOP 10-15%, investors 15-25%) is what makes the next round possible. Foundra's financial modeling and cap table planning walks first-time founders through this exact exercise alongside tools like Carta and Pulley, so the number you negotiate makes sense across the whole funding path, not just one round. You can also pull in free calculators from foundra.ai/tools/ to sanity-check your runway, burn, and dilution before you sit across from a check writer.

What mistakes do first-time founders make on valuation?

The most common valuation mistakes first-time founders make are anchoring too high, accepting bad terms in exchange for a headline number, and treating the cap table like an afterthought. Each one quietly kills the next round before you even start it.

Anchoring too high. Founders see a Twitter screenshot of a $20M pre-money pre-seed and decide that's the floor. It isn't. The Twitter screenshot is survivorship bias. For every loud high-valuation deal, there are fifty quiet ones that priced at half that. If you walk into pitches asking for $15M pre on a prototype, most investors will pass without telling you why. They don't want to spend the meeting talking you down.

Trading clean terms for a headline number. A 2x liquidation preference on a $10M valuation is a worse deal than a 1x non-participating preference on $6M. Liquidation preferences, anti-dilution clauses, pro-rata rights, board seats, founder vesting cliffs, all of these matter. A high valuation paired with founder-unfriendly terms is how founders end up owning a sliver of their own exit. Read the term sheet alongside the number.

Treating the cap table as paperwork. The cap table is the most consequential spreadsheet in your company, full stop. If you give 5% to your first advisor casually, give 10% to a friend who helped with the deck, and take a $300K SAFE at a $2M cap because that's what your uncle offered, by the time you're raising a real seed round you've already diluted yourself to 50%. Investors at Series A see that and walk. They want founders with enough ownership to stay motivated through eight more years of work.

Key takeaways

A few things to lock in before you start the next pitch.

Valuation isn't an objective number. It's a negotiated price reflecting ownership math, dealflow, and competitive dynamics. Methods like Berkus, Scorecard, VC method, and comparables are how the number gets justified, not how it's truly decided.

Pre-revenue startups should triangulate from comparable rounds in their sector and geography, then adjust for team, traction, and risk. Pre-seed founders in the US in 2026 are mostly raising in the $4M to $8M pre-money range. SAFEs use a valuation cap, not a fixed valuation.

Pre-money plus the round size equals post-money. Always confirm which one a term sheet quotes. The difference compounds.

Investors are solving for ownership percentage that makes their fund math work. The methods justify the number they already had in mind. Your leverage comes from running a competitive process and proving traction signals investors actually care about: paying customers, LOIs, beta users, team pedigree.

First-time founders take a discount. Earn it back with execution evidence, then negotiate hard once you have leverage.

Don't optimize for the highest possible valuation. Optimize for one that allows a clean step-up at the next round.

FAQ

How do I calculate my startup's pre-money valuation?
Find recent comparable seed rounds in your sector and geography (Crunchbase, Pitchbook, AngelList), take the median pre-money, then adjust up or down based on team quality, traction, and market signals. A scorecard-style adjustment of plus or minus 20% to 30% is normal. Cross-check with the VC method by working backwards from a credible exit scenario.

What's a typical pre-seed valuation in 2026?
US pre-seed pre-money valuations are mostly $4M to $8M. The variance is driven by sector, founder pedigree, and traction. SaaS and AI categories run higher. Hardware and consumer run lower. Pre-revenue with no prior exits anchors at the low end of the range.

Can I value my startup without revenue?
Yes. The Berkus method, Scorecard method, and Risk Factor Summation are designed for pre-revenue startups. None give a precise answer. They give you a defensible range to enter a negotiation with. Most pre-seed founders raise on SAFEs with a valuation cap, which sidesteps the precise number question.

What's the difference between a valuation cap and a valuation?
A valuation is the actual price set in a priced equity round (a Series Seed or Series A). A valuation cap is the maximum valuation at which a SAFE or convertible note converts at the next priced round. Caps are common at pre-seed because they let you raise quickly without setting a price.

How much should I raise at pre-seed?
Most US pre-seed rounds are $500K to $2M. The sizing should give you 18 to 24 months of runway to hit clear seed-stage milestones (usually $20K-$30K MRR, or a working product with measurable usage, or LOIs from real customers). Work backwards from milestones to decide the check size, then the valuation follows.

Should I raise on a SAFE or a priced round at pre-seed?
Most first-time founders should raise on post-money SAFEs at pre-seed. They're fast, cheap (no lawyers needed for closing), and the dilution math is predictable. Priced rounds make sense once you're raising $3M+ or have institutional leads who want board seats. The threshold has crept up. Pre-seed priced rounds are rare in 2026.

How to Write a Positioning Statement for Your Startup

Spencer Claydon — Tue, 19 May 2026 15:11:11 +0000

Most first-time founders confuse positioning with branding, messaging, or a clever tagline. It's none of those. Positioning is the strategic choice you make about who you serve, what you replace, and why anyone should care. Everything downstream works better when the positioning underneath is sharp. And it usually isn't.

This is the piece you write before the marketing plan. Get it wrong and you spend a year tweaking funnels that were never going to work. Get it right and a lot of things you've been forcing suddenly click.

Here's the practical version. Templates, examples, and the mistakes I keep watching founders make.

What is a positioning statement, really?

A positioning statement is a one-paragraph answer to four questions: who is this for, what is it, what are they using now, and why is yours different in a way that matters. That's it. It lives on a Notion doc, not your homepage.

The classic Geoffrey Moore template from Crossing the Chasm still works:

For [target customer] who [statement of need], our [product category] provides [key benefit]. Unlike [primary competitor or alternative], our product [primary differentiator].

It looks academic, and that's the point. The discipline is in filling each blank with something specific and provable. Your customers will never read this sentence. You will read it every week for a year.

Confusing it with a tagline is the most common mistake. A tagline is a hook. A positioning statement is a strategic document. Stripe's tagline is "Payments infrastructure for the internet." Their internal positioning almost certainly answers things like "compared to PayPal" and "for developers who hated dealing with banks." Those words don't show up on the homepage, but they shaped every product decision.

Why does positioning matter so much for first-time founders?

Positioning matters because it's the lens every other decision passes through, and first-time founders almost always skip it. April Dunford, who literally wrote the book on this (Obviously Awesome), found that most weak product launches trace back to a positioning problem, not a product problem. The team built something useful, then described it in a way nobody understood, against the wrong alternative, for the wrong audience.

A few things shift when your positioning is tight:

You stop arguing with the wrong customers. The objections you hear sound less like "I don't get it" and more like "how do I buy this." That's the tell.

Your conversion rate goes up without redesigning the site. Same traffic, same product, sharper words on the page, more signups. I've watched this happen on landing pages where literally nothing changed except the headline and the first sentence.

Your team stops making contradictory calls. The designer, the developer, and the founder all answer "should we build feature X" the same way because they share a north star.

Hiring gets easier too. Candidates self-select. So do investors.

What's the difference between positioning, messaging, and branding?

Positioning is the strategic decision. Messaging is how you express that decision in words for different audiences. Branding is the visual and emotional wrapper around it. They are not the same thing and they get built in that order.

Here's a quick mental model. Positioning: we are the X for Y, not the Z. Messaging: depending on who's reading, here's how we say that. Branding: this is what it looks and feels like when we say it.

Build branding before positioning and you get a beautiful logo on top of incoherent strategy. Build messaging before positioning and the homepage and sales deck contradict each other.

Think of it this way. Positioning is the foundation of the house. Messaging is the framing. Branding is the paint. You can repaint in a weekend. You cannot move a foundation.

How do you actually write a positioning statement, step by step?

Block two hours. Open a doc. Fill in five sections in this order, because doing them out of order is where most founders get stuck.

Step 1: Pick your target customer, narrower than feels comfortable.

If you wrote "small business owners," try again. "Solo founders running e-commerce stores under $50K/month MRR who use Shopify" is closer. The narrower you go, the easier everything else becomes. You can always expand later. Notion famously started positioned for personal note-takers and engineers, then went wide. Slack started for engineering teams at small companies. Figma started for designers at companies where the design team felt blocked by Sketch. None of them started as horizontal everything-platforms.

If you can't picture a specific person at a specific stage of a specific kind of company, the target isn't tight enough.

Step 2: Define the "from where" alternative they're using today.

This is the question that breaks the most positioning attempts. Founders write "there's no real alternative to us" and that's almost never true. People are solving the problem somehow. With spreadsheets. With consultants. With duct tape. With nothing. With a competitor you don't want to name. Whatever it is, name it. The alternative is the comparison your customer's brain is making whether you like it or not, so make it explicit.

For a startup planning tool, the alternative isn't only LivePlan. It's also a blank Google Doc. A pile of YouTube videos. A $200/hour business coach. Or "I'll just wing it." Write down all the alternatives, then pick the one most of your buyers are coming from.

Step 3: Name your category, in plain language.

What kind of thing is this? "Strategic planning platform for first-time founders" reads differently from "AI-powered business intelligence solution." If the category sounds like a buzzword soup, your customer's brain will reject it before they finish reading.

If you're creating a new category, fine, but you still need to anchor it to something familiar. "Notion is a workspace, like Google Docs, but more flexible." That's how new categories get into people's heads, by tying back to something they already understand.

Step 4: Pick one differentiator that matters to your target customer.

Not three. One. Three differentiators is a feature list, not a position. The differentiator should be something your customer would say out loud if they were explaining you to a friend. Bonus points if your competitors couldn't credibly say the same thing.

Be honest. "Easy to use" is not a differentiator. Every product claims that. "Built specifically for solo founders who've never written a financial model before" is a differentiator, because most competitors are aimed at established small businesses with bookkeepers.

Step 5: Stitch it together using Moore's template.

Now write the sentence. Sit with it for a day. Read it out loud. If any phrase sounds like LinkedIn copy, rewrite it. Run it through three filters: is it specific, is it provable, is it ours alone? If the same sentence could describe three competitors with minor word swaps, you haven't positioned yet. You've described.

What does a great positioning statement look like in practice?

The best ones are boring on the page and sharp in the room. Here are four worked examples for hypothetical (and one real-ish) startups to show what good and bad look like side by side.

Example 1, fictional SaaS for restaurant inventory:

Weak: "BiteTrack is an AI-powered platform that helps restaurants optimize operations."

Stronger: "For independent restaurant owners running 1-3 locations who track inventory in spreadsheets and lose 4-7% of revenue to waste, BiteTrack is an inventory app that logs deliveries from photos. Unlike enterprise tech like Toast, it works in 10 minutes a day and costs less than a single shift of labor."

The strong version names the customer, the alternative (spreadsheets), the category (inventory app), and the differentiator (10 minutes a day, cheap).

Example 2, fictional B2B sales tool:

Weak: "We're an AI-powered sales acceleration platform for modern teams."

Stronger: "For two-person founder-led sales teams selling B2B SaaS in the $1K to $5K monthly ACV range who can't justify a full Salesforce stack, our tool combines lightweight CRM and outbound sequencing for $79/month. Unlike HubSpot Starter, we don't make you upgrade to access basic features."

Example 3, your startup planning tool category:

Weak: "Foundra is the leading planning solution for entrepreneurs."

Stronger: "For first-time founders who have an idea but don't know where to start, Foundra is a strategic planning platform that walks you through 15 investor-ready deliverables, from validation to go-to-market. Unlike LivePlan, which is built for SMB owners writing bank loan applications, Foundra is built for the founder figuring out if the idea is real before they ever pitch anyone."

Notice the pattern. Every strong version names a specific person, a specific alternative, and one clear differentiator. None of them are clever. They're just clear.

If you're staring at a blank doc and the questions feel abstract, a tool like Foundra can walk first-time founders through the underlying validation and audience work that has to happen before the positioning statement makes sense. Notion templates, the Obviously Awesome worksheet from April Dunford, or even a focused two-hour session with a smart friend can do the same job. The format matters less than doing the thinking.

What are the most common positioning mistakes?

Five mistakes show up over and over. If you're stuck, you're probably hitting one of these.

Mistake one: positioning to "everyone." The phrase "for any business that wants to grow" is a tell. It feels safe and inclusive. It's actually a guarantee that no specific buyer will feel seen. Pick a niche, win it, expand. That's the playbook.

Mistake two: positioning against the wrong alternative. If your buyers are coming from spreadsheets but you're positioning against Salesforce, you're answering the wrong objection. The alternative is whatever your buyer was doing the day before they found you, not whoever your investors say is the competitor.

Mistake three: leading with a feature instead of an outcome. "We have a Kanban view" is a feature. "You'll stop losing track of deals on Friday afternoons" is an outcome. Customers buy outcomes. Founders sell features. Bridge the gap.

Mistake four: making the differentiator something everyone claims. "Easy to use," "intuitive," "AI-powered," "modern interface." These words mean nothing because every competitor says them. If your differentiator could be lifted onto a competitor's homepage without anyone noticing, it's not a differentiator.

Mistake five: writing it once and never revisiting. Positioning isn't permanent. As you learn more about who actually buys, who actually pays, and who actually renews, the position should sharpen. Most founders write a positioning statement at month three and never look at it again, even when the customer base has shifted by month nine. Block 30 minutes every quarter to reread and edit.

How do you test if your positioning is working?

Five quick checks you can run this week.

Show your positioning statement to five customers who already bought. Ask: does this describe what you bought? If three or more pause, you're describing something different from what they're paying for. That's a problem.

Show your homepage headline to a stranger for five seconds, then take it away and ask what the product does. If they can't repeat it back roughly, your positioning isn't reaching the surface yet.

Track your sales call objections for two weeks. If the same objection keeps showing up, your positioning isn't preempting it. Adjust the statement, then adjust the website.

Measure your demo-to-trial or trial-to-paid rate against a control. A sharper position usually moves these numbers within a month. If nothing changes, you may have rewritten the words without rewriting the strategy underneath.

Ask three friendly competitors' customers what made them pick that other tool. The answer is your positioning gap.

Should your positioning statement appear on your website?

No, not as written. The positioning statement is an internal document. The website is the messaging derived from it.

Your website headline is one expression of the positioning. Your cold email is another. Your sales deck is another. They all reference the same underlying truth, but they're tuned for the audience reading them. A homepage talks to a cold visitor in 8 seconds. A pricing page talks to a curious evaluator. A sales call talks to someone with 20 minutes and questions. The positioning underneath is constant. The words on top are not.

So write the positioning statement first. Use it as a north star. Then write the homepage. Then write the email. Then write the deck. In that order.

Key takeaways

Positioning is a strategic decision, not a tagline. It lives on a doc, not your homepage.

The Moore template is still the cleanest starting point: for [customer] who [need], our [category] provides [benefit]. Unlike [alternative], we [differentiator].

Pick your target customer narrow enough that you can describe them as a specific person at a specific stage. "Small business owners" is not narrow. "Solo Shopify founders under $50K MRR" is.

Name the real alternative your customer is using today, not the one your investors think you compete with.

Pick one differentiator, not three. If a competitor could say the same thing, it's not a differentiator.

Revisit it quarterly. Positioning sharpens as you learn who's actually buying.

FAQ

How long should a positioning statement be?
One paragraph, two to four sentences. If you can't say it in that space, you don't have one yet. The work isn't to write more, it's to choose what to leave out.

Is positioning the same as a value proposition?
No. Positioning is the strategic frame: who you serve, what you replace, what's different. A value proposition is one expression of that, tuned for a specific audience or page. Positioning is the source, value props are the output.

How often should I rewrite my positioning statement?
Set a quarterly review, even if it's just 30 minutes. Most rewrites are minor word changes. Major rewrites happen when you learn that the actual buyer is different from the assumed buyer, which happens to almost every startup at least once.

Do I need a positioning statement if I'm pre-product or pre-revenue?
Yes, more than ever. Without one, you can't write a landing page, run an ad, or have a coherent sales conversation. The first draft will be a hypothesis. That's fine. Test it.

Can AI write my positioning statement for me?
It can give you a draft, and the draft will sound fine on first read. It won't make the strategic choices for you: who you're for, what you're against, why anyone cares. Those decisions require talking to real customers and making real trade-offs. Use AI to wordsmith, not to decide.

What if my positioning changes after launch?
Expected. Pivot the statement when the data tells you to, not when a board member says you should expand. The statement is a hypothesis you sharpen over time, not a vow.

If you want a structured walkthrough alongside the rest of your strategic plan, foundra.ai/tools/ has free resources for early-stage founders. The work is the same either way: pick your customer, name your alternative, choose your difference. Then go test it.

How to Build a Startup Roadmap (Founder's Guide)

Spencer Claydon — Sun, 17 May 2026 15:09:36 +0000

Most first-time founders skip the roadmap entirely, then crash into the same wall around month four. They've shipped the MVP, the launch went fine, and now nobody on the team knows what the next 90 days look like. Engineering is building two things in parallel that shouldn't ship together. Sales is promising a feature that's not on the calendar. The founder is reacting to whoever yells loudest in Slack.

A startup roadmap fixes that. Not the 40-tab spreadsheet you saw at your old corporate job. A real one. Short. Honest about uncertainty. Built so you can change it without throwing the document away.

Here's how to put one together that you'll actually use.

What is a startup roadmap?

A startup roadmap is a single document that shows what you're building, when, and why, across a defined time horizon. It connects company strategy to weekly execution. For an early-stage startup, this usually means three to six months out, not three years.

The point isn't to predict the future. It's to make trade-offs visible. Every roadmap is a list of things you're choosing to do and, by implication, a longer list of things you're choosing not to do. That second list matters more than the first.

A useful startup roadmap has four properties. It fits on one screen. It ties every item to an outcome, not just an output. It marks which items are committed versus exploratory. And it gets reviewed on a fixed cadence, usually every two weeks.

Why do most first-time founders avoid building one?

Most first-time founders avoid building a roadmap because it feels premature. You only have three engineers. You're talking to customers daily. Plans change every week. So writing things down feels like fake corporate ceremony.

That instinct is half right. The mistake is confusing the artifact with the practice. The artifact (a Gantt chart, a Notion page, a Jira filter) doesn't matter much. The practice (forcing yourself to write down the next 90 days before you start coding) is the thing that prevents wasted months.

I've watched seed-stage teams spend six weeks on a feature nobody asked for because nobody made anyone defend it on paper first. The roadmap is the place that defense happens.

What are the parts of a startup roadmap?

The parts of a startup roadmap are: a strategic anchor, time horizons, themes, initiatives, and a clear owner per initiative. That's it. Skip any of these and the document collapses into a wishlist.

The strategic anchor is one sentence that explains what the company is trying to prove or achieve in the current period. Examples: "Get 100 paying customers in the design-agency vertical by end of Q3," or "Reduce activation time from 11 minutes to under 4 by mid-summer." That sentence sits at the top of the roadmap. Every initiative below it should obviously connect.

Time horizons split the roadmap into rough buckets. For an early-stage startup, three buckets are plenty: Now (this 4-6 week sprint cycle), Next (the cycle after this one), and Later (4-12 weeks out, still fuzzy). Skip the "Someday" bucket. Someday is where good ideas go to rot.

Themes group related initiatives so the team can see priorities at a glance. Common themes for early-stage companies are Growth, Retention, Onboarding, Reliability, and Monetization. Three to five themes is plenty. If you have ten, you don't have themes, you have chaos.

Initiatives are the actual things you'll build or ship. Each one needs a name, a brief description of the outcome it produces (not the feature itself), an owner, and a rough size estimate (small, medium, large is fine, no need to pretend you can estimate in days).

What time horizons should a startup roadmap cover?

A startup roadmap should cover the next 90 days in detail and the following 90 days in rough strokes. Anything beyond six months is fiction at this stage, and pretending otherwise just trains the team to ignore the document.

Inside that 90-day window, build the roadmap in cycles. A six-week cycle works well for most early teams. Two weeks is too short to ship anything meaningful. A full quarter is too long before you reassess. Six weeks gives engineering room to focus, gives leadership room to course-correct, and matches the cadence Basecamp documented in Shape Up, which a lot of seed-stage teams have adopted.

The further-out half (months four through six) should be a list of themes and rough bets, not specific features. You're not committing. You're signaling intent. When the time comes, you'll re-plan based on what you've learned.

How do you choose what goes on the roadmap?

You choose what goes on the roadmap by working backward from the one outcome that matters most this quarter. Everything else competes for the leftover slots, and most ideas lose. This is the brutal part.

Start with the strategic anchor. If the anchor is "Get 100 paying customers in the design-agency vertical," then every candidate initiative has to answer a single question: does this make 100 paying agency customers more or less likely in the next 90 days?

A new analytics dashboard? Probably not. Onboarding for a non-agency vertical? No. A self-serve checkout flow that lets agencies sign up without a sales call? Yes, that goes on.

Run every candidate through three filters before it earns a slot:

Connection to the strategic anchor. If you can't draw a line from this initiative to the anchor in one sentence, cut it.
Confidence in the outcome. High-confidence bets (we know this fixes a real problem we've heard from 20 customers) get priority over low-confidence ones (we think customers might like this).
Reversibility. Cheap, reversible bets can sneak onto the roadmap on weaker evidence. Expensive, irreversible bets need much stronger justification.

You can map this thinking out in a spreadsheet, a Notion board, or a planning tool like Foundra that walks first-time founders through the strategic-anchor exercise step by step. The tool isn't the point. The discipline is.

How do you handle competing priorities and stakeholders?

You handle competing priorities by making the trade-offs visible on the roadmap itself, then forcing every stakeholder to make the case for their item in the same format. This sounds bureaucratic. In practice it takes about 20 minutes a week and prevents most of the political damage that kills early teams.

Sales wants Feature A. Customer success wants Feature B. Your co-founder wants to rebuild the auth system. You can't do all three this cycle. Instead of mediating in DMs, you require each stakeholder to fill in the same one-pager: what's the proposed initiative, what outcome does it produce, what's the evidence, what's the size estimate, what gets dropped to make room.

Now the conversation is about the trade-off, not about who has more authority. Most founders find that 60% of these requests die at the one-pager stage because the person making the request realizes they can't defend it on paper.

This is also why a roadmap with too many items is worse than no roadmap. If everything is on the list, nothing is prioritized. Cap each six-week cycle at three to five committed initiatives. Anything else goes in the Next bucket or stays in someone's notebook.

What tools should you use to build a startup roadmap?

You should use whatever tool your team already works in. The roadmap should live where your team already looks daily, not in a separate document nobody opens. For most early-stage startups that means Notion, Linear, Airtable, or a shared Google Doc.

Specialized tools (Productboard, Aha!, Jira Roadmaps) are built for companies with 30+ product people. They'll slow you down at five-person scale.

A good lightweight setup looks like this: a single Notion page or Linear project with three columns (Now, Next, Later), a strategic anchor pinned at the top, themes as page sections, and each initiative as a sub-page with the one-pager attached. Anyone on the team can read it in 60 seconds.

If you prefer something more structured, founders also use frameworks like Foundra, LivePlan, or a templated Notion workspace to keep the roadmap connected to the rest of the business plan (financials, go-to-market, competitive position). The right pick depends on whether you want the roadmap to be a standalone artifact or to live alongside your broader planning docs.

How often should you update your startup roadmap?

You should update your startup roadmap every two weeks for active items, and re-plan the whole document every six weeks at the end of each cycle. Updating less often than that means the document goes stale and the team stops trusting it.

The bi-weekly update is a 30-minute meeting. Pull up the Now column. Each owner reports: shipped, on track, slipping, or blocked. Mark initiatives accordingly. Adjust dates only if something fundamental changed, not because you slipped a week (that's noise, not signal).

The end-of-cycle re-plan is a longer session, usually two to three hours. Look back at the cycle: what shipped, what didn't, what surprised you. Then rebuild the Now column from scratch based on what you've learned. Items in the Next column get reconsidered. Some get promoted, some get cut, some get rewritten.

The Later column gets updated quarterly. That's plenty.

What are the most common startup roadmap mistakes?

The most common startup roadmap mistakes are: building one for show, overcommitting the current cycle, mixing outputs with outcomes, hiding uncertainty, and forgetting to kill items that no longer matter.

Building one for show. Founders sometimes build a roadmap because an investor asked. They share it once, then go back to whatever they were doing. The roadmap has to drive weekly decisions or it's just a document.

Overcommitting the current cycle. Capacity math is hard. Most teams underestimate how much time gets eaten by bug fixes, customer calls, sales support, and life. Plan to use 60% of nominal capacity on committed work. The other 40% covers reality.

Mixing outputs with outcomes. "Ship the new dashboard" is an output. "Increase weekly active accounts from 12 to 25" is an outcome. The roadmap should be written in outcomes, with outputs as the implementation detail underneath.

Hiding uncertainty. Roadmaps that present every item as equally confident lie to the team. Mark exploratory bets clearly. Spike, prototype, and research items belong on the roadmap, but they need a different visual treatment so nobody thinks they're a commitment to ship.

Forgetting to kill items. The reason most roadmaps balloon to 30 initiatives is that nothing ever leaves the list. Each cycle, ruthlessly remove anything that hasn't moved and isn't going to. Archive it. If it matters later, it'll come back.

Key takeaways

A startup roadmap is a single document that connects strategy to weekly execution. It should fit on one screen.

Use three time horizons: Now (current six-week cycle), Next (following cycle), Later (4-12 weeks out, fuzzy).

Anchor every roadmap to one strategic outcome for the quarter. Every initiative must obviously serve that anchor.

Cap each cycle at three to five committed initiatives. More than that and you've built a wishlist.

Write initiatives as outcomes, not outputs. "Increase activation rate to 40%" beats "Ship onboarding v2."

Review every two weeks, re-plan every six weeks. Anything less frequent and the document goes stale.

Use whatever tool your team already lives in. Linear, Notion, or a shared doc beat specialized roadmap software at early stage.

FAQ

How long should a startup roadmap be?
Short. One screen, ideally. If you can't see the whole roadmap without scrolling more than once, you've added too much. Three to five committed initiatives per cycle, organized by theme, with a strategic anchor at the top.

Should I share my roadmap with investors?
Yes, in summary form. Investors don't need every initiative. They need to see the strategic anchor, the themes for the quarter, and one or two examples of committed work. A two-paragraph version goes in every investor update. The full version stays internal.

What's the difference between a roadmap and a product backlog?
A roadmap shows what you're committed to building in the next 90 days and why. A backlog is a longer list of candidate ideas without time commitments. The backlog feeds the roadmap. Most teams confuse them, which is how you end up with a "roadmap" that's actually a 200-item Google Doc.

Do I need a roadmap before product-market fit?
Yes, but a shorter one. Pre-PMF, the roadmap is mostly about which experiments you'll run and which customer segments you'll test, not feature commitments. Six weeks of experiments, framed as outcomes (something learned, not something shipped), with the strategic anchor being "find PMF in [specific segment]."

Can I just use a Gantt chart?
You can, but most early-stage teams find Gantt charts overpromise certainty they don't have. Kanban-style Now/Next/Later columns communicate uncertainty better. If your team is heavily milestone-driven (regulated industries, hardware, deep tech) a Gantt view can work, but pair it with explicit confidence levels per milestone.

How do I get my team to actually use the roadmap?
Make every meeting reference it. Standup: which roadmap item are you working on? 1:1: how does this work map to the roadmap? Customer call debrief: does what we heard change our priorities? After three weeks of this, the roadmap becomes the team's shared mental model. Skip the references and it becomes a document nobody opens.

If you want a starting point, foundra.ai/key-reads/ has more on connecting your roadmap to financial models, go-to-market, and the rest of your planning stack. The roadmap is the operational layer. It works best when the strategy underneath it is written down too.

How to Hire Your First Employee at a Startup (Founder's Guide)

Spencer Claydon — Sat, 16 May 2026 15:11:54 +0000

You've shipped the MVP. You've got a few paying customers. The roadmap is starting to outrun your nights and weekends. So you start thinking about hiring your first real employee.

This is one of the most consequential moves a first-time founder makes. Pick wrong and you'll burn six months of runway training somebody who never quite fits. Pick right and you'll double your output and protect your sanity. Hire #1 is solvable if you treat it like a strategic decision, not a vibes call. This guide walks through when to hire, what to hire, how to pay, how much equity to grant, and how to run the process so you don't blow it.

When should you make your first startup hire?

You should make your first startup hire when there's a specific bottleneck that's costing you more than the hire will cost. The wrong trigger is "I'm tired and want help." The right trigger is "I keep delaying X because I'm doing Y, and X is the highest-impact thing in my business right now."

For most software startups, that bottleneck shows up around $5K to $15K in monthly recurring revenue, or roughly 30 to 50 paying customers. Before that you don't have the cash flow to absorb a hire without slashing your runway in half. After that you're usually drowning.

Calculate it directly. Fully loaded cost of a first hire in the US ranges from $90K to $180K per year once you include payroll taxes, basic benefits, and equipment. That's $7,500 to $15,000 a month against your burn. If your runway drops below 9 months after the hire, raise first or wait. If you'd rather pay yourself nothing than keep doing the thing you'd be hiring for, you waited too long.

What role should your first employee fill?

Your first employee should free up the thing only you can do. For a technical founder that usually means hiring a generalist on the go-to-market side. For a non-technical founder it's almost always an engineer. The pattern: if you spend 60% of your time on something a junior version of you could handle, that's the hire.

Three archetypes work for hire #1 at a pre-Series A startup.

A founding engineer who can ship features without spec'ing them. Pay range is $130K to $180K base with 1% to 2% equity at a pre-seed company. Stripe's first non-founder hire (Greg Brockman) wrote integrations and product simultaneously. Linear's early team did the same.

A founding GTM hire who runs sales, content, and customer success at the same time. Pay range is $100K to $160K base with 0.5% to 1.5% equity. They demo, write the blog, run onboarding calls, and stitch HubSpot to Stripe themselves. Notion's Akshay Kothari operated as this hire for a long time.

A founding operator who closes 80% of the operational gaps so you can keep selling and building. Think recruiting, vendor management, finance ops, customer support. Pay range $90K to $140K with 0.25% to 1% equity. Lattice and Brex both hired this role early.

If you find yourself listing three "would be nice to have" roles, the answer is usually a generalist instead of a specialist. Specialists make sense once you have something to specialize in.

Should you hire an employee or a contractor for your first role?

You should hire a contractor first if the role is shorter than 4 months, scoped tightly, or you're not sure you trust your roadmap yet. You should hire an employee if you want commitment, equity alignment, and a person who'll defend the company when it's hard. Contractors are faster to start and easier to end. Employees are more invested but cost more emotionally and financially to remove.

A useful sequence is "contract to hire." Hire someone on a 3-month contract through a platform like Deel, Toptal, or A.Team. Pay them a market rate. Treat the contract like a tryout where both sides find out if it works. Conversion rates from strong contract starts to full-time are commonly cited in the 40 to 60% range at early-stage companies.

A few rules of thumb that save founders pain.

Don't pay contractors in equity only. The IRS, state labor boards, and the contractor's lawyer will all eventually have something to say about that arrangement.

Don't classify a contractor as a 1099 if they work full-time for you, set their own hours, or take direction every day. That's an employee. Misclassification penalties in California can run $5,000 to $25,000 per violation. Run the IRS 20-factor test before you commit.

Use Gusto, Rippling, or Justworks for US payroll. Use Deel or Remote.com for international hires. Don't try to run payroll yourself. The $40 to $80 a month a PEO charges is the cheapest insurance you'll buy.

How do you find startup-ready candidates without a recruiter?

You find startup-ready candidates by recruiting from your existing network and from communities where startup-curious people already hang out. Recruiters cost 20 to 25% of first-year base salary, which means a $140K hire costs an extra $28K to $35K up front. At hire #1, that's runway you don't have. Most founders close their best first hire from a warm source.

Where to actually look.

Your past coworkers. The single highest-conversion source for early hires. Make a list of 20 people you've worked with who you've thought "I'd hire them tomorrow" about. Email them this week. Not all 20 will be available. Three to five will be open to a conversation, and one or two of those will be a real fit.

Your customers and users. Founders forget this one. The people who already love your product and have relevant skills are the highest-trust hires you'll ever make. PostHog, Linear, and Notion have all hired heavily from their user base.

Public communities. For engineers: GitHub, contributors to open source projects in your stack, the Recurse Center alumni list, and r/SideProject. For GTM: r/sales, RevGenius, Modern Sales Pros, and the founding GTM Slack channels run by Pavilion. For operators: On Deck cohorts, Lenny's Newsletter community, and the COO Alliance.

Job boards that actually work for early-stage roles. Hacker News "Who's Hiring," Wellfound (formerly AngelList Talent), Y Combinator Work at a Startup, and Lever's startup job board. Skip Indeed and ZipRecruiter for hire #1. The signal-to-noise ratio is poor at this stage.

When you publish the role, write it like a founder writing to a peer, not a corporate JD. Tell them what your first 90 days will actually look like, the three problems they'll own, the cap table truth, and the equity offer. The best candidates filter on honesty.

What should you pay your first employee?

You should pay your first employee 70 to 90% of their market base salary in cash, with the gap made up in meaningful equity. Below 70% you'll lose to a competing offer. Above 90% defeats the point of startup equity. The exact number depends on your runway and stage.

Real ranges for first hires in US startups, drawn from the 2025 Carta and Pave compensation reports.

Founding engineer (full stack, 4 to 8 years of experience): $130K to $180K base. Market rate at a Series B company is $200K to $230K. Your discount: 20 to 35%.

Founding GTM lead (account exec or growth marketer with 5+ years of experience): $100K to $160K base plus a clear variable component if revenue-tied. Market: $140K to $200K. Discount: 20 to 30%.

Founding operator (chief of staff, ops lead, BizOps hybrid): $90K to $140K base. Market: $120K to $170K. Discount: 15 to 30%.

Founding designer (product designer with 4+ years): $120K to $160K base. Market: $150K to $210K. Discount: 15 to 30%.

The cleanest framing: pay them slightly below what they'd get at a Series B company, and grant them equity that could be worth 5x to 20x more if the company works. Founders who try to underpay at hire #1 spend the next year backfilling and re-hiring. The cost of a bad first hire (search time, lost work, severance, morale tax) is conservatively 6 to 12 months of their salary. Pay close to market.

If you can't afford close-to-market, that's a signal you should raise first, not hire first.

How much equity should your first hire get?

Your first employee at a pre-seed startup should get between 0.5% and 2% in stock options, depending on seniority, role criticality, and how much cash you're paying them. Cash and equity are interchangeable to the company, not to the candidate. Lower cash, higher equity. Higher cash, lower equity.

Carta's 2025 compensation report puts the median first non-founder hire at 1% with a 4-year vest and 1-year cliff. Index Ventures' Option Plan tool, the most-used founder reference for this question, suggests these bands for a US software startup pre-Series A:

Employee 1 (founding engineer or GTM): 0.75% to 2%
Employee 2 to 3: 0.5% to 1.5%
Employees 4 to 10: 0.25% to 1%
Employees 11 to 20: 0.1% to 0.5%

A few mechanics every first-time founder gets wrong.

Use ISOs, not NSOs, if your hire is a US employee. Tax treatment is better and the candidate cares.

Set a 4-year vest with a 1-year cliff as standard. If you don't include the cliff, you can't part ways with a bad hire after 3 months without giving them 3 months of equity. The cliff exists for both sides.

Get a 409A valuation done before you grant options. Carta, Pulley, or LTSE Equity will run one for $500 to $2,000. Without it, your strike price isn't defensible and your hire will eventually have a tax problem.

Talk to your hire about the difference between options and shares, the strike price, the dilution they'll see at the next round, and what an exercise window looks like if they leave. Founders who avoid this conversation get the equity grant wrong. The transparent ones convert offers at 75%+ rates.

How do you run the interview process when you've never hired before?

You run the interview process by replacing the panel-interview ritual with a paid trial and a small number of high-signal conversations. Most founders waste hire #1 on a 6-round process modeled on companies 100x their size. You don't need that. You need three things: signal that they can do the work, signal that they want the work, and signal that you can work with them.

A process that's worked across hundreds of early-stage hires:

A 30-minute intro call. You explain the company and the role. They explain their story. Both sides leave with one question: "do I want a second conversation?"

A scoped paid trial. 6 to 16 hours of real work, paid at their market hourly rate. For an engineer, ship a small feature against the production codebase. For a GTM hire, write a cold email sequence, run a discovery call, or draft an outbound list. For an operator, take a real internal problem and write a one-page plan. This is the single most predictive step you'll run. Skip it at your peril.

A reference call with 2 to 3 people they've actually worked with, not "I knew them in college." Ask the same five questions to every reference: "What did they own?" "What did they struggle with?" "Would you hire them again?" "Who else should I talk to?" "Anything I should worry about?" The "who else should I talk to" question consistently surfaces references the candidate didn't list.

A working session on a real problem with the founder. 90 minutes. Whiteboard or shared doc. You're testing how they think, push back, and ask questions when they have incomplete information. This replaces 4 rounds of behavioral interviews and catches culture mismatches that traditional interviews miss.

If you're stuck on whether to make an offer, the answer is no. Hire #1 is a high-stakes decision and ambivalence is data.

How do you onboard your first employee so they actually stick?

You onboard your first employee by treating week one as a structured plan, not a free-form ramp. The number-one reason early hires leave in the first 90 days isn't the work. It's that they show up Monday and the founder hasn't decided what they should do. Write the plan before they sign.

A 30-60-90 day plan for hire #1 that's worked at companies like Notion, Linear, and PostHog in their early days:

Days 1 to 7. Shadow you on every customer call, sales conversation, and product decision. Get full access to every system. Document one thing they're surprised by. Ship one tiny thing (a doc, a bug fix, a customer email).

Days 8 to 30. Take over a discrete responsibility. For an engineer, own one feature end to end. For a GTM hire, own one stage of the funnel. Daily 15-minute standups. Weekly 60-minute one-on-ones where you talk about how it's going, not status.

Days 31 to 60. They're now the owner of the area you hired them for. You stop touching it day to day. They report on outcomes in your weekly meeting. Bring them to a board update or investor call so they understand the bigger picture.

Days 61 to 90. They're hiring or scoping the next person in their function. They're proposing changes to how you operate, not just executing. If by day 90 they're still asking you what to do every morning, that's a signal. Have the direct conversation.

Two more onboarding moves that compound. First, give them write access to your strategic planning workspace. Whether you're keeping plans in Notion, Linear, Foundra, or a shared doc, your first hire needs to see the financial model, the GTM plan, and the roadmap. Founders who hide the plan from hire #1 create a two-tier company that doesn't scale. Second, run a "no surprises" weekly. 15 minutes where you and the hire each name one thing you're worried about. It surfaces trust issues, frustration, and bad fits before they become resignations.

Key takeaways

Hire when the bottleneck is bigger than the cost. The right trigger is a specific, recurring blocker, not generalized exhaustion. For most software startups that means 9+ months of runway and $5K to $15K in MRR.

Hire the role that frees up the thing only you can do. Generalists beat specialists at hire #1. Founding engineers, founding GTM, and founding operators are the three archetypes that work.

Pay close to market in cash, make up the gap with meaningful equity. Pre-seed first hires typically land at 0.5% to 2% equity, 4-year vest, 1-year cliff, with cash at 70 to 90% of market base.

Skip the panel interview. Run a paid trial, two reference calls, and a working session on a real problem. The paid trial is the single most predictive signal you'll get.

Onboard with a 30-60-90 day plan you write before they sign. Day 90 should look like full ownership of the area you hired them for. Founders who skip the plan lose their first hire to a competitor within 12 months.

Frequently asked questions

Can I pay my first employee in equity only?

No, not in the US, and not anywhere that has employment law worth respecting. Full-time employees are entitled to minimum wage and, depending on state, overtime. Equity-only "employees" are almost always misclassified contractors at best, and unpaid laborers in the eyes of the IRS at worst. If cash is the blocker, hire a contractor part time or raise first.

How long should my first hire's trial period be?

A paid trial of 6 to 16 hours of real work is enough to get a strong signal on output. A contract-to-hire arrangement of 60 to 90 days is enough to test working style. Anything longer than 90 days starts to feel like a worse version of full-time employment for the candidate, and the strongest people will walk.

Should I hire a senior person or someone earlier in their career?

Hire the most senior person you can afford who's willing to take a 20 to 30% cash haircut. Senior hires bring pattern recognition you don't have. Junior hires bring more hours and more upside for you, but they need management you can't yet provide. The exception is if you've managed people before and want a force multiplier you can mold.

What if my first hire doesn't work out?

Have the conversation by day 60. If it's not working by then, it usually doesn't get better. Be direct, document the issues, and offer a severance package of 2 to 4 weeks plus 30 days of equity vesting acceleration if it's not a fit. Treating the exit well protects your reputation, which matters more than the cash you save by being stingy.

Do I need to set up benefits for one employee?

You need worker's comp, payroll tax registration in your state, and at minimum health insurance contribution in most states (California, Massachusetts, and a few others require it explicitly). Gusto and Rippling will set this up in an afternoon for $50 to $100 a month. Skip 401(k), dental, vision, and life insurance until hire #3 or 4.

Where do I find templates for offer letters and equity grants?

The Y Combinator post-money SAFE library and the Cooley Go template library both include offer letters, equity grants, and at-will employment templates that are free and lawyer-approved. Index Ventures' Option Plan tool covers equity grant sizing. For a strategic-planning view of how this hire fits into the bigger company plan, the founder community at foundra.ai/key-reads/ has a number of deep dives on roadmap, runway, and team building.

How to Raise a Pre-Seed Round (Founder's Guide)

Spencer Claydon — Sat, 16 May 2026 01:04:29 +0000

Most first-time founders walk into pre-seed fundraising thinking it's a smaller version of a Series A. It isn't. The economics are different, the investors are different, and the things that actually move a pre-seed check across the line have almost nothing to do with traction. If you're trying to figure out how to raise a pre-seed round without burning six months of runway on dead-end intro emails, here's the actual playbook.

I've watched founders raise $750K in three weeks with no product, and I've watched founders with paying customers struggle for nine months. The difference is rarely the idea. It's almost always the prep work, the target list, and whether the founder understands what a pre-seed investor is actually buying.

What is a pre-seed round, exactly?

A pre-seed round is the first institutional money you raise, usually $250K to $1.5M, before you have meaningful revenue or product-market fit. It sits between friends-and-family money and a seed round. Pre-seed checks pay for your first 12 to 18 months: enough to build a product, run early go-to-market experiments, and generate the signal a seed investor will want to see.

Five years ago, "pre-seed" barely existed as a category. Most investors lumped everything before a Series A into "seed." That's changed. Funds like Hustle Fund, Pear VC, Afore Capital, Boost VC, K9 Ventures, Bee Partners, and Susa Ventures explicitly write pre-seed checks. So do a wave of solo capitalists like Elad Gil, Lenny Rachitsky, and Gokul Rajaram, plus accelerators like Y Combinator and Techstars whose program investments effectively function as pre-seed rounds.

What makes a round "pre-seed" isn't the dollar amount, it's the stage. You're raising on a story, a founding team, and maybe a prototype. Not on metrics.

How much should you raise at pre-seed?

Raise enough to hit a milestone that unlocks the next round, plus a 6-month buffer. For most software startups in 2026, that means $500K to $1M. For hardware or biotech, $1M to $2M. For a side-project-becoming-a-business, $150K to $400K can be plenty.

The math is unforgiving. If your burn is $40K a month with two founders and one engineer, $500K gives you 12.5 months. That's tight. Most pre-seed founders run hotter than they expect because they hire too soon or pay themselves too much. A realistic monthly burn breakdown:

Two cofounders at $5K/month each (below market): $10K
One engineer at $130K salary plus benefits: $13K
Tools, hosting, software: $1.5K
Marketing experiments: $3K
Legal, accounting, misc: $1.5K
Total: $29K/month

At that burn, $500K gives you 17 months. $750K gives you almost 26. The right answer depends on what you're trying to prove. If you can get to $20K MRR in 12 months, that's a clean seed story. If you need 18 months to hit that bar because of a slower sales cycle, raise more.

Don't raise less than you need to hit the next milestone. Two undersized rounds back-to-back is one of the most reliable ways to lose your company.

When are you actually ready to raise a pre-seed round?

You're ready to raise when you can tell a credible story about three things: why now, why you, and why this is going to be big. You don't need revenue. You don't need a working product. You need conviction backed by enough evidence that a thoughtful investor can believe you.

The "why now" piece matters more than founders realize. Pre-seed investors are pattern-matching on inflection points: a new platform, a regulatory shift, a behavior change, a technology cost curve that just bent. "AI got cheaper" was the why-now for thousands of 2023-2025 pre-seed rounds. "Construction companies finally went mobile" was a why-now for ServiceTitan a decade ago. If you can't answer why this couldn't have been built five years ago, the round will be hard.

"Why you" is about founder-market fit. The investor wants to believe you're the person who's going to keep showing up at 11pm on a Tuesday three years from now when everything is on fire. Domain experience helps. So does a track record of finishing hard things. So does an obsessive interest in the problem that predates the company.

Concrete signals you're probably ready to start raising:

You've done 40+ customer discovery interviews and can quote pain points back verbatim
You have a clickable prototype or a working MVP, even if ugly
You have 3 to 10 design partners or paying pilot customers, ideally with letters of intent
You can recite your TAM and the market structure from memory
You can answer "what would have to be true for this to be a $1B company" in two sentences

If you can do four of those five, start meeting investors. If you can only do one or two, do another month of work first. Fundraising compounds: a strong first meeting begets a strong second meeting, and a confused first meeting closes doors.

Who invests in pre-seed rounds?

Three groups write pre-seed checks: dedicated pre-seed funds, generalist seed funds that occasionally lead pre-seeds, and angels. Each one expects a different conversation, and most founders waste time pitching the wrong group.

Dedicated pre-seed funds write the smallest checks (often $250K to $750K) but move fastest and care most about founder-market fit. Hustle Fund, Afore Capital, Pear VC, K9 Ventures, Bee Partners, Boost VC, Forum Ventures, Antler, On Deck, and Replit Ventures all live in this category. They see hundreds of decks a week. They decide quickly. They expect a clean narrative and don't need a fully-built product.

Generalist seed funds like Initialized, Cowboy Ventures, Slow Ventures, Susa, Uncork, Bloomberg Beta, Lerer Hippeau, Bolt, NFX, and First Round Capital sometimes lead pre-seeds, especially for founders they know or for "obvious" markets. Their bar is higher but their checks are larger ($500K to $2M). They're also more likely to follow on, which matters.

Angels write the smallest checks ($10K to $100K) but often deliver the most value per dollar. A check from Elad Gil, Naval Ravikant, Jason Calacanis, Lenny Rachitsky, Gokul Rajaram, or Sahil Lavingia signals to the market. A check from a relevant operator angel (a former CMO of HubSpot, an early Stripe engineer, the founder of a recent unicorn in your space) opens doors you couldn't open yourself.

Most pre-seed rounds in 2026 look like this: one lead writing $300K to $500K, then 8 to 15 angels filling out another $200K to $500K. Plan for that structure before you start.

How do you find pre-seed investors without a warm intro?

Build a target list of 60 to 100 investors, find a path to each one, and run the process like a sales pipeline. Warm intros remain the highest-conversion channel, but cold outreach works at pre-seed if your email is sharp and the targeting is right. Spray-and-pray doesn't work in either direction.

Start by reverse-engineering portfolios. Pull up Crunchbase, Signal NFX, Visible, or OpenVC. Search for investors who've backed startups in your category, at your stage, in the last 18 months. Note check size, lead vs. follow, and how often they pre-seed. A spreadsheet with columns for fund, partner, fit, check size, warm-intro path, and status is enough. Notion works. So does Airtable, Google Sheets, Affinity, or a structured planning workspace like Foundra alongside a CRM-style tracker. The tool matters less than the discipline.

For warm intros, build a list of 30 to 50 founders who've raised in the last 24 months from your target investors and ask three to five of them per week for an intro. Founders refer almost universally if you're not a stranger and your ask is specific. Tell them what fund and which partner. Send the deck and a one-paragraph forwardable email. Don't ask them to "introduce you to investors." Ask them to "forward this to Hadley if you think he'd like it."

For cold outreach, the format that works is: subject line that names a real pattern, two sentences of context, one sentence on the company, one sentence on traction or differentiation, a clear ask. Three to five sentences total. No deck attached unless they ask. Send Tuesday or Wednesday morning. Personalize beyond first name: reference a portfolio company they led, a thesis post they wrote, a podcast clip. Pre-seed investors reply to cold email more than people think. 2 to 5 percent reply rate is normal. 8 percent is exceptional.

Track everything in your pipeline. First meeting, second meeting, partner meeting, in diligence, soft yes, term sheet, closed. Move investors through stages. Drop anyone who hasn't responded in 10 days from the active list. The goal is to compress timing so multiple investors are at decision points at the same time, which is how you create pressure and a real round, not a year-long slog.

What does a pre-seed pitch deck need to include?

A pre-seed deck is 10 to 12 slides covering problem, solution, why now, market, business model, traction, team, competition, financials, and the ask. The decks that close at pre-seed are tight, story-driven, and front-load the founder narrative. Long decks at this stage usually mean the founder hasn't figured out the story yet.

Slide-by-slide, what investors are actually looking for:

Cover: Company name, one-line description, your name, contact. Make it readable in a thumbnail.
Problem: What hurts, and how much. Quote a customer.
Solution: What you built or are building. One sentence plus a screenshot.
Why now: The shift that made this possible. This slide closes more rounds than most founders realize.
Market: TAM, SAM, SOM with credible sources. Top-down number plus a bottom-up sanity check.
Business model: How you make money. Pricing, ACV target, unit economics if you have them.
Traction: What you've proven. Discovery interviews count. LOIs count. Paying pilots count.
Team: Why you. The slide where most pre-seed decisions actually get made.
Competition: A 2x2 or table, not a logo wall. Show how you're different, not just better.
Financials: A simple 18-month forecast. Hiring plan. Burn rate. No pretend Series A spreadsheet.
Ask: How much you're raising, on what terms, and what the money buys.

Skip the appendix unless you actually need it. Skip the "vision" slide. Skip the J-curve graph with no data behind it. Pre-seed investors have seen 200 of those this month.

If you want a structured way to draft the deliverables that feed into a deck (financial model, GTM, competitive analysis, ICP), planning tools like Foundra, Notion templates, or a clean spreadsheet stack work better than starting from a blank page. The deck is the last 10 percent. The 90 percent is the thinking behind it.

SAFE or priced round at pre-seed?

Use a SAFE for almost every pre-seed round. Priced rounds at pre-seed are slow, expensive, and rarely worth the legal fees. SAFEs let you close investors one at a time as they say yes, rather than waiting for everyone to sign the same documents.

The standard pre-seed instrument is the YC post-money SAFE with a valuation cap. As of mid-2026, typical caps are $6M to $12M for software pre-seeds, $8M to $15M for AI-native startups with strong technical teams, and higher for hot deals or repeat founders. Discounts (typically 20 percent) are sometimes layered on top, though most modern pre-seeds skip the discount and just use a cap.

Convertible notes still exist but have mostly faded. They have an interest rate, a maturity date, and create awkward situations when the next round takes longer than 18 months. SAFEs sidestep all of that.

Stay away from "uncapped" SAFEs unless an investor pushes very hard and the check is huge. An uncapped SAFE means the investor gets whatever valuation your seed round prices at, which can become punishing if you have a great seed round. A "MFN" (most-favored-nation) provision is fine and common, but read the fine print.

For deeper detail on instrument choice, see the Foundra guide on SAFE vs. convertible notes. The short version: SAFE with a cap, raise on one set of terms, close on a rolling basis.

How long does raising a pre-seed round take?

Plan for 8 to 16 weeks from first meeting to last wire. Founders who say they raised a pre-seed in two weeks usually had warm relationships and a hot market. Founders who take six months usually started before they were ready or pitched the wrong investors.

A realistic timeline:

Weeks 1 to 2: Final deck, target list, intro requests sent
Weeks 3 to 5: First meetings (target 25 to 40 first meetings)
Weeks 4 to 6: Second meetings, partner meetings (target 8 to 15 second meetings)
Weeks 6 to 8: Diligence, first commitments, lead lined up
Weeks 8 to 12: Filling out the round with angels and smaller funds
Weeks 10 to 14: Documents signed, money in the bank

Wires are the slowest part. An investor saying yes on a Tuesday doesn't mean money on Wednesday. Plan for 2 to 4 weeks between a verbal yes and a closed wire, especially with smaller angel checks.

If you're four weeks in and nobody's getting to a second meeting, something is broken. Pause, get five real critiques from founders who've raised, and fix the deck or the targeting before sending more emails. Slogging through 80 first meetings with a broken deck is the most common pre-seed failure mode.

Key takeaways

Pre-seed fundraising is a structured sales process, not a creative act. The work that wins is the work nobody can see: a tight target list, a sharp story, evidence that you've done 50 customer interviews, and a pipeline you actually manage.

Raise enough to hit the next milestone with margin. $500K to $1M is the modal pre-seed for software companies in 2026. Don't undersize. Two underfunded rounds back-to-back will end the company faster than one bigger raise with the right investors.

Pick the right investors for your stage. Dedicated pre-seed funds and operator angels move faster than generalist seed funds at this stage and often add more value per dollar.

Use a SAFE with a cap. Skip the legal complexity of a priced round until seed.

Run the process like sales. Pipeline tracking, intro requests, follow-ups, and a clear close calendar will close your round faster than any single brilliant pitch.

FAQ

Do I need traction to raise a pre-seed round?
No. You need a credible story, a strong founding team, and enough customer discovery work to prove you understand the problem deeply. Letters of intent, signed pilots, or a working prototype help, but the modal pre-seed round closes on conviction and team, not on revenue.

What's the difference between pre-seed and seed?
Pre-seed is the first institutional check, typically $250K to $1.5M, on story and team. Seed is the next round, typically $2M to $6M, raised on early product-market-fit signal: paying users, retention, growing usage, or repeatable sales motion. The line has blurred, and some "seed" rounds in 2026 look like 2018 pre-seeds, but the spirit holds.

Can I raise a pre-seed without a technical cofounder?
Yes, but it's harder. Investors will ask how you'll build product. Have a clear answer: a contracted CTO with a path to joining, a fractional engineering lead, a strong agency relationship, or a credible no-code build plan. The best non-technical founders raising pre-seed in 2026 either have deep domain expertise or a recruited technical lead lined up to join post-funding.

How many investor meetings should I plan for?
Plan for 60 to 100 conversations to close a round. That funnels to 30 to 40 first meetings, 10 to 15 second meetings, 3 to 5 deep-dive partner meetings, and 1 to 2 leads. Most rounds get filled by 8 to 15 angels alongside the lead. Build the funnel wide enough at the top, or you'll get stuck.

Should I raise from a YC-style accelerator or skip it?
Depends on your network and your category. YC, Techstars, Antler, and similar programs add real value if you don't have a strong founder network: brand, intros, batch effects, and structured pressure. If you already have warm investor relationships and a working product, the dilution can be expensive. Apply if it's free to apply. Decide once you have an offer.

What's a fair pre-seed valuation cap?
For software pre-seeds in 2026, $6M to $12M post-money is the common range. AI-native, technical-team-heavy startups push higher ($10M to $20M). Repeat founders with prior exits routinely get $15M+. The cap matters less than founders think at pre-seed: a 50 percent higher cap costs you maybe 2 to 3 percent of additional dilution. The investor matters more than the cap.

Raising a pre-seed round is one of the most over-mythologized parts of starting a company. It's not a moment of brilliance. It's a 10-week project with a target list, a deck, a pipeline, and a close calendar. Treat it that way and you'll close. If you want more frameworks for the work that goes into the deck (financial models, GTM, competitive analysis, ICP definition), the rest of the Foundra library at foundra.ai/key-reads/ covers each piece in depth.

How to Get Press Coverage for Your Startup (Without a PR Agency)

Spencer Claydon — Thu, 14 May 2026 15:10:17 +0000

Most first-time founders try to get press the same way they try to raise their first round: by emailing strangers with a generic pitch and hoping. It doesn't work, and then they conclude that press is broken or only for connected people.

Press isn't broken. The pitch is.

I've watched dozens of pre-seed and seed founders land coverage in TechCrunch, The Information, Business Insider, and trade publications without retainers or PR firms. The ones who succeed do four things the ones who fail don't: they pitch a story, not a product. They pitch the right reporter, not a list. They time it to a news hook. And they make the journalist's job easier, not harder.

This guide breaks down the actual playbook. No fluff, no "build relationships" abstractions. Specific reporter-finding tactics, the cold pitch template that gets replies, the press kit components a journalist actually opens, and what a realistic press timeline looks like for a first-time founder.

When should you start pitching press for your startup?

Start pitching press 4 to 6 weeks before you have something concrete to announce, not the week of. Press cycles run on lead time. Daily tech outlets like TechCrunch or The Verge sometimes turn stories around in 48 hours, but most reporters at larger outlets work 2 to 4 weeks out. Trade publications and weekly columns plan even further ahead.

That doesn't mean you should pitch the second you have an idea. You need a real news hook: a launch, a fundraise, a notable hire, a milestone (10,000 users, $1M ARR, a meaningful partnership), or a piece of original data. "We exist" is not a news hook. "We exist and here's a surprising finding from our 3,000 users" is.

If you're pre-launch, the only press worth chasing is your launch itself, and you should pitch it about 3 weeks before launch day so the story can run that morning. If you're post-launch, line up your next pitch around your next milestone, not your next quiet month.

What kind of press coverage actually helps a startup?

The press coverage that actually moves the needle for a first-time founder is targeted trade and niche publication coverage, not the TechCrunch front page. Founders fixate on TechCrunch because it's famous, but a feature in a publication your customers actually read converts better than a glancing mention in a tier-one tech outlet.

Think of press in three tiers:

Tier 1: Tech and business mainstream. TechCrunch, The Verge, Business Insider, Forbes, Wired, Fast Company, The Information, Axios. High prestige, hard to land, mostly helps with fundraising signal and hiring. Direct customer conversion is often weak because the audience is broad.

Tier 2: Trade and vertical publications. If you're building for marketers, this is Marketing Brew, AdAge, Modern Retail. For developers, it's The Pragmatic Engineer, InfoQ, Hacker Noon. For healthcare, it's STAT News, Fierce Healthcare. These are gold for first-time founders because the readers are exactly your customers.

Tier 3: Newsletters and creator-led media. Lenny's Newsletter, The Generalist, Not Boring, Stratechery, The Hustle. Often higher conversion than Tier 1 because the writer's audience trusts them on product recommendations.

A founder I know skipped TechCrunch and pitched a 4,000-subscriber niche newsletter for ops leaders. The newsletter sent them 280 signups. A peer who got a TechCrunch mention got 90 signups and a wave of recruiter spam. Pick your tier based on whose attention actually matters.

How do you find the right journalists to pitch?

The right journalists to pitch are the ones who have written about companies like yours in the last 90 days. Not the same category five years ago. Not "writes about tech." The reporter whose last three pieces covered a competitor, an adjacent space, or your exact customer base.

Here's the process:

Pick 5 to 8 competitors or adjacent companies that have gotten press in the last year.
Google each company name plus "raises" or "launches" plus the year. Note who wrote each piece.
Look at the reporter's last 10 articles (their byline page on the outlet or their X/Twitter). Are they still on the beat? Reporters rotate beats constantly.
Build a list of 20 to 30 names, ranked by relevance. The reporter who wrote about three of your competitors is gold. The reporter who covered one tangentially related company two years ago is filler.

Tools that help: Muck Rack and Cision (expensive, $500 to $1,500/month for paid versions), Twitter/X advanced search (free, surprisingly effective), and Google News alerts on competitor names. For free options, set a Google Alert on every competitor and adjacent product you can think of. Read the bylines for 30 days. You'll have a better target list than 90% of agencies.

One more thing: never pitch tips@outlet.com or news@outlet.com. Those are graveyards. Pitch the individual reporter, by name, at their email. Most outlets put it in their bio. If not, the convention is usually firstname.lastname@outlet.com or firstinitial+lastname@outlet.com.

How do you write a cold pitch email that gets opened?

A cold pitch that gets opened follows a specific structure: short subject line, 3 to 5 sentence body, one clear ask, no attachments. Anything else looks like spam.

Here's the structure that works:

Subject line: 4 to 8 words. State the news, not the company. "Notion alternative for founders raises $2M" beats "Excited to share our launch."

First sentence: The news hook in one line. "Foundra is launching today with $400K in pre-seed and 4,000 first-time founders on the waitlist."

Second sentence: Why this reporter, specifically. "I saw your piece on planning tools for solo founders last month and thought you might be tracking this space."

Third sentence: What makes this story interesting beyond the announcement. "We tracked 1,200 first-time founders for 6 months and found 73% give up before writing their first business plan. That's the story I think is more interesting than the launch itself."

Fourth sentence: The ask. "Can I send you a 1-page brief and 15 minutes Tuesday or Wednesday?"

That's it. No CEO bio, no "revolutionary platform," no logo. If they want more, they'll ask. Reporters at outlets like TechCrunch get 200 to 800 pitches a week. The ones that get opened are short, specific, and offer a story angle, not a press release.

If you want a real-world example, search for "Lenny's Newsletter pitch template" or "Reporters share what they want." Multiple journalists (Erin Griffith at NYT, Alex Konrad formerly at Forbes, others) have published the exact format they prefer. It matches what I just described.

What should a startup press kit include?

A startup press kit should include exactly five things: a one-paragraph company description, founder names and bios in 2 sentences each, 3 to 5 product screenshots, a logo file in two formats, and one quotable line from the founder. That's it.

Founders overbuild press kits. Reporters won't read a 12-page brand book. They want to grab 4 assets in 90 seconds and write.

Specifically:

Boilerplate paragraph: 75 to 120 words. Who you are, what you do, who it's for, where you're based, who funded you (if applicable). This goes verbatim at the bottom of most articles, so write it as if it's a wire-service description.
Founder bios: 2 sentences each. Name, role, the one previous credit that makes you credible (where you worked or what you built).
Screenshots: PNG, 1600x1000 or so, no watermarks. Reporters need to drop these into a CMS without resizing. Make it easy.
Logo: SVG and PNG, on transparent background. Outlets use both.
One quote: A pull-quote from the founder, 1 or 2 sentences. Something with a point of view, not "We're excited to launch." Try: "Most planning tools are built for second-time founders who already know what they're doing. First-timers get lost in templates designed for people who don't need them."

Host this on a single page (Notion, a hidden /press route on your site, a Dropbox folder) and put the link in every pitch. Make it click-once accessible. The Verge, The Information, and Business Insider have all written stories where the entire process was: click link, copy paragraph, drop screenshot, publish.

How do you build a press list before you need it?

You build a press list by spending 20 minutes a week reading bylines and adding names to a spreadsheet for 3 months before you ever pitch. The founders who succeed at press treat it like a slow-build list, not a launch-week scramble.

Set this up in a simple sheet (Airtable, Google Sheets, Notion, whatever) with columns for: reporter name, outlet, beat, last 3 articles, email, last contact date, notes. Don't worry about a CRM. The list will be 30 to 60 names total.

Then do three things weekly:

Read 5 to 10 articles in your space and add new bylines you haven't seen before.
Reply to one reporter's tweet or LinkedIn post with a useful observation. Not "great piece," not a pitch. A real comment. Do this for 8 to 12 weeks and reporters start to recognize your name.
If a reporter writes about a competitor, send a quick note: "Saw your piece on X. I'm building something adjacent: happy to be a source if you ever need an outside perspective on this category." No pitch, no ask, just availability.

This is the unsexy version of "build relationships." It's also the version that actually works. By the time you have a launch or a milestone, you're emailing reporters who already know your name. Pitch reply rates jump from 1 to 3% cold to 15 to 25% warm. Same email, different relationship.

Some founders use Foundra to keep their go-to-market plan and press timeline in one workspace alongside their financial model and positioning notes, but a plain Notion page or a tab in your launch spreadsheet works fine too. The format doesn't matter. Consistency does.

What happens after a journalist responds?

After a journalist responds, your job is to make their job easier, not to pitch them harder. Reply within 2 hours during business days. Offer 2 or 3 specific time slots. Send the press kit link. Don't ask follow-up questions like "What's the angle?" That's their decision, not yours.

If they ask for an interview, prep a one-page brief with the 5 to 7 talking points you want to land. Practice each one out loud. The most common rookie mistake is rambling. A good interview answer is 30 to 60 seconds. Reporters edit ruthlessly. If you ramble, they'll quote the wrong sentence.

If they ask for data, send it within 24 hours in a clean format (CSV or a Notion doc, not a screenshot of a slide). Reporters love founders who deliver on time. They tell their colleagues, and your name spreads inside the newsroom. This is how second pieces happen.

If the story runs, send a short thank-you note (one line, no pitch). Then wait 90 days before reaching out again with something new. The fastest way to burn a reporter is to pitch them three times in a month.

If the story doesn't run, don't follow up more than once. "Hey, any update on this?" is fine after a week. After that, assume it's dead and move on. Reporters spike stories for hundreds of reasons unrelated to you. Take it personally and you'll write angry follow-ups that kill the relationship for future pitches.

Key takeaways

Most founders treat press as a one-time event tied to a launch. The ones who win at it treat it as a slow-build muscle: 20 minutes a week, 3 months ahead of when they need it.

The pitch is more important than the press release. Three sentences, one news hook, one specific reporter, one clear ask. No attachments. No "exciting announcement."

Tier matters more than prestige. A 4,000-subscriber newsletter that reaches your exact customers outconverts a TechCrunch mention almost every time. Pick the outlet based on who reads it, not how famous it is.

Press kits should take 90 seconds to use. One paragraph, two bios, four screenshots, one logo, one quote. Hosted at one URL. Anything more is friction.

Reporters are people doing a hard job. The founders who get repeat coverage are the ones who reply fast, deliver clean data, and don't waste a journalist's time. Be that founder.

FAQ

How much does it cost to get press for a startup?
Zero if you do it yourself. PR agencies charge $4,000 to $12,000 a month with 3 to 6 month minimums, and first-time founders almost never see ROI at that price point. The agency model works for Series B and up, not pre-seed. Spend the same money on a part-time freelance comms person ($1,500 to $3,000/month) or do it yourself in 4 hours a week.

How long does it take to get press coverage?
From cold pitch to published story: 1 to 6 weeks on average. The bigger the outlet, the longer the lead time. Newsletters often turn around in 5 to 10 days. TechCrunch can run a launch piece same-day if it's hot, but more commonly takes 1 to 3 weeks of back-and-forth. Plan for 4 to 6 weeks from first pitch to publish.

What's the best time of day to pitch a journalist?
Tuesday through Thursday, between 7 AM and 10 AM in the reporter's local timezone. Monday is meeting day, Friday is winding-down day. Mornings beat afternoons because reporters' inboxes fill up across the day. Avoid major news weeks (election week, major tech event weeks like CES, WWDC, F8) because your pitch will get buried.

Do I need a press release to get coverage?
No. Press releases are a vestigial format. Reporters at modern outlets prefer a 3-sentence email and a link to a press kit. The exception is wire services (Business Wire, PR Newswire) for SEO and Google News indexing, which costs $400 to $900 per release and provides minimal direct coverage value for early-stage startups. Skip the wire until you have a fundraise or partnership announcement that needs the formal record.

How many reporters should I pitch for one announcement?
For a launch or fundraise, 15 to 30 carefully selected reporters across 2 to 3 tiers is the right range. Exclusive offers (giving one outlet 24 hours of head start) work well for Tier 1 because they incentivize the reporter to actually publish. For trade publications and newsletters, parallel pitching is fine. Never blast 200 reporters with the same email. They talk to each other, and they'll all spike the story.

What if a journalist ignores my pitch?
Follow up once, 5 to 7 days later, with a one-sentence bump. "Bumping this in case the original got buried. Happy to send a 1-pager if useful." If no reply after that, move on. Persistence past one bump reads as desperate and burns the relationship. Better to wait 3 months and pitch the next milestone.

If you're building the broader story your press hook will plug into, the planning side (financial model, positioning, go-to-market) is what makes the pitch coherent. Tools like a structured workspace, a planning platform like Foundra, or a well-kept Notion doc all work. The mechanism matters less than having the story written down before you start emailing reporters. For more founder playbooks, see foundra.ai/key-reads/.

Sources and references: TechCrunch reporter byline pages, The Information staff page, Erin Griffith's public pitch guidance, Alex Konrad's pitch template threads, Muck Rack journalist directory, Lenny's Newsletter audience data, Business Wire and PR Newswire current pricing, Y Combinator essays on PR for early-stage startups.

How to Come Up With a Startup Idea That's Worth Building

Spencer Claydon — Wed, 13 May 2026 15:08:03 +0000

How to Come Up With a Startup Idea That's Worth Building

Most first-time founders get this part backwards. They sit down, stare at a blank page, and try to "think of an idea." Hours go by. Maybe a notebook fills up. Nothing sticks.

That's not how good ideas show up. Good ideas are found, not invented. They live inside problems you've already noticed but haven't named yet. The job isn't to be more creative. The job is to look in the right places.

This guide walks through where startup ideas actually come from, how to spot one that's worth your time, and how to know when a "great idea" is really just a hobby project in disguise. By the end you'll have a short list of candidates and a way to pick which one to validate next.

Why is it so hard to come up with a startup idea?

It's hard because most people are searching for inspiration instead of friction. A startup idea isn't a flash of brilliance. It's a problem that bothers someone enough to pay for the fix.

Three things trip up first-time founders. First, they confuse novelty with value. The idea doesn't need to be new. It needs to be useful. Second, they aim for "huge" before "real." A $10M business that exists beats a $1B fantasy that doesn't. Third, they look in places they don't understand. If you've never worked in healthcare logistics, building a healthcare logistics tool is going to be brutal.

The fix is to start with what you already know and what already annoys you. The boring problems in your own life and work are where the best ideas hide.

Where do good startup ideas actually come from?

Good startup ideas come from problems you've personally felt, work you've done before, or industries you have unfair access to. Paul Graham at Y Combinator calls this "living in the future." You notice something missing that other people haven't noticed yet because they're not where you are.

Here's the pattern across most successful startups:

Airbnb started because two broke designers couldn't make rent and noticed a conference had no hotel rooms left. Stripe came from the Collison brothers being frustrated with how painful it was to accept payments online as developers. Calendly started when Tope Awotona kept rescheduling sales meetings and thought there had to be a better way. None of these are genius ideas. They're obvious in hindsight. That's the point.

The four richest veins for ideas are:

Problems in your own day-to-day life. Things that waste your time, frustrate you, or cost too much.
Problems in your job or industry. The annoying processes everyone complains about but no one fixes.
Inefficiencies you spot in markets you understand. Where customers are clearly underserved or overcharged.
New technology or platforms that just got cheap or accessible. AI, no-code, new APIs, regulation changes.

Notice what's not on the list: "things that sound cool" and "stuff I read about in TechCrunch."

What's the best framework for generating startup ideas?

The best framework is to mine three sources at once: your own pain, other people's complaints, and unfair access you have to a market or skill. You're not brainstorming in the abstract. You're collecting real signals.

Set aside two hours and run this exercise:

Step 1: List 20 things that annoyed you this month. Anything. Software that crashed. A service that overcharged. A task that took too long. Don't filter. Just list.

Step 2: List 10 problems you've heard friends or coworkers complain about. Group chats, Slack channels, dinner conversations. What do people gripe about?

Step 3: List 5 things you know how to do that most people don't. This is your unfair advantage. Maybe you can read tax documents fast. Maybe you've shipped three apps. Maybe you understand how restaurants order inventory.

Step 4: Cross-reference the three lists. Where do they overlap? An annoyance you've felt, that others share, where you have unfair skill or access, is the gold zone.

You won't get a perfect idea out of one session. You'll get five or six candidates. That's enough to move to the next step.

How do I know if my startup idea is actually worth pursuing?

A startup idea is worth pursuing if real people will pay real money to solve the problem today, and there's a path for one founder to reach those people. That's it. Three filters: payment, urgency, and reachability.

Run every candidate through these questions:

Does someone already pay to solve this? If yes, you have a market. The competitor is your proof. If no, you have a much harder sell.
How often does the problem show up? Daily and painful is great. Once-a-year and mild is not.
Can I reach 100 of these people without spending a dollar on ads? If you can't find your first 100 customers in places you already know (LinkedIn, a subreddit, a Slack community, your industry network), distribution is going to crush you later.
Do I want to work on this for the next 5 years? Building takes longer than you think. If the problem bores you in month two, it's not the one.

If an idea fails any of these, it's not dead. It just needs work. Maybe you need to narrow the audience. Maybe the problem isn't painful enough yet. Maybe you're the wrong person for it. That's fine. Move on.

I've watched dozens of founders fall in love with ideas that pass the "cool" test and fail the "pay-for-it-now" test. The market doesn't care how clever your idea is. It cares whether you're scratching an itch that already hurts.

Should I solve a problem I have or a problem I see?

Solve a problem you have if you can. It's faster, cheaper, and you don't have to guess what the customer wants. You are the customer.

Solving a problem you only see from the outside is doable but harder. You'll need to talk to a lot of strangers, learn an industry you don't live in, and resist the temptation to design for yourself instead of the actual user. Most first-time founders underestimate this gap. They build what they'd want and wonder why farmers, dentists, or warehouse managers don't sign up.

If you don't have your own painful problem to solve, the next best thing is to embed yourself in the world of the people who do. Take a job. Volunteer. Spend 30 days interviewing 30 people in the target industry. You can't build a tool for plumbers if you've never sat in a plumber's truck.

The exception: if you have an unfair distribution advantage. If you already have 50,000 newsletter subscribers in a niche, that audience can pull you into a market you don't deeply know. Distribution covers a lot of sins.

What are bad signs that a startup idea won't work?

The clearest bad signs are: no one's complaining about it, you can't explain it in one sentence, the customer is "everyone," and you can't find existing solutions (even bad ones).

Watch out for these red flags:

"There's nothing like this on the market." Usually means there's no market, not that you're a genius. Real opportunities almost always have competitors. Competitors are the proof people pay.
"It's like Uber for X." If you have to start with an analogy, you haven't pressure-tested the value. Just describe what it does and who buys it.
"It'll go viral." Maybe. Probably not. Build for organic word of mouth among a tight group first. Virality is a bonus, not a strategy.
"Everyone needs this." No they don't. Pick a specific person, with a specific job, in a specific situation, with a specific budget. "Marketing managers at 50-to-200 person B2B SaaS companies in the US" is a real customer. "Small businesses" is not.
You'd never personally pay for it. If you wouldn't pay, the bar is much higher for proving someone else will.

The worst red flag is the idea you can't stop polishing in your head but won't go talk to a single potential customer about. That's a fantasy, not a startup.

How do I move from idea to validation?

Once you've narrowed to one or two ideas, you move from thinking to talking. The next step isn't building. It's customer discovery: 10 to 20 conversations with people in your target market.

Here's the move:

Write a one-sentence description of what you're considering building and who it's for.
List 20 people who fit the customer profile and how you can reach each one.
Ask each of them about their current process, not about your idea. "Walk me through how you handle X today" beats "Would you use a tool that does Y?"
Look for repeated complaints across conversations. That's the signal.
If you hear the same pain three times from three different people, you have something worth prototyping. If not, refine and keep listening.

This is the boring middle nobody likes. It's also where 80% of startup failures get prevented. Spend a week here and you'll save six months later.

If you want a structured place to keep this work organized, you can do it in a Notion doc, a Google Sheet, or a planning tool like Foundra that walks first-time founders through idea selection, customer interviews, and the early business model. The format matters less than actually doing it.

What if I have too many ideas?

Pick the one where the customer is easiest to reach. That's almost always the right answer for a first-time founder.

When you have five candidates that all look reasonable, the tiebreaker isn't "which is biggest" or "which is most interesting." It's "which one can I get in front of 20 paying customers fastest." Smaller markets you can actually reach beat huge markets you can't. You can always expand. You can't expand from zero.

Other tiebreakers, in order of importance: which one bothers you the most, which one you'd still be excited about in a year, which one fits the time and money you have to commit, and which one would still be a useful product even if it stays small.

The wrong tiebreaker is which one sounds most impressive at a dinner party.

Key Takeaways

The short version of everything above:

Good startup ideas come from problems you've felt, work you've done, or markets you can reach. Not from staring at a wall.
Mine three lists at once: your annoyances, other people's complaints, and your unfair skills or access.
An idea is worth pursuing if people pay to solve it today, the problem is frequent and painful, and you can reach 100 customers without paid ads.
Solve problems you have when possible. If you can't, embed yourself in the world of the people who do.
Beware of "no competitors," "everyone needs this," and the idea you'll polish forever but never test.
The move from idea to validation is conversations, not building. 10 to 20 customer interviews before you write a line of code.
When in doubt, pick the idea where reaching the customer is easiest.

FAQ

How long does it take to come up with a good startup idea?
Some founders find theirs in a week. Others take a year of working in an industry before they spot the problem. Don't treat it as a race. Treat it as a search.

Can I copy an existing startup idea?
Yes, with a twist. Pick a specific underserved segment, a different distribution channel, or a fundamentally better experience. "Salesforce for dentists" is a real business if you understand dentists. Pure clones with no edge rarely work.

What if I'm not technical? Can I still come up with a startup idea?
Absolutely. Many great ideas don't require code at first. Manual services, no-code prototypes, and concierge MVPs validate ideas without engineers. Find the problem first, worry about the tech stack later.

Should I quit my job to find a startup idea?
No. Find the idea while employed. Your job is often the best source of problems worth solving, and you'll need the runway. Quit when you have customer signal, not before.

How do I know if my idea is too small?
If you can map out 1,000 paying customers in a market with no real competitors, it's probably big enough to start. You don't need a billion-dollar market on day one. You need a beachhead.

What's the difference between idea generation and idea validation?
Idea generation is finding candidates worth testing. Idea validation is figuring out whether one of those candidates has a real market. They're different stages, and most founders skip straight from generation to building. That's the expensive mistake.

If you want a place to organize your candidate ideas, score them against these filters, and run customer interviews in one structured workspace, that's the kind of work Foundra is built for. Foundra walks first-time founders through idea selection, customer discovery, and the early planning steps so you stop hopping between docs and start making decisions.

Find more practical guides for first-time founders at foundra.ai/key-reads/.

How to Launch on Product Hunt (First-Time Founder's Guide)

Spencer Claydon — Tue, 12 May 2026 15:08:54 +0000

You spent six months building. You finally have something to show. Then you read about a SaaS that hit #1 on Product Hunt and got 3,000 signups in 24 hours, and you think: that should be me.

Here's the part nobody tells you. Most Product Hunt launches do not work. The average product gets fewer than 50 upvotes. Maybe 200 visits to the landing page. A handful of signups. The founders who post on Monday morning and refresh all day, hoping the upvotes climb, usually end the day disappointed.

The launches that actually work are not lucky. They are prepared. They have a list, a story, a hunter, a launch day plan, and a follow-through strategy that runs for two weeks after the post goes live. This guide walks through how to launch on Product Hunt as a first-time founder, with the specific moves that separate a flop from a Top 5 finish.

What is Product Hunt and why does launching there still matter in 2026?

Product Hunt is a daily ranking of new products voted on by makers, investors, and early adopters. Posts go live at 12:01 AM Pacific Time, and the products with the most upvotes by midnight win Product of the Day. Top 5 finishers get featured in the daily newsletter that goes to roughly 200,000 subscribers, plus the homepage badge that lives on the listing forever.

The reason it still matters: Product Hunt is one of the few channels left where a single day of effort can produce thousands of qualified visitors. A Top 5 finish typically drives 2,000 to 8,000 site visits in 24 hours, and the badge plus permanent listing keeps generating trickle traffic for years. Loom, Notion, Linear, Superhuman, Cron, Raycast, and dozens of other tools you use daily launched there. The audience skews technical, product-curious, and willing to try new things, which is exactly who first-time founders want as early users.

That said, Product Hunt is not a growth strategy. It's an amplifier. If you have no audience, no story, and no follow-through, a Product Hunt launch will produce a small spike and then nothing. If you have any of those three, it can compound into your first 500 customers.

How long before launch should you start preparing?

You need at least 4 to 6 weeks of preparation before the launch day. Founders who decide on a Tuesday to launch next Monday almost always underperform, because the work that wins Product Hunt happens in the weeks before, not on the day itself.

Here's what the timeline actually looks like:

Six weeks out: lock the launch date, pick a hunter, start building your supporter list. Five weeks out: write your tagline and description, line up your assets. Four weeks out: warm up your network, post in build-in-public threads, start your Product Hunt Ship page if you're using one. Three weeks out: outreach to your 100 closest contacts, schedule your social posts, prep your team. Two weeks out: invite 200+ people to your supporter list, send teaser content. One week out: final asset polish, run dress rehearsals, write the comment thread you'll post at 12:01 AM. Launch week: execute.

The biggest single predictor of a successful Product Hunt launch is the size of your warm list before launch day. Not the product. Not the assets. The list. Founders who launch with 500 people in their corner usually hit Top 5. Founders who launch with 50 usually finish outside the top 20.

How do you pick the right launch date?

The best launch days are Tuesday, Wednesday, and Thursday. Skip Monday because it's the most competitive day. Skip Friday and weekends because traffic and engagement drop. Skip the first week of January and the last two weeks of December because everyone in the U.S. is offline.

Check the Product Hunt homepage in the week before your planned launch and look at the products currently lined up. If a major launch from a YC company or a known brand is going up the same day, push your date by 48 hours. You don't need an empty day, but you don't want to fight a 5,000-upvote behemoth either. Sweet spot: a Tuesday or Wednesday with no obvious heavyweight on the schedule.

Also consider your audience's timezone. Product Hunt rankings are decided on Pacific time, but voting happens globally. If your audience is mostly European, your peak vote window is the morning hours in Europe, which is the middle of the night in Pacific time. That can hurt your ranking because the U.S. early-morning voters define the leaderboard. Plan your outreach to compensate.

Should you use a hunter, and how do you find one?

You should use a hunter only if you can find one with a relevant audience and an active profile. The hunter is the person whose name appears at the top of your post. They don't control upvotes, but they get notified followers when they hunt a product, and a hunter with 5,000 followers can bring a couple hundred eyeballs in the first hour.

The myth that you need a famous hunter to win is dead. Product Hunt changed the algorithm years ago so that hunter follower count carries less weight. What still matters is whether the hunter's audience is your audience. A hunter with 1,000 followers who all build SaaS tools is more valuable for a SaaS launch than a hunter with 10,000 random followers.

How to find a good hunter: search Product Hunt for products similar to yours in the last six months, find who hunted the ones that did well, and reach out. Look for active hunters who have hunted at least 5 products in the last 90 days. Send a short personal message: who you are, what you're launching, why their audience would care, when you plan to launch. Most active hunters reply within 48 hours.

If you can't find a good hunter, hunt yourself. Self-hunted launches have won Product of the Day many times. Loom, Tally, and Linear all had self-hunted launches at some point. The hunter is a small lever, not a deciding factor.

What pre-launch assets do you actually need?

You need eight specific assets ready 72 hours before launch:

A clear tagline under 60 characters. The tagline appears in feeds, newsletters, and search results, and it has to land in one read. Test it on five friends who don't know what you built. If three of them ask "what does that mean?", rewrite. Good examples from past launches: Tally said "Free, beautiful forms without limits." Cron said "The next-generation calendar for professionals."

A 260-character description that finishes the sentence the tagline started. Lead with the outcome, not the feature list. What does the user get? Why now? What changed?

Three to five gallery images at 1270x760 pixels. The first image is your headline image and shows the product in use. The next images show specific features or use cases. Real screenshots beat mockups. Mockups beat illustrations.

A 30 to 60 second demo video or GIF. The video doesn't need production polish. It needs to show the product solving a real problem in under a minute. Loom recordings work fine. So do screen captures with light captions. Skip the founder talking-head intro.

A first comment that opens the conversation. The first comment from the maker is pinned to the top and is read by everyone who clicks through. Keep it under 200 words. Say who you are, what you built, why you built it, what's free, and ask one specific question to seed replies.

A simple landing page with the Product Hunt badge embedded. The badge proves social validation to anyone who clicks through. It also feeds back into your Product Hunt ranking because click-throughs to your site are tracked.

A list of 20 to 30 prepared responses to common questions. People will ask about pricing, security, comparisons to other tools, your roadmap, whether you have an API, and so on. Write the answers in advance so you can post them in the comments quickly without sounding rehearsed.

A short "thanks for the support" message and a one-tap social share link. You'll send this to everyone who upvotes or comments, and it should make it trivial for them to share your launch on X, LinkedIn, or in their Slack groups.

How do you build a supporter list before launch?

Start with your existing network, expand through public building, and gate the final push through a Ship page or waitlist.

Existing network: your contacts list, your email subscribers, your X followers, your LinkedIn connections, anyone who DMed you about your product in the last year. Send each of them a personal message, not a bulk email, two weeks before launch. The message should say what you're launching, why it matters to them specifically, and ask if they'd be willing to upvote and comment on launch day. Personal beats automated by a factor of three or four for response rates.

Public building: post about the launch in places where your audience hangs out. Indie Hackers, Reddit, Hacker News, relevant Slack and Discord communities. Don't drop a link and run. Share lessons from the build, ask questions, help other founders. Two weeks of consistent presence in three communities will pull more launch-day upvotes than a single drop-and-go post.

Ship page or waitlist: Product Hunt's Ship product lets you build a list of people who want to be notified when you launch. The list translates directly into upvotes on launch day, because Ship sends a notification to everyone on the list the moment your launch goes live. A Ship page with 800 subscribers will reliably produce 200 to 400 upvotes in the first six hours.

Foundra users running through the launch phase of the planning system typically start their supporter list at the same time they finalize the go-to-market plan, which gives them six to eight weeks of runway before launch day. Other tools to track your list include Loops, Beehiiv, and Kit on the email side, and Tally or Typeform for collecting signups.

What does launch day actually look like, hour by hour?

Launch day starts at midnight Pacific and ends 24 hours later. Most of the action happens in the first 4 hours and the last 2 hours. Here's an hour-by-hour playbook:

12:01 AM Pacific: post goes live. Confirm the listing looks correct, the assets render, and the first comment is pinned. Send the launch notification to your Ship list, your email list, and your top 100 personal contacts.

12:01 to 2:00 AM: focus on Asia-Pacific and U.S. West Coast night owls. Post in any Slack, Discord, or Telegram communities where your audience is up. Reply to every comment that comes in. Speed of reply matters: the algorithm rewards engagement, and people are more likely to upvote if they see the founder is active.

6:00 AM Pacific: U.S. East Coast wakes up. This is the peak voting window for English-speaking products. Post your first dedicated launch tweet, your LinkedIn announcement, and a short post in any subreddits where your product is on-topic. Send a personal message to the next 100 contacts on your list.

9:00 AM to noon: U.S. business hours. Post in maker Slack groups, founder communities, and any company channels where you have permission. Email anyone who replied to your launch teaser two weeks ago. Reply to every comment within 20 minutes.

12:00 to 4:00 PM Pacific: European audiences wind down, U.S. peak. Maintain comment velocity. If you have any press contacts, this is the moment to share the launch and ask for a tweet or a mention. Refresh the leaderboard every hour. If you're outside the Top 5, send a second wave of outreach asking specifically for an upvote and a short comment.

4:00 PM to midnight: closing window. The final 8 hours separate Top 5 finishers from everyone else. Most founders run out of steam here. Don't. Send a "we have 8 hours left, here's where we are, here's how you can help" note to anyone who hasn't engaged. Post a mid-launch update on X and LinkedIn with the upvote count and a thank-you to commenters. Keep replying.

Midnight Pacific: launch closes. Wait for the dust to settle, then post a thank-you to everyone who supported, with the final ranking.

What do you do in the two weeks after launch?

The launch isn't over when the clock hits midnight. The two weeks after are where most of the long-tail value gets captured.

Day 1 after launch: thank-you wave. Send a personal note to every commenter, every upvoter you can identify, and everyone who shared the launch. Post a recap on X, LinkedIn, Indie Hackers, and Hacker News if the result is worth sharing. The recap should include the number of upvotes, the final rank, the traffic numbers, and one specific lesson. Recap posts often get more engagement than the launch itself.

Day 2 to 7: convert traffic into customers. Most Product Hunt visitors don't buy on day one. They sign up for the email list, try the free tier, or bookmark the site. Your job in the first week is to convert that traffic. Send a 3-email sequence to new signups: welcome, here's how to get value in 10 minutes, here's a case study or use case. Onboarding email sequences from Customer.io, Loops, and Kit work fine for this.

Day 8 to 14: amplify the win. Use the Top X badge on your landing page, your X bio, your LinkedIn header, and your email signature. Pitch outlets that cover Product Hunt launches: TechCrunch, The Verge, indie newsletters like The Generalist or Lenny's Newsletter, podcast hosts in your space. A Top 5 finish on Product Hunt is a hook, and journalists do pick up the better stories.

Day 14 onward: the long tail. Your Product Hunt listing keeps getting visits for years. A consistent stream of upvotes and comments after launch day helps the listing rank in Product Hunt's search and in Google. Drop back into the listing once a week to reply to new comments. Update the gallery and description when you ship major features.

How do you measure if your launch was successful?

The right success metrics depend on your goal, but most founders should measure these five: total upvotes, final ranking, site traffic during and after launch, qualified signups or trial starts, and downstream revenue from the cohort.

Top 5 of the day is the upvote benchmark most founders aim for. That's usually around 400 to 700 upvotes depending on the day, though it can climb above 1,000 on heavy days. Product of the Day usually requires 800+ upvotes. Top 10 is a respectable result and still gets you a featured spot in the daily newsletter.

Traffic numbers vary widely. A Top 5 finish typically produces 2,000 to 8,000 visits in 24 hours, with a long tail of 50 to 200 visits per day for the next two months. A Product of the Day win can push the launch-day total above 15,000 visits. If your landing page converts at 5 to 10 percent to email signup, that's 100 to 800 new emails on launch day.

Trial starts and paid conversion are the metrics that actually pay the bills. Track both: how many of the launch-day visitors started a trial, and what percentage of those converted to paid in the following 30 days. A solid SaaS conversion benchmark from a Product Hunt cohort is 1 to 3 percent of visitors to trial, and 10 to 20 percent of trial users to paid. Anything above that means your product-market fit is real. Below it means the launch worked but the funnel didn't.

Revenue is the final scoreboard. Some founders count direct revenue in the first 60 days, others count lifetime value of the cohort. Either way, a successful Product Hunt launch should produce at least 10 to 20 times your launch-day prep cost in revenue over the following year. If it doesn't, the channel isn't your bottleneck. The product or the funnel is.

Key Takeaways

The launch begins 4 to 6 weeks before launch day, not at midnight Pacific. Most of the work that decides whether you finish Top 5 or top 50 happens in the weeks before, not in the 24-hour window. If you only have a week, push the date.

A warm supporter list of 300 to 800 people is the single biggest predictor of success. Build it through Ship pages, personal outreach, and consistent presence in three to five communities for the six weeks before launch.

Tuesday, Wednesday, or Thursday wins. Skip Mondays, weekends, and the first and last weeks of the year. Check the schedule and avoid going head-to-head with a known heavyweight launch.

Hunters help, but they don't decide the outcome. Pick a hunter with a relevant audience and an active profile, or hunt yourself. Don't waste two weeks chasing a "famous" hunter.

Launch day is a 24-hour sprint. The first 4 hours and the last 2 hours decide your rank. Reply to every comment within 20 minutes. Send three waves of outreach across the day, timed to U.S. East Coast wake-up, peak business hours, and the final closing window.

Eight assets, ready 72 hours before launch: tagline, description, gallery images, demo video, first comment, landing page with badge, prepared FAQ responses, thank-you and share links.

The two weeks after launch matter as much as the day itself. Recap posts, thank-you waves, onboarding sequences, and press pitches turn a one-day spike into a lasting acquisition channel.

Measure five things: upvotes, ranking, traffic, qualified signups or trials, and downstream revenue. The product wins the ranking. The funnel wins the revenue.

FAQ

How many upvotes do I need to win Product of the Day?
You typically need 800 to 1,200 upvotes to win Product of the Day, though the number varies based on competition. Top 5 usually requires 400 to 700 upvotes, and Top 10 requires 250 to 400. The exact number changes day by day, so focus on relative ranking, not absolute counts.

Can I ask people to upvote my product directly?
Product Hunt's rules prohibit explicit "please upvote" language in public posts and outreach. You can share the link, you can ask for support, you can ask people to check it out and leave a comment. The line between "please upvote" and "I'd love your support today" is real, and crossing it can get your launch flagged or demoted. When in doubt, share the link without a verb.

Should I launch multiple times for the same product?
Yes, if the product has changed materially. Notion, Linear, and Figma have all launched on Product Hunt multiple times across major version updates, new product lines, or significant feature additions. The rule of thumb: if your most active early users would describe it as a new product, launch again. If they'd call it an update, don't.

What if my launch flops?
Most launches do flop relative to expectations. A flop is recoverable. Capture the email signups you did get, reply to every comment on the listing for the next two weeks, and ship a meaningful update within 90 days. You can launch again on the same product later if the new version is materially different. A bad first launch doesn't blacklist you, and most users don't remember.

Do I need to be on Product Hunt's homepage to get traffic?
Not entirely. The homepage drives the bulk of launch-day traffic, but the daily newsletter (going to 200,000+ subscribers) and the permanent listing also produce long-tail visits. A product that finishes in the Top 20 but never makes the front page will still pull 500 to 1,500 visits in the first 48 hours and keep generating a trickle for months.

Should I pay for Product Hunt ads or boosts?
Skip them for your first launch. Product Hunt ads don't influence ranking, and the boosts available through some third-party services are against the platform's terms of service and can get your launch removed. Spend the budget on a better demo video or on outreach instead.