dealflow

Startup Red Flags: Investor Screening Guide

Brian Nichols is the co-founder of Angel Squad, a community where you’ll learn how to angel invest and get a chance to invest as little as $1k into Hustle Fund’s top performing early-stage startups.

The charmer problem

Consider two founder profiles. This is an illustrative contrast, not a claim about two named companies or their outcomes.

The first founder is an extraordinary fundraiser. They tell a compelling story, read the room well, and arrive with verbal commitments from other investors. Ask about customer acquisition, customer discovery, or retention, though, and the answers stay vague.

The second founder is quieter and less polished. The market sounds boring. Yet she can explain which potential customers she called, what objections she heard, which message she tested, and what happened next.

The first founder may still build a great company. The second may still fail. The point is narrower: pitch performance and operating substance are different signals. Startup red flags help you find the gap, then evidence tells you whether the gap matters.

Why charm can distort an investor's read

Charm is useful. It can help a founder recruit talent, win customers, and raise capital. Charisma itself is not a red flag.

The problem starts when a strong delivery earns credit that the underlying answer has not earned. An investor hears a smooth response, feels momentum, and stops asking for the customer note, dashboard, or calculation behind it. That is the all-pitch, no-substance risk.

Urgency deserves the same care. A round can have a real deadline and genuine demand. It can also create pressure that shortens your process. Treat urgency as a scheduling fact to confirm, not evidence that the company is good or the founder is evasive.

Your own instincts can carry bias, too. As Elizabeth Yin writes in Democratizing Knowledge, “Investors use their life perspective to assess. For this reason, we need more funders with more varied life perspectives.” Polish, accent, eye contact, shared background, and social ease can all shape a first impression without proving anything about execution.

Slow the conversation down. Ask the same material question later in different words, request the evidence beneath the answer, and compare the two responses. A feeling can generate a question. It should not settle the investment decision.

Eight startup red flags to investigate

A red flag is a prompt, not proof. Pre-product founders cannot show mature retention data. Pre-revenue founders can still show customer interviews, prototype use, letters of intent, or design-partner work. Once revenue arrives, the evidence should move toward customer cohorts, renewals, sales cycles, acquisition costs, gross margin, and cash planning.

Use the stage the company claims to have reached. Then assess whether the founders understand the evidence that should exist at that stage.

1. The founders do not know their core numbers

In one founder call handled by our Hustle Fund team, the concern was not that the metrics were weak. The founder could not explain monthly traffic, conversion rate, returning-customer percentage, or customer acquisition cost (CAC). Those were basic operating measures for that business, and the lack of command mattered more than an unimpressive result would have.

Why it matters: Founders do not need every number memorized, especially before launch. They do need to know which measures drive the company and where to find them.

Ask: “Which three numbers do you use to understand whether the business is improving, and what changed in the last month?”

Verify: Review the dashboard, payment data, funnel report, or operating sheet the team already uses. At pre-product, inspect an experiment log or customer-discovery tracker instead.

Decision: Investigate further if the founder can name the right measures and provide a clear follow-up. Likely pass if basic figures that should exist remain unavailable, conflict with the pitch, or change without a reasonable explanation.

2. Hard questions trigger reflexive defensiveness

There is a difference between holding your ground with data and treating every challenge as an attack. A strong founder can disagree with you, explain why, and still engage with the evidence.

Why it matters: Startups run into customer objections, employee dissent, missed plans, and new market information. A founder who cannot examine a hard question during diligence may struggle to process those inputs later.

Ask: “What evidence would change your view on this assumption?”

Verify: Revisit one live assumption in a second conversation. Ask references for a specific example of how the founder handled disagreement or unwelcome data.

Decision: Investigate further after one tense answer. People have bad meetings. Likely pass when dismissal, blame, or hostility repeats across topics and prevents reasonable diligence.

3. The company is chasing too many directions

Several markets or experiments can be sensible during discovery. The signal turns concerning when every customer is ideal, every feature is urgent, and nobody can explain what the team has chosen to ignore.

Why it matters: A small team has limited time and cash. Without a clear wedge, activity can disguise weak prioritization.

Ask: “Which customer, use case, or product request are you deliberately saying no to right now, and why?”

Verify: Compare the answer with the roadmap, recent releases, pipeline, hiring plan, and how people actually spend their time. Our 5T startup framework can help you place focus beside team, target market, technology, traction, and terms.

Decision: Investigate further when the company is running bounded tests with stated decision dates. Likely pass when the founders cannot identify a priority, stopping rule, or credible path from experiments to focus.

4. The founders cannot discuss what is not working

Every startup has misses. A pitch with no failed experiment, customer objection, delayed hire, or changed assumption gives you little evidence of intellectual honesty.

Why it matters: Investors need an accurate view before investing and candid communication afterward. A founder who can name a miss, its cause, and the resulting action gives you more signal than one who performs certainty.

Ask: “What did you believe six months ago that you no longer believe, and what changed your mind?”

Verify: Look for the before and after in product changelogs, experiment notes, board or investor updates, customer records, and references.

Decision: Investigate further if the founder needs time and returns with a concrete example. Likely pass when material setbacks are hidden, rewritten repeatedly, or blamed on everyone else with no change in behavior.

5. Material answers are inconsistent or unverifiable

Small differences are normal. Revenue may be booked, collected, or annualized. Pipeline may mean an introductory call to one founder and a signed proposal to another. The concern is a material claim that keeps changing after you define the terms.

Why it matters: Diligence depends on shared facts. Inconsistency can reveal weak reporting, poor internal communication, or a claim that the evidence does not support.

Ask: “I may be using a different definition. Can you walk me from the source data to this number?”

Verify: Reconcile the pitch with bank or payment records, customer lists, signed agreements, product analytics, and the same metric reported across time. Give the founder a fair chance to correct an honest error.

Decision: Investigate further when the discrepancy is small, defined, and reconciled. Likely pass when a central traction, ownership, or cash claim remains materially inconsistent after clarification.

6. Co-founders show unresolved conflict or unclear ownership

Healthy co-founders disagree. What matters is whether they can make a decision, support it, and resolve tension without leaving the company stuck.

Why it matters: Overlapping authority, different commitment levels, or unspoken equity resentment can slow decisions when the startup has little room for delay.

Ask: “Tell me about the last important decision you disagreed on. Who made the call, and what happened afterward?”

Verify: Speak with each founder separately. Compare role ownership, time commitments, decision rights, equity expectations, and the account given by a former colleague or investor.

Decision: Investigate further when roles are evolving but the process is explicit. Likely pass when founders give incompatible accounts of commitment, ownership, or authority and have no credible way to resolve the conflict.

7. Customer evidence is weaker than the pitch suggests

A long prospect list is not the same as demand. Neither is praise from friendly users. The evidence should match the claim: discovery notes for a customer insight, active use for engagement, paid behavior for willingness to pay, and renewals or cohorts for retention.

Why it matters: Founders can be sincerely excited and still misread polite interest. Direct customer evidence tests whether the problem is painful, the buyer is reachable, and the product changes behavior.

Ask: “Why did the last three prospects decline, and what did you change after those conversations?”

Verify: Review anonymized interview notes, usage data, conversion by source, churn reasons, renewals, invoices, or a few customer references. For a pre-product startup, examine the quality and range of discovery work rather than demanding revenue.

Decision: Investigate further when the evidence is early but the founder can separate facts from hypotheses and name the next test. Likely pass when claimed traction cannot be substantiated or months of activity have produced no learning about the customer.

8. Runway and use of funds are disconnected from a milestone

An exact forecast will be wrong. It can still reveal whether the founders understand monthly burn, hiring costs, timing, and what this round is meant to prove.

Why it matters: “Hire and grow” is not a financing plan. Investors need to see how cash buys enough time to reach a meaningful product, customer, revenue, or regulatory milestone.

Ask: “What specific milestone should this round fund, what assumptions drive the runway, and what would you cut first if progress is slower?”

Verify: Reconcile current cash, monthly burn, planned hires, debt or other obligations, and a simple monthly forecast with the amount being raised. At pre-seed, rough scenarios are reasonable. At seed, expect operating data to inform them.

Decision: Investigate further when assumptions are explicit and the team can adjust them. Likely pass when the cash and burn figures do not reconcile, the round does not fund a clear learning or value milestone, or the founders cannot explain a downside plan.

A repeatable way to verify a red flag

A checklist keeps you from replacing one bias with another. As Elizabeth Yin writes in Democratizing Knowledge, “The more disciplined you are in your thought process/rubric, the more you can improve over time.” The goal is consistency and learning, not a fake mathematical answer.

  1. Calibrate to stage. Write down what the company should reasonably know now. Separate missing maturity from missing honesty or operating command.
  2. Record the concern neutrally. Replace “founder is evasive” with “the founder gave two definitions of active customer.” A specific observation is easier to test.
  3. Ask one neutral follow-up. Invite an explanation without telegraphing the answer you want. Keep the core question consistent across founders.
  4. Request existing evidence. Ask for a dashboard, customer note, contract, product log, forecast, or reference the team already uses. Do not turn diligence into a presentation-design contest.
  5. Check another source. Speak with a customer, former colleague, co-founder, or existing investor when the concern is material. Ask for examples, not adjectives.
  6. Compare words with behavior. Did the founder provide the promised information? Did the explanation stay consistent? Did new evidence change the plan?
  7. Record what remains unresolved. Note the evidence for and against the concern, its impact if true, and what you still do not know. Then make your own decision instead of borrowing the lead investor's conviction.

A peer can challenge your interpretation and spot questions you missed. They should not make the decision for you.

Twelve startup investors gather around a restaurant table at an Atlanta meetup.
Angel Squad members at a local meetup in Atlanta.

For company, product, financial, and document checks beyond founder screening, use our full angel investing diligence checklist.

Green flags backed by evidence

The inverse of a red flag is not a charming answer. It is a pattern you can see in the work.

Customer understanding. The founder can explain why people buy, decline, stall, or churn. They know the top objections and can show how those lessons changed messaging, product, pricing, or sales.

Intellectual honesty. The founder distinguishes fact, estimate, and hypothesis. They can say “I don't know” without stopping there, then propose a credible way to learn.

Coachability with judgment. The founder listens and considers new information without agreeing automatically. Ask about useful advice they rejected and the evidence behind that choice. Coachability is visible in how someone processes input, not how agreeable they seem.

Learning and follow-through. Look for a problem, response, and result inside the work: a missed onboarding target led to new interviews, a customer loss changed qualification, or a failed hire changed the scorecard. Personal hardship, immigration history, pedigree, extroversion, or polish should not serve as proxies for execution.

None of these signals predicts success. Early-stage investing remains uncertain, illiquid, and capable of a total loss. The value of the process is a clearer view of the risks you are choosing to take.

Separate pitch performance from substance

Charming founders can be excellent operators. Quieter founders can make poor decisions. A great pitch does not equal a great company, and an awkward pitch does not equal a bad one.

Slow down, ask the neutral follow-up, and inspect the evidence appropriate to the company's stage. When something feels off, turn the feeling into a written question and a verification step. If the material concern survives fair investigation, pass. If the evidence resolves it, update your view.

If you want to practice this discipline with an angel-investing community and review real opportunities alongside other operators and investors, apply to Angel Squad.