Kea Insight / Analyst Relations
Founders Need Analyst Relations for One Reason: Internal Conviction Is Not Market Evidence
Founders are usually the people most convinced by the company’s story. That is exactly why they need an external test of it.
Founders know why the company exists. They remember the problem that triggered the first product decision, the customers who took an early risk and the arguments that persuaded investors, hires and partners to join. That history is valuable. It also creates a blind spot: internal conviction can become a substitute for external evidence.
Analyst Relations is useful to founders because it forces the company to explain itself to people who did not live through that history. A relevant analyst does not automatically care about the origin story, the fundraising deck or the engineering decisions that feel important internally. They care about the market, the buyer problem, the alternatives, the evidence and whether the company has earned a place in the conversation.
The goal is not to turn the founder into an AR specialist. It is to use the analyst perspective as a disciplined test of the decisions founders already own: positioning, market choice, product direction, evidence and where scarce executive attention should go.
Founder conviction is useful until it becomes the market assumption
Every start-up needs conviction. Without it, difficult product choices, early hiring and long sales cycles become impossible. The problem starts when the company assumes the market shares that conviction simply because the internal logic feels obvious.
A founder may see a new category where buyers see an unfamiliar product. The team may believe a technical capability is the differentiator while customers value a different outcome. Leadership may think an incumbent is obsolete while enterprise buyers still see it as the safe choice. A funding round may validate the company’s potential without validating the way buyers understand the market.
These are not failures. They are normal gaps between building a company from the inside and being understood from the outside.
The risk is allowing the founder’s explanation to become the only explanation the company ever tests. Sales repeats it, marketing polishes it, product reinforces it and eventually the business becomes very good at telling itself the same story.
Analyst Relations can interrupt that loop.
Analysts give founders an informed outside test
A relevant analyst sees more than one company trying to explain the market. They hear from competitors, buyers, customers and adjacent vendors. They may agree with the founder’s view, reject it or ask questions the company has been avoiding.
That does not make the analyst automatically right. It makes the conversation useful.
The founder should listen for where the external model of the market differs from the internal one. Does the analyst place the company in the same category? Do they understand the target buyer? Which competitors do they see as credible alternatives? Which claims need more evidence? Which part of the story sounds genuinely different and which part sounds like the same language every vendor uses?
One conversation is not a mandate to change strategy. Several independent conversations surfacing the same issue are harder to dismiss.
This is where AR becomes upstream market intelligence rather than a calendar-management function. The work is valuable when it helps leadership test an assumption before that assumption becomes a year of product investment, a new market entry or a positioning platform the rest of the company is forced to defend.
Our Insight The analyst disagrees with you. That does not make them wrong. goes deeper into how to test critical feedback rather than either obeying or dismissing it.
The founder story has to survive without the founder in the room
Founders are often unusually good at adding missing context in real time. They can explain why a feature exists, what a customer really meant, how a market changed and why the company made an unusual strategic choice. That ability can hide a weakness in the wider market story.
If the company only makes sense when the founder is explaining it, the story is not yet doing enough work.
Analysts are a useful test because the conversation has to be compressed. The company needs to explain the customer problem, the market context, the alternatives, the approach and the evidence without relying on ten years of background knowledge. The analyst should be able to place the company afterwards without reconstructing the entire founder narrative.
That same discipline helps elsewhere. Enterprise buyers, partners, new employees and investors all encounter versions of the company without the founder standing beside every sentence. A clearer market story travels further because other people can repeat it accurately.
This is why the distinction between pitch and positioning matters. A founder can deliver an exceptional pitch and still leave the market unsure where the company belongs. The Pitch Is Not the Positioning explains why the market needs a version of the story it can recognise and reuse.
Evidence matters more as the company moves upmarket
Early customers can buy on belief, access and speed. Larger enterprises need more proof.
The founder may know the product works because they have watched customers use it. An enterprise buyer wants to know whether it works in an environment like theirs, whether the vendor can support the deployment, whether the security and compliance story is credible and whether other organisations have accepted the same risk.
Analysts tend to ask many of the same questions because they are trying to understand whether the company belongs in a serious market conversation. That makes briefing preparation a useful evidence audit.
Which claims can the company substantiate today? Which customer examples actually prove enterprise readiness? Which capabilities are generally available rather than planned? Where is the roadmap doing too much work in the story? Where does the company claim differentiation without a clear comparison?
For a founder, these questions can be uncomfortable because they expose the gap between ambition and proof. That is precisely the value.
Strong AR does not ask the founder to become less ambitious. It makes the boundary between current evidence and future ambition clearer, so both can be communicated credibly.
Founders should spend attention, not become the AR department
Founder involvement matters most when the conversation requires founder-level context: market creation, strategic direction, category logic, major product shifts and the decisions behind them.
It does not mean the founder should own analyst mapping, scheduling, research tracking, follow-up and every routine update. Executive attention is too expensive for that.
A serious AR programme should protect founder time by deciding which analysts deserve it and why. That means understanding the analyst’s coverage, buyer relevance, research responsibility and current relationship with the company before asking for an hour of executive attention.
The founder’s job in the conversation is then clear: explain what only leadership can explain, bring the evidence that requires executive credibility and listen carefully when the outside view challenges an internal assumption.
The rest of the programme should create continuity around that moment. Product provides technical truth. Customer teams provide deployment evidence. Sales brings buyer feedback. AR prepares the interaction, records what changed and makes sure the next useful action happens.
That is very different from asking the founder to “do some AR”.
Turn the learning into operating decisions
The value of founder participation is lost if the output is a set of interesting meeting notes.
Every important interaction should end with a small number of decisions. Does the category explanation need work? Is the analyst map wrong? Is the company missing a proof point? Does product need to investigate a recurring market concern? Has a buyer segment become more relevant? Is leadership assuming a competitive advantage that external evidence does not support?
Some findings will require action. Others should simply be monitored until more evidence appears. The discipline is in making the distinction visible and assigning ownership where something genuinely needs to change.
Founders do not need Analyst Relations because they lack conviction. They need it because conviction is strongest when it survives informed external challenge.
The founder knows what the company is trying to become. The market still needs evidence of what it is today.
That is the gap a good AR programme helps leadership manage.
Start with the Kea AR Readiness Check if you want to test whether the company has the story, evidence and executive commitment for a serious programme, or explore Analyst Relations as a Service when the company needs senior AR capability without building the full function internally.
Put this into practice
Give your market story stronger evidence.
Bring leadership, product and marketing together to test the story, identify proof gaps and prepare for informed analyst questions.
Explore AR WorkshopsNot sure where to start? Take the eight-question AR Readiness Check.
