Hwi-jae Ahn, Principal & Team Lead, Bluepoint

Early-stage investing often begins before there is meaningful revenue, reliable data, or clear market validation. So what allows an investor to put their name and credibility behind a founder who has not yet been proven?

Hwi-jae Ahn, Principal and Team Lead at Bluepoint, does not see seed investing as a search for perfect evidence. Instead, she looks for whether a team still has meaningful questions to solve, how much it evolves over time, and whether founders can absorb outside input without simply copying it—turning it into execution that is distinctly their own.

In this interview, Ahn discusses what she looks for in early-stage founders, the difference between questions that make founders defensive and those that help them think more clearly, and what investors must be willing to risk—their time, reputation, and even the possibility of being wrong—if they want to move beyond observation and engage responsibly with unproven potential.

Q1. When you look at a founder who still has little revenue, few meaningful metrics, and limited market validation, what makes you think, I’m willing to be one of the first people to put my name behind this person?

I think it is right to begin by acknowledging something: the evidence is not always sufficient. 

The moment someone says, at the seed stage, “I made this decision based on sufficient evidence,” it is usually a form of retrospective justification. That is also why I stripped away the word “analysis” in a LinkedIn post I wrote. 

So I would like to slightly reframe the question. Rather than asking, “What evidence do I use to make a decision?" I would ask, “What do I look for when there is not yet enough evidence?

First, I look for whether there are still live questions inside the team.

I mean questions the founders have already pushed as far as they can on their own but still cannot solve alone—questions where bringing in an outside perspective immediately accelerates the team’s thinking. I see that kind of team as ready to begin the seed journey.

By contrast, there are teams with polished decks but no real questions. Every slide contains an answer, yet they cannot explain what is actually blocking them right now.

I would much rather meet a team with a rough deck and live questions. A well-made deck is a well-presented argument; it is not the essence of the person behind it.

Second, I look at the slope, not the point.

A single meeting is just one point. You cannot draw a slope or a direction from one point. So I try to meet the same team several times and observe what has moved between those meetings.

If I casually shared a perspective in our last meeting and, by the next meeting, everything I said has been reflected almost exactly as I said it, I do not necessarily take that as a positive signal. In fact, it can be closer to a red flag.

Changing everything because someone told you to is not receptiveness. It can mean that you do not yet have a philosophy of your own. What I mean by receptiveness is the speed at which someone can turn external stimulation into their own execution. The key word is their own.

They take in an outside perspective, but they do not copy it. They digest it, act on it, and bring it back in a form that is one step beyond what I originally suggested. 

There are moments when a founder says: “I tried what you suggested, but after doing it, I realized this part was actually different.”

That is the moment when I begin to trust them.

The absence of metrics does not mean there is nothing to observe. At seed stage, this slope is one of the few tangible indicators I can actually observe.

Third, I look at the unprepared self.

An IR pitch is the prepared self. It is the founder presenting the most organized, polished version of themselves, and of course that should be evaluated for what it is.

But there are things that do not appear in a pitch. Questions like, “How are things going these days?” or “Could we try the product ourselves?” may sound casual, but for me they are also a form of observation.

A great deal becomes visible in those moments: how seriously they treat a single casual user, whether they hide when they are stuck or talk about it honestly, whether they truly live with the problem they are trying to solve every day—or whether that problem only comes alive when they are pitching.

I currently oversee Starting Point, a space planned and operated by Bluepoint, and I like that this kind of observation becomes much easier with the teams working there.

And based on those three things, there is one additional condition I place on myself: 

Can I become convinced?  For example, when evaluating a consumer product team, I once signed up for morning swimming classes so that I could actually use the product myself. It was not because I wanted to be excessive. Reading materials and saying, “This looks good, let’s invest,” without ever using the product felt slightly fraudulent to me.

Once I used it myself, I noticed things that had not been visible in meetings. Only after physically confirming that final detail did I feel conviction.

When it comes to a deeply technical field that I cannot fully understand, the process has to be different.

I cannot become a cybersecurity expert. Nor can I understand the field as deeply as someone who has spent years in it within a short period of time.

So if my conviction came from believing that I fully understood the technology, that would be false confidence. In those cases, my conviction comes from two places.

One is where the world is moving—where capital is beginning to flow and why this particular problem is becoming important now.

The other is, ultimately, the team’s receptiveness. I am not trying to verify every technical layer myself. I am trying to determine whether these are the people who will continue digging into that depth themselves.

That is why I try to read newspapers and other writing as much as I can. When I was younger, I practically lived with books in my hands, but since becoming a working professional, I do not think I read nearly as much. Perhaps that is just an excuse.

Finally, just before I put my name behind a team, there is one question I ask myself: “When this team goes out to raise its next round, can I personally call the next investor and sell this team to them?”

If the essence of seed capital is reputation infrastructure, then the raw material of that infrastructure is my own credibility.

Company money can be deployed once an investment committee is convinced. But my name is something I personally have to take responsibility for. 

As far as I know, this is the most honest standard I have. Of course, even after looking at all of these things, I will still be wrong. Probably often. I think seed investing is less about getting it right and more about being willing to go first while knowing that you may be wrong.

Q2. What do you think distinguishes questions that make founders stronger from questions that instead make them defensive?

I think the difference is not in the content of the question itself, but in ownership—who already holds the answer.

With questions that make founders defensive, I usually already have an answer in my own head. I am asking merely to confirm it.

There are a few types. Test questions — I hold the correct answer and ask the founder to produce it. The founder immediately enters answer-sheet mode.

Questions designed to relieve my own anxiety — for example, “What happens if a large corporation enters the market?” It sounds like I am asking the founder, but in reality I am asking them to soothe my own anxiety. I am asking about something they cannot control, so defensiveness is almost inevitable.

Questions designed to prove that I am smart — questions whose real purpose is to demonstrate what I know. Those are not really questions. They are statements.

When founders receive those kinds of questions, they enter defensive mode or persuasion mode. And once someone enters persuasion mode, information stops coming out.

That is why I try not to interpret a founder’s defensiveness as a personality flaw or weakness. Often, it is simply a side effect of my own question.

By contrast, the questions that make founders stronger are questions I do not know the answer to either. I think a large part of my work involves giving language to things that do not yet have names.

More precisely, though, it is not about me naming those things for the founder. It is about helping the founder name them for themselves.

A good question does not necessarily demand new information. It draws out something the person already knows but has never yet turned into a sentence.

Good questions remain with you after the meeting ends.  If a perfectly clean answer comes out immediately in the room, there is a good chance it was not actually that strong a question.

Even on the same topic, questions can be very different. “Why is this market large?”  That is an interrogation. It asks for numbers, so defensiveness follows.

But: “If the market is currently this size, what would have to change for it to become much larger? And of those changes, which ones can you directly create yourself?”

Now we are thinking together. I do not know the answer either. Likewise, “Why now?” should not be a question used to grade whether the timing is correct.

It should be a question about how this person interprets and understands the clock of the era and industry they are operating in. And “What are you willing to give up?” should not be used to test commitment. It should make their priorities tangible.

This is also why I do not like to hand founders answers too quickly. There are three reasons, and the third is the most practical. 

First, at the seed stage, I have almost no data in my hands.

The moment I give an answer, it is not a validated answer. It is simply my intuition. If I present that intuition as the correct answer, I end up trapping the team inside my own intuition.

Second, the founder usually understands the domain far more deeply than I do.

Third, an answer designed by someone else will not survive the next fundraising round.

Only an answer that has truly become your own can be defended all the way through.

A team that simply carries my answer into a Series A meeting will often collapse by the second follow-up question.

There is one more thing I would add. The weight of a question does not come from the question itself. It comes from distance. The exact same sentence can feel like an evaluation if you meet someone once in a formal review setting, but it can feel like a conversation if you are beside them every day.

When an investor appears once every few months, judges the founder, and then disappears, founders begin performing themselves for those few encounters. Once that happens, almost any question will produce defensiveness. That is why I believe half of designing good questions is not question design at all.

It is relationship design. Saying, “I do not know this area very well, so this may be the wrong question,” before asking something is part of the same principle.

To be candid, I am still not very good at this. I am especially worse at it in areas where I think I know something. When I know the subject, my questions keep trying to turn into statements.

Q3. “Analysis” can sometimes become a safe form of distance. If an investor wants to move beyond being an observer and become responsibly involved in the potential of someone who has not yet been proven, what do you think they have to be willing to risk?

That is a very good question, and I think it is exactly right.   What I have come to believe is this: Analysis is safe not because it is accurate, but because it is recoverable.

Even if the analysis turns out to be wrong, there is still an exit.  “The market was difficult.”, “The execution fell short.” The sentence remains, but I do not.

A name, on the other hand, cannot be taken back. So I have come to think that becoming involved means being willing to put down something that cannot be recovered first.

The things we have to accept can be organized in that way.

1. A wrong answer that remains on the record

A seed-stage judgment may not be graded for five to seven years. During that entire period, I continue to exist as the person who made that judgment. An observer can update an opinion. But the fact that you once put your name behind someone cannot be updated away.

2. Spending time in advance

A founder may spend years building a company, while I make a judgment after only a handful of meetings.

No matter how much time I spend, that asymmetry can never be eliminated entirely. There seems to be only one way to reduce it: spend my time before the equity is secured. Signing up for swimming classes to use a product and meeting founders every week during office hours are ultimately expressions of the same idea.

If the investment never happens, that time is not recoverable. But unless I spend unrecoverable time in advance, my trust remains an impression rather than an observation.

And I do not think I can put my name behind someone based on an impression. I would add one thing here. If this kind of advance investment is treated purely as a matter of individual diligence, it will not happen consistently.

Investors are human too. When we get busy, we conserve our time. So I lean toward the view that this needs to become structural.

The investor should not appear as an occasional event. The investor should already exist inside the founder’s everyday environment, so that the frequency of interaction and stimulation naturally increases. In that kind of structure, trust is not granted once on the final investment committee day. It accumulates little by little every day.

That is one of the reasons I believe our Starting Point space is different.

3. Spending reputation in advance

When I email or call the next investor on behalf of a team, what I am spending is not only the company’s reputation but also my own credibility.

That may be an expenditure I never recover. The moment an investor begins protecting that too carefully, they naturally become an observer. They say positive things to everyone, but they never actively put their credibility behind anyone. 

That is the state I am most wary of. 

4. Being willing to occupy the position of being disliked

An observer can remain a nice person until the very end. Once you become involved, you sometimes have to say uncomfortable things. And if those things turn out to be wrong, that also remains on the record. 

You have to be willing to be disliked by the founder, and sometimes to remain a minority opinion inside your own organization. Being prepared to answer the question, “Why did you push for this?” is also part of what you have to accept.

That said, I think involvement and intrusion must be clearly distinguished. Paradoxically, giving someone the answer is not necessarily involvement. It can be closer to control. You trap the team inside your own intuition and then convince yourself that you have helped.

Responsible involvement, as I understand it, lies on the opposite side. 

You leave the decision with the founder. You stay beside them long enough for that decision to become clearer. You put materials on the table, ask questions, and wait until the founder can name the answer for themselves.

That approach is much more expensive. It takes time. It may never be recovered. And it is often invisible. So if I had to summarize it, I would say: The difference between an observer and someone who is truly involved is not distance. It is expenditure.

You can be physically close to someone and still remain an observer if you have nothing at stake. To be candid, I cannot confidently say that I am currently willing to bear all four of these costs every time.

But I have at least developed one question I can use to check myself:  Am I only spending things that I can recover, or am I also betting something that may never come back? I cannot answer that question confidently every time.  But at the very least, I keep asking it of myself.

Seed investing is not about predicting the future with certainty. It is closer to recognizing potential before sufficient evidence exists—and being willing to attach your own judgment and credibility to that belief while knowing you may be wrong.

For Ahn, responsible involvement does not mean giving founders the answers. The decision must remain theirs. The investor’s role is to stay close enough to ask better questions, invest time before the outcome is known, and, when necessary, put personal reputation behind the people they choose to support.

Ultimately, the difference between an observer and someone who truly engages is not simply proximity. It is what they are willing to put at risk without knowing whether it will ever be returned. Her perspective raises a deeper question about early-stage investing: not only what an investor knows, but what they are willing to commit before certainty exists.