Company Overview

IPS Holdings is a small Japanese IT services company listed on the TSE Standard market. Economically, it is a specialist SAP partner: it helps mid-sized and upper-mid-sized companies install SAP-based ERP systems, then supports those systems after go-live. The company shifted to a holding-company structure in July 2025, but the underlying business is still that of a focused SAP implementation and maintenance firm.

The latest clean official annual base is FY2025. That year ended on 2025-06-30 and the annual securities report was filed on 2025-09-26. More recent data is partial and unaudited: official quarterly earnings disclosures through 9M FY2026 and management guidance for the full FY2026 year. Current price and market capitalization are current market data as of 2026-07-21.

On the supplied market-data date, the stock trades at ¥1,101 and the equity is worth ¥2,519,060,475. The authoritative deterministic block does not provide a usable net cash or net debt figure; it lists net cash as unavailable because debt-input fields are incomplete. I will not invent that number. What hard audited FY2025 data do show is ¥1.227bn of cash, ¥1.235bn of total liabilities, and only ¥18 thousand of interest expense, so there is no visible leverage stress.

The cleanest earnings base is the audited FY2025 result: revenue ¥3.733bn, operating income ¥363m, and net income ¥272m. More recent official but unaudited 9M FY2026 data show revenue ¥2.788bn, operating income ¥306m, and net income ¥185m. Management guidance for FY2026 is revenue ¥3.8bn, operating income ¥364m, and net income ¥252m. The supplied owner earnings of ¥321.989m are a model estimate for FY2025, not an audited fact.

How the Company Makes Money

IPS makes money in two linked ways. First, it wins SAP ERP implementation projects. These are project-based, people-intensive engagements where revenue depends on consultant utilization, delivery discipline, and the ability to avoid project overruns. Second, after installation it earns recurring revenue from maintenance, operations support, add-ons, upgrades, and related services. In FY2025 audited data, the ERP implementation business produced ¥2.922bn of sales, while maintenance and other services produced ¥811m. That means roughly 78% of revenue still comes from implementation work.

The attractive part of the model is specialization. IPS is not a generic SIer. It has spent decades inside one ecosystem, has SAP’s platinum partner status, says it has installed SAP at more than 180 customers, and uses its own implementation library and templates under the EasyOne brand. That lowers deployment time, raises win probability in its niche, and lets a small company punch above its weight. It also targets a specific customer band rather than trying to serve everyone.

The fragile part is equally obvious. This is a human-capital business with vendor dependence. Fixed-asset intensity is low, but economic capital intensity is not low: the real assets are trained consultants, project managers, implementation know-how, and customer references. Cash flow can swing sharply with billing milestones, receivables, payables, and advance payments. The business is also concentrated. Management discloses that one customer represented 15.9% of FY2025 sales.

This matters for classification. IPS looks like a durable niche franchise if SAP remains important and if the company preserves its specialized delivery capability. It does not look like a true high-return compounder with an unlimited runway. Growth is capped by hiring capacity, the SAP ecosystem, and the degree to which implementation work stays value-added rather than becoming standardized and price-driven.

Why the Stock Fell

The stock does not appear to be reacting to a scandal, balance-sheet accident, or obvious accounting problem. I do not see a verified company-specific blow-up after the FY2025 annual report. The more plausible explanation is a de-rating of expectations.

FY2025 was strong on reported numbers. Audited revenue rose 19.3%, operating income rose 10.5%, and net income rose 20.1%. But when management reported those results on 2025-08-08, it guided FY2026 to only 1.8% revenue growth, 0.3% operating profit growth, and a 7.3% decline in net income. That is a sharp slowdown immediately after a strong year.

The stock seems to have traded down as the market absorbed that deceleration. Using market data, today’s market cap of ¥2.519bn is about 16% below the roughly ¥2.995bn filing-date market value embedded in the FY2025 annual data. Management then kept FY2026 guidance unchanged through Q1, H1, and Q3. That reinforced the idea that FY2025 may have captured a good part of the current project wave and that FY2026 will be more about digestion than acceleration.

The dominant market narrative is straightforward: large projects boosted FY2025, SAP public-cloud adoption will standardize and compress implementation economics, and the company may be moving from a favorable migration phase into a flatter, lower-visibility phase. Whether that is correct is the central question.

What the Market Is Assuming

One-time or cyclical concern: revenue and profit are project-timing sensitive. That concern is real, but the numbers do not support a collapse narrative. On audited annual data, revenue rose from ¥2.728bn in FY2022 to ¥2.831bn in FY2023, ¥3.129bn in FY2024, and ¥3.733bn in FY2025. Operating income also rose from ¥242m to ¥303m, ¥328m, and ¥363m. More recent unaudited quarterly data are lumpy but not broken: Q1 FY2026 revenue fell 7.5% year on year, but H1 revenue still grew 1.5%, and 9M revenue grew 4.1%. This is a project business, and the quarterly pattern looks like timing noise plus tougher comparisons, not a broken demand engine.

Medium-term headwind: margins may be peaking. Management has been spending on public-cloud templates, product development, and consulting capacity. That shows up in the numbers. FY2025 revenue growth was strong, yet the audited operating margin slipped to 9.7% from 10.5% in FY2024. On single-quarter unaudited data, Q2 FY2026 revenue grew about 8.8% and Q3 grew about 9.3%, but standalone quarterly net income was slightly down year on year in both quarters. That pattern says the revenue line is still alive, but some of the incremental economics are being competed away or reinvested.

Long-term threat: the market is assuming that SAP public cloud changes the value chain. This is the serious issue. Management itself acknowledges that public-cloud deployment pushes more “fit to standard” work and less heavy customization. If implementation becomes more standardized, billable hours and pricing power can compress. IPS is trying to offset that by selling higher-value consulting, customer enablement, and its own templates, but that is exactly where the market is skeptical.

The long-term bear case is not fully confirmed by current data. FY2025 orders were strong: total orders were ¥3.721bn, up 30.3% year on year, and ERP implementation orders were up 56.8%. ERP backlog rose to ¥369m, up 6.4%. Total backlog was roughly flat to slightly down at ¥649m. That does not look like demand falling off a cliff. What it does look like is a company with decent demand but uncertain long-run margin structure.

There is also an evidence gap the market may be filling with pessimism. IPS is a single-segment company and does not give the level of cohort, contract-duration, or customer-lifetime detail that would let an outside investor cleanly separate migration work from durable post-implementation economics. When visibility is limited, the market usually pays a lower multiple.

Temporary or Structural?

SAP dependence. This is the biggest real structural risk. Management discloses that ERP implementation represented 78.3% of FY2025 sales and that the maintenance side is also SAP-related. The damaged mechanism, if this risk materializes, is direct: partner economics, customer access, and product relevance. If SAP changed partner terms materially or if IPS lost strategic standing in the ecosystem, that would be structural damage and not realistically reversible within three years. It is not observed today, but it is always present.

Public-cloud standardization and commoditization. This is structural but survivable. The damaged mechanism is pricing power and billable customization hours. It is reversible only if IPS successfully moves more of its value into templates, upstream consulting, change management, training, adoption support, and post-go-live services. The current evidence shows pressure, but not failure: revenue is still growing, and orders are still coming in. So this is a live structural risk, not a proven impairment.

Talent scarcity. This is not truly structural unless it persists long enough to break delivery quality or customer acquisition. The mechanism is capacity: no consultants, no projects. Within three years it is reversible through recruitment, training, compensation, and offshore leverage. Audited employee count rose from 147 in FY2024 to 157 in FY2025, and the company’s IR page says group employees were 164 as of 2025-07-01. That does not prove talent abundance, but it does show that the issue has not yet translated into contraction.

Project concentration and working-capital volatility. This is not truly structural. It affects optics, not necessarily franchise value. The mechanism is quarter-to-quarter volatility in cutover timing, receivables, payables, and advance payments. That is why operating cash flow swung from negative ¥258m in FY2022 to positive ¥493m in FY2023, back to negative ¥76m in FY2024, and then to positive ¥539m in FY2025. A project business can look cheap or expensive depending on where you catch the cash cycle.

The time-as-a-moat test gives a mixed result. In two years, a well-funded competitor cannot easily rebuild IPS’s specific reference base, SAP delivery playbook, and customer trust in the same niche. In five years, the moat weakens because large integrators can push standardized cloud offerings downmarket and hire away talent. In ten years, the moat depends less on implementation skill and more on whether IPS can own a meaningful layer of consulting, templates, and support around SAP rather than just supplying labor. That is a real moat, but it is a modest one.

My classification is therefore clear: the observed problem is mostly TIME—slower growth, margin digestion, and market skepticism after a strong year. But the business carries a genuine ESSENCE risk through SAP dependence and cloud-driven commoditization. That essence risk is not new; the market is simply focusing on it more aggressively now.

Is the Market Wrong? By How Much?

The first thing to say is that the asset case is weak. On the supplied deterministic “worth-dead” data, NCAV is ¥1.117bn, only 44.36% of the current market cap. Liquidation value is unavailable. This is not a classic Graham net-net. If the business were permanently impaired, the balance-sheet floor would not protect you much at today’s price.

The “worth-alive” case is better. The authoritative FY2025 block gives book value of ¥1.677bn, P/B of 1.50x, and owner earnings of ¥321.989m, implying an owner-earnings yield of 12.78% and a 7.82-year payback. Those are respectable numbers for a niche service business. But I do not want to capitalize the full FY2025 owner-earnings figure without a haircut, because FY2025 cash flow was helped by working-capital movements and prior years show meaningful volatility. My valuation is therefore FY2025-based, adjusted with 9M FY2026 official updates and FY2026 company guidance. I do not use unverified TTM data.

Moat-and-mispricing score: 5/10. The niche has value, but the stock is not obviously mispriced. The market is paying for a living business, not for a liquidation floor, and that is broadly the right frame.

Per-share values below use 2,287,975 shares, implied by the supplied 2026-07-21 market cap and share price and consistent with the latest treasury-adjusted quarterly share count.

Scenario Owner earnings base Normalization Required equity yield Net cash/debt adjustment Implied equity value Implied value per share Vs. current price
Bear ¥230m My estimate: assumes cloud standardization compresses margins and FY2025 cash conversion was flattered by working-capital timing 14.0% ¥0 applied because authoritative net cash/debt is unavailable ¥1.64bn ¥718 -34.8%
Base ¥290m My estimate: going concern remains intact, but I haircut FY2025 model owner earnings for volatility and slower FY2026 growth 11.5% ¥0 applied because authoritative net cash/debt is unavailable ¥2.52bn ¥1,102 +0.1%
Bull ¥330m My estimate: FY2025 owner earnings broadly sustain, order flow converts, and public-cloud transition is absorbed without lasting margin damage 9.5% ¥0 applied because authoritative net cash/debt is unavailable ¥3.47bn ¥1,518 +37.9%

The key point is not the exact decimal. It is the shape of the payoff. IPS is not cheap on dead value; it is only attractive if live earning power holds. On my base case, the market is roughly right. On my bull case, there is meaningful upside, but that upside requires confidence that public-cloud standardization does not hollow out the niche. On my bear case, the downside is substantial because the balance-sheet floor is too low to rescue the equity.

So the market is probably not very wrong. It may be somewhat pessimistic on near-term earnings quality, but it is rational to demand a high yield from a micro-cap, SAP-dependent, people-driven services company with only modest hard-asset protection. The mispricing, if any, is moderate rather than large.

Key Facts, Estimates, and Judgments

Item Value / assessment Type As of Why it matters / falsification check
Business SAP-focused ERP implementation and maintenance specialist Official fact FY2025 annual / company IR Thesis depends on niche specialization, not broad IT exposure
Latest clean official annual base FY2025 annual report filed 2025-09-26 Official fact - audited annual data 2025-09-26 This is the clean base; I do not substitute unverified TTM
Current share price / market cap ¥1,101 / ¥2,519,060,475 Current market data 2026-07-21 Valuation and upside/downside are measured from here
Net cash / net debt Unavailable in authoritative deterministic block; audited cash was ¥1.227bn and FY2025 interest expense was ¥18k Current snapshot limitation + official fact FY2025 / 2026-07-21 snapshot If hidden leverage is larger than it appears, the valuation is too high; if actual net cash is positive, the valuation is conservative
FY2025 earnings base Revenue ¥3.733bn, operating income ¥363m, net income ¥272m Official fact - audited annual data FY2025 Core earnings anchor for the valuation
More recent official data 9M FY2026 revenue ¥2.788bn, operating income ¥306m, net income ¥185m Official fact - unaudited quarterly data 2026-03-31 Shows business is still growing, though not explosively
FY2026 management outlook Revenue ¥3.8bn, operating income ¥364m, net income ¥252m, dividend ¥38 Company guidance Unchanged through 2026-05-08 If FY2026 misses despite strong 9M progress, market skepticism is validated
Revenue mix ERP implementation ¥2.922bn; maintenance/other ¥811m Official fact - audited annual data FY2025 Shows dependence on project revenue and SAP-linked economics
SAP concentration ERP implementation is 78.3% of sales and maintenance is also SAP-related Official fact / judgment on importance FY2025 If SAP partner economics worsen, the thesis breaks quickly
Worth-dead NCAV ¥1.117bn, or about ¥488 per share Model estimate from supplied deterministic block 2025-06-30 base / 2026-07-21 market Shows weak downside asset protection; this is not a net-net
Worth-alive Owner earnings ¥321.989m, owner-earnings yield 12.78%, payback 7.82 years Model estimate from supplied deterministic block 2025-06-30 base / 2026-07-21 market Shows the stock only works if live earnings endure
Core judgment Current weakness is mostly TIME, but with real latent ESSENCE risk from SAP dependence and cloud commoditization Judgment Current Main thing that would change the thesis is evidence that public-cloud migration is structurally lowering IPS’s earning power
Strongest falsification checks Loss of SAP standing; multi-year margin compression despite stable revenue; sustained weak cash conversion after working-capital normalization; shrinking maintenance revenue alongside flattening implementation demand Judgment Current Any of these would move the case from TIME toward ESSENCE