Founding TKC as a shared computing bureau for accounting firms (1966)
A company built to defend, not to attack
What marks this founding decision out is that it looks less like an offensive venture going after a new market than like a company set up to protect the work of its founder and his fellow professionals. In the middle of his fight with the authorities, Iizuka Takeshi learned first-hand how precarious the footing of the accounting profession was. Onto that came the wave of computerisation he had seen in the West, and with it the prospect that staying manual would sweep the whole occupation away. That the words “defence of the professional domain” were placed first in the articles of incorporation was surely because those two experiences pointed to the same conclusion.
That a company begun in defence would go on growing for half a century was not, however, foreseeable at the outset. A design based on shared use invites losses unless the customers are there in numbers, and losses did indeed accumulate in the early years. Only once the mechanism of a membership organisation — drawing customers inside the business — began to work did two narrowly defined customer groups turn from narrowness into depth. Whether defining your business territory tightly at the start becomes a strength or a constraint is a question this company would be handed back again and again, in later decisions about diversification and in its changes of president.
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 TKC
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
TKC’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/9746/manifest.json | Resource index |
| GET | /api/9746/history.json | History overview |
| GET | /api/9746/timeline.json | Chronology |
| GET | /api/decisions.json | All management decisions (index) |
| GET | /api/9746/decisions.json | Management decisions (index) |
| GET | /api/9746/decisions/{slug}.json | One decision (full dossier) |
| GET | /api/9746/executives.json | Executives |
| GET | /api/9746/shareholders.json | Major shareholders |
| GET | /api/9746/financials.json | Financial statements |
| GET | /api/9746/financials-longterm.json | Long-term results |
| GET | /api/9746/segments.json | Business segments |
| GET | /api/9746/regions.json | Sales by region |
| GET | /api/9746/workforce.json | Workforce |