Before I Offer Advice, I Owe a Founder Three Questions

Imagine a founder arriving at an advisory conversation with a familiar question: should we hire a sales leader, rebuild the product, or raise prices? The temptation is to choose an option quickly. A confident answer can make the meeting feel productive before either person understands the problem.

My direct answer is this: before giving startup advice, an advisor should ask What are we really trying to change? What do we know, and what are we assuming? What can this team realistically do next?

For me, those questions define the difference between offering an opinion and accepting responsibility for its consequences. They also remind me that the founder, not the advisor, will live with the decision.

1. What are we really trying to change?

A founder’s opening question is often a proposed solution wearing the clothes of a problem.

“Should we hire?” might mean the founder is exhausted. It might mean sales conversations are not converting. It might mean customers require more implementation support than the business can comfortably provide. Each possibility calls for a different response.

I want to understand the desired change before discussing the proposed action. Is the goal more revenue, better retention, faster onboarding, or simply enough breathing room to make thoughtful decisions?

My perspective is shaped by enterprise SaaS and product building at Vahmine Technologies, where I am Founder & Growth Head. Our work spans Toolyt field sales automation, Dale interactive demos, Acadle’s learning platform, and enterprise automation services. That range makes me cautious about treating every growth question as a marketing question or every customer request as a product requirement.

A useful follow-up is: What would become noticeably better if we solved this?

If the answer remains vague, I should not rush toward a recommendation. Advice becomes more useful when the founder and advisor can describe the same destination, even if the route remains uncertain.

2. What do we know, and what are we assuming?

Once the intended change is clear, I want to examine the evidence beneath it.

There is a meaningful difference between customers asking for a feature, customers using that feature, and customers paying because it exists. There is also a difference between a difficult sales conversation and proof that the pricing is wrong.

I do not ask for evidence to turn advisory into an interrogation. I ask because an elegant explanation can become convincing through repetition alone.

In technology and product consulting, the proposed solution can arrive before the underlying uncertainty has been named. My responsibility is to slow that sequence down. What has the team directly observed? What has it heard second-hand? What is still a belief?

My advisory roles with BeagleSecurity and Zopnote make this distinction especially important to me. Familiarity with startups does not give me automatic knowledge of another team’s customers or constraints.

I would rather say, “We need to test that assumption,” than turn my experience into borrowed certainty.

The practical follow-up is: What evidence would make us change our minds? If nothing could change the recommendation, we may be defending a preference rather than evaluating a decision.

3. What can this team realistically do next?

Even sound advice can be wrong for the team receiving it.

A recommendation has to fit the people available, the cash required, the founder’s attention, and the commitments already made. Suggesting a new channel is easy. Operating it while maintaining the product and supporting customers is another matter.

I want to know what must stop if something new begins. Without that question, advice quietly becomes an additional workload.

I also ask which decisions are reversible. A small experiment can create learning without forcing the company into a large commitment. Other decisions deserve slower consideration because reversing them would be expensive or disruptive.

My work in education leadership and the Modern Innovation Hub in Kerala reinforces a principle I bring to advisory: useful guidance should strengthen someone’s ability to act independently.

The follow-up here is: What is the smallest responsible next step, and who will own it? The answer should belong to the team, not merely sound impressive in the meeting.

A checklist before the recommendation

Before I offer advice, I want us to be able to answer:

• Outcome: What specific change are we seeking?
• Evidence: Which observations support our understanding?
• Uncertainty: Which assumption matters most to test?
• Capacity: What can the team take on, and what must pause?
• Action: Who owns the next step, and when will we review it?

I do not see these questions as a script. They are a discipline against answering too early.

A good advisory conversation may end with a recommendation. It may also end with a better question and a modest experiment. I consider either worthwhile if the founder leaves with clearer judgment.

The measure I return to is simple: did I help the founder see the decision more clearly, or did I merely make my own experience more visible?