The Grand Design: pooling customer data held branch by branch (1993)
Solving a financial problem as a question of sales method
Read the 1993 Grand Design as an early anticipation of “DX” and you miss the point. What set it in motion was not technology but debt — ¥86.8bn of borrowings, about half of annual sales. Where the only ways to reduce them were to sell more or to cut more, what Otsuka Yuji chose was to consolidate customer information that had been held branch by branch into a single file, and to reorganize the sales force so that the same number of people could sell more. The character of the plan shows in exactly that: a financial problem, solved as a problem of how selling is done.
It did not work at once. Recurring profit in the year ended December 1993, when the plan was settled, was only ¥1.15bn, and by the year ended December 1998 earnings had fallen for the first time since the founding, to ¥1.7bn. Otsuka Yuji himself names 1998 as the year the core-systems work began, which suggests something like five years between drawing the picture and the shape of the company changing. That Otsuka Minoru was in the same period moving the front line by rebuilding the personnel evaluation system should be counted among the causes as well.
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 Otsuka Corporation
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
Otsuka Corporation’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/4768/manifest.json | Resource index |
| GET | /api/4768/history.json | History overview |
| GET | /api/4768/timeline.json | Chronology |
| GET | /api/decisions.json | All management decisions (index) |
| GET | /api/4768/decisions.json | Management decisions (index) |
| GET | /api/4768/decisions/{slug}.json | One decision (full dossier) |
| GET | /api/4768/executives.json | Executives |
| GET | /api/4768/shareholders.json | Major shareholders |
| GET | /api/4768/financials.json | Financial statements |
| GET | /api/4768/financials-longterm.json | Long-term results |
| GET | /api/4768/segments.json | Business segments |
| GET | /api/4768/regions.json | Sales by region |
| GET | /api/4768/workforce.json | Workforce |