Capcom is on one of the best runs in its history, and its president just explained why — a deliberate move away from games built around a single star creator.
Who said it
Haruhiro Tsujimoto, president of Capcom, credited the company's turnaround — in Capcom's FY2025 financial results materials — to a shift toward team-led development, which let franchises like Resident Evil survive the departure of creators such as Shinji Mikami.
"When a title becomes a series, it often ends up relying heavily on a particular developer... If that person doesn't follow through, there's no sequel... We therefore opted for a complete overhaul of each title. We didn't mind even if sales dropped temporarily, and by adopting a team-based game development approach, Capcom underwent a radical transformation."
— Haruhiro Tsujimoto, President, Capcom
What it means for players
It's the strategy behind Capcom's relentless release cadence and consistent quality — Resident Evil remakes, Monster Hunter, Devil May Cry and more. Tsujimoto added that the model also transfers expertise to newer staff, helping each series keep its standard high over time.
The proof is cheap on PC right now
Capcom's recent hits are exactly the kind of catalogue that ends up heavily discounted on PC. Lowest verified USD prices:
| Game | Lowest price |
|---|---|
| Resident Evil Village | from $5.28 |
| Monster Hunter World: Iceborne | from $5.99 (all-time low) |
| Resident Evil 2 | from $6.30 |
| Devil May Cry 5 | from $7.00 |
| Resident Evil 4 Remake | from $7.76 |
| Monster Hunter Wilds | from $13.49 |
FAQ
Why is Capcom doing so well?
President Haruhiro Tsujimoto credits a shift from single-creator to team-driven development, plus full reinvention of each franchise.
What's the cheapest Capcom game on PC right now?
Resident Evil Village from $5.28, with Monster Hunter World: Iceborne at an all-time low of $5.99 — compare stores on each game's page.
Sources
- Capcom Investor Relations — FY2025 financial results materials
- Haruhiro Tsujimoto (President & COO, Capcom) — comments on team-driven development
