Founding Cookpad: staging the revenue on a user-posted recipe service (1998)
Gather for free, recover by staying on food: the user-posted model
The heart of Cookpad’s founding was to open recipes for free — widening the base of people posting and searching — and then to layer monetisation on top in stages: advertising in 2002, paid membership in 2004. Having, at the very start of the business, chosen a $4 (¥500)-a-month charge only to withdraw it after barely two months, Sano switched the order — build value and scale first, recover later — and that reordering set the course of everything that followed. A business carrying losses in the year to April 2005 had, by the year to April 2008, grown into one generating more than $5.8M (¥600m) in sales and around $2.9M (¥300m) in ordinary profit — precisely because a base widened for free supported several revenue streams, advertising and paid membership, at once.
What stands out is that this revenue base was built while staying specialised in a single field — cooking. Against the temptation to broaden the sources of revenue, Sano instead preached “stop doing Good,” narrowing the aim and concentrating resources on the single point of making cooking a pleasure. To what looked like an either/or — paid or free, expand or specialise — the founding-period judgement offered an answer: layer paid membership on top of a base widened for free, and let several revenue streams coexist while staying specialised in cooking. The discipline of continually asking what the value is as seen by the user became the template for the paid-membership model that would carry on after listing, and set the skeleton of a business that supports the everyday domain of cooking with information technology.
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 Cookpad
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
Cookpad’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/2193/manifest.json | Resource index |
| GET | /api/2193/history.json | History overview |
| GET | /api/2193/timeline.json | Chronology |
| GET | /api/decisions.json | All management decisions (index) |
| GET | /api/2193/decisions.json | Management decisions (index) |
| GET | /api/2193/decisions/{slug}.json | One decision (full dossier) |
| GET | /api/2193/executives.json | Executives |
| GET | /api/2193/shareholders.json | Major shareholders |
| GET | /api/2193/financials.json | Financial statements |
| GET | /api/2193/financials-longterm.json | Long-term results |
| GET | /api/2193/segments.json | Business segments |
| GET | /api/2193/regions.json | Sales by region |
| GET | /api/2193/workforce.json | Workforce |