How to say I do not know to investors and employees

Founders often feel a crushing pressure to be the smartest person in every room. You might feel that if you do not have an immediate answer for an investor or a definitive directive for an employee, you are failing as a leader. This blog entry examines why the opposite is true. We will explore how honesty about your knowledge gaps actually creates a foundation of trust and how you can navigate these moments without losing authority. We will cover the psychological shift required to admit ignorance, the specific ways to communicate this to your stakeholders, and how to ensure that not knowing something does not turn into a reason for your business to stop moving.

When you are building a company from nothing, your most valuable currency is your credibility. If an investor asks a complex question about your customer acquisition cost in a specific sub-sector and you make up a number to sound confident, you are taking a massive risk. If they check that number later and find it is wrong, you have lost their trust forever. They will wonder what else you are making up. When I work with startups, I often see founders treat every question like a test they must pass with a perfect score. In reality, the test is not about the data point itself. The test is about your integrity and your process for finding the truth.

Admitting you do not know something shows that you value accuracy over your own ego. It signals to everyone that when you do provide a definitive answer, it can be taken to the bank. This creates a culture of high information integrity. In a startup environment, moving fast is essential, but moving fast based on false data is the quickest way to hit a wall. By saying you do not know, you allow the organization to pause and gather the correct facts before committing resources to a specific path.

Investors are not looking for a human encyclopedia. They are looking for a partner who can navigate uncertainty. When you are in a pitch or a board meeting and a question comes up that hits a blind spot, use it as an opportunity to show how your brain works. Instead of guessing, explain why that specific metric or piece of information has not been your priority yet. This gives the investor insight into your strategic thinking and how you allocate your attention.

When I work with founders during their seed rounds, I tell them that an investor is buying into your ability to solve problems, not your ability to remember every spreadsheet cell. If you can clearly articulate the steps you will take to find the answer, you have satisfied the underlying concern. You are showing them that you are a person who respects the reality of the business. Ask yourself these questions when preparing for these interactions:

• What are the three most likely areas where I lack deep data right now?
• Why have I chosen to focus elsewhere for the time being?
• What is the specific process I will use to get this data if it becomes a priority?

By having these answers ready, your I do not know becomes a strategic statement rather than a sign of weakness. It shows you are in control of your roadmap and you know exactly where the edges of your current knowledge reside.

Your team looks to you for direction, but they are also very good at sensing when you are bluffing. If you pretend to have a perfect plan when the market is shifting or a product launch is failing, you create a culture of fear. Employees will feel that they also cannot admit when they are lost or when they lack information. This leads to a company filled with people who are pretending to work on things they do not understand.

When you are honest with your team, you give them permission to be honest with you. This is how you build psychological safety. If an engineer asks about a long term technical requirement that hasn’t been scoped, saying I do not know yet allows the team to focus on what is known. It reduces the noise. You can ask your team members for their input on how to reach that answer, which further empowers them. Try asking these questions during your next team meeting:

• What are we assuming is true that we actually have no data for?
• If we admit we do not know the outcome of this project, how does that change our immediate next steps?
• How can we test our way into an answer instead of debating it?

This shift in language moves the team away from anxiety and toward discovery. It turns a potential leadership failure into a collaborative research mission.

Saying I do not know should never be the end of the sentence. It should be the start of a clear, actionable process. I have found that the most successful founders use a three part framework to handle these situations. First, they acknowledge the gap. Second, they provide context on why it is a gap. Third, they define the timeline for the follow up.

For example, you might say: I do not have the churn numbers for our enterprise tier from last month. We are currently integrating a new tracking tool to get more granular data on those specific accounts. I will have that report to you by Thursday. This response is professional, transparent, and proactive. It shows you are already moving toward a solution. It is much better than a guess that might be off by ten percent.

Consider these steps when you are put on the spot:

• State the unknown clearly without using filler words or apologies.
• Explain the current status of that information or why it was deprioritized.
• Commit to a specific time or method for delivering the answer.

This approach maintains your authority while demonstrating that you are a truth seeker. It proves that you are more interested in building a solid business than in looking like you have all the answers.

One of the biggest risks in a startup is that admitting you do not know something can lead to analysis paralysis. Founders and teams can get stuck in endless debates about what the answer might be. This is a trap. In the startup world, movement is always better than debate. If the answer is truly unknown, the only way to find it is usually to do something.

Instead of debating the unknown in a conference room for three hours, decide what the smallest possible action is that would give you more information. If you do not know if customers will like a feature, do not debate it based on your gut feeling. Build a prototype and show it to five people. If you do not know the right price point, run a small test.

Doing is a form of learning. Criticizing or debating without data is a waste of your limited runway. When I see a team stuck because they are afraid to admit they do not know the path forward, I remind them that the path is created by walking. The difficulty of doing is real, and it is much harder than sitting back and criticizing a plan. But the doing is what builds the company. Embrace the unknown as a signal to move faster toward the facts, not as a reason to stop and second guess your vision. Your goal is to build something remarkable, and that requires a solid foundation built on reality, not on the performance of knowing everything.