32 resources from SaaStr we point founders to, and the questions each answers.
📄 Article
✓ Link checkedFreeBeginner
Why we picked it
This is the founder-voice argument for our exact answer, written by the founder of EchoSign. Lemkin's four reasons map one-to-one onto why you send updates with zero legal obligation: they force you to face your own numbers honestly (he tells of a founder who dodged updates for four months and only then saw his unit economics had rotted), they end the isolation, they create financial-discipline checkpoints, and they respect the people who wired you money. It nails the point that the update is most valuable precisely when you least want to write it.
Why we picked it
This is the market-type analysis your question needs, from someone who has funded hundreds of SaaS companies. Lemkin quantifies the cost of a slow bootstrap (roughly two extra years to reach initial traction, two more to reach scale) and names the exact market where it breaks: competing head-on with three other funded teams doing the same thing at a low win rate. He also names where it wins: weak direct competition, underserved SMB segments, and a geographic cost edge, a list that maps directly onto Indian SaaS.
Bootstrapping to your first 1M ARR then raising avoids early dilution and works, but budget roughly four extra years to IPO
It fails when you are fighting funded competitors head-on in the same segment with a low win rate, the winner-take-all trap
A cost or geographic edge (his examples: Atlassian in Australia, Qualtrics in Utah) buys you the time a bootstrap needs, and Indian engineering economics are exactly this edge
Why we picked it
This is a straight judgment call from Jason Lemkin, who has seen thousands of SaaS pricing pages, on when hiding your price is a real strategy versus just fear. He is honest that early-stage founders who are still experimenting with what to charge have a legitimate reason to keep enterprise numbers off the page, while also naming the cost: smaller buyers bounce when they cannot self-qualify on budget. Read it as a starting point for your own call, not a rule.
Hiding price buys you flexibility while you are still figuring out what to charge, but it adds friction and quietly turns away smaller buyers who want to check budget before they talk to anyone.
The right answer depends on who you sell to: self-serve and smaller deals reward showing a real number, genuinely custom enterprise deals can justify a Contact button.
Buyers now expect transparency and AI-first products are leaning further into it, so treat hiding price as a deliberate choice you can defend, not a default.
Why we picked it
This is the cleanest statement of the per-round rule of thumb backed by Carta's data across 1,200+ rounds: roughly 20 percent at seed, 20 percent at Series A, 15 percent at Series B, then 10 to 15 percent. Lemkin's blunt closing point (that dilution adds up and there are real benefits to being efficient instead of chasing every round) is exactly our stance. Do the arithmetic on those numbers and two founders splitting the company are already near the single digits by Series B if every round runs hot, which is why you model forward before you sign.
Why we picked it
This is the data-room number, not the slide: a free, download-and-fill spreadsheet from a Point Nine partner that builds MRR movements, churn, CAC payback, LTV, a headcount-driven cost plan, and a monthly cash position. Build the shape of your business here, then lift the three to five headline numbers onto your traction slide and hand this whole file over when an investor asks for the proof.
Why we picked it
For the practitioner gut-check on how much services revenue is actually healthy, SaaStr is the reference voice, and Jason Lemkin has run these numbers across hundreds of software companies. His consistent take: roughly 8 to 10 percent of revenue from services is normal, up to about 20 to 25 percent is still fine for true enterprise, and services that speed adoption and lock in customers are worth doing even at break-even. Listen for the framing that services should support the product, not become the business.
On
SaaStrby Jason Lemkinepisodes roughly 25 to 40 min
Most enterprise SaaS companies pull about 8 to 10 percent of revenue from services, and up to roughly 25 percent is still normal for genuine enterprise deals.
Many companies run services near break-even on purpose, because they speed adoption and reduce buyer fear, not because they are a profit center.
If services revenue creeps past about a quarter of the total, investors start pricing you as a services business, not a software one.
Why we picked it
This is the exact question you are asking, answered by someone who has sold a lot of enterprise software. Lemkin gives you a usable rule instead of platitudes: say yes when the feature is reusable by other customers and fits your next 24 months of roadmap, charge for it either as a one-time fee or a higher annual price, and cap the share of engineering you spend on any one big deal. It is a starting point for turning a gut call into a repeatable filter.
Say yes mainly when the requested feature can be sold to other customers and already fits your roughly 24-month roadmap, not because one account is loud or large.
Price the custom work, either as a one-time fee or baked into a higher annual contract, so bespoke building at least breaks even instead of quietly becoming a cost center.
Put a ceiling on it: allow only a small slice of engineering (he suggests around 10 percent of story points) for big-deal customization, and do one or two at a time so the roadmap stays yours.
Why we picked it
This is the most concrete, no-fluff answer we found to the actual mechanics question: how much do I give up to get a customer to pay a year (or three) upfront. Lemkin's key move is worth stealing, price the monthly/non-annual plan higher and frame annual as the discount, so you collect cash today without truly eroding your price. It is a starting point on the numbers, not a rule; your churn and stage change the math.
From
SaaStrby Jason LemkinShort read, about 6 to 8 minutes
A 15 to 20 percent annual discount is the well-understood norm for smaller customers, but you can mark up monthly pricing about 25 percent so the annual price is your real target and the discount is mostly on paper.
Go deep on multi-year prepay only if churn is high; if you would have renewed that customer anyway, a big 3-year discount trades a lot of future revenue for cash today.
For strong brands, guaranteed no-price-increase for 3 years can beat a headline percentage discount, especially with enterprise buyers.
Why we picked it
Jason Lemkin has funded and built enough companies to say plainly that staying revenue-funded and keeping your ownership is doable, while being honest that it takes roughly four years longer to reach real scale. It is a useful counterweight when the whole ecosystem is telling you the only way up is to sell equity. Treat it as one experienced perspective on the trade you are making, not a promise that slow-and-owned always wins.
You can reach real scale without VC, but expect it to take meaningfully longer, so keeping control has a time cost you should name upfront.
Bootstrapped companies usually win by starting with smaller customers and moving upmarket slowly, since you cannot buy an expensive enterprise sales team on day one.
The point of preserving ownership is optionality: a smaller cap table means fewer people you owe an exit to, which is worth protecting when you take on any outside cash.
Why we picked it
Where Graham gives the principle, Lemkin gives the honest tradeoff table so you can actually decide. He lays out both sides (a high cap buys runway and dilution protection, but it locks you into 2x-or-bust expectations, higher burn, and a narrower set of exits that clear investor return hurdles) and names the asymmetry that should govern the call: crush your numbers and nobody remembers the price you charged, miss them and the high mark is what everyone remembers.
Why we picked it
This is the piece for the judgment call in the question: what actually crosses the line into disclosure. Lemkin's rule is sharp, explain the stumble before it shows up in the numbers, not after, which draws a clean boundary between a material risk you must flag and the day-to-day friction you keep to yourself. It tells you the difference between an investor who backs you in the next round and one who feels lied to.
Why we picked it
Lemkin, who has funded and passed on many bridges, tells you bluntly which bucket you fall into: the 0x 'bridge to nowhere' (founder hid the burn until weeks of cash were left), the 1x survival extension, or the 10x bridge for a proven winner hit by a temporary headwind. His single most useful line for an Indian founder short on runway: communicate cash position monthly and raise the topic with 6 to 8 months left, not at crisis, because that is the difference between a confident insider yes and a panicked one. It shows you the exact founder behavior that reads as opportunity versus desperation.
Why we picked it
This is the reset playbook in one page. Lemkin makes the distinction that saves you from panicking: a soft miss (still growing quarter over quarter, just slower than your deck) gets acknowledged and moved past, while a hard miss (bookings actually down) gets an immediate re-forecast of revenue AND cash. His hardest line is the one that resets your credibility: stop managing burn against your stretch deck and run on the base plan only, which is exactly the muscle an Anywhere Founder in India needs when the runway math is unforgiving.
Separate a soft miss (still growing, missed a stretch goal) from a hard miss (bookings declined); they call for different reactions, and treating a soft miss like a crisis burns trust for no reason.
Re-forecast revenue and cash the moment you know, accept the miss is permanent (you cannot make it up next quarter), and bring in an outside pair of eyes for the root-cause read.
Communicate a credible recovery plan with clear milestones, and stop running your burn against stretch projections: budget to the base plan you can actually hit.
Why we picked it
A Sequoia partner says the quiet part out loud: the reaction to the miss matters more than the miss itself. Hilaly's move is to control the narrative by walking in with your own analysis already done, and to name whether the miss is tactical (a wrong hire you can fix) or structural (the market shifted under you) so investors calibrate to reality instead of imagining the worst. It reframes the update from a confession into you setting the new plan, which is precisely the under-promise-then-beat-it posture that rebuilds a track record.
On
SaaStrby Aaref Hilaly (Sequoia Capital)25 min (video + transcript)
Own the miss and control the narrative: present the analysis upfront yourself rather than letting investors fill the silence with a worse story.
Distinguish a tactical miss (fixable, like a bad hire) from a structural one (competition, market), because investors treat those very differently and you want them calibrated correctly.
Put the board to work on recovery (intros, recruiting, product calls) so they are invested in the comeback instead of just grading the shortfall.
Why we picked it
This is the empirical spine for the employee half of your answer, built on Carta data from 50,000 real cap tables, not opinion. It shows equity drops fast: hire #1 sits around 1.5% at median (0.5% to 4% range), hire #2 at 0.85%, hire #3 already near 0.5%. That anchors your 0.5% to 2% call for a genuinely early, critical below-market hire and tells you exactly how fast to shrink grants as you keep hiring.
Why we picked it
Lemkin gives you the exact sequencing this question needs: close 10 to 20 customers yourself first, then hire two reps (not one, so you can tell talent from luck), and do not touch a VP of Sales until those reps are already hitting quota. His one-line filter, do not hire someone you would not buy your own product from, is the sharpest gut-check an untrained founder can apply in an interview.
Why we picked it
When the big customer's wishlist lands on your desk, this gives you a hard gate instead of a gut call: build the custom feature only if it is already on your 24-month roadmap, the contract is 1+ year and paid a lot (never for a pilot), the customer does not demand exclusivity, and you have met them yourself. Lemkin's reframe is the repeatability test in action: if one enterprise wants it and it fits your roadmap, at least nine more will, so it stops being custom and becomes product direction. His "do 1 to 2, not the 10 to 12 sales asks for" line is the discipline that keeps one account from eating the plan.
Only build the custom ask if it is already on your roadmap AND a paid 1+ year contract, otherwise it is a services project in disguise.
If a big customer wants something on your roadmap, treat it as a paid preview of what nine other big customers will want, which is the definition of repeatable.
Sales will surface 10 to 12 custom features a year; you can only afford 1 to 2 that reshape timing, so the CEO, not sales, holds the gate.
Why we picked it
This is the sharpest answer to the exact timing question: it names the two ways founders blow it (exiting too early and watching conversion rates collapse, or staying so long they become the permanent bottleneck) and gives concrete ARR thresholds ($1M to $2M before you transition, $10M for vertical SaaS). Its most useful, non-obvious call: hire strong Account Executives first, not a VP of Sales, because a VP hired against an unproven motion has nothing to run.
Why we picked it
Jason Lemkin makes the case that the person who ghosted you almost never made a conscious decision to ignore you, they just got buried in their own priorities, and the fix is the same one that works with any stalled prospect: professional persistence. It reframes silence as something to work through rather than take personally. Read it the next time a sure thing deal has gone quiet on you.
Why we picked it
Jason Lemkin's argument is that a single first rep gives you almost no signal: you can't tell if a slow start is the person, the market, or your playbook. Hiring two at once turns your first sales hire into a small experiment instead of a bet.
Why we picked it
Jason Lemkin runs through the specific, repeated mistakes he sees founders make when hiring too early or hiring the wrong profile. Useful as a pre-mortem: listen to it right before you write the job description.
Why we picked it
A direct answer to the exact question in the title: yes, charge for pilots, and here's roughly how much. Jason Lemkin argues that an unpaid pilot is really just an extended demo, and that even a modest fee changes how much attention and honesty you get back from the customer. Read this if you need a straight answer, not a framework.
Why we picked it
Picks up right where the previous piece leaves off: once you've decided to charge for the pilot, how do you actually structure it so it converts. It's specific about setting a success metric and a decision date up front, which is the exact mechanism this question's answer points to. Short and practical.
Why we picked it
The other side of the discount question: sometimes a genuinely low price is the right strategy, not a concession. Jason Lemkin lays out the narrow set of conditions where that's true, which helps you tell the difference between a deliberate low-price strategy and just caving to the first customer who pushes back. Read it so your discount decisions are a choice, not a habit.
Why we picked it
Jason Lemkin has watched thousands of SaaS founders make this hire, and this is his running list of what goes wrong. The number one mistake he names is hiring before the founder has closed the first 10 to 20 customers themselves, which is exactly the trap our short answer is warning against.
Why we picked it
Lemkin has watched thousands of SaaS companies go through this exact stage and is blunt about where founder led sales quietly stops working, usually earlier than founders admit to themselves. Read it as a warning label: know the ceiling you are selling toward, especially when a timezone gap is already eating into your own selling hours.
Why we picked it
Jason Lemkin has seen thousands of founder emails as an investor himself, and this piece is written from that side of the inbox, telling you exactly what makes him keep reading versus archive. It's a useful counterweight to advice written by copywriters, since it comes from the actual recipient of these emails.
Why we picked it
This is the exact question our short answer addresses, asked and answered directly by a B2B investor and operator who reads a huge volume of founder outreach. It is a quick, blunt gut check on whether a specific number is fine or a red flag, the reassurance, or wake-up call, a founder staring at their own reply rate actually needs.
Why we picked it
A direct answer to a founder asking almost exactly your question. Lemkin's fix is blunt: fewer, better-targeted emails to the right stakeholder with a pitch so sharp that trusted advisors would react to it, instead of a wider blast that nobody reads twice.
Why we picked it
This is the real time data point behind the ceiling described in the short answer, straight from a community of SaaS founders and sales leaders reporting what is actually happening to their outbound numbers right now. Read it to calibrate whether what you are feeling in your own reply rates is you doing something wrong or the channel itself getting harder for everyone.
Why we picked it
Lemkin has watched thousands of B2B SaaS companies try outbound and this piece is his blunt verdict: it works, but only when it is narrow, researched, and persistent, which is the same targeting and personalization argument our short answer makes. Read it if you are wondering whether outbound is even worth the effort for a small team, he has seen both the failures and the wins up close.
Why we picked it
Lemkin lays out a specific, staged interview count for B2B SaaS founders: the first five to map the space, the next five to confirm patterns, and interviews eleven through twenty to sharpen your pitch and thesis. It is opinionated and specific in a way that is genuinely useful as a starting benchmark, while still leaving room for your own judgment about when patterns repeat. Use it as a concrete checkpoint if you are building for business buyers.
