How Follonica makes a living
Three economic levels, a handful of industries and one very seasonal calendar. Below, the structure of the local economy — and the iron-age history that still shapes it.
Primary, secondary, tertiary
Economists sort activity into levels — extracting, making and serving. Follonica's mix leans hard toward the tertiary, a common story on the Tuscan coast.
Employment by economic level
Share of local jobs (illustrative)
Extracting & growing
Maremma olive groves and vineyards, honey, market gardens and a small artisanal fishing fleet. Increasingly monetised through agritourism rather than raw output.
Making & building
Construction, metal and mechanical workshops, boat maintenance, food processing. The direct descendant of the town's foundry DNA.
Serving & hosting
Hotels, campsites, restaurants, bars, beach concessions, retail, real-estate and public services. This is the modern engine of Follonica.
Where the jobs actually are
Zoom past the three big levels and the working town comes into focus: a service economy built around visitors, property and the everyday needs of a mid-sized coastal community.
Estimated employment by industry
Share of local jobs, largest first (illustrative)
An economy with a summer heartbeat
Follonica's defining economic fact is seasonality. Population and spending swell in July and August, then fall back — a rhythm that shapes hiring, housing and public budgets.
People present in town, by month
Residents + visitors, indexed (illustrative)
Why it matters
A four-fold summer swing means beach concessions, restaurants and shops must earn a year's margin in a season, while roads, water and waste must be sized for the peak but paid for year-round.
The quiet months
Extending the season — spring cycling, autumn food events, off-peak wellness — is the single biggest lever local planners reach for. You can pull that lever yourself in the game.
Two hundred years, two economies
Follonica is unusual: an Italian coastal town that was industrial before it was touristic. Its structure flipped almost completely inside a century.
- 1577–1700s
Medici-era ironworking uses local water and forest charcoal near the coast; the area is thinly settled and malarial.
- 1830s
Grand Duke Leopold II of Lorraine invests heavily in the Regie Fonderie. Iron ore from Elba is smelted here; a company town takes shape.
- 1838
The Church of San Leopoldo is completed with a cast-iron portico and fittings — the foundry showing off in its own building material.
- late 1800s
Under the new Italian state the works pass to private and national operators; Follonica is, above all, an iron town.
- 1900s
Land reclamation tames the marshes; rail and roads improve; the beach and pinewood begin to draw visitors.
- mid-1900s
Heavy iron production winds down. The industrial monoculture that built the town no longer sustains it.
- 1960s–1990s
Mass beach tourism and second-home building remake the economy around summer.
- 2013
The MAGMA museum opens inside the old furnace hall — heritage becomes a tourism asset in its own right.
Structure of employment: then vs now
Share of jobs by level, ~1920s vs today (illustrative)
Data note & sources
This is an educational explainer, not an official statistical release. The charts use rounded, representative estimates assembled to illustrate the shape of Follonica's economy — the direction and rough magnitude of things — rather than to report exact, audited figures.
They draw on the kinds of public sources you would consult for the real numbers:
- ISTAT — Italy's national statistics institute (population, census, employment by sector).
- Comune di Follonica — municipal open data, tourism and planning documents.
- Regione Toscana / Toscana Notizie — regional tourism and economic statistics.
- Parco Nazionale delle Colline Metallifere (Tuscan Mining UNESCO Global Geopark) and MAGMA — for the mining and foundry history.
Want to make this rigorous? Swap the illustrative arrays in the page markup for verified ISTAT/Comune figures and update this note with the exact tables and years. The chart code reads its data straight from the HTML, so no build step is required.