Company Overview
Ricksoft is a small Japanese enterprise-software specialist. It sells and implements Atlassian-centered workflow tools, provides related consulting and managed services, and develops its own add-on products for the Atlassian ecosystem. In plain English, it helps large companies run software development, IT service management, and internal knowledge workflows on modern cloud tools.
Data freshness matters here. The latest clean official annual base is FY2026, ended 28 February 2026 and filed on 27 May 2026. As of this report, FY2027 first-quarter results are not yet official; the next earnings release is scheduled for 14 July 2026. So the operating and balance-sheet numbers below are mostly audited annual data for FY2026, while the share price and market capitalization are current market-data snapshots.
| Core item | Value | Type |
|---|---|---|
| Market capitalization | About JPY 4.36bn | Market-data estimate, based on a recent share price around JPY 968 |
| Net cash / (net debt) | About JPY 3.94bn net cash | Audited FY2026 annual data; cash of JPY 3.94bn and no material interest-bearing debt disclosed |
| Net income, trailing 12 months | JPY 263.8m | Audited FY2026 annual data |
| Current P/E | About 16x | Market price divided by audited FY2026 EPS of JPY 58.7 |
| Normalized P/E | About 13-14x | Own estimate, assuming normalized EPS of roughly JPY 70-75 after partial margin repair |
| Revenue CAGR | About 19.7% over 5 years; about 24.7% over 3 years | Audited annual data |
| Net income / EPS CAGR | No clean positive CAGR; earnings have been flat-to-down despite strong sales growth | Audited annual data |
Growth is real, but it has been driven by larger Atlassian license and renewal deals and by rapid growth in professional services. FY2026 revenue rose 20.4% to JPY 10.89bn. Within that, professional services revenue rose 53.5% to JPY 1.40bn. What has not happened is profit conversion: gross profit was essentially flat year on year despite the strong top-line growth.
| Owner earnings sanity check | Value | Type |
|---|---|---|
| Net income | JPY 263.8m | Audited FY2026 annual data |
| Less: sustaining capex | About JPY 20m | Own estimate; FY2026 reported capex was JPY 20.7m |
| Plus/minus working capital | Assume roughly neutral on a normalized basis | Own estimate; actual FY2026 working capital was heavily distorted by prepaid license balances and contract liabilities |
| Rough owner earnings | About JPY 240-245m | Own estimate |
| Owner earnings yield | About 5.5%-5.7% on total equity value | Own estimate using current market cap |
This owner-earnings result is not meaningfully different from the headline P/E. The reason is simple: this is a capital-light business, so capex is low, but one-year cash flow is noisy because the company prepays license costs and collects customer cash in advance. That makes reported free cash flow swing around more than true earning power.
Capital efficiency is mixed. ROE has ranged from roughly 8% to 18% in the last several years and was 8.3% in FY2026. A rough ROIC proxy was around 11% in FY2026. More important than the point estimate is the trend: from FY2023 to FY2026, revenue rose from JPY 5.62bn to JPY 10.89bn, but operating income fell from JPY 547m to JPY 377m. That means recent incremental capital has not been earning high returns.
Business quality is decent, but not pristine. Profits still come mainly from selling and supporting Atlassian-centered tools into enterprise customers, where switching costs can be real once workflows are embedded. The good part is stickiness, certifications, and a land-and-expand model inside large customers. The weak part is that Ricksoft does not control the economics of its core ecosystem. That matters more than the growth story.
How the Company Makes Money
Ricksoft reports one segment, but economically the business has three parts.
| FY2026 revenue stream | Revenue | Share of sales | What it means |
|---|---|---|---|
| Technology solutions | JPY 8.86bn | About 81% | Mainly Atlassian license sales and related solution proposals |
| Professional services | JPY 1.40bn | About 13% | Implementation, customization, support, training, operations |
| Own products | JPY 0.63bn | About 6% | Ricksoft-developed add-ons sold through Atlassian Marketplace |
The economic engine has historically been straightforward: win an enterprise account through tool selection and implementation, then expand usage across departments, renew licenses, and attach higher-value services. Management explicitly describes this as a land-and-expand model. That creates customer stickiness because once a large organization standardizes workflow, project tracking, or knowledge management on these tools, replacement is inconvenient and disruptive.
The most important fact is that Atlassian license sales accounted for 78.0% of FY2026 revenue. So while Ricksoft looks superficially like a software company, a large part of its economics still resembles a specialized value-added reseller with consulting attached. That distinction explains the current problem: revenue can grow quickly while gross margin gets squeezed if the vendor takes more of the pool.
Where do profits actually come from? Today, still mostly from the Atlassian-centered installed base and the services that sit on top of it. Where future profits need to come from is different: more professional services, more consulting, more managed service revenue, and more self-developed products. The market is waiting to see whether that shift will actually restore margin.
Why the Stock Fell
The stock did not fall because demand disappeared. It fell because the market stopped trusting the quality of the earnings model.
A recent market-data quote is around JPY 968, but the important move happened earlier: the shares hit a 52-week low of JPY 737 on 27 May 2026, down from a 52-week high of JPY 1,230. The catalyst was FY2026 results and, even more, FY2027 guidance. FY2026 sales rose 20.4%, but operating profit fell 17.8% and net income fell 25.8%. Then management guided FY2027 revenue up another 12.0% while guiding operating profit down another 46.7% and net income down 39.3%.
- Investors saw a company growing revenue but shrinking profit.
- Gross margin fell sharply because license costs rose faster than sales.
- Management said the professional-services business is being restructured, including temporary order restrictions.
- Contract liabilities surged, which improved future revenue visibility but made current-period accounting harder to trust.
- The company still pays no dividend, so the large cash balance gets little credit unless it turns into better earnings or better capital allocation.
In plain terms: the market is asking whether Ricksoft is becoming a bigger but worse business.
What the Market Is Assuming
(a) One-time, cyclical, or sentiment-driven factors
- The market dislikes the optics of revenue growing while profit is deferred or compressed.
- Contract liabilities make the income statement look weaker than underlying order activity.
- Small-cap illiquidity likely amplified the selloff.
(b) Medium-term business headwinds
- License gross margin has already deteriorated, and it may not bounce back soon.
- Professional-services reform is consuming time and depressing near-term utilization.
- Management is choosing growth and restructuring over near-term profit.
- Own products are still too small to offset weak license economics.
(c) Potential long-term structural threats
- Ricksoft is too dependent on Atlassian.
- The vendor, not Ricksoft, controls the core license economics.
- If Atlassian changes partner rules or sells more directly, Ricksoft’s economics weaken.
- The company may never become a truly high-margin software business.
Reality check versus the market narrative
| Concern | Quantitative reality check | Assessment |
|---|---|---|
| Demand is collapsing | Revenue rose from JPY 5.62bn in FY2023 to JPY 9.04bn in FY2025 and JPY 10.89bn in FY2026. FY2026 total orders were JPY 13.04bn, up 34.0%. | False. Demand is strong. |
| The balance sheet is getting dangerous | Cash rose from JPY 3.16bn in FY2024 to JPY 3.30bn in FY2025 and JPY 3.94bn in FY2026. No material interest-bearing debt is disclosed. | False. This is not a leverage problem. |
| Deferred revenue is low quality | Contract liabilities rose from JPY 1.06bn in FY2023 to JPY 2.28bn in FY2024, JPY 2.35bn in FY2025, and JPY 4.48bn in FY2026. | Mixed. It is real revenue visibility, but not the same as free profit. |
| The margin hit is only accounting noise | Gross profit was JPY 2.374bn in FY2025 and JPY 2.373bn in FY2026 despite 20.4% revenue growth. Gross margin fell from 26.2% to 21.8%. Operating margin fell from 5.1% to 3.5%, and FY2027 guidance implies 1.6%. | True. Margin damage is real. |
| Services will automatically fix the problem | Professional-services revenue grew 53.5% in FY2026 to JPY 1.40bn, but FY2027 guidance still calls for a sharp profit decline. | Unproven. The direction is right; the economics are not yet proven. |
Temporary or Structural?
The answer is mixed. The demand side problem is temporary. The margin-control problem is structural. The business is not broken, but the current profit model is weaker than it looked two years ago.
| Structural concern | Damaged mechanism | Can time heal it within 3 years? | Classification |
|---|---|---|---|
| Atlassian concentration | Gross profit capture on the core license stream. Ricksoft does not set the vendor economics. | Only partly. Ricksoft can diversify mix, but it cannot force Atlassian to improve partner margins. | Real structural but survivable |
| Platform dependency | Customer acquisition and renewal economics are mediated by one ecosystem. FY2026 revenue was still 78% Atlassian-license related. | Slowly, not quickly. Diversification into Workato, Miro, consulting, and own products can help, but not in one year. | Real structural but survivable |
| Professional-services restructuring | Utilization, delivery discipline, and pricing in the services arm. | Yes. This is organizational, not capital-intensive. If execution improves, it can heal within 1-3 years. | Not truly structural |
| Large contract-liability build | Reported revenue timing, not the core value-creation mechanism. | Yes. This should unwind through delivery and revenue recognition. | Not truly structural |
The key distinction is this: there is no evidence that customers are leaving, no evidence of financial stress, and no evidence that Ricksoft has lost its place in the ecosystem. There is evidence that its share of the economics inside that ecosystem has worsened. That is an essence issue, but not a death sentence.
Time-as-a-moat test
| If you had the current market cap in cash | Rebuild possible? | What would still block you? |
|---|---|---|
| Within 2 years | No | Atlassian certifications, enterprise references, partner rank, installed-base trust, and a usable add-on portfolio cannot be recreated that quickly. |
| Within 5 years | Partially | You could hire engineers and build a reseller/integration business, but credibility with large Japanese enterprises and ecosystem positioning would still lag. |
| Within 10 years | Probably yes | The moat is mostly time, trust, certifications, and ecosystem position, not hard technology. It is real, but it is not impregnable. |
So the moat exists, but it is a time-and-trust moat, not a deep product moat. That means it has value, but it also means vendor power matters a lot.
Is the Market Wrong? By How Much?
The market is partly wrong, but not dramatically so. It is too negative if it assumes demand is weak, the contract-liability build is meaningless, or the balance sheet is fragile. It is broadly right if it assumes that Ricksoft’s old margin structure has been impaired and that the company now has to prove a new, service-heavier profit model.
Moat & Mispricing Score: 5/10. Ricksoft is not a broken business, but it is also not a clean compounder today. The market is correctly penalizing single-vendor dependence and worsening gross margin. What the market may be getting wrong is the duration and severity of the repair: the company has real demand, no balance-sheet stress, and unusually strong revenue visibility through contract liabilities. Even so, without evidence of gross-margin stabilization, the upside is moderate rather than obvious.
Current implied yield: using rough FY2026 owner earnings of about JPY 244m, the stock offers only about a 5.6% owner-earnings yield on the full current equity value. That looks mediocre. But if one credits only JPY 1.5bn of the cash balance as genuinely excess and treats the rest as operating cash tied to prepaids and contract liabilities, the operating business is being valued at roughly JPY 2.86bn, which implies an adjusted owner-earnings yield of roughly 8.5%. That is much closer to a reasonable required yield for a small, concentrated software-services company.
| Intrinsic value case | Earnings base | Required equity yield | Operating value | Excess cash added | Equity value | Value per share | Vs. current price |
|---|---|---|---|---|---|---|---|
| Bear | JPY 180m owner earnings | 10% | JPY 1.80bn | JPY 1.00bn | JPY 2.80bn | About JPY 620 | About -36% |
| Base | JPY 255m owner earnings | 9% | JPY 2.83bn | JPY 1.50bn | JPY 4.33bn | About JPY 960 | Roughly flat |
| Bull | JPY 330m owner earnings | 8% | JPY 4.13bn | JPY 2.00bn | JPY 6.13bn | About JPY 1,360 | About +41% |
Valuation basis. These are own estimates, not official numbers. They are anchored on audited FY2026 net income of JPY 263.8m, FY2027 management guidance for net income of JPY 160m, low sustaining capex, and a conservative treatment of cash. I am not treating the full JPY 3.94bn cash balance as excess because this business carries large prepaid license balances and contract liabilities as part of normal operations.
Bottom line: the stock looks roughly fairly valued to mildly cheap, not deeply mispriced. The share price can work if margins stabilize and services become genuinely more profitable. If they do not, the current valuation is not low enough to make the structural risks disappear.
Key Facts, Estimates, and Judgments
| Item | Figure / conclusion | Category |
|---|---|---|
| Latest clean official annual base | FY2026, ended 28 February 2026, filed 27 May 2026 | Audited annual data |
| More recent official data | None yet; FY2027 Q1 release scheduled for 14 July 2026 | Company announcement / reporting calendar |
| FY2026 revenue | JPY 10.89bn | Audited annual data |
| FY2026 operating income | JPY 376.8m | Audited annual data |
| FY2026 net income | JPY 263.8m | Audited annual data |
| FY2026 cash | JPY 3.94bn | Audited annual data |
| FY2026 contract liabilities | JPY 4.48bn | Audited annual data |
| FY2027 guidance | Revenue JPY 12.20bn, operating income JPY 200m, net income JPY 160m | Company guidance from 29 April 2026 earnings release |
| Current share price / market cap used | About JPY 968 / JPY 4.36bn | Market-data estimate |
| Rough owner earnings | About JPY 240-255m | Own estimate |
| Normalized EPS used for sanity-check P/E | About JPY 70-75 | Own estimate |
| Core judgment | Demand is healthy; margin control is the real issue | Judgment |
| Structural diagnosis | Vendor dependence is structural, but survivable; services restructuring is not structural | Judgment |
| Investment conclusion | Not a busted story, but not yet a clear bargain; wait for evidence of gross-margin stabilization | Judgment |
If the next few quarters show that professional services can lift mix and that license-margin pressure is no longer getting worse, the equity can justify a higher value. If gross margin keeps falling, Ricksoft will remain a low-multiple, vendor-dependent services business, and the market will be right to stay skeptical.