TT Ono

How to Pitch Investors: Crafting a Deck That Gets a Second MeetingHow to Pitch Investors: Crafting a Deck That Gets a Second Meeting

Investors see hundreds of pitch decks a year and remember almost none of them. The goal of a first meeting isn’t to close a deal — it’s to earn a second meeting. That reframing changes what a deck should actually do: it needs to be clear, credible, and memorable enough to survive being described to a partner who wasn’t in the room.

Lead with the problem, not the origin story

Founders often want to open with how they discovered the idea. Investors care first about whether the problem is real, large, and urgent. Open with a sharp articulation of the problem and who has it, then let your story serve as evidence of why you’re the right team to solve it — not the other way around.

Show traction, even if it’s small

Even modest traction — a handful of paying customers, a strong week-over-week growth rate, a waitlist with real signups — is more persuasive than an ambitious market-size slide with no evidence behind it. Investors are pattern-matching for signs that real people want what you’re building. Traction, however small, is the clearest signal you can offer.

Be honest about risk

Every startup has real risks: competitive, technical, regulatory, or market-related. Decks that pretend these risks don’t exist read as naive rather than confident. Naming your biggest risk directly, and explaining how you’re mitigating or plan to test it, builds more credibility than glossing over it.

Keep the deck short and let the conversation do the work

Ten to fifteen slides is usually enough: problem, solution, market, product, traction, business model, team, and ask. A deck stuffed with every detail of the business tries to answer questions before they’re asked, and ends up harder to follow. Save detail for the appendix and for the conversation that follows.

The takeaway

A pitch deck’s job is narrow: get you into the room again. Optimize for clarity and credibility over comprehensiveness, and let follow-up conversations carry the depth.

Pricing Strategies for Early-Stage SaaS StartupsPricing Strategies for Early-Stage SaaS Startups

Pricing is one of the few levers a startup can pull that directly and immediately affects revenue, yet most early-stage founders set their price once, almost arbitrarily, and never revisit it. Getting pricing right early doesn’t just affect this month’s revenue — it shapes who your customers are, how they perceive your product, and how sustainable your growth will be.

Price the value, not the cost

Cost-plus pricing — figuring out what it costs you to deliver the product and adding a margin — is intuitive but usually wrong for software. Software’s marginal cost of delivery is often near zero, so cost tells you almost nothing about what to charge. Instead, anchor your price to the value the product creates for the customer: time saved, revenue generated, or risk avoided. A tool that saves a team ten hours a week is worth pricing against that time, not against your hosting bill.

Talk to customers about price before you set it

Many founders are afraid to discuss price directly with prospective customers, worried it will scare them away. In practice, asking “what would you expect to pay for something that solves this problem” during early customer conversations produces far better pricing intuition than guessing. Willingness-to-pay conversations, done honestly, are some of the highest-leverage conversations a founder can have.

Start with fewer tiers than you think you need

Early-stage products often haven’t earned the complexity of a five-tier pricing page. Two or three clear tiers, differentiated by a small number of meaningful features or usage limits, are usually enough. Overly granular pricing early on creates decision paralysis for prospects and maintenance overhead for you, without the customer volume to justify the complexity.

Don’t be afraid to raise prices

A common early mistake is underpricing out of fear of rejection, then feeling stuck because existing customers expect the low price to continue. It’s far easier to raise prices for new customers going forward than to raise them retroactively on existing ones. If your close rate on a price is close to 100%, that’s usually a sign the price is too low, not a sign of product-market fit.

The takeaway

Pricing isn’t a one-time decision made in a spreadsheet — it’s an ongoing conversation with the market. Revisit it deliberately as you learn more about the value you actually deliver.

The Founder’s Guide to Hiring Your First Ten EmployeesThe Founder’s Guide to Hiring Your First Ten Employees

The first ten hires at a startup shape the company’s culture more than any handbook or mission statement ever will. These are the people who will set the tone for how work gets done, how disagreements are handled, and what “normal” looks like as the company scales. Getting these hires right matters disproportionately.

Hire for the problems you have, not the org chart you imagine

Early founders often try to hire as if they’re building a scaled company, bringing on specialists for roles that don’t need to exist yet. In the earliest stage, prioritize generalists who can operate with ambiguity and pick up tasks outside their formal job description. A “Head of Marketing” title means little at ten people; someone willing to write copy, run ads, and answer support tickets in the same afternoon is worth far more.

Reference checks matter more than interviews

Interviews are performances; references are closer to the truth. At the early stage, a bad hire is enormously costly — not just in salary but in the time it takes to notice the mismatch, manage it, and eventually part ways. Spend real time on reference calls, and ask specific behavioral questions (“tell me about a time this person disagreed with a decision”) rather than generic ones that produce generic answers.

Be explicit about equity and expectations

Early employees often join partly for equity, and ambiguity here creates resentment later. Be clear and consistent about how equity is determined, how vesting works, and what the person can realistically expect it to be worth under different outcomes. Overpromising to close a hire is a short-term win and a long-term liability.

Culture is built through decisions, not slogans

Whatever values you claim to hold will be tested by an early, uncomfortable decision — letting go of a well-liked but underperforming early hire, being honest with the team about a missed milestone, or turning down a bad-fit customer. How founders handle these moments, not what’s printed on the wall, is what actually defines culture for the first ten employees and everyone who joins after them.

The takeaway

Every early hire is disproportionately influential. Slow down more than feels comfortable on these decisions — the cost of a bad early hire is measured in years, not weeks.

Building a Minimum Viable Product That Actually Tests Your AssumptionsBuilding a Minimum Viable Product That Actually Tests Your Assumptions

“MVP” is one of the most misunderstood terms in the startup world. Many founders hear “minimum viable product” and build a stripped-down version of their full vision — fewer features, same architecture, same audience. That’s not an MVP, that’s just a smaller product. A real MVP is a tool for testing a specific, risky assumption as cheaply as possible.

Identify your riskiest assumption first

Every startup idea rests on a stack of assumptions: that a problem exists, that people will pay to solve it, that you can acquire customers affordably, that you can deliver the solution technically. Before building anything, rank these assumptions by how risky and how uncertain they are. Your MVP should be designed around testing the single assumption that would kill the company if it turned out to be false.

The product doesn’t need to scale — it needs to teach you something

An MVP is disposable by design. If you’re testing whether people will pay for a curated newsletter, you don’t need a subscription platform — you need an email sent manually to twenty people and a payment link. If you’re testing whether a marketplace can match supply and demand, you can run the matching by hand behind the scenes while the user sees a polished interface. This is sometimes called a “concierge MVP,” and it’s one of the fastest ways to learn without engineering investment.

Set a learning goal, not a feature list

Before building, write down the specific question the MVP needs to answer, and what result would count as a “yes” versus a “no.” Without this, it’s easy to ship an MVP, get ambiguous results, and convince yourself the ambiguous result was actually encouraging.

Resist scope creep from day one

The moment an MVP starts picking up a few early users, there’s a strong temptation to add “just one more feature” they’ve requested. Every addition dilutes the clarity of what you’re testing. Keep a running list of feature requests, but hold the line on the MVP’s scope until you’ve answered the question you set out to answer.

The takeaway

A good MVP is uncomfortable to launch because it feels too small. That discomfort is a feature, not a bug — it means you’re testing the assumption rather than protecting your ego with a nicer-looking, more defensible product.

Bootstrapping vs Venture Capital: Choosing the Right Funding PathBootstrapping vs Venture Capital: Choosing the Right Funding Path

One of the earliest and most consequential decisions a founder makes has nothing to do with product — it’s how the company gets funded. Bootstrapping and venture capital aren’t just two sources of money, they’re two entirely different operating philosophies, and picking the wrong one for your business can create years of friction.

What bootstrapping actually demands

Bootstrapping means growing the company from its own revenue, personal savings, or small loans rather than outside equity investment. It forces discipline: every hire and every feature has to be justified by cash the business is generating or has in the bank. The upside is control — founders keep their equity and can make decisions on their own timeline rather than an investor’s. The downside is speed. Bootstrapped companies typically grow slower because they can’t outspend competitors to capture a market quickly.

What venture capital actually demands

Venture capital trades equity for growth capital, and it comes with an implicit contract: investors are betting on outsized returns, which means they expect the company to pursue rapid, often aggressive growth, usually toward an eventual acquisition or IPO. This isn’t free money — it’s money with a specific expectation attached, and it can pull a founder toward decisions (aggressive hiring, paid growth, market expansion) that make sense for a venture-scale outcome but not necessarily for a healthy, sustainable business.

Match the funding model to the business model

The real question isn’t “which is better” — it’s which model fits the economics of what you’re building. A business with high gross margins, network effects, and a large addressable market is often a legitimate fit for venture capital, because the capital can be used to capture a market before competitors do. A services business, a niche tool with a smaller total addressable market, or a business with thin margins is often a poor fit for venture capital, no matter how fundable it looks on paper — because the growth expectations that come with the money won’t match what the business can realistically deliver.

You can also mix approaches

Many successful companies bootstrap to initial traction and revenue before raising outside capital, using that early traction to raise on better terms and with more leverage. Others take on revenue-based financing or small angel rounds that don’t carry the same growth expectations as institutional venture capital. The funding landscape isn’t binary, and founders shouldn’t treat it that way.

The takeaway

Ask what kind of company you’re actually trying to build before you ask how to fund it. The money always comes with strings, implicit or explicit — the job is to make sure those strings pull in the same direction you already wanted to go.

How to Validate Your Startup Idea Before Writing a Single Line of CodeHow to Validate Your Startup Idea Before Writing a Single Line of Code

Every founder falls in love with an idea at some point. The danger isn’t having the idea — it’s building an entire company around it before checking whether anyone actually wants what you’re planning to make. Idea validation is the process of testing your assumptions cheaply, quickly, and honestly, before you commit months of runway and emotional energy to something the market may not need.

Start with the problem, not the solution

Founders often describe their startup by its features: “we’re building an app that does X.” That’s backwards. Before anything else, write down the problem you believe exists, who has it, and how painful it currently is. If you can’t describe the problem in one sentence without mentioning your product, you haven’t found it yet.

Talk to real people, not friends and family

Friends and family will tell you your idea is great because they love you, not because they’d pay for it. Seek out strangers who match your target customer profile. Ask open-ended questions about how they currently solve the problem, what they’ve tried, and what frustrates them about existing options. Resist the urge to pitch — you’re there to listen, not to sell.

Look for evidence of existing behavior

The strongest validation signal isn’t what people say, it’s what they already do. Are people cobbling together spreadsheets, hiring freelancers, or paying for a clunky workaround to solve this problem today? Existing workaround spend is a much better predictor of willingness to pay than survey enthusiasm.

Build a smoke test before you build a product

A landing page describing your product with a “Join the waitlist” or “Pre-order now” button can tell you a lot in a week. Track how many visitors convert into signups or, better yet, actual payment commitments. A low-cost ad campaign driving traffic to that page gives you a rough cost of acquisition and a real conversion rate before you’ve written a line of production code.

Set a kill criterion in advance

Decide upfront what result would tell you to walk away. Without a predetermined threshold, it’s easy to rationalize weak signals as promising ones. Write down the number — signups, conversion rate, or interviews confirming the pain point — that would make you pursue this idea, and the number that would make you shelve it.

The takeaway

Validation isn’t a single test, it’s a habit of staying skeptical of your own idea long enough to gather real evidence. The founders who save themselves years of wasted effort are the ones willing to kill a bad idea in week two instead of month eighteen.