"Local", in our line of work, often means "we can drop by". For us it means something else, and it shapes what we build.
Since 1999, we've worked in Lyon and the region. Twenty-six years. We could have moved elsewhere, or diluted into a "national" market. We stayed, not sentimentally, by professional choice. A provider rooted in a territory for twenty-six years doesn't build the same tools as a provider parachuting in. Not necessarily better: different. Here's what it changes in practice.
We already know your market
We've seen several generations of restaurateurs, wine merchants, schools, museums, winemakers open and close here. We know a Lyon restaurant runs on a different clientele cycle than a Marseille one, not for sentimental reasons but tourist flow, corporate-events weight, student rhythm. When we build you a tool, we factor that in. We know roughly when your peaks hit, which clientele dominates in your district, which months go quiet. A generic tool doesn't.
We already know your networks
Who talks to whom, in Lyon, in your trade? Which accountants, which institutions, which referrers really count? We haven't met them all, but we know the terrain. A Parisian or national provider has a generic map. That changes what we propose. A communications tool that doesn't know your district has its own recommendation dynamic misses 30% of the effect. One that knows can target.
We already know local habits
People in Lyon don't spend the way Parisians do. Not an opinion: a fact. We know when wallets open, when calendars close, when emails go unanswered (Fête des Lumières, for one, reshapes much of December in the city centre). In a planning, ticketing, or ordering tool, those details are decisive. A generic tool treats them as exceptions. A tool made in Lyon treats them as the rule.
What it changes in the final tool
Take a concrete case: a planning tool for a Lyon museum. A national provider offers a standard interface: weekdays, weekends, national holidays. We know the three days around Fête des Lumières blow up night attendance, and require a different visitor flow, stock, and team schedule. The tool is built with those three days as major events, not exceptions. Twenty-six years in Lyon isn't a date on a plaque. It's a library of cases.
What we've seen on the ground
A design detail we put into Le Petit Musée du Vin's app and wouldn't have thought of without local knowledge: handling the periods when the museum sees more English-speaking tourists than locals, with automatic default-language switching for public displays.
FAQ
Do you only work in Lyon? We work in Lyon first because that's where we have depth. We accept projects elsewhere when the need resembles a case we've already handled. We decline when local context is decisive and we don't know it.
Does that make your rates higher? Not higher: better adapted. We don't sell "a tool", we sell a tool that works where you are.
You're in Lyon or the region, building something that has to fit the ground? Tell us how you work today. We'll come see. Let's talk →