Three weeks ago, I stopped by to see the manager of a small maintenance company, about twenty minutes from Rennes. Eight employees, a full order book, and on his desk: two screens on… and a spiral-bound notebook placed between them. The week’s interventions were written in the notebook in pen. 'The software doesn’t do it the way I want,' he told me, shrugging. So he doubles everything: once in the SaaS they sold him, once in the notebook 'to be sure.'
This manager doesn’t have a motivation problem. He has a tool problem. And that’s exactly where a business application developer can change his week—especially when they’re just around the corner.
A business tool isn’t just another piece of software
When I talk about custom business applications, people often imagine a big, expensive project reserved for large companies. In reality, it’s the opposite. It’s a tool tailored to your way of working: yours. Not thirty features you only use three of, but the three that waste two hours of your day—done right.For this maintenance manager, the real issue wasn’t 'I need software.' It was: 'I want to see, every Monday morning, who’s going where during the week, and know at a glance what hasn’t been invoiced.' No generic SaaS checked those boxes without forcing him to twist his workflow to fit their mold. A custom tool, on the other hand, starts with his notebook—not a template designed for a business that isn’t his.Why 'near Rennes' makes a difference
You might think a developer can be managed remotely from anywhere. That’s true on paper. But a business tool isn’t built by reading a requirements document: it’s built by watching someone work.
Being on-site around Rennes means I can sit in your office for an hour, watch that infamous Excel file open for real, and hear the 'oh yeah, but we never do it like that.' Those little details are what make the difference between a tool people adopt and one they abandon after a month.
Proximity, in concrete terms, gives three things:- We meet in person. A kickoff meeting at your table is worth ten video calls. You show me, I understand the ground reality, and we don’t waste three weeks on misunderstandings.
- Responsiveness.
A bug on Tuesday morning, a 'hey, we should add this'—I’m in the same time zone, the same week, reachable—no offshore hotline with ticket number 4712.
- No black box. You know who’s coding your tool; you can make me coffee while showing me the problem. It might seem trivial, but it’s what makes a project succeed.The Rennes metropolitan area is a fabric of SMEs and micro-enterprises running on jury-rigged tools because custom solutions have long seemed out of reach. A local freelancer is precisely the way to get one without the cost or bureaucracy of an agency.
A concrete example: Monday morning the week beforeLet’s go back to the maintenance company. Today, their Monday morning looks like this: they open their schedule in a software, copy the interventions into the notebook, call two technicians to confirm, and realize on Thursday that three interventions from the previous week were never invoiced. Multiply that by a year: that’s thousands of euros slipping through the cracks—not out of malice, just friction.A custom tool here could fit on three screens: the week’s schedule showing who’s going where, an intervention sheet a technician fills out from their phone after leaving the site, and an 'unbilled' list that updates automatically as soon as an intervention is marked complete. Nothing flashy. Just the end of the notebook—and the end of forgotten invoices.
This isn’t science fiction or a six-month project. It’s the kind of tool you scope in one meeting and deliver in small pieces, starting with what hurts the most.‘How much does it cost?’—the real questionLet’s be direct, because it’s the question everyone asks without daring to: yes, developing a custom tool represents a budget. But the right comparison isn’t 'custom vs. free.' It’s 'the cost of the tool vs. the cost of your current workflow'—the hours spent copying, the forgotten invoices, the errors you have to fix.
My approach boils down to three points. We start with the problem that hurts the most, not a bloated system. I give you a honest ballpark estimate from the first conversation, not a vague quote. And if, after listening to you, I realize an existing software would work just as well for much less, I’ll tell you—I’d rather have a client who comes back than a forced sale.
FAQ
Do you need to be a large company for a custom tool?
No, quite the opposite. SMEs and micro-enterprises are the ones who benefit the most from automating the two or three tasks eating up their days. We size the tool to the need, not the other way around.
How long before I have something usable?
We deliver in stages. A first version that solves the most painful problem can be up and running in a few weeks, then we expand based on real-world feedback.
I’m in Vitré, Bruz, Cesson… does it still work?
Yes. I work with companies across the entire Rennes metropolitan area and Brittany. Proximity is a plus, not a boundary—we always find the right balance between on-site meetings and remote follow-up.What if I already have software I don’t like?We first look at whether we can improve it or connect it to a small complementary tool before starting from scratch. Starting over is never the first option I propose.If you recognize yourself in the manager with the spiral notebook, the simplest thing is to talk about it. I always start with an audit of your workflow and a written action plan—you leave with something useful, even if we don’t end up working together.Discuss my projectje vous le dis — je préfère un client qui revient qu'une vente forcée.
FAQ
Faut-il être une grosse entreprise pour un outil sur mesure ?
Non, au contraire. Les TPE et PME sont celles qui gagnent le plus à automatiser les deux ou trois tâches qui grignotent leurs journées. On dimensionne l'outil au besoin, pas l'inverse.
Combien de temps avant d'avoir quelque chose d'utilisable ?
On livre par étapes. Une première version qui règle le problème le plus douloureux peut être en service en quelques semaines, puis on enrichit selon les retours du terrain.
Je suis à Vitré, Bruz, Cesson… ça marche aussi ?
Oui. Je travaille avec des entreprises de tout le bassin rennais et de Bretagne. La proximité est un plus, pas une frontière — on trouve toujours le bon mélange entre rendez-vous sur place et suivi à distance.
Et si j'ai déjà un logiciel que je n'aime pas ?
On regarde d'abord si on peut l'améliorer ou le connecter à un petit outil complémentaire avant de tout refaire. Repartir de zéro n'est jamais la première option que je propose.
Si vous vous reconnaissez dans le gérant au cahier à spirales, le plus simple est d'en parler. Je commence toujours par un audit de votre organisation et un plan d'action écrit — vous repartez avec quelque chose d'utile, même si on ne travaille pas ensemble ensuite.
