IPS HOLDINGS CO LTD

Company Overview

IPS Holdings is a small Japanese enterprise-software services company. It helps mid-sized and upper-mid-sized companies install, customize, upgrade, and maintain SAP-based ERP systems. In plain English, it sits between SAP and the customer: it turns a complex package into a working finance, purchasing, logistics, and operations system. It also provides post-installation maintenance and related support.

Data freshness matters here. The latest clean official annual base is FY2025 ended June 2025. More recent data is partial: the company disclosed 9M FY2026 results through March 2026 on 8 May 2026, and the latest detailed balance-sheet and cash-flow snapshot is the 1H FY2026 filing through December 2025. The company has not yet released full FY2026 results.

The business has grown, but this is not a clean SaaS compounding story. It is a specialized implementation and maintenance business with real skill, recurring customer relationships, and a strong balance sheet, but also with project lumpiness, vendor dependence, and limited scale.

How the Company Makes Money

IPS makes money in two linked ways. First, it wins SAP ERP implementation projects. These are larger, lumpier, and more dependent on project timing and go-live milestones. Second, once the customer is live, it earns maintenance, upgrade, and related support revenue. That second stream is smaller but steadier.

What is actually driving growth? Two concrete drivers matter. First, Japanese mid-sized manufacturers and distributors still need ERP modernization, and SAP’s S/4HANA and public-cloud migration create real project demand. Second, IPS has a niche position inside that ecosystem: it targets companies roughly in the JPY 10bn to 200bn revenue band, where a focused specialist can still beat larger generalists on delivery speed and industry-specific templates.

The company’s differentiation is not a consumer brand or patented software monopoly. It is a bundle of narrower advantages: SAP Platinum partner status, a two-decade delivery history, its EasyOne implementation templates and add-ons, customer references, and a reputation for serving the Japanese mid-market rather than only very large enterprises. Management also says only around 20 meaningful SAP implementation players remain after years of attrition. That matters. It does not create an impregnable moat, but it does raise the bar for a new entrant.

Where do profits actually come from? The company does not disclose segment profit because it reports as a single segment. So exact profit mix is unavailable. The hard fact is that nearly four-fifths of revenue still comes from implementation work, so most profit probably still comes from efficient delivery of SAP projects, with maintenance providing continuity, upgrade work, and customer retention.

Owner earnings sanity check. I would not use reported P/E alone here, because part of FY2025 cash generation benefited from working-capital timing and the company is spending real money to adapt its templates and capabilities to SAP’s public-cloud model.

This is modestly lower than the headline earnings yield implied by the P/E. The reason is simple: FY2025 benefited from favorable working-capital movement, and some of the spending tied to public-cloud readiness looks economically recurring even if it is not all expensed as plain maintenance.

Capital efficiency is good. ROE has held around 16-18% for four straight audited years: 15.7% in FY2022, 17.3% in FY2023, 16.5% in FY2024, and 17.5% in FY2025. Reported ROIC measures are high but noisy because the business is asset-light and carries low invested capital; the latest official metrics show Greenblatt-style ROIC around 17% and operating ROIC around 28%. I would treat that as evidence of a good business model, not a precise number.

Is incremental capital earning high returns? Broadly yes. From FY2022 to FY2025, revenue rose from JPY 2.73bn to JPY 3.73bn and net income from JPY 178m to JPY 272m, while headcount rose only from 135 to 157. That suggests added people and added know-how have still produced attractive incremental returns.

Why the Stock Fell

The stock has not collapsed, but it has been stuck in a low-expectation range. Around early July 2026 it traded near JPY 1,203, roughly 6% above the 52-week low of JPY 1,135 and about 8% below the 52-week high of JPY 1,312. For a microcap with low liquidity, that is enough to tell you the market is not paying up for the story.

The plain-English reason is that investors seem to believe FY2025 may have been close to a local peak in profitability. Audited FY2025 revenue grew 19.3%, but FY2026 company guidance called for only 1.8% revenue growth, 0.3% operating profit growth, and a 7.3% decline in net income. That is a sharp deceleration.

There are also two more specific worries. First, the company is spending more to adapt to SAP’s public-cloud model, which raises the fear that the business is being forced to reinvest just to stand still. Second, the business remains project-driven and customer-concentrated, so investors do not trust any single strong year. In FY2025, one customer, Nippon Denpa Kogyo, was still 15.9% of sales.

What the Market Is Assuming

(a) One-time, cyclical, or sentiment-driven factors

• FY2025 benefited from large project go-lives that will not repeat cleanly in FY2026.
• FY2026 guidance implies a soft fourth quarter.
• The stock is illiquid and lightly followed, so sentiment can dominate fundamentals.
• Microcap IT services businesses rarely get full credit for cash unless growth is obvious.

(b) Medium-term business headwinds

• SAP public-cloud migration requires more template, consulting, and capability investment.
• Hiring skilled SAP talent is difficult and expensive.
• Project timing can swing revenue and profit materially between quarters.
• Customer concentration creates earnings lumpiness.

(c) Potential long-term structural threats

• The company is heavily dependent on SAP’s ecosystem and partner economics.
• Public-cloud standardization could reduce high-value customization work.
• Larger integrators or SAP itself could capture more of the mid-market value pool.
• The moat may be narrower than the recent ROE suggests because this is still a people-and-partner business, not a software license annuity.

Temporary or Structural?

Reality check versus market narrative. The market is right to be cautious, but several feared problems are not yet visible in the numbers.

For SaaS metrics like ARR and churn, the data simply does not exist here. This is not a subscription software issuer. The right hard checks are revenue, order intake, backlog, margins, ROE, cash, and leverage.

Structural risks only.

My bottom-line diagnosis is that the current issue is more time than essence. The business is being asked to adapt to SAP’s public-cloud economics, but the hard data still show growth, cash, and acceptable margins. The one genuine structural fragility is vendor concentration. That does not mean impairment is happening now; it means the ceiling on quality is lower than the reported ROE might suggest.

Is the Market Wrong? By How Much?

The market is not making a huge mistake, but it may be somewhat too pessimistic. At today’s price, investors are valuing IPS as a small, lumpy, vendor-dependent services business with flat near-term earnings. That is broadly fair. Where the market may be underestimating value is in the balance-sheet protection and the still-healthy SAP migration demand. Where the market is correctly skeptical is on durability: this is not a software toll bridge.

At roughly JPY 1,203 per share, the stock implies an owner-earnings yield of about 8% on my base estimate. That is not screamingly cheap, but it is respectable for a business with net cash and mid-teens ROE. On management’s FY2026 guidance, the stock trades at about 10.9x earnings. I think the correct required equity yield is around 10% for the base case, because the business is good but not fortress-like.

This is a FY2025-based valuation adjusted with 9M FY2026 updates and the latest official half-year cash figure. It is not a price target. The critical uncertainty is how much of the current cloud-transition spending is temporary catch-up versus economically recurring maintenance of competitiveness. If more of it is recurring, the bear case becomes more relevant.

So: the market is probably a bit too cold, but not obviously wrong by a mile. My base case is mild undervaluation, not a dramatic dislocation.

Key Facts, Estimates, and Judgments

Time-as-a-moat test. If I had IPS’s current market capitalization in cash, I could fund a competing team, but I still could not quickly recreate the business. In 2 years, probably not: SAP partner status, delivery references, templates, and trust would block you. In 5 years, maybe you could build a credible challenger if SAP supported you and you hired scarce consultants well. In 10 years, yes, but only with consistent execution. The blockers are not capital intensity; they are ecosystem access, trained talent, customer references, and accumulated process know-how.

Moat & mispricing score: 6/10. The moat is real but narrower than a casual glance at ROE would suggest. The market is correctly discounting single-vendor dependence, project lumpiness, and limited scale. What it may be getting wrong is treating the current slowdown as if the business has already lost its earning power; the numbers still show healthy demand, cash, and decent returns. That leaves a modest valuation gap, not a heroic one.

Final judgment: the current problem is mostly time, not essence. The structural risks are real, especially SAP dependence, but the present numbers do not show franchise damage. The shares look mildly undervalued, backed by cash, but the business quality is not strong enough to justify calling this a clear major mispricing.