PRODUCT HUNT — LAUNCHING SOON 🙌

The 1752vc Pitch Deck Analyzer goes live on Product Hunt soon. Get on the launch list and we'll send you the link the moment we're live — plus 5 free deck reviews if you join the conversation on the day.

👉 Count me in

The easiest founder meeting to waste is the first one.

On paper, it looks simple. The invite says 30 minutes. The founder has a deck. You skim the website, glance at LinkedIn, scan the market, and show up with a few questions. The founder talks. You nod. You ask about traction, competition, the round. The call ends with some version of "This was great — keep me posted." 

You took the meeting. You didn't learn anything. 

Here's the reality: for emerging angels, scouts, and venture fellows, the first meeting is the earliest place your judgment shows. Not because you're supposed to decide in 30 minutes — you're not. But because those 30 minutes reveal whether you know how to listen, where to push, what to ignore, and how to tell a compelling pitch from a compelling company. 

The first meeting is a live test of the founder's clarity, the customer's pain, the product insight, the market timing, the team — and your own discipline. The best investors aren't trying to sound smart. They're trying to understand what's true, what's still unknown, and what would have to be true for this company to become exceptional. 

That's the trap most new investors walk into. They show up trying to prove they belong in the room. Complicated questions. Adjacent-company name-drops. Jumping to market size before they understand the basic pain. But the job isn't to perform intelligence. The job is to create insight. 

So, drop the impossible goals. You're not trying to catch the founder in a mistake. You're not proving you know the market better than they do. 

You're answering one question: is this worth another conversation or deep dive diligence? 

A founder meeting is not an interview 

The most common mistake is treating the first call like an interview. A list of questions, worked through one by one. What's your TAM? Your revenue? Your competitors? Your go-to-market? How much are you raising? At what valuation? 

None of those are wrong. Most need answering eventually. But asked mechanically, they get mechanical answers. The founder goes into pitch mode. You go into note-taking mode. The conversation becomes a transaction instead of a way to understand the company. 

A good meeting feels like a focused conversation, not a deposition. You're still evaluating. You're still mapping the risks. But the goal isn't to collect information — it's to understand how the founder thinks. 

Can they define the problem clearly? Do they know the customer cold? Can they explain why the existing solutions fall short? Are they honest about what's not working? Can they say, in plain English, why this company should exist? 

A founder can have a polished deck and be fuzzy on the customer. Impressive early traction and no clear wedge. Charisma and a habit of dodging the hard questions. Meanwhile, some of the strongest founders aren't slick at all. They haven't rehearsed every line. But they're specific. They know the pain. They've learned something from the market. They can tell you why this company has a right to win. 

That's what you're listening for. 

Prepare with a point of view, not a conclusion 

You don't need five hours of prep. In early-stage investing that's usually a fantasy. But spend enough time that you don't waste the founder's, or ask questions a website answered for you. 

A verdict sounds like: "I think this is good." Or "this market's too crowded." A point of view sounds like: "I think this is workflow automation for overburdened finance teams — but I need to know if the buyer feels acute pain." You're not preparing to prove you understand the company. You're preparing so the meeting has a shape. 

Walk in knowing where to dig on five things: 

The problem. Not the category. Not the trend. The actual pain. Who has it, how often, how badly, and what happens if it goes unsolved. A great team on a weak problem still struggles. A beautiful product aimed at a vague pain becomes a nice-to-have. 

The solution. What they built, how it works, why it beats the alternatives. Some founders nail a real pain but build something too lightweight to fix it. Others build something technically dazzling that customers won't bother to adopt. 

The customer. "Everyone" is not a customer. Who's the buyer, the user, the decision-maker — and what's the evidence this is the right one? Interviews, pilots, design partners, revenue, retention. Are people paying, or just being polite? 

The team. Not complete forever — complete enough for the next chapter. Technical problem: can they build it? Enterprise sale: does someone know that motion? Regulated market: do they understand the constraints? 

The market. A real problem for a real customer can still be a small business. Is the market large, or growing fast, or freshly unlocked by a shift in tech, regulation, behavior, or cost? Could the wedge expand into a platform? 

That's the prep that matters. Not memorizing the slides. Knowing where to point the conversation. 

The first five minutes set the tone 

The open matters more than people think. Founders spend their lives pitching — fundraising, selling, recruiting, fighting fires, drowning in conflicting advice. A good investor makes the conversation feel useful, fast. 

The best opening is usually simple: "I read the overview, but I'd love to hear it in your own words. What are you building, who's it for, and what pulled you into this problem?" 

That hands the founder the frame without forcing them to perform the deck slide by slide. It points straight at what matters — product, customer, motivation. 

Then listen. Don't interrupt too fast. The first few minutes tell you a lot. Some founders explain the company with startling clarity. Others reach for jargon. Some start with the customer's pain. Others start with the technology. You're not grading polish. Some great founders aren't slick; some slick ones aren't great. You're listening for clarity of thought. 

If after five minutes you still don't understand what they do, ask them to simplify: "Can you explain it as if I were the customer, not an investor?" Founders pitch in market language. Customers don't buy market language — they buy a fix for a problem they recognize. If the founder can't make that switch, notice it. 

Start with the problem, not the product 

The best early-stage companies start with a painful, specific problem. So, this is where the conversation should slow down. 

The temptation is to race into product, traction, and the round. But if you don't understand the problem, everything downstream gets harder to read. The real job here is to separate a problem that sounds plausible from a problem that creates urgency. 

Plenty of startups solve real problems that aren't urgent enough to matter. The customer agrees it's interesting. Takes the meeting. Says "this would be great to have." Then doesn't buy. Or buys slowly. Or pilots and never converts. Interest is not urgency. 

The tell is the workaround. A strong founder can describe the customer's current hack in detail — the spreadsheets, the manual process, the consultants, the email chains, the five people across three departments duct-taping together something that should've been automated years ago. Workarounds are evidence of pain. If customers are already spending time, money, or political capital to patch the problem, the founder may be onto something. 

The weak version is all future, no present. "Every company will need AI for procurement" might be directionally true. It's not investable. Which company? Which buyer? What budget? What breaks without this? 

Early-stage investing requires imagination. It doesn't require fantasy. The founder should connect the big vision to a specific wedge — because the wedge is where the company earns the right to get bigger. 

The solution has to match the pain 

Once you understand the problem, the question isn't "is this product good?" It's: is this the right way to solve this problem, for this customer, right now? 

A product can be technically impressive and miss the customer entirely. Beautifully designed and too lightweight for the job. Powerful and too much behavior change to adopt. So watch what the customers do. Use it once and vanish — that tells you something. Hack it into the workflow, invite colleagues, beg for integrations, complain when it breaks — that tells you something else. 

At the earliest stages, evidence is thin. A pre-seed company may have no revenue. A seed company may still be hunting for repeatability. Fine. Your job isn't to demand Series B metrics from a seed deal. Your job is to gauge learning velocity. What did the founder believe six months ago that they've abandoned? What have customers asked for that the team refuses to build? What's been harder than expected? Where did the market pull them somewhere they didn't plan to go? 

A founder learning fast beats a founder with a perfect answer to every question. Early companies are made of uncertainty. The question isn't whether they know everything. It's whether they're getting closer to the truth. 

The customer cannot be theoretical 

After problem and product, the customer has to come into focus. "Everyone" is not a customer. "Enterprises" isn't specific. "Consumers" rarely is either. A strong founder can tell you who feels the pain first, who uses it, who pays, who approves, and who might block it. Those are rarely the same person. The user feels the pain, the manager owns the workflow, procurement stalls the deal, finance approves the budget, leadership only cares if it touches revenue, cost, or risk. If the founder can't draw that map, go-to-market will be harder than they think. 

Validation matters — but only the right kind. Interviews are useful; interviews aren't demand. Pilots are useful; pilots aren't revenue. Waitlists are useful; waitlists aren't usage. LOIs are useful; LOIs aren't committed budget. Not all traction is equal. A handful of deeply engaged design partners in the exact segment beats a giant waitlist that'll never activate. Ten customers with urgent pain beat ten thousand signups who were curious for five minutes. 

The best signal is pull. Are customers asking to use it? Bringing it to colleagues? Pushing for the right features? Willing to pay? Frustrated when they can't get access? You're not looking for perfect proof at this stage. You're looking for the beginnings of truth. 

The team has to be right for this problem 

A lot of investors talk team in generic terms. Are the founders impressive? Right schools? Recognizable logos? Seem sharp? Not enough. 

The better question: is this team right for this problem, this customer, this market, this stage? Deep technical problem — can they build? Selling into enterprises — does someone know procurement, security reviews, internal champions? Healthcare, finance, defense — do they understand the constraints? Distribution the hard part — do they have a credible path to customers? 

The team doesn't need to be complete forever. It needs to be complete enough for the next phase. Every early-stage startup has missing pieces. The question is whether the founders know what's missing and can recruit, learn, or compensate. "We know enterprise sales is the gap, and here's how we're testing into it" is a different founder from the one who waves off go-to-market as a later problem. 

Founder-market fit isn't a slogan. There should be a reason this specific team sees something others missed. They don't need 20 years in the industry. They need earned insight into the problem, the customer, the product, or the channel. 

The market has to support the ambition 

A company can solve a real problem, serve a real customer, and still not be venture-scale. That doesn't make it a bad business. It might be profitable and durable. But venture math needs the possibility of a very large outcome. 

This is where new investors make one of two mistakes. They over-index on whether they personally like the product. Or they take the market-size slide at face value. Neither works. 

The question isn't whether the market looks big in a deck. It's whether there's a credible path from the initial wedge to a much larger company. A strong founder connects the present wedge to a strategic position: "We start with compliance automation for small fintech lenders because the pain is acute and the buyer is reachable — but the long game is the operating system for non-bank lending." True or not, that's something real to evaluate. 

The weak answer: "Our TAM is $100 billion and we only need 1%." That's not a strategy. That's arithmetic. 

Close with clarity 

The end of the call is where investors go vague. "This is really interesting." "Let's stay close." "Send me the deck." "Keep me posted." Sometimes that's fine. Usually it's useless. 

A better close creates clarity. By the end you should know the round, the timeline, and the next step. How much they're raising. How much is committed. What kind of investors they want. Their timeline for allocation decisions. One of the most useful closing questions: "Anything we didn't cover that you think investors usually miss?" It hands the founder room to surface a hidden risk, a real insight, or what they think the market gets wrong. 

Then be honest about your next step. Interested? Say so, specifically: "I want to dig in. The customer pain and your domain insight are compelling — I'd like to review the deck and talk to a customer or two." Intrigued but unsure? Name what you need: "I'm interested, but I need to get sharper on whether this is a must-have or a nice-to-have." Not a fit? Don't fake it: "I appreciate the walkthrough. I don't think I'm the right investor for this round, but I'll watch what you build." 

Founders remember investors who are clear. They also remember the ones who wasted their time. You don't need to be harsh. You need to be honest. 

The meeting isn't over when the Zoom ends 

The most important work often happens in the five minutes after the call — while it's still fresh, before impressions harden into a vague feeling. And feelings don't compare well over time. 

So force yourself to write. Explain the company in one plain sentence. Name the core insight: what does the founder believe that might be right and non-obvious? Write the single strongest reason it works and the single biggest reason it dies. Name the edge — insight, speed, distribution, taste, data, trust, timing, focus. 

Most important, write down what you'd need to believe to invest. That one move turns vague uncertainty into a diligence agenda. Not "I like this." Instead: "I'd need to believe mid-market CFOs feel this pain urgently enough to buy in under 60 days." Or: "I'd need to believe this services-heavy workflow becomes repeatable software." Or: "I'd need to believe the data advantage compounds with every customer." 

That's how judgment gets built. Not through vibes. Through explicit assumptions. Over time, your notes become your own pattern-recognition engine. You start to see which founder answers correlate with progress, which risks are fatal and which are survivable, where your instincts are sharp and where they're noise. That's the craft. 

Your job is not to be impressive 

A lot of emerging investors feel the pull to ask the brilliant question. The one that makes the founder pause and think, this person is smart. The instinct is understandable. It's also a distraction. 

Your job isn't to perform intelligence. It's to create insight. Sometimes that means asking the basic question. Admitting what you don't understand. Staying quiet long enough for the founder to say the real thing. Asking the same question again, simpler. 

The best meetings aren't adversarial. They're not casual either. They're high-signal conversations between people trying to figure out whether there's a fit. In 30 minutes you're testing whether the problem is urgent, the solution fits, the customer is real, the team can execute, the market can carry the ambition, and the company has an edge. 

You won't answer everything. You're not supposed to. But you can answer enough to know what happens next. 

That's the point of the first meeting. It's not the whole process. It's the front door. The better you get at opening it thoughtfully, the better your deal flow, your diligence, your founder relationships, and your judgment become. 

One founder. One conversation. One sharper question at a time.