Rahul Sasi, founder of CloudSEK and a security researcher, explains why ideas matter only after someone starts implementing them. His account connects the origin of a product company in India with three ongoing founder responsibilities: finding exceptional people, creating customer value, and building a culture united by a clear purpose.
Before founding CloudSEK, Rahul travelled internationally as a cybersecurity speaker and contributed to open-source security work. During conferences, he collected material from startup booths and studied the companies while travelling. He noticed that many security vendors came from the United States, the United Kingdom, or Israel, even though many Asian professionals worked for them.
That observation led to a question: why could a world-class cybersecurity product not be built from this region and sold globally? While working at Citrix, Rahul also identified a product gap in digital-risk monitoring, where services rather than products dominated the market. In 2015, he left his job and began building the company.
Rahul distinguishes having an idea from implementing one. He researched the need, believed that a regional product company could compete internationally, and saw room for a product in an area served mainly through manual services. Yet none of those observations mattered until he acted and began learning through execution.
The company’s product evolved, but its underlying purpose remained stable: use technology to convert cybersecurity knowledge into intelligence and automate tasks that people had previously repeated manually. Rahul separates that durable mission from the product, which should change when customers and evidence reveal a better implementation.
Rahul compares his role to assembling a team of people whose abilities complement one another. He does not view the founder as the person with every superpower. Instead, a large share of his time goes into identifying strong people, helping teams recruit them, and aligning everyone around a common objective.
When the right people own responsibilities, constant checking is unnecessary. Rahul treats repeated follow-up as a sign that the hiring or delegation decision may have been wrong. This allows him to spend less time monitoring routine operations and more time on product, talent, and culture.
Selling a product is not the same as sustaining its usefulness. A skilled salesperson may be able to close an initial deal, but retention depends on whether the customer continues to receive value. Rahul therefore spends long hours thinking with the team about what should come next and how the product can solve meaningful problems.
This emphasis also explains why the company can change product details without abandoning its mission. Customer value is the test. The team can pivot an implementation while continuing to pursue automation and better cybersecurity decisions.
For Rahul, culture is what turns individuals into a cohesive group. He compares it to a tribe whose members share beliefs and work toward the same objective. CloudSEK even uses “Cloudster” rather than “employee” to reinforce a sense of common identity.
Culture is not treated as decoration around the technical work. It is one of the founder’s central responsibilities because talented people and a strong product still need a shared reason to act together.
Rahul urges mentees to ask questions that may appear simplistic. Everyday objects, designs, and conventions have reasons behind them; asking “why” exposes knowledge that passive observation misses. Fear of asking a supposedly foolish question limits discovery.
His second major lesson is persistence. Initial ability in school, university, or a first job is not enough if effort later becomes inconsistent. Progress compounds when someone continues to practise and investigate instead of alternating between bursts of effort and long periods of disengagement.
