The Multi-Tier Subcontracting Pyramid Under Pressure: What Happens to Body-Shop SIers When AI Writes the Code

#ai #business #consulting #beginners

Key Points

Japan's tajuu-shitauke (multi-layer subcontracting) structure routes enterprise IT work from a prime contractor (motoke) down through one or more subcontractor tiers to the engineers who actually write and test the code, a pattern that's persisted, largely unchanged, since the mainframe era.
Each tier historically takes its margin off the top before passing reduced-price work downward. A client-paid ¥1,000,000 monthly rate can leave the engineer actually doing the work with roughly ¥350,000 to ¥400,000 after cascading through two or three intermediary layers.
AI-assisted coding tools compress exactly the layer this structure depends on most: routine implementation, testing, and documentation work performed by second- and third-tier subcontractors and individual SES engineers.
The pyramid's top (client relationships, architecture, governance) looks likely to hold up. Its middle and bottom, firms and engineers whose entire value proposition is executing defined tasks at a lower price than the tier above, are facing the sharpest margin compression in the industry.
Japan's 2026 Subcontract Act reform, which expanded transparency requirements to creative and consulting services, gives lower-tier firms a real legal lever to push back on unfair pass-through pricing right as AI is already reshaping what "fair" pricing even means.

Introduction

A subcontractor relationship I've watched come under real strain recently is a fairly typical version of what's starting to happen across the industry. This is a second-tier firm that built a stable, unglamorous business supplying detailed-design and coding-and-testing engineers to a prime contractor's enterprise projects, at a rate that undercuts the tier above it. That's the entire business model: execute defined tasks, reliably, for less than the next tier up would charge. As the prime contractor's own AI-assisted tooling starts producing that same detailed-design and coding output directly, at a fraction of the cost and turnaround time, there's no lower price the second-tier firm can offer to stay competitive. It isn't underpriced. It's becoming structurally obsolete.

The pyramid this firm sits inside is one of the most distinctive features of Japan's IT industry. The prime contractor, or motoke, wins the client relationship and the overall project, then delegates substantial portions of detailed design, implementation, integration testing, and commissioning to one or more subcontractor tiers below it. Prime contractors capture the largest margins, commonly cited around 30-40%. First-tier subcontractors run 20-30%. Second-tier and below drop to 10-15%. Individual engineers, often working under System Engineering Service (SES) staffing arrangements, sit at the bottom, with compensation shrinking at each layer above them. A documented rate cascade shows the mechanism concretely: a client paying roughly ¥1,000,000 a month for an engineer's time can leave that engineer with something in the range of ¥350,000 to ¥400,000 after the intermediary tiers each take their cut.

This structure has survived for decades because it solved a real coordination problem: large enterprise projects needed a way to scale headcount up and down without every firm in the chain carrying the client relationship or the delivery risk directly. AI-assisted coding isn't attacking that coordination function. It's attacking the thing the lower tiers are actually selling, person-hours of implementation and testing labor, priced progressively lower the further down the pyramid you look. As a prime contractor, or increasingly the client itself, can generate a larger share of that same output directly, the lower tiers' entire value proposition, execute cheaply, stops being a viable business on its own.

Pyramid Layer Economics Under AI Compression

graph TD
    Client[Client] -->|pays full rate| Prime[Prime Contractor Motoke]
    Prime -->|passes down reduced rate, keeps 30 to 40 percent margin| Tier1[First-Tier Subcontractor]
    Tier1 -->|passes down reduced rate, keeps 20 to 30 percent margin| Tier2[Second-Tier Subcontractor]
    Tier2 -->|passes down reduced rate, keeps 10 to 15 percent margin| SES[Individual Engineer SES]
    AI[AI-Assisted Coding Tooling] -.->|replaces routine output of| Tier2
    AI -.->|replaces routine output of| SES

Layer	Historical Role	Historical Margin	Effect of AI-Assisted Coding
Client	Pays full contracted rate	N/A	Increasingly aware of the gap between what AI can produce and what's still being billed for
Prime contractor (motoke)	Client relationship, architecture, governance, overall delivery risk	~30-40%	Largely intact so far. Judgment and relationship work AI doesn't replace
First-tier subcontractor	Mid-scale delivery management, some architecture	~20-30%	Under pressure, but retains value where it manages integration complexity AI can't own alone
Second-tier subcontractor and below	Detailed design, coding, testing execution	~10-15%	Hardest hit. This is exactly the work AI-assisted tooling compresses
Individual engineer (SES)	Task-level implementation	Remainder after cascading cuts	Displaced where the task is routine; in higher demand where verification and AI-output review are the actual job

Recommendation: if your firm's position in this chain has always been "we execute the same task the tier above us does, for less," that position won't survive AI-assisted coding regardless of how thin you cut your margin further. The layers most likely to survive are the ones pricing judgment, integration complexity, or client trust, not marginal labor cost.

What's Likely to Survive, and What a Lower-Tier Firm Should Change Now

Firms moving up the value chain, not just down on price. The subcontractors most likely to survive won't compete on being cheaper than the tier above. They're taking on integration and governance responsibility that used to sit with the prime contractor, becoming harder to replace with AI output alone.
Firms specializing in verifying AI-generated output, not just producing more of it. Reviewing and validating AI-generated code against a client's actual production constraints is turning out to require exactly the kind of experienced-engineer judgment that routine implementation work didn't.
Firms using Japan's 2026 Subcontract Act reform actively. The reform's expanded transparency requirements give lower-tier firms real standing to contest unfair pass-through pricing. Firms that understand and use this leverage should renegotiate from a stronger position than firms that don't know the reform applies to them.
Firms consolidating instead of competing on the same shrinking margin. Some second- and third-tier firms are merging capabilities, combining a compressed coding-and-testing practice with a smaller firm's domain expertise, to offer something closer to the first-tier's integration value than to commodity execution.
Firms that change nothing. These are the most exposed to winding down, getting acquired for their client relationships and remaining engineers, or shrinking into a much smaller commodity-execution niche with correspondingly thinner margins.

Questions to Ask Your Team

Where does our firm actually sit in our clients' delivery chains, and is our value proposition still "we execute this cheaper than the tier above," or has it genuinely moved to something AI-assisted tooling can't produce directly?
If a prime contractor above us started generating our layer's output directly with AI tooling, what would we still have left to sell them?
Are we aware of what Japan's 2026 Subcontract Act reform actually changed for transparency and fair pricing in multi-tier arrangements, and have we used it in a renegotiation?
Have we tested whether our engineers are more valuable reviewing and validating AI-generated output than producing new output themselves, and are we pricing that shift yet?

Conclusion

The multi-tier subcontracting pyramid isn't collapsing, and it's not going to. What it built its lower tiers on, the assumption that there's always a cheaper price for the same routine task one layer further down, is what's breaking. Firms most likely to weather the pressure are moving toward judgment, integration, and verification work. Firms trying to survive by cutting their price further into an already-thin margin are the most exposed. The prime-contractor layer looks likely to hold up fine, because it was never really selling person-hours in the first place. Everyone underneath it needs to figure out, quickly, whether they've been selling person-hours the whole time, and if so, what else they actually have.

DEV Community