Custom web application development in Besançon, France
A shared spreadsheet nobody dares edit any more, an off-the-shelf tool that imposes its own rules, three systems that will not talk to each other: at some point the process costs more than the tool meant to carry it. A bespoke application starts from the way you actually work rather than the other way round. I design and build it in Vue.js and Nuxt, with an interface your teams pick up without a three-day training course, and an architecture that takes on new uses without everything needing a rewrite.
Custom web application development
Bespoke web applications: fast, scalable and designed around the way your business actually works.
Key benefits
- Modern architecture (Vue, Nuxt)
- Fast, intuitive interface
- Security and scalability
- API & payment integrations
Expected outcomes
Who this is for
- Small companies running an entire operation from shared files that have become unmanageable
- Businesses whose off-the-shelf software forces daily workarounds
- Founders who need to validate an idea with a solid first version
- Organisations that want to open a client portal or a dashboard to their users
Does your need look more like this?
How a project unfolds
Functional scoping
We start from your real processes, not from a feature list. I map out the journeys, the screens and the business rules, and flag along the way what deserves simplifying before it gets coded. Free quote within 48 hours.
Screen mockups
The key screens are mocked up and signed off before development. This is where we decide what belongs in the first version and what can wait: an application that ships too late helps nobody.
Iterative development
I deliver in functional batches you can try as they land, rather than discovering everything at the end. Accounts, roles and access rights are part of the build.
User acceptance
Your teams test the application on real cases before it opens up. The adjustments from this phase are budgeted for, because they are what separates a tool people use from a tool people work around.
Go-live and follow-up
Deployment, technical documentation and support through the first weeks. Later changes are handled as they come or in batches, at whatever pace suits you.
Included in the engagement
- Functional scoping and mapping of user journeys
- A bespoke interface, designed around how you work
- Development in Vue.js and Nuxt, with accounts, roles and access rights
- The integrations you need: third-party APIs, online payments, exports
- A user acceptance phase before go-live
- Technical documentation and deployment
Not included
- Hosting and third-party subscriptions, taken out in your name
- Manual data migration from a legacy tool, quoted by volume
- Day-to-day user support, which belongs to a maintenance agreement
- Writing the business content displayed inside the application
Frequently asked questions
How much does a custom web application cost?
Unlike a marketing website, an application cannot be priced off a catalogue: the figure depends on the number of screens, the business rules and the integrations. That is precisely what scoping is for. It produces a free, itemised quote within 48 hours, which you remain free not to act on.
How long does it take to build an application?
Allow 6 to 12 weeks for a first version usable in real conditions. Iterative development gives you something to try well before the end: you do not discover the application on delivery day.
Do you build mobile applications too?
Yes. Depending on the use case I build either a web application that works properly on mobile, or an application distributed through the App Store and Google Play. The choice is made during scoping: store distribution adds review and update constraints that are not worth it for every project.
Who owns the application code?
You do, entirely, on delivery. The repository is transferred to you and you can hand future work to whoever you like. I do not work with proprietary code that would tie you to me.
Will I be able to extend the application later?
That is what the initial scoping is for: the architecture is designed so that adding a module does not mean starting over. Later changes are then handled as they come or in batches, according to your priorities and budget.
Who handles hosting and maintenance?
Hosting is taken out in your name, with a provider we choose together, so you keep control of it. I handle configuration and deployment. Beyond that, a maintenance agreement can cover updates and support, or we work on demand.
