Saksoft (SAKSOFT)

Fast Grower

FairStock Score: 32/100 — RISKY

Score breakdown: P/E: 2/3 · ROCE: 1/2 · Growth: 2/2 · Dividend: 0/1

Key Financials

Current Price₹165.71
Market Cap₹2,118.42 Cr
P/E Ratio16.64
ROCE24.04%
ROE33.64%
Dividend Yield0.6%
Profit Growth-9.3%
Debt/Equity0.06
Sales Growth-0.2%
Promoter Holding66.68%
52-Week Range₹107.59 — ₹224.75
SectorIT - Software
Book Value₹60.93

Strengths

Concerns

AI Analysis

At ₹143.60, Saksoft capitalizes at ₹1,878 Cr. I always ask: what am I getting? The company earns a superb 33.64% ROE and 24.04% ROCE with negligible debt — Debt/Equity of 0.07. That is the sort of economics that draws my attention. But Graham would insist on a margin of safety. At 14.33 times earnings and 9 times book, the market is paying up for that quality. Book value is only ₹15.96, so the asset safety net is thin. Profit grew 21.13% while sales grew 10.56%; the market likes that, but as an investor I need to know whether margins can stay or grow. Latest quarter sales were ₹251 Cr and net profit ₹29 Cr, roughly an 11.5% net margin. The 7/9 Piotroski score suggests financial health is decent. Promoters own 66.68%, so their interests are aligned with mine. I am cautious. The share is 37% below its 52-week high of ₹229.68, and Mr. Market has been moody. A 0.56% dividend yield is not much compensation while waiting. Sales growth under 11% doesn't justify calling this a high-octane grower, but the 21% profit growth and sub-1 PEG ratio of 0.90 make it a candidate for a fast grower at a fair price. Graham would urge me to watch that the earnings growth is real, not engineered by one-offs. With a FairStock Score of 50, the picture is mixed. I would not buy blindly; I want sustained order flows, stable margins, and no dilution. If the company can keep ROE in the 30s and convert profits to cash, this might be a fine compounding machine. But I need a better margin of safety than a 9 times book value.

Data from BSE/NSE filings. AI analysis is for educational purposes only — not investment advice. Scoring methodology · Disclaimer