Skip to content
Published on

Japan IT Industry Subcontracting Structure: SIer, SES, and the Pyramid System Explained

Authors

1. Overview of the Japanese IT Industry

1.1 Market Size and Growth

The Japanese IT market is the second-largest in Asia after China. According to IDC Japan, the domestic IT market is projected to reach approximately 26.6 trillion yen in 2025, representing an 8.2% year-over-year increase. The compound annual growth rate (CAGR) from 2023 to 2028 is estimated at 6.3%, with the market expected to reach 30.2 trillion yen by 2028.

According to the Yano Research Institute, the private-sector IT market in Japan is forecast at 16.68 trillion yen for FY2025 (up 5.0% YoY) and 17.1 trillion yen for FY2026 (up 2.5% YoY).

1.2 Unique Characteristics of Japan IT Industry

The Japanese IT industry has several distinctive features compared to other countries:

  • SI (System Integration) Dominance: Contract-based development far outweighs product/service businesses
  • Large Enterprise Leadership: A handful of major corporations dominate the market
  • Multi-layered Subcontracting: A pyramid structure where work flows from prime contractors down to subcontractors
  • Legacy Dependency: Aging systems built with COBOL, VB.NET remain in active use
  • Talent Shortage: The Ministry of Economy, Trade and Industry (METI) projects a shortage of up to 790,000 IT professionals by 2030

2. The Pyramid Structure of Japan IT

2.1 What is Tajuu-Shitauke (Multi-layered Subcontracting)?

Tajuu-shitauke (multi-layered subcontracting) is the most defining structural characteristic of the Japanese IT industry. The prime contractor (motoke) wins a project from the client and then delegates significant portions of the actual development work to subcontractors.

Client (End User / Enterprise)
    |
    v
Prime Contractor (Motoke) - NTT Data, Fujitsu, NEC, etc.
    |  Project management, requirements, basic design
    v
1st-tier Subcontractor (Ichiji-uke) - Mid-size SI companies
    |  Detailed design, partial implementation
    v
2nd-tier Subcontractor (Niji-uke) - Small SI companies
    |  Implementation, unit testing
    v
3rd-tier Subcontractor (Sanji-uke) - Small firms, SES companies
    |  Coding, test execution
    v
Individual Freelancers / SES Engineers

2.2 Roles and Reality at Each Layer

Prime Contractor (Motoke)

  • Direct contract with the client
  • Handles project management, requirements definition, and basic design
  • Highest profit margins (typically 30-40%)
  • Representative companies: NTT Data, Fujitsu, NEC, Hitachi, NRI

1st-tier Subcontractor (Ichiji-uke)

  • Receives detailed design and partial development work from the prime contractor
  • Mostly mid-size SI companies
  • Margins: 20-30%
  • Representative companies: SCSK, TIS, Otsuka Corporation

2nd-tier and Below

  • Performs actual coding and testing
  • Narrow scope of work with low unit prices
  • Margins: 10-15%
  • Difficult to understand the overall project picture

2.3 Problems with Multi-layered Subcontracting

ProblemDescription
Declining unit pricesEngineer compensation decreases at each layer
Skill stagnationLower tiers get assigned simpler tasks, limiting growth
Communication overheadRequirements can be distorted through multiple layers
Unclear accountabilityBlame-shifting becomes common when issues arise
Long working hoursLower tiers face the most deadline pressure

3. What is an SIer?

3.1 Definition

SIer (System Integrator, pronounced "esu-ai-yaa" in Japanese) refers to companies that comprehensively handle enterprise information system development. It is one of the most commonly used terms in the Japanese IT industry.

Key responsibilities of SIers include:

  • Consulting: Analyzing client business challenges and proposing IT solutions
  • Requirements Definition (Youken-Teigi): Defining system functions and performance requirements
  • Design (Sekkei): Basic design (Kihon-Sekkei) and detailed design (Shousai-Sekkei)
  • Development (Kaihatsu): Programming and implementation
  • Testing (Tesuto): Unit, integration, and system testing
  • Operations/Maintenance (Unyou/Hoshu): Post-launch system maintenance

3.2 Classification of SIers

Japanese SIers are broadly classified into four categories based on their origins:

Maker-affiliated SIers (Maker-kei)

SIers that originated from the IT services divisions of hardware manufacturers.

  • Fujitsu, NEC, Hitachi Solutions
  • Strength in integration with proprietary hardware
  • Stable but potentially vendor-locked

User-affiliated SIers (User-kei)

SIers that spun off from the IT departments of large enterprises.

  • NRI (Nomura Research Institute), SCSK (Sumitomo Corporation group), ISID (Dentsu group)
  • Deep domain knowledge from parent company industries
  • May have high parent company dependency

Independent SIers (Dokuritsu-kei)

SIers not affiliated with any specific large corporation.

  • TIS, Otsuka Corporation, NET ONE SYSTEMS
  • Vendor-neutral flexibility
  • Relatively weaker brand recognition

Foreign-affiliated SIers (Gaishi-kei)

Japanese subsidiaries of overseas IT companies.

  • Accenture Japan, IBM Japan, Deloitte Digital
  • Active adoption of global methodologies and cutting-edge technologies
  • Performance-based culture, higher compensation

3.3 SIer Business Model

[Flow of Contract-based Development]

1. Receive RFP (Request for Proposal)
   -- Client issues RFP with requirements

2. Proposal / Estimate
   -- SIer proposes team structure, schedule, and cost

3. Contract Award
   -- Ukeoi (deliverable-based) or Jun-inin (service-based) contract

4. Requirements Definition to Basic Design
   -- Primarily handled by prime contractor

5. Detailed Design to Development to Testing
   -- Often delegated to subcontractors

6. Delivery / Acceptance
   -- System delivered to client

7. Operations / Maintenance
   -- Ongoing revenue through separate contract

4. The Reality of SES (System Engineering Service)

4.1 What is SES?

SES (System Engineering Service) is a contract arrangement where engineers are stationed at client sites to provide technical services. Legally, it falls under Jun-inin contracts (quasi-delegation) and is distinct from dispatch (haken) contracts.

4.2 Differences Between SES and Dispatch

AspectSES (Jun-inin)Dispatch (Haken)
Contract typeQuasi-delegationDispatch contract
Command authorityVendor (employer)Client (dispatch destination)
Work instructionsVendor-side managerClient-side manager
License requiredNoDispatch business license required
Work managementManaged by vendorManaged by client

4.3 The Gray Zone Problem

The biggest issue with SES contracts is "gisou-ukeoi" (disguised subcontracting) or "gisou-haken" (disguised dispatch). While the contract is technically SES (quasi-delegation), clients often directly instruct engineers on-site. This is legally problematic but remains a widespread practice in the Japanese IT industry.

4.4 SES Industry Issues

Resume Fraud (Keireki-Sashou)

Some unscrupulous SES companies inflate engineers' resumes before submitting them to clients. In 2024, a court ordered damages exceeding 5.15 million yen in a related case.

Mismatched Assignments

Cases have been reported where aspiring engineers are assigned to call centers, electronics retail stores, or security guard duties completely unrelated to IT.

Low Rates and Opaque Margins

Through the multi-layered structure, the actual amount reaching engineers is significantly reduced.

[Example of SES Rate Flow - Monthly Basis]

Client payment: 1,000,000 yen/month
    | (Prime contractor margin 30%)
    v
Prime contractor to 1st SES: 700,000 yen/month
    | (1st SES margin 20%)
    v
1st SES to 2nd SES: 560,000 yen/month
    | (2nd SES margin 20%)
    v
2nd SES to Engineer salary: ~350,000-400,000 yen/month
    (After social insurance, admin costs, etc.)

4.5 Improvements in the SES Industry

Recent improvements include:

  • More SES companies offering full-time employee (seishain) positions
  • Better benefits (fukuri-kousei) and training programs
  • Emergence of specialized SES focusing on specific technology domains
  • Efforts toward rate transparency

5. Why Japan Remains SI-Centric

5.1 Historical Background

Japan's SI-centric structure was formed during the mainframe era of the 1960s-70s. Large enterprises established the practice of outsourcing system development to external SI companies instead of building internal IT departments, and this structure has persisted for over half a century.

5.2 Cultural Factors

Lifetime Employment (Shuushin-Koyou)

In traditional Japanese employment culture, working at one company until retirement was the norm. This resulted in IT talent concentrating in SI companies rather than accumulating within business enterprises.

Risk-Averse Decision Making

Japanese companies tend to prioritize "not failing" over innovation, preferring to entrust system development to proven large SIers.

IT as Cost, Not Investment

Many Japanese companies perceive IT as a "cost" rather than an "investment," favoring outsourcing over building internal development capabilities.

5.3 The Legacy Chain - The 2025 Digital Cliff

The "2025 Digital Cliff" (2025-nen no Gake), warned about in METI's 2018 DX Report, symbolizes the structural problems of Japan's IT industry:

  • Legacy system aging and complexity as the biggest barrier to DX
  • Potential economic losses of up to 12 trillion yen annually after 2025
  • Mass retirement of engineers proficient in COBOL and similar legacy languages
  • 62.7% of companies still operating legacy systems

Despite this warning, DX progress in Japanese companies has been slow, with growing polarization between companies actively pursuing DX and those lagging behind.

5.4 Signs of Change

However, signs of change are emerging:

  • In-house Development Trend: Some large enterprises are strengthening internal development teams
  • Cloud-Native Transition: Expanding use of AWS, Azure, and GCP
  • Agile Adoption: Moving away from waterfall-only approaches
  • Startup Growth: Technology-focused companies like Mercari, SmartNews, and LINE are growing
  • Increased DX Investment: The information services sector projects 11.7% growth in 2025 due to data center investment

6. Key Japanese IT Industry Terminology

JapaneseReadingMeaning
請負契約Ukeoi-keiyakuDeliverable-based contract with completion obligation
準委任契約Jun-inin-keiyakuService-based contract focused on work performance
派遣契約Haken-keiyakuWorker dispatch contract
偽装請負Gisou-ukeoiDisguised subcontracting

6.2 Organization/Position Terms

JapaneseReadingMeaning
元請けMotokePrime contractor
下請けShitaukeSubcontractor
孫請けMagoukeSub-subcontractor (2nd tier)
常駐JouchuuOn-site/stationed at client
客先常駐Kyakusaki-jouchuuClient-site assignment
プロパーPropaaIn-house full-time employee
協力会社Kyouryoku-gaishaPartner company (euphemism for subcontractor)

6.3 Development Process Terms

JapaneseReadingMeaning
要件定義Youken-teigiRequirements definition
基本設計Kihon-sekkeiBasic design (external design)
詳細設計Shousai-sekkeiDetailed design (internal design)
単体テストTantai-tesutoUnit testing
結合テストKetsugou-tesutoIntegration testing
総合テストSougou-tesutoSystem testing
受入テストUkeire-tesutoAcceptance testing

7. Career Advice for IT Professionals

7.1 What to Look for When Job Hunting in Japan

Red Flags to Avoid

  • Companies that cannot explain specific projects or tech stacks in interviews
  • SES companies emphasizing "no experience welcome" with unclear training programs
  • Companies at the 2nd or 3rd subcontractor tier (limited rates and growth opportunities)
  • Companies focused solely on "staffing" rather than specific technologies

Recommendations

  • Target prime contractor or 1st-tier subcontractor level companies when possible
  • Prioritize companies with in-house products/services (Web-kei, Jisha-kaihatsu)
  • Check employer review sites: OpenWork, Tenshoku-Kaigi
  • For SES, prefer companies that practice rate transparency (tanka-koukai)

7.2 Career Development Strategy

[Typical Career Path in Japan IT]

SES/Subcontractor Programmer (1-3 years)
    |
    v
Mid-tier SIer or Web Company SE (3-5 years)
    |
    v
(Option 1) Large SIer or Prime Contractor PM/Consultant
(Option 2) Senior Engineer at Web/Product Company
(Option 3) Foreign-affiliated Consulting/IT Company
(Option 4) Freelance (Freelancer)

8. Conclusion

Japan's multi-layered subcontracting structure is a deeply rooted system that has persisted for decades. While it offers stability and the capability to execute large-scale projects, it also carries structural problems including deteriorating engineer compensation, delayed technological innovation, and talent drain.

The "2025 Digital Cliff" has prompted gradual change in the Japanese IT industry, but fundamental structural transformation will take time. Those looking to work in Japan's IT sector should accurately understand this structure to make informed career decisions.


References

  • IDC Japan - Domestic IT Market Forecast 2025
  • Ministry of Economy, Trade and Industry (METI) - DX Report, IT Statistics
  • Yano Research Institute - Domestic Enterprise IT Investment Survey 2024
  • IPA (Information-technology Promotion Agency) - IT Human Resources White Paper