Capcom

The second restructuring: the recoil from over-investing in mobile (2012)

Key decision·2012· Capcom — the full company history →

What a second restructuring revealed

As the label “second” makes plain, this was not Capcom’s first restructuring. If the first, of 2003–04, was a “defensive” reform that brought development and sales under management control, the one in 2012 can be read as a painful exercise in selection and concentration after a bet on a growth market backfired. Posting a 55% profit decline in the year after a record-sales year brought home to the company how an investment in a growth field could shake its core console business.

Ironically, the lessons of the mobile business it cut loose here seem in part to have pointed the company, a few years later, toward another technology investment — the RE Engine. Whether it could admit the failed investment while the financial wound was still shallow, and re-narrow its focus, was arguably one cause of the later run of twelve straight years of profit growth. The founder’s phrase, mi-no-take management, looks to have been tested at precisely this moment.

Revenue and net margin, FY2007–FY2017

Revenue in ¥ bn (bars) and net margin in % (line), for the years around the decision. Shaded columns are FY2012 onwards — after it was taken.

Source: securities reports

Read the full dossier in Japanese →

The Japanese edition carries the complete record of this decision — the situation that forced it, the options weighed, what actually followed, and the sources behind every claim.

Other key decisions at Capcom


Yen amounts are converted at the average rate of each figure’s own year — not today’s rate; the revenue chart is shown in yen. Exchange rates & sources — the full ¥/US$ table →


Disclaimer

  • This page is provided for general information only and is not investment advice, nor a recommendation to buy or sell any security.
  • Figures are compiled independently and include our own estimates, approximations and machine-processed data; we make no warranty as to their accuracy or completeness.
  • Sources are primarily each company’s securities reports and other public filings, but errors and omissions may remain.
  • Any use of this information is at the reader’s own risk. Past performance does not indicate future results.
  • Company names, logos and other marks belong to their respective owners.

Data API

Capcom’s history, financials, executives and shareholders are published as static JSON — no key, plain GET. Full specification →

Method Endpoint Returns
GET /api/companies.json All companies
GET /api/9697/manifest.json Resource index
GET /api/9697/history.json History overview
GET /api/9697/timeline.json Chronology
GET /api/decisions.json All management decisions (index)
GET /api/9697/decisions.json Management decisions (index)
GET /api/9697/decisions/{slug}.json One decision (full dossier)
GET /api/9697/executives.json Executives
GET /api/9697/shareholders.json Major shareholders
GET /api/9697/financials.json Financial statements
GET /api/9697/financials-longterm.json Long-term results
GET /api/9697/segments.json Business segments
GET /api/9697/regions.json Sales by region
GET /api/9697/workforce.json Workforce