Booking a loss on purpose: winding up Mexico, writing down the U.S. holding company (1998)
What a decision to drop the pretense left behind
Tsujimoto’s remark that he “dropped the pretense” and chose loss-making books can be read as, for a Japanese manager of that era, a rather unusual call. For a founder who leased rather than owned his head-office building and preached mi-no-take management, deciding to clear unrealised losses in a single stroke rather than carry them forward sat squarely along the line of his philosophy. The anecdote that he recognised losses beyond even what the auditors had flagged reflects a consistent pattern of judgment — choosing what helps the future numbers over dressing up the present ones.
Tsujimoto’s reading at the time — that “software development is entering an age strongly governed by a company’s financial health” — reads almost as a premonition of the later RE Engine era, when development budgets of tens of billions of yen became ordinary. Had he not chosen in 1998 to clean the wound before it could damage the balance sheet, the financial base that underpins the run of consecutive profit growth from the 2010s might have taken a different shape.
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 |