DEV Community: Spencer Claydon

How to Build a Cap Table for Your Startup

Spencer Claydon — Sun, 14 Jun 2026 15:09:26 +0000

How to Build a Cap Table for Your Startup

You raise a round, hire your first two engineers, bring on an advisor, and six months later someone asks a simple question: who actually owns this company? If you can't answer that in 30 seconds with a clean document, you have a problem. That document is your cap table, and most first-time founders either ignore it until an investor asks for it or build one so messy it costs them later. Cleaning up a broken cap table before a financing can delay the round by weeks and rack up legal fees that run into the tens of thousands. So let's build one the right way, from zero, before it matters.

What is a cap table, exactly?

A cap table (short for capitalization table) is a record of who owns what in your company. It lists every shareholder, how many shares they hold, what percentage of the company that represents, and what type of security it is.

Think of it as the answer to "if we sold the company tomorrow, who gets paid and how much?" In the earliest days it might be two founders splitting 10 million shares. By Series A it tracks founders, employees with options, angel investors, a venture fund, and a SAFE or two that converted into equity. The table grows every time you issue stock, grant options, or take money.

Here's the thing. A cap table isn't a legal filing. It's a working document you maintain, and its only job is to be accurate. An accurate cap table builds trust with investors. A sloppy one signals that you don't have your house in order, and that follows you into every negotiation.

Why does your cap table matter before you raise?

Your cap table matters before you raise because investors read it as a signal of how you run the company. A clean, well-modeled cap table tells them you understand dilution, you've planned for an option pool, and you won't surprise them with hidden agreements later.

There's a real cost to getting this wrong. Errors like unsigned stock agreements, miscalculated ownership, or missed filings can delay funding by 4 to 8 weeks and add meaningful legal expense during diligence. One analysis put the average cost of serious cap table mistakes at over $2 million when they trigger repricing or disputes. That's not a number you want attached to your seed round.

It also matters for you personally. Founders who don't model dilution end up shocked when they realize how little they own after a couple of rounds. The median founder gives up roughly 19% in a seed round and another 20% to 30% at Series A. Run that math across three rounds and your starting 50% can drop below 20% fast. You can't negotiate well against a process you don't understand.

What goes on a cap table?

A cap table lists every security the company has issued and who holds it. At minimum, each row shows the holder's name, the security type, the number of shares or units, and the resulting ownership percentage on a fully diluted basis.

The main categories you'll track:

Common stock. This is what founders and most early employees hold. Founders usually buy their shares for a fraction of a cent at incorporation.
Preferred stock. This is what venture investors get. It comes with extra rights like liquidation preferences, which is why it sits in its own bucket.
Options and the option pool. Shares reserved for employees and advisors, granted over time with vesting. The reserved-but-unissued portion still counts.
Convertible instruments. SAFEs and convertible notes that haven't turned into equity yet. These convert at a future round, and you need to model what they become.
Warrants. Less common early on, but track them if a lender or partner holds any.

One distinction trips up almost everyone: authorized versus issued versus fully diluted. Authorized shares are the maximum your charter allows you to create. Issued shares are what's actually been handed out. Fully diluted shares include everything outstanding plus all options, warrants, and convertibles as if they all existed today. Investors always negotiate ownership on a fully diluted basis. If you quote someone an issued-shares percentage, you're describing a company that doesn't really exist.

How do you build a cap table from scratch?

You build a cap table by starting with founder shares at incorporation and adding a new row every time ownership changes. The goal is one source of truth that you update the same day anything happens, not a file you reconstruct in a panic before a meeting.

Here's a practical sequence.

First, set your total share count at incorporation. Most startups authorize 10 million shares and issue the founder shares out of that. The exact number is arbitrary. What matters is the split. Two equal cofounders might each take 4 million shares, leaving room for a pool and future issuances.

Second, record the founder grants with the details that actually matter: number of shares, price paid, purchase date, and vesting schedule. The standard is four-year vesting with a one-year cliff. Write down the vesting start date, because it drives a tax filing we'll get to in a minute.

Third, carve out your option pool as its own line, even before you've hired anyone. Reserving the pool early makes your fully diluted math honest from day one.

Fourth, add every subsequent event as a new entry. New hire gets options? New row. Angel writes a $25,000 check on a SAFE? New row, flagged as a convertible. Advisor gets 0.5%? New row. Date and document each one.

Fifth, build a simple dilution model alongside the table. This is where you answer "what happens to my ownership if I raise $1.5 million at a $8 million post-money valuation?" You don't need fancy software for this part. A spreadsheet works, and tools like Foundra can help first-time founders model the financial side of a raise (what different round sizes do to ownership and runway) before you ever talk to an investor. You can find planning tools for this at foundra.ai/tools/. The point is to see the dilution before you sign it, not after.

How does dilution work across funding rounds?

Dilution works by issuing new shares to investors, which shrinks everyone else's percentage even though the number of shares you own stays the same. You're trading a smaller slice of a (hopefully) much bigger pie.

Walk through a simplified example. Say two cofounders each own 50% of a company with 8 million shares issued, plus a 2 million share option pool, for 10 million fully diluted. You raise a seed round where the investor gets 20%. To give them 20%, the company issues new shares, and after the round each founder's stake drops from 50% to around 40%. Nobody took anything from you. The denominator just got bigger.

Now do it again at Series A, where investors take another 25% and you expand the option pool. Each founder might land somewhere near 28% to 30%. This is normal. Across the whole journey, expect roughly 20% to 25% dilution per priced round, with seed often in the high teens to about 20% and Series A in the 20% to 30% range.

Two things founders miss. SAFEs and notes from earlier convert at the priced round, and that conversion dilutes you too, sometimes more than you expected if you raised a lot on uncapped or high-cap instruments. And the option pool refresh that investors request usually comes out of the pre-money valuation, meaning you absorb that dilution, not the new investor. Model both, or the headline terms will lie to you.

What about the option pool, and how big should it be?

Your option pool is the chunk of equity reserved for future employees and advisors, and it typically lands between 10% and 15% at the seed stage. Investors will push for a pool to be in place before they invest so their own stake doesn't get diluted by your future hires.

The data is worth knowing because there's a gap between what gets asked for and what's actually used. The median seed-stage option pool sits around 11.8%, with top-quartile companies closer to 16%. Investors sometimes ask for a "standard" 20% pool, but that 20% figure is often a negotiating move that lowers their effective price per share, since the pool comes out of your pre-money. Most startups only use 60% to 70% of their pool before the next round, which means an oversized pool is just extra dilution you handed yourself for no reason.

So size it to your actual hiring plan over the next 12 to 18 months, not to a round number. If you plan to hire four people and one advisor, build the pool from those grant sizes and add a small buffer. Then you can push back when an investor asks for more than you need.

Should you use a spreadsheet or cap table software?

Use a spreadsheet when you're pre-funding with a handful of shareholders, and move to dedicated software once you've raised money or started granting options to employees. The crossover point is usually your first priced round or your fifth or sixth stakeholder.

A spreadsheet is free and flexible, and for two founders and an advisor it's plenty. The risk is that spreadsheets break quietly. A formula error or a forgotten SAFE doesn't announce itself, and you find it during diligence at the worst possible moment.

Once real money and options are involved, software earns its keep because it ties the cap table to the underlying legal documents and handles things like 409A valuations and option grant tracking. A few common options for early-stage founders:

Carta Launch is free for early companies with up to 25 stakeholders and under $1 million raised, which covers most pre-seed setups.
Pulley offers a free tier and scales up to around $120 a month, and it's popular with accelerator-backed founders.
Cake Equity is well-rated for teams scaling headcount, and founders switching from pricier platforms report meaningful savings.

The tool matters less than the habit. Whatever you pick, update it the day something changes and keep the signed documents attached. A cap table is only worth as much as its accuracy.

What are the most common cap table mistakes?

The most common cap table mistakes are missing the 83(b) election deadline, confusing share types, and letting the document fall out of date. Each one is cheap to avoid and expensive to fix.

The 83(b) election is the big one. When you buy founder stock subject to vesting, you have 30 days from the purchase or transfer date to file an 83(b) election with the IRS. File it, and you're taxed on the tiny value of your shares today. Miss it, and you can owe tax as your shares vest and appreciate. The horror story is real: a founder with a million shares that grow from a tenth of a cent to $5 could face millions in taxable income with no liquidity to pay it. The clock starts at the transfer date (usually board approval), not when you sign, and there's no fixing a missed deadline.

The second mistake is mixing up authorized, issued, and fully diluted shares, which leads to mispriced grants and broken promises to hires. Quote ownership on a fully diluted basis, every time.

The rest are blocking and tackling. Unsigned stock purchase agreements. Verbal equity promises with no paper. Option grants approved by nobody. Forgetting to record a SAFE. None of these feel urgent in the moment, and all of them surface during diligence. Keep a clean stock ledger, attach the signed documents, and update the table the same day. Boring discipline beats a panicked cleanup.

Key takeaways

A cap table records who owns what in your company, and its only job is to be accurate. Investors read a clean one as a sign you run a tight ship.
Always think in fully diluted terms, which include options and convertibles as if they existed today, not just issued shares.
Expect roughly 20% to 25% dilution per priced round. The median founder gives up around 19% at seed and 20% to 30% at Series A.
Size your option pool (usually 10% to 15% at seed) to your real hiring plan, not to an investor's round-number ask. Most pools are only 60% to 70% used.
File your 83(b) election within 30 days of buying vesting stock. There's no second chance.
Start in a spreadsheet, then move to a tool like Carta Launch, Pulley, or Cake Equity once you raise or grant options. Model dilution before you sign, not after.

FAQ

What is a cap table in simple terms?
It's a list of everyone who owns a piece of your company, how much they own, and what kind of ownership it is. It answers "who gets what if we sell or raise money."

Do I need a cap table before I raise money?
Yes. Investors expect a clean, fully diluted cap table during diligence, and modeling your dilution beforehand is how you negotiate well. A messy one can delay a round by 4 to 8 weeks.

What's the difference between issued and fully diluted shares?
Issued shares are what's actually been handed out. Fully diluted shares include everything outstanding plus all options, warrants, and convertibles as if they existed today. Investors negotiate on the fully diluted number.

How big should my option pool be?
At seed, most pools run 10% to 15%, with a median near 12%. Size it to your hiring plan over the next 12 to 18 months rather than accepting a default 20% ask, since unused pool is just extra dilution.

When do I need cap table software instead of a spreadsheet?
Switch once you raise a priced round or start granting employee options, usually around your fifth or sixth stakeholder. Free tiers like Carta Launch cover most pre-seed companies.

What is an 83(b) election and why does it matter?
It's a tax filing you make within 30 days of buying vesting founder stock. Filing it lets you pay tax on the tiny value today instead of on the appreciated value as shares vest. Missing the deadline can create a large, avoidable tax bill.

Freemium vs Free Trial: Which Model Should You Pick?

Spencer Claydon — Sat, 13 Jun 2026 15:09:27 +0000

Freemium vs Free Trial: Which Model Should You Pick?

You've built something people can use. Now comes the question that quietly decides whether your startup makes money or just collects logos: do you give the product away forever with a paid tier on top, or hand people the full thing for two weeks and then ask for a card?

That's the freemium vs free trial decision. And founders agonize over it for the wrong reasons. They copy whatever Slack or Notion did without asking whether their product behaves anything like Slack or Notion. Pick wrong and you either drown in free users who never pay or scare off the curious ones who would have.

Here's the thing. There's no universally "better" model. There's a better model for your specific product, market, and cost structure. Let's walk through how to figure out which one is yours.

What's the difference between freemium and a free trial?

Freemium gives users a permanently free version of your product with limited features, while a free trial gives full access for a fixed window and then ends. That's the core split: freemium limits what you get forever, a trial limits how long you get everything.

With freemium, someone can use your free tier for years and never pay a cent. Think Spotify's ad-supported plan or Dropbox's 2GB. The free version is a real product, not a teaser. You're betting that enough free users eventually hit a wall and upgrade.

A free trial is a deadline. You get the whole product, every feature, for 7, 14, or 30 days. Then it locks. No deadline, no urgency, so the trial leans on a countdown to force the decision.

Some companies run both. HubSpot has free tools and trial-based upgrades. But for a first-time founder picking a default, you usually start with one.

Which model converts better, freemium or free trial?

Free trials convert at a higher rate than freemium, but that comparison is misleading because the two count completely different denominators. Trials turn a higher percentage of signups into payers; freemium turns a tiny slice of a much larger pool.

The benchmarks tell the story. A good freemium self-serve conversion rate sits around 3 to 5 percent, with exceptional products reaching 6 to 8 percent. Free trials look far healthier on paper: opt-in trials (no card upfront) convert around 8 to 9 percent, and credit-card-required trials hit roughly 31 percent according to widely cited SaaS benchmarks.

But read that carefully. A freemium product might pull 50,000 signups because the barrier is zero, then convert 4 percent into 2,000 customers. A trial product might pull 5,000 signups because asking for commitment scares people off, then convert 12 percent into 600 customers. Different shapes, different volumes.

So "which converts better" is the wrong question. The real question is which model produces more paying customers for the traffic and budget you actually have. A high conversion rate on a trickle of signups can lose to a low rate on a flood.

When does freemium actually make sense?

Freemium works when your free users create value just by existing, when the product spreads on its own, and when serving a free user costs you almost nothing. If none of those are true, freemium becomes a charity.

The first condition is network effects or virality. Slack got more useful as more teammates joined. Dropbox grew because shared folders dragged new people in. Calendly spreads every time someone sends a booking link to a non-user. In each case the free user is a marketing channel, not a freeloader.

The second is low marginal cost. Serving one more free Notion user costs pennies. If every free user runs expensive compute, sends you support tickets, or burns through API calls you pay for, freemium quietly bleeds you. I've watched founders give away a feature that cost them $4 a month per user to serve, then wonder why growth made the burn worse.

The third is a huge addressable market. Freemium needs scale because conversion is low. If only 4 percent pay, you need a lot of free users to build real revenue. A niche B2B tool with 8,000 possible buyers worldwide can't run the freemium math. A consumer app with tens of millions of potential users can.

Canva, Spotify, Zoom, and Mailchimp all fit this profile: broad market, cheap to serve one more person, and a product that gets shown off or shared in normal use.

When is a free trial the better call?

A free trial wins when your product delivers obvious value fast, when buyers are businesses with budgets, and when serving users costs enough that free-forever would hurt. Trials suit products people evaluate deliberately rather than stumble into.

If someone can feel the "aha" inside a week, a trial is ideal. Project management tools, analytics dashboards, and design software all show their worth quickly once you load real data in. The countdown then nudges a decision while the value is fresh.

Trials also fit higher-priced B2B products. When you're charging $200 a month, buyers expect to test the real thing before committing, and they're used to procurement timelines. A 14-day trial mirrors how they already buy. Ahrefs famously runs no free tier at all, because its data is expensive to produce and its buyers are serious.

And trials protect your margins when the product is costly to run. You're not supporting an unlimited population of non-payers forever. The free window closes, the cost stops, and only committed users stay.

One tactical note: requiring a credit card upfront roughly triples conversion rate (from about 9 percent to about 31 percent in the benchmarks) but slashes the number of signups. Card-required filters for intent. Opt-in casts a wider net. Test both if you can; don't assume.

What are the hidden costs of each model?

Both models carry costs that don't show up until you're months in, and they're the reason founders regret rushed decisions. Freemium's hidden cost is support and infrastructure; a trial's hidden cost is acquisition pressure and churn at the wall.

Freemium's quiet tax is that free users still email you, still need uptime, still consume resources, and still shape your roadmap with requests they'll never pay for. Your support load scales with total users, not paying ones. Many founders end up spending half their week serving people who structurally will never convert.

A free trial's hidden cost is the cliff. Everyone churns on day 14 unless you've earned the upgrade, so you need strong onboarding, activation nudges, and a reason to stay that lands inside the window. Trials also put constant pressure on the top of the funnel: since fewer people sign up, you need more traffic or spend to feed the same revenue.

There's also a positioning cost to freemium that people miss. A generous free tier can anchor your product as "the free thing," making it harder to charge real money later. Once users expect free, clawing features back to paid feels like a betrayal. You can box yourself into a corner you designed.

How do you choose between freemium and free trial?

Run your product through five questions and let the answers point you, rather than copying a company whose economics differ from yours. The model should follow your cost structure, market size, and how fast value lands.

Ask these:

Does serving one more free user cost me almost nothing? If yes, freemium is viable. If each user is expensive, lean trial.
Is my total market huge, or niche? Big and broad favors freemium. Small and specialized favors a trial.
Does the product spread on its own through normal use? Built-in virality rewards freemium. No virality means a trial captures value better.
How fast does someone feel the value? Instant and shareable suits freemium. A deliberate "load your data and see" suits a timed trial.
Who pays, a consumer or a business with a budget? Consumers lean freemium. Businesses tolerate, even expect, trials.

If you answer "cheap to serve, broad market, viral, instant value, consumer," you're a freemium company. If you answer "costly to serve, niche, no virality, deliberate value, B2B," you're a trial company. Most startups land somewhere in between, and that's fine. Pick the model that matches the majority of your answers, then adjust with data.

This is exactly the kind of decision worth mapping out before you write a line of pricing code. You can sketch it in a spreadsheet, in Notion, or in a planning tool like Foundra that walks first-time founders through monetization and go-to-market choices alongside the rest of the plan. The point is to decide on purpose, not by default.

Can you switch models later, or start with both?

Yes, you can switch or combine, but each path has friction, so go in with eyes open rather than treating it as free flexibility. Moving from trial to freemium is usually easier than the reverse.

Adding a free tier later (trial to freemium) tends to go smoothly. You already know your activation patterns and which features hook people, so you can carve a sensible free slice. Notion and many others widened access this way once they understood their funnel.

Going the other direction (freemium to trial, or pulling features back behind the paywall) is painful. Existing free users feel robbed, you get churn and angry threads, and your reputation takes a hit. If you're unsure, start with a trial. It's the easier door to walk back through.

Running both at once, a "reverse trial," is increasingly common: give full access for 14 days, then drop users into a limited free tier instead of a hard wall. You get the trial's urgency and the freemium safety net. It's more complex to build and measure, so it's usually a phase-two move once you've learned how people actually use the product.

Key takeaways

Freemium limits features forever; a free trial limits time. They attract different users and produce different funnel shapes.
Trials convert at a higher rate (roughly 8 to 31 percent depending on whether a card is required) but freemium converts a small slice (3 to 8 percent) of a much larger pool. Volume can beat rate.
Choose freemium when serving a user is cheap, the market is huge, the product spreads on its own, and value is instant. Think Slack, Dropbox, Spotify.
Choose a free trial when the product is costly to run, the market is niche or B2B, and value lands fast inside a short window. Think Ahrefs.
Watch the hidden costs: freemium taxes you with support and infrastructure; trials pressure your funnel and churn hard at the deadline.
Switching from trial to freemium is easier than the reverse, so when in doubt, start with a trial. Map the decision deliberately before you build it.

FAQ

Is freemium or free trial better for a B2B SaaS startup?
A free trial is usually the better default for B2B, especially at higher price points, because business buyers expect to evaluate the full product before committing and are comfortable with short timelines. Freemium can still work for B2B if the product spreads inside teams, like Slack did, but most niche B2B tools convert better with a card-required or opt-in trial.

What's a good freemium conversion rate?
A good freemium self-serve conversion rate is about 3 to 5 percent, and 6 to 8 percent is exceptional. Because the rate is low, freemium only works at scale, so you need a large pool of free users for those percentages to add up to real revenue.

Should I require a credit card for my free trial?
Requiring a card roughly triples your trial-to-paid conversion rate (from around 9 percent to around 31 percent in common benchmarks) but sharply cuts how many people sign up. Card-required filters for serious buyers; opt-in fills the funnel. If you have lots of traffic, opt-in can win on volume; if traffic is scarce, card-required concentrates intent.

How long should a free trial be?
Most SaaS trials run 7 to 14 days, and shorter often beats longer because it creates urgency and forces engagement while interest is high. Pick a length that lets a motivated user reach the product's "aha" moment, then end it. A 30-day trial usually just delays the decision without improving it.

Can I offer both freemium and a free trial?
Yes, the "reverse trial" gives full access for a set period, then drops users into a limited free tier instead of cutting them off, combining a trial's urgency with freemium's safety net. It's more complex to build and measure, so most startups add it after they understand their funnel rather than launching with it.

What model do most successful startups use?
It splits by category: broad consumer and viral products lean freemium (Spotify, Canva, Zoom, Dropbox), while higher-priced or data-heavy B2B products lean toward trials or no free tier at all (Ahrefs). The pattern isn't about which is trendier, it's about cost to serve, market size, and how the product spreads.

How to Know When to Pivot Your Startup (5 Clear Signals)

Spencer Claydon — Mon, 08 Jun 2026 15:11:54 +0000

How to Know When to Pivot Your Startup (5 Clear Signals)

Six months in, your numbers aren't moving. Customers say nice things on calls, then ghost the invoice. You've shipped three rebuilds. Engagement is flat. You're staring at the runway spreadsheet wondering if you're about to make the worst mistake of your career, or if you already have and just haven't admitted it.

This is where the pivot question lives. Knowing when to pivot your startup is one of the highest-leverage decisions a first-time founder ever makes. Pivot too early and you abandon a thing that was about to compound. Pivot too late and you burn the runway you needed to build the right thing. This piece breaks down the signals, the framework, and the trap doors so you can make the call with data instead of dread.

What does it actually mean to pivot a startup?

A startup pivot is a structured change to your business model, product, customer, or channel, made because the current version isn't producing the growth you need. It's not quitting. It's not a redesign. It's a deliberate decision to change one core variable while keeping the rest of the business intact.

Eric Ries coined the modern definition in The Lean Startup: "a structured course correction designed to test a new fundamental hypothesis about the product, strategy, and engine of growth." The important word is hypothesis. A pivot replaces a hypothesis that didn't work with a new one. It's not panic. It's not a complete reset. It's a swap of the variable that's most clearly broken.

Famous examples make the pattern obvious. Slack started as a multiplayer game called Glitch and pivoted to the internal chat tool the team had built for themselves. Instagram started as a check-in app called Burbn and pivoted to photo sharing after the team noticed users only cared about that one feature. YouTube was a dating site. Shopify was a snowboard store. Twitter started inside a podcasting company called Odeo. In every case the founders kept something (the team, the tech, the insight) and changed something else (the product, the audience, or the model). That's the shape of a real pivot.

How do you know when to pivot your startup?

You know it's time to pivot when at least two of these five signals show up at once and stay for 60 to 90 days despite serious effort to fix them.

1. Your retention is broken and you can't figure out why. Acquisition is the easy part. Retention is the truth. If users sign up, try the product, and never come back, you don't have a startup. You have a feature people were curious about. Sean Ellis suggests a useful threshold: if fewer than 40% of users would be "very disappointed" if your product disappeared, you don't have product-market fit. After 90 days of trying to fix activation, onboarding, and core loops without that number moving, retention is telling you the product itself is wrong, not the polish.

2. You're growing, but only when you push. Paid acquisition works. Outbound works. Your founder energy works. But the moment you stop pushing, nothing moves. No word of mouth, no organic compounding, no return visits. Real product-market fit pulls. If you're always pushing, you're not there.

3. Your unit economics don't work and can't work. You've done the math. CAC is $400 and LTV is $180. You've tried to fix the inputs: raised price, lowered CAC, extended retention. The gap is structural. If you can't see a credible path to fixing it in the next two quarters, the business model itself needs to change.

4. Customers want a different thing than what you built. You keep hearing the same off-script comment: "I love this, but what I really need is..." When that off-script ask shows up in 30%+ of conversations and points to the same adjacent problem, that's a market telling you the real product. Burbn's users wanted photo sharing. Glitch's team wanted internal chat.

5. Your founders' conviction is gone. You no longer believe the thing. You're showing up because of sunk cost, not because you can see the future. Startups are 5+ year commitments executed on grim days. If you've stopped believing in the specific problem, no amount of tactical change will save you. The fix isn't always a pivot. Sometimes it's a break. But ignoring it is the most expensive mistake on this list.

One signal can be noise. Two or more, persistent for a full quarter, is the data calling. Make the decision with that data, not with the next bad week.

What's the difference between pivoting and persevering?

The difference is whether your current hypothesis is still being tested, or whether the test has finished and the answer is no.

You should persevere when you're still learning. Every cohort is teaching you something. Retention numbers are slowly improving as you tune the product. Customer conversations are surfacing new specifics, not the same dead end. You haven't yet shipped the version that would truly test your core hypothesis. In that case the right move is to stay heads down and ship.

You should pivot when the hypothesis has been tested and the result is clear. You've shipped three real iterations. You've talked to 50+ customers. You've tried two go-to-market motions. The data is in. It says no. Spending the next quarter polishing a no is the most expensive thing a founder can do.

The honest test: write down the specific hypothesis you're testing in one sentence. Then write down what would have to be true in the data for you to know it's working. If those metrics aren't moving after a real shot, you've answered the question. Persevering past that point isn't grit. It's denial wearing grit as a costume.

What are the most common types of startup pivots?

There are six pivot types that account for most of the successful course corrections in startup history.

Customer segment pivot. Same product, different buyer. You built it for SMBs and they churn at 8% monthly. Enterprise customers love it and pay 10x. Move upmarket. Slack did versions of this early on. Notion went deeper into prosumers before becoming a real B2B tool.

Problem pivot. Same customer, different problem. You serve restaurants. You sold them reservations software. Turns out their bigger problem is staffing. Build for the bigger problem with the same customer relationships intact.

Product/feature pivot. Same problem, different product. Instagram zoomed in on the one feature inside Burbn that worked. Groupon shrank The Point's broad "collective action" platform into one specific product: daily deals.

Business model pivot. Same product, different way to make money. Move from one-time fee to subscription. From freemium to sales-led. From B2C to B2B2C. The product stays. The economics change.

Channel pivot. Same product, different distribution. You were going direct-to-consumer and CAC is brutal. Move to partnerships, a marketplace, or a wholesale motion.

Technology pivot. Same problem and customer, different tech. You built on-prem; the market moved to SaaS. You built generic AI; the market wants vertical AI. Value prop stays. Platform changes.

Most founders pick one variable to change, not all six. The pivot that works is the smallest change that clears the broken signal. Change one thing. Test. Read the data.

How do you decide what to pivot to?

You decide what to pivot to by mining the data you already have, not by brainstorming new ideas from scratch.

Look at three sources. First, your retained users. If any cohort stuck, study them obsessively. Who are they? What problem are they actually solving with your product? That cohort is almost always pointing at a better business hiding inside the one you have. Second, your off-script conversations. Pull the last 30 customer calls and tag the recurring "what I really need" comments. Patterns there are gold. Third, your team's accidental wins. The Slack pivot wasn't strategic. The team had built internal chat because they needed it. What your team builds for itself is usually what other teams secretly need too.

A useful filter: the new direction should pass three tests. Can you reach the new customer with the team and assets you already have? Is the problem big enough that a $39 to $390 per month price feels small? Can you ship a credible v1 in 6 to 12 weeks without raising more money? If any answer is no, you're not pivoting. You're starting a different company. That might be the right call, but name it.

Frameworks like the lean canvas help structure this. So do the free planning tools at foundra.ai/tools/. The point isn't the template. The point is to force the new hypothesis into one page so the team can pressure-test it before the rebuild.

How do you pivot without losing your team and investors?

You pivot without losing them by getting in front of the decision with data, not after the decision with hope.

For your team: pivots that go badly are almost always the ones where the founder announces the change at an all-hands and the team hears it as panic. Pivots that go well start with one or two trusted teammates pulled into the data weeks before. By the time you announce, the senior people already know the why. Frame it as the team's pivot, not yours. What destroys morale is a founder who looks scared. What builds it is a founder who shows the numbers, names the broken hypothesis, and lays out the new bet in detail.

For your investors: they expect pivots. What they don't expect is to find out from a casual update three months in. Brief them before the decision is final. Show them the data. Walk them through the new hypothesis and what would have to be true for it to work. Tell them how much runway the pivot needs and what milestones you'll hit. Investors fund founders who run the company with eyes open and cut founders who look like they're flailing. The difference is mostly about how you communicate, not whether you pivot.

For your customers (if you have paying ones): be direct. Tell them what's changing and why. Offer them a path. Either they come with you or you help them transition off. Founders who burn paying customers during a pivot lose the reference accounts they'll need for the next chapter.

What are the biggest mistakes founders make when pivoting?

The biggest pivot mistakes are pivoting too small, pivoting too often, and pivoting to the wrong variable.

Pivoting too small is the most common. The product was a productivity tool for marketers. The new pivot is a productivity tool for marketing managers at SaaS companies between 50 and 200 employees. That's not a pivot. That's a positioning tweak. If the underlying signal is broken retention, a tighter ICP almost never fixes it.

Pivoting too often kills momentum. A team that pivots every 90 days never ships the version that would actually test the hypothesis. Commit fully for at least 6 months. If you find yourself drafting a third pivot inside a year, the problem usually isn't the strategy. It's a conviction problem worth surfacing.

Pivoting to the wrong variable wastes runway. If acquisition is broken, don't pivot the product. If the product is broken, don't pivot the channel. Identify which variable the data is actually flagging and change that one, not the one you find most fun to change. Founders who love product over-pivot product. Founders who love sales over-pivot channel. Catch your own bias.

The last mistake is rebranding a pivot as a "small adjustment" to avoid the optics hit. People can read it. Call it what it is.

Key takeaways

The pivot decision is a data decision dressed up as an emotional one. Strip the emotion and look at what the numbers and conversations are telling you over a full quarter, not a bad week. Two or more of the five signals (broken retention, push-only growth, broken unit economics, off-script customer asks, lost founder conviction) is the data calling. Pick the smallest variable that clears the broken signal. Decide what to pivot to by studying your retained users and accidental wins, not by brainstorming fresh ideas. Bring your team and investors in before the decision is final. Commit for at least 6 months before considering another pivot.

If you're working through this decision right now, write your current hypothesis on one page, name the metrics that would prove it's working, and check whether the data is moving. Foundra's free planning tools at foundra.ai/tools/ can help force that one-page clarity before you spend more weeks building.

The founders who pivot well aren't braver than the ones who don't. They just look at the data sooner and act on it without flinching.

FAQ

How long should you give a startup before you pivot?
At least one full quarter of real product effort against a clear hypothesis, with at least 30 customer conversations and 3 meaningful product iterations. Less than that and you don't have enough data to know whether the idea or the execution is broken. More than 9 months stuck on flat numbers and you're probably past due.

What percentage of startups pivot?
Research from the Startup Genome Report and CB Insights consistently shows that around 70 to 75% of successful startups pivot at least once before finding the model that works. Pivoting isn't a sign of failure. It's a sign of a team that's reading the data.

Can you pivot without telling investors?
You technically can, but you almost certainly shouldn't. Most early-stage investor agreements include material change clauses, and even when they don't, finding out about a pivot through a casual mention later destroys trust faster than the pivot itself. Brief them before the decision is final. Investors fund founders who run the business with their eyes open.

Is a pivot the same as a rebrand or repositioning?
No. A rebrand changes the name, look, or message. A repositioning changes how you talk about the same product to the same buyer. A pivot changes a core variable: the customer, the problem, the product, the model, the channel, or the tech.

How do you know if you're pivoting too often?
If you've changed core direction more than twice in a year, you're probably pivoting too often. The new hypothesis needs at least 4 to 6 months of focused execution before you can fairly read the data. Founders who pivot every quarter rarely give any version a fair shot.

Should a solo founder pivot the same way a team does?
The decision logic is identical. The communication burden is lighter. The risk is that solo founders skip the customer conversations and pivot on gut feel because there's no one in the room forcing them to defend the data. Build a small group of founder peers or advisors who can pressure-test the new hypothesis before you commit.

How to Write a Cold Email to Investors That Gets Replies

Spencer Claydon — Sun, 07 Jun 2026 15:10:25 +0000

How to Write a Cold Email to Investors That Gets Replies

If you don't have warm intros, you'll need to cold email investors. Most founders do it badly. They write long, vague pitches that read like a press release and end with a calendar link, then wonder why nobody replies.

The math on cold outreach for first-time founders isn't friendly. A solid cold email to a relevant investor converts to a meeting at around 5 to 15 percent. Bad cold emails sit at under 1 percent. The difference isn't luck. It's craft. A good cold email respects the investor's time, signals real traction in three sentences, and asks for something small.

This guide walks through how to write a cold email to investors the way a founder who's done it would explain it. We'll cover what to say, what to cut, how to find the right addresses, and the specific patterns that move reply rates from ignorable to 1 in 5.

When should you cold email investors instead of getting warm intros?

You should cold email investors when warm intros are too slow, too few, or unavailable, which is the default situation for most first-time founders. Warm intros remain the highest-converting channel, but the assumption that you should never cold email is wrong. Investors invest in cold deals. They reply to cold emails. They have to, because if they only met founders inside their existing network, they'd miss the next outlier.

That said, cold outreach is best used in three situations. The first is when you're early in building your network and the only intro path leads through people who don't know your work yet. The second is when you've identified a specific partner whose thesis aligns precisely with what you're building, and you can write an email that proves it. The third is when you're filling out a round and need to add 5 to 10 more conversations quickly.

Don't cold email if you can get a warm intro inside two weeks. Don't cold email 200 funds with the same template. A cold email is a sniper rifle, not a shotgun. Pick 30 to 60 investors, research each one, and write something they couldn't get from anyone else.

What makes a cold email to an investor actually work?

A cold email works when it gives the investor a reason to reply in under 90 seconds of reading. That means relevance, specificity, signal, and a small ask. Miss any of those four and your email gets archived.

Relevance means the investor invests in your stage, sector, and geography. Pitching a seed deep tech round to a Series B SaaS investor is a self-inflicted no. Spend 5 minutes per investor reading their portfolio and recent posts before you write anything.

Specificity means the email is clearly to that person, not a generic blast. Reference a portfolio company, a podcast appearance, a recent tweet, or a thesis essay. Two sentences of real research beats four paragraphs of flattery.

Signal means traction, team, or insight that makes the investor want to learn more. Numbers do the heavy lifting here. A 40 percent week-over-week growth number, a $15K monthly revenue figure, or a 35-customer pilot list moves an investor more than a vision statement ever will. If you don't have numbers, lead with a non-obvious insight about your market that proves you understand it.

A small ask means a 15 to 20 minute call, not a 60 minute meeting and a deck review. The bar to a yes should be low. Asking for "feedback" or "your perspective" sometimes works for very early-stage outreach but is more likely to look like you're avoiding the real ask. Ask for the call directly.

What's the right structure for a cold email to an investor?

The right structure is short, scannable, and front-loaded with the most interesting thing about your company. The 7-sentence structure below is what most successful fundraising founders converge on after a few rounds of iteration.

Sentence 1: A specific reason you're writing to this investor, not any investor.

Sentences 2 to 3: One sentence on what you do, in plain English, and one sentence on why now.

Sentences 4 to 5: The strongest traction or proof point you have, with numbers. If you have no traction, replace this with a sharp insight about the problem that proves you've done the work.

Sentence 6: Round info if you're raising, in one line. Stage, size, lead status, close timing.

Sentence 7: The ask. A 15-minute call this week or next.

Subject line: short, specific, and includes a number or a noun the investor cares about. Examples that get opened: "Foundra: $9K MRR, 40% WoW, pre-seed", "From a [Portfolio Co] customer: notes on the AI sales tooling market", or "[Mutual contact name] suggested I reach out, pre-seed AI infra".

Skip the deck attachment. Link it in a single sentence after your sign-off if they want to dig in: "Deck here if useful: [link]." Attachments trigger spam filters and add friction. A Notion or Pitch link the investor can preview is better than a PDF.

How should you find investor email addresses and pick targets?

You find investor emails through fund websites, Signal, OpenVC, LinkedIn Sales Navigator, and email-finding tools like Hunter, Apollo, or Clearbit. Most investor emails follow predictable formats: firstname@fund.com, first.last@fund.com, or firstinitiallastname@fund.com. Try the most common format first, then verify with a tool like NeverBounce or Hunter's email verifier before sending.

For target selection, build a list of 40 to 80 investors using these filters in this order. First, stage match. If you're raising a $1M pre-seed, target funds that lead or follow at pre-seed and seed. Series A funds will not look at you. Second, sector match. Read the last 5 to 10 investments. If they're nothing like you, skip. Third, partner match. Find the specific partner at the fund who has invested in adjacent companies or written about your space. Cold emails to "info@" or "hello@" go nowhere. Pitching the senior partner when an associate covers your space wastes everyone's time.

Useful sources to build the list. NFX Signal is free and excellent for identifying active early-stage investors. OpenVC has 5,000+ investor profiles with check sizes and theses. AngelList for angel investors and emerging managers. Crunchbase for investor histories. LinkedIn for partner backgrounds and recent activity. X (Twitter) for the partners who write publicly about your space, which tells you they care.

Many founders find their first investor traction by tracking who recently invested in companies one degree adjacent to theirs. If three different funds led seed rounds in your nearest analogues in the last 18 months, those three funds are the right starting list.

What should you absolutely not put in a cold email to an investor?

You should not put long backstories, jargon, hedging language, calendar links before context, or paragraphs longer than two sentences. The single biggest mistake first-time founders make is treating the cold email as a place to explain their entire company. It's not. It's a place to earn the meeting.

Cut these patterns immediately. Long opening paragraphs about your "journey" or "mission". The investor doesn't know you yet, so the personal mission feels like noise. Jargon-stacked descriptions like "AI-native vertical SaaS platform for the modern healthcare workflow". If your mom can't understand the sentence, rewrite it.

Drop the hedging. "I know you're busy, but..." or "I hope this isn't too forward..." signals you don't believe the email is worth their time, so why should they? Confidence isn't bragging. It's clarity.

Avoid the "What I'm looking for: smart capital, strategic guidance, and a true partner" line. Every founder says it. None of them mean anything by it.

Don't open with a Calendly link. Calendly links in the first email feel transactional and presumptuous. Ask for the meeting, then send the link after they say yes.

And don't BCC 50 investors on the same email. They will know. Investors talk to each other, and a forwarded chain showing up in someone's inbox three times is the cleanest possible signal that the round is being shopped indiscriminately.

How do you follow up on a cold email to an investor without being annoying?

You follow up two to three times, spaced 5 to 7 days apart, with each follow-up adding new information. Most first-time founders give up after one unanswered email. Most successful fundraising founders convert 30 to 40 percent of their replies on follow-up 2 or 3.

The first follow-up should be 5 days after the original. Keep it short. "Quick bump on the below. Since I wrote, we shipped X and closed Y in revenue. Still open to a 15-minute call next week?" The new information matters. Without it, the follow-up looks needy.

The second follow-up, 7 days after the first, should add real signal: a new customer, a new investor commit, a press mention, or a metric update. "Update: [Tier-1 fund] just committed $500K to our pre-seed and we have $300K remaining. Closing in 3 weeks. Worth a quick 15 minutes before we wrap?" Scarcity is real if it's real. Faking scarcity blows up immediately the moment investors talk.

After follow-up 2 or 3, stop. Three emails over three weeks with no reply means it's a no. Move on. Don't send a passive-aggressive "I assume you're not interested" email. It burns the relationship for the next round.

The reply rate math: out of 50 cold emails, expect 10 to 20 responses across 3 touchpoints. Of those, 4 to 8 convert to first meetings. Of those, 1 to 3 progress to second meetings. That conversion funnel only works if your underlying email is strong. A weak email at scale just teaches the market your company isn't interesting.

What does a good cold email to an investor actually look like?

A good cold email looks short, sharp, and clearly written for one specific investor. Here's a working example built for a fictional pre-seed AI sales tooling startup, written to a fictional partner at a fund that's invested in adjacent companies.

Subject: AI sales tooling: $11K MRR, 38% WoW growth, pre-seed

Hi Rachel,

I noticed you led the seed round in Clay last year and wrote about why outbound is being rebuilt from the ground up. We're building a related layer for the next stage of that thesis.

Foundra Outreach (working name) is an AI-native cold email platform for B2B sales teams that generates personalized first-touch emails from a single ICP definition and learns from reply data. Outbound reply rates have collapsed in the last 18 months, and the existing tools optimize for volume, not signal.

We launched the closed beta 8 weeks ago. 27 paying B2B customers, $11,400 MRR, 38% week-over-week growth across the last 6 weeks. Founder is ex-Outreach engineering, former founder of a B2B SaaS acquired in 2023.

Raising a $1.2M pre-seed with $600K committed from [named angel] and [named seed fund]. Closing in 4 weeks.

Open to a 15 minute call next Tuesday or Wednesday?

Best,
Spencer

Word count: 138. Read time: 35 seconds. Every sentence does work. The opener proves research. Sentences 2 to 3 explain the company and the market shift. Sentences 4 to 5 give numbers and team signal. Sentence 6 frames the round. Sentence 7 makes the small ask. No deck attached, no calendar link, no fluff.

You can swap the specifics for your business and keep the same structure. Founders who follow this template consistently report 1 in 5 to 1 in 7 reply rates against well-targeted investor lists.

Key takeaways

Cold email investors when warm intros aren't fast enough, but pick 30 to 60 high-fit investors and write something custom for each one. The investor cold email that works is short, specific, front-loaded with traction, and ends with a small ask. Use the 7-sentence structure, never attach a deck in the first email, and follow up two to three times with new information.

Skip the long backstory, the jargon, the Calendly link in email 1, and the BCC blast. Track your reply rates and iterate on your subject lines and traction sentences every week. If your structure is right and your numbers are real, replies will come.

For a free framework to clean up your traction story and round narrative before you start sending, check the planning tools at foundra.ai/tools/. Most cold emails fail because the founder hasn't clarified their own story yet, not because the email itself is bad.

FAQ

How long should a cold email to an investor be?
Under 150 words, ideally 100 to 130. Investors read on their phones between meetings. If they have to scroll, they archive.

Should I attach my pitch deck to a cold email?
No. Link it after your sign-off if you want, but never attach. Attachments trigger spam filters and slow down loading. A linked Notion, Pitch, or DocSend page lets the investor preview without commitment.

Is it okay to cold email a senior partner at a fund?
Yes, if your traction or team actually matches their bar. If you're earlier than their typical check, target the principal or associate who covers your space. They have the incentive to find new deals and bring them in.

What time of day should I send cold emails to investors?
Tuesday through Thursday, between 7 and 9 am local time for the investor. Avoid Mondays (full inbox) and Fridays (mental checkout). Send to one timezone at a time so follow-ups land on the right day.

How many investors should I cold email at once?
Start with 10 to 15 highly-targeted emails. Read the reply rate. Iterate on subject line and traction sentence. Then scale to 30 to 60 total over 3 to 4 weeks. Anything beyond 80 starts to look like spray-and-pray and your conversion will collapse.

What if I have no traction or revenue yet?
Lead with an insight that proves you understand the market in a way most founders don't, plus team signal. Pre-revenue cold emails work, but only with a sharp wedge and a relevant founder background. If neither is true, build for 3 more months before raising.

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.