@Sanjay__Bakshi The most rational course of action is to buy below your expected value, hold when it's between your expected value and overvalued zone and sell above overvalued zone (No in-betweens or holding extra cash).
But there are many impediments in executing each step.
More from Dinesh Sairam
This thread is for investors or those who are interested in CDSL as an investment. Often the central reason quoted for an investment here is the gush of FCF the business produces and some float money also to boot. But this argument ignores a central problem as well. (1/11)
I completely agree that CDSL is a business that produces ample amount of Free Cash. So, it begs the question: "What are they doing with all that cash?" Generally, firms can utilize the cash on their books in 4 ways: Dividends, Acquisitions, Capex/Investments and Buybacks. (2/11)
CDSL does have a Dividend Payout Ratio of ~35-40%. But Dividends are the least efficient way of utilizing cash, due to the Triple Taxation on Dividends. More
Handled well, Inorganic Growth is so lucrative that some companies build their business models around acquisitions (Say, MSSL or Cyient). However, CDSL literally CAN'T be one such company. Read 7 (c) of the below regulatory document to know more:
https://t.co/071lwnnwJ4
(4/11)
CDSL can also reinvest cash into their own business, like most companies do. But CDSL (And most Exchanges) have little need for Capex/Reinvestment. CDSL's IPO came in at Rs. 523.99 Crores. Two years in, the Cash and Investments on their books stands at Rs. 650 Crores. (5/11)
I completely agree that CDSL is a business that produces ample amount of Free Cash. So, it begs the question: "What are they doing with all that cash?" Generally, firms can utilize the cash on their books in 4 ways: Dividends, Acquisitions, Capex/Investments and Buybacks. (2/11)
CDSL does have a Dividend Payout Ratio of ~35-40%. But Dividends are the least efficient way of utilizing cash, due to the Triple Taxation on Dividends. More
Handled well, Inorganic Growth is so lucrative that some companies build their business models around acquisitions (Say, MSSL or Cyient). However, CDSL literally CAN'T be one such company. Read 7 (c) of the below regulatory document to know more:
https://t.co/071lwnnwJ4
(4/11)

CDSL can also reinvest cash into their own business, like most companies do. But CDSL (And most Exchanges) have little need for Capex/Reinvestment. CDSL's IPO came in at Rs. 523.99 Crores. Two years in, the Cash and Investments on their books stands at Rs. 650 Crores. (5/11)

More from Wise investing
You May Also Like
A brief analysis and comparison of the CSS for Twitter's PWA vs Twitter's legacy desktop website. The difference is dramatic and I'll touch on some reasons why.
Legacy site *downloads* ~630 KB CSS per theme and writing direction.
6,769 rules
9,252 selectors
16.7k declarations
3,370 unique declarations
44 media queries
36 unique colors
50 unique background colors
46 unique font sizes
39 unique z-indices
https://t.co/qyl4Bt1i5x
PWA *incrementally generates* ~30 KB CSS that handles all themes and writing directions.
735 rules
740 selectors
757 declarations
730 unique declarations
0 media queries
11 unique colors
32 unique background colors
15 unique font sizes
7 unique z-indices
https://t.co/w7oNG5KUkJ
The legacy site's CSS is what happens when hundreds of people directly write CSS over many years. Specificity wars, redundancy, a house of cards that can't be fixed. The result is extremely inefficient and error-prone styling that punishes users and developers.
The PWA's CSS is generated on-demand by a JS framework that manages styles and outputs "atomic CSS". The framework can enforce strict constraints and perform optimisations, which is why the CSS is so much smaller and safer. Style conflicts and unbounded CSS growth are avoided.
Legacy site *downloads* ~630 KB CSS per theme and writing direction.
6,769 rules
9,252 selectors
16.7k declarations
3,370 unique declarations
44 media queries
36 unique colors
50 unique background colors
46 unique font sizes
39 unique z-indices
https://t.co/qyl4Bt1i5x

PWA *incrementally generates* ~30 KB CSS that handles all themes and writing directions.
735 rules
740 selectors
757 declarations
730 unique declarations
0 media queries
11 unique colors
32 unique background colors
15 unique font sizes
7 unique z-indices
https://t.co/w7oNG5KUkJ

The legacy site's CSS is what happens when hundreds of people directly write CSS over many years. Specificity wars, redundancy, a house of cards that can't be fixed. The result is extremely inefficient and error-prone styling that punishes users and developers.
The PWA's CSS is generated on-demand by a JS framework that manages styles and outputs "atomic CSS". The framework can enforce strict constraints and perform optimisations, which is why the CSS is so much smaller and safer. Style conflicts and unbounded CSS growth are avoided.