Website and web app development in Labège
From brochure site to business tool. Labège concentrates technology companies, software vendors and demanding engineering teams. Here the subject often goes beyond presentation: it is about interfaces, data, integrations and code that will still need maintaining in three years.
And anywhere else, remotely
The projects I take on
Three kinds of need, from the simplest to the most technical.
Product or corporate site
Explaining a technical offer to decision-makers who are not all engineers, without caricaturing the product or drowning the reader.
Application interface
Dashboards, client portals, back-offices: dense screens that must stay legible and fast to use every day.
Custom development
Internal tool, automation, connection to an API or an existing system. For when off-the-shelf products do not match the real need.
What matters when the project is technical
Four requirements I hold myself to on this kind of work.
-
01
Code someone else can take over
The project is versioned and structured so another team can pick it up. You do not depend on me indefinitely.
-
02
Measured performance
Core Web Vitals, page weight, network requests: what is not measured is not under control. The figures are verifiable.
-
03
Genuine accessibility
Keyboard navigation, sufficient contrast, semantic structure. An increasingly firm requirement for large accounts and public bodies.
-
04
Sound foundations
Prepared statements, input validation, session handling, HTTPS everywhere. The minimum, but applied systematically.
Recent work
Real projects, delivered and live.
The method on a technical project
Frame before coding, deliver in increments.
-
1
Scoping
We define the functional perimeter and identify what is essential at launch, as opposed to what can wait.
-
2
Written specification
A short but precise document: screens, data, business rules, edge cases. It is the reference throughout.
-
3
Wireframes
Key screens are drawn and approved before development. Fixing a mockup costs infinitely less than fixing code.
-
4
Iterative development
Regular deliveries to a staging environment, so adjustments happen along the way rather than at the end.
-
5
Acceptance and release
Functional testing, performance checks, switchover and full handover of code and access.
FAQ: Labège
Your most common questions
Tell me about your situation: I reply personally within 48 hours.
Contact meYes. Labège is part of my immediate area from Toulouse, and technical projects run very well remotely: regular progress reviews and a staging environment available at all times.
Yes, for interfaces that warrant it: dashboards, applications with complex state, highly interactive screens. For a content site, a lighter approach gives better results in both performance and search.
Yes, provided we start by reading the existing code. I would rather say honestly that a codebase is too degraded to continue than pile fixes onto unstable foundations.
Yes, entirely, on delivery. You get the repository, the access and the documentation another team would need to take over.
Custom development starts at €2,500, but the price depends entirely on the functional scope. The initial scoping exists precisely to price it seriously rather than by guesswork.
Around Labège
A technical project in Labège?
Describe the need and I will tell you honestly whether I am the right person. Quote within 48 hours.
I reply personally, within 48h.