Ramping up engineer hiring and bringing technology in-house (2006)
Owning technology bred the next business
The meaning of this decision goes beyond immediate server reinforcement. For an ad agency — a sales-led company — to hire engineers itself and entrust the design and operation of its infrastructure to a technology chief was a decision to shift the centre of the company’s capabilities from sales to technology. As symbolised by a design that used MySQL and Oracle for different purposes, bringing things in-house was not merely securing manpower but creating a state in which it could optimise its own services with its own technology. Having decided to own media, it had to own the technology to support it too — the 2004 Ameba choice inevitably summoned this in-housing.
And the technological strength grown in this period did not stop at Ameba alone. An organisation able to design and run large-scale services in-house later became the parent body sending people and know-how into fields where technology decides competitiveness — the Cygames games business, and the ad-tech unit handling ad-delivery technology. The starting point at which CyberAgent, begun as a sales company, came to be recognised as a place for engineers to work also lies in this 2006 turn. Entry into media prompted the in-housing of technology, and that technology in turn bred the next business — the first link of this chain was tied here.
Revenue and net margin, FY2001–FY2011
Revenue in ¥ bn (bars) and net margin in % (line), for the years around the decision. Shaded columns are FY2006 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 CyberAgent
- 2000 Listing on TSE Mothers at the peak of the dot-com bubble — and the crash (2000)
- 2001 The Murakami Fund closes in, and a takeover defence (2001)
- 2004 Launching the Ameba blog and entering the media business (2004)
- 2019 Governance reform triggered by a 57.56% approval for the president’s reappointment (2019)
- 2022 ABEMA’s free live-streaming of all 64 World Cup matches (2022)
- 2023 Announcing the succession plan and the generational handover from the founder (2023)
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
CyberAgent’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/4751/manifest.json | Resource index |
| GET | /api/4751/history.json | History overview |
| GET | /api/4751/timeline.json | Chronology |
| GET | /api/decisions.json | All management decisions (index) |
| GET | /api/4751/decisions.json | Management decisions (index) |
| GET | /api/4751/decisions/{slug}.json | One decision (full dossier) |
| GET | /api/4751/executives.json | Executives |
| GET | /api/4751/shareholders.json | Major shareholders |
| GET | /api/4751/financials.json | Financial statements |
| GET | /api/4751/financials-longterm.json | Long-term results |
| GET | /api/4751/segments.json | Business segments |
| GET | /api/4751/regions.json | Sales by region |
| GET | /api/4751/workforce.json | Workforce |