Lyon

Business application development in Lyon and the Rhône-Alpes region

A critical process cannot be modelled over a video call. It is understood by sitting next to the person who has been keying in declarations for eight years and watching what they actually do — including the workarounds they invented and no procedure mentions.

Lyon 3e

offices at 12 rue de la Part-Dieu — workshops and acceptance run on site

60+

member companies using the platform we delivered to a Lyon buying group

Go · React · PostgreSQL

a single technical base, with no in-house proprietary framework

MEKANO is a business application development studio based in Lyon, at 12 rue de la Part-Dieu in the 3rd arrondissement. We build management applications for small and mid-sized companies and for buying groups: member portals, supplier approval, revenue declarations, year-end rebate engines, document management. At a fixed price, in accepted batches, with the source code handed over.

Proximity as a method, not as local colour

Being based in Lyon is not a sentimental argument. It is a constraint of method: the way we work assumes physical moments, and those moments become expensive to arrange once they involve a flight. Three of them are hard to replace.

Scoping workshops happen on site

In your offices, with the people who execute the process. We look at the actual workbooks, the actual contracts, the actual chasing letters. The unwritten rules — the ones that derail projects — surface through observation, rarely through questioning.

Acceptance runs with your users

The acceptance script is executed in your offices, on your machines, with your anonymised data. Remote acceptance catches functional defects but misses usage friction, which is the leading cause of a tool being rejected.

Someone can be there in thirty minutes

When a decision is blocking a batch, settling it takes an hour on site rather than a slot found three weeks later. On a project running in two-week sprints, that gap is paid directly in schedule.

The rest of the work — development, code review, end-of-sprint demos, fixes — happens remotely, as it does everywhere. We do not claim that proximity improves the quality of the code. It improves the quality of what we understand about your business, and that is where management projects are won or lost.

The regional economy we work with

The Lyon area concentrates exactly the kind of company we serve: mid-sized organisations with specific business processes and rarely an IT department sized to lead a rebuild.

  • Industrial small and mid-sized firms whose production, job tracking or after-sales processes live in an ageing ERP topped up with spreadsheets.
  • Buying groups, central purchasing bodies, cooperatives and member networks whose supplier approval and rebate calculations rest on a few workbooks and two people.
  • Refrigeration, air conditioning, HVAC and professional kitchen businesses — a sector whose approval and rebate mechanics we know from having delivered a full platform into it.
  • Food processing, with its traceability, batch and documentary control constraints.
  • Specialist retail and franchise networks, with revenue reporting per outlet and periodic closings.

The common factor is not the sector but the situation: a critical process carried by a tool that is no longer sustainable, and nobody in-house whose actual job is to lead the rebuild. The trigger is almost always the same — a retirement, a disputed amount, a vendor who no longer answers.

Where we travel

CityWhat the distance allows
LyonWorkshops, acceptance and steering meetings on site, on demand
VilleurbanneSame as Lyon: same-day attendance where needed
Bourg-en-BresseOn-site workshops and acceptance, there and back in a day
Saint-ÉtienneOn-site workshops and acceptance, there and back in a day
GrenobleOn-site workshops and acceptance, there and back in a day
ValenceOn-site workshops and acceptance, there and back in a day
AnnecyOn-site workshops and acceptance, a full day on site
Clermont-FerrandWorkshops grouped into a full day, planned in advance
The criterion is not mileage but whether we can turn up without the trip becoming an event to be negotiated.

How a project starts here

  1. A thirty-minute discovery call

    By video, to say plainly whether your need fits what we do. We decline when the subject calls for a standard off-the-shelf package — payroll, general accounting — rather than custom development.

  2. A first meeting in your offices

    To see the tool in place and the people using it. That is how we size the scoping phase, and how you judge who you would be working with for several months.

  3. Three weeks of scoping and prototyping

    Two on-site workshops, a working prototype of your priority use case, a firm quote for the full build. €6,000 to €10,000 excluding VAT depending on scope, deducted in full from the fixed price if the project proceeds.

  4. The fixed-price project, in batches

    Two-week sprints with a demo, contractual milestones with formal acceptance and a signed report, gradual go-live, then maintenance. The source code is handed over to you.

And outside the region?

We work outside Rhône-Alpes when the project warrants it, and part of the exchange happens remotely in any case. The rule we apply is simple: if the schedule allows the scoping workshops and acceptance sessions to be held in person, distance is not an obstacle. If it means replacing those moments with video calls, we say so before signing rather than discover it at the third batch.

MEKANO is led by its founder, Chrys Vlachou, who personally handles scoping and project direction on every engagement. A project team is assembled for each build — project manager, back-end development, front-end development — and named in the contract. You know who is working on your application, and there is no account manager standing between you and the team.

Frequently asked questions

Do we need to be in the Rhône-Alpes region to work with you?
No. We work outside the region when the project warrants it, and most development happens remotely in any case. Our only requirement is being able to hold the scoping workshops and acceptance sessions in person: those are the moments where the business is understood and usage friction is caught. Where distance makes those meetings unlikely, we say so before signing rather than discover it mid-project.
Do you travel throughout the project or only during scoping?
At the two points that justify it: scoping and milestone acceptance. In between, two-week sprints are steered by video, each closing with a demo of the running software. In practice, on a six-month project in the Lyon area, that means being on site every four to six weeks, plus ad-hoc visits when a decision is blocking a batch.
Do you only work with buying groups?
No, though it is our most documented ground. We also work with industrial small and mid-sized firms, food processing and specialist retail. What our projects share is not the client's legal form but the situation: a critical management process carried by an exhausted tool or by spreadsheets, and no in-house team whose actual job is to lead the rebuild.
Can you take over an application built by another supplier?
It depends on one thing: what you actually hold. With the source code, operating documentation and reproducible infrastructure, taking over is feasible and we start with an audit before committing to anything. Without a written assignment of rights, or with a dependency on the previous supplier's proprietary component, taking over is legally or technically impossible, and the question becomes one of gradual replacement.
What budget should we plan for a first management application?
The entry offer — scoping, prototype and a firm quote in three weeks — costs €6,000 to €10,000 excluding VAT depending on scope, and is deducted from the fixed price if the project goes ahead. For the build itself we do not publish a generic range: it would be wrong in both directions. The quote issued after the three weeks is firm, cut into batches, and you remain free to fund only the first one.

Let's talk about your situation

Thirty minutes, no commitment. You leave with a straight answer on feasibility, a budget order of magnitude and the next steps.

Book the call