(business software)
Custom business software
The tool your business is missing, built from Marseille around the way you work.
When your business runs on a spreadsheet only you know how to read, a tool is missing. I build the one that follows the way you work, rather than the other way round.
Free, no commitment. Reply within 24 working hours.
(who for)
Your
organisation
Your organisation
Four organisations where custom business software changes the working day.
Small business owner
Your data lives in several files, on several computers, and nobody knows any more which one is the reference.
Practice or agency
You pay for three subscriptions that do not talk to each other, and you retype the same information into each of them.
Service business
Quotes, scheduling, jobs, invoicing. The chain exists, but it still runs on paper, the phone and what everyone remembers.
A trade with its own rules
No off-the-shelf software fits the way you do things, so you shape your work around the tool instead of the reverse.
The
parts list
Time on the ground
I spend time with you and your teams to see how the work really happens, not how it is supposed to happen. We then set out your stages, your documents and your rules, including the ones nobody has ever written down anywhere.
Scope of the first version
We keep what saves time straight away and push the rest back. Useful software in three months beats complete software in two years, and that split is what keeps the budget in line.
Interface shaped by use
The screens use your vocabulary and your daily gestures, and each person only reaches what their role justifies. Anything that repeats identically, reminders, calculations, quotes, invoices, reports, is produced by the software instead of being redone by hand, and your figures stay current without anyone rebuilding them.
Your existing data
Your current files are imported and checked, so you start with your own history rather than an empty database. A test migration runs before the switchover, to catch duplicates and missing information while there is still time.
Training and adoption
Your teams test the screens from the design stage, and not only management: software designed with its users gets adopted, software imposed ends up next to the original spreadsheet. Training happens on their real files, and a written guide stays available for whoever joins later.
Built to evolve, and yours
Adding a stage or a field six months later does not mean rebuilding everything. Hosting is in Europe, access encrypted, daily backups tested. The code belongs to you and you have an up-to-date copy from delivery.
(process)
The
assembly
The assembly
From immersion in your organisation to go-live, module by module.
- Stage 01 // Within 48 hours
First conversation
You describe your business and what is costing you time. I tell you whether custom software is the right answer, or whether an existing tool would do.
- Format
- Video or phone · 30 min
- Answer
- Custom or off-the-shelf
- Stage 02 // 1 to 2 weeks
Immersion and scoping
I observe how you work, on site or remotely, write down what the software has to do and price each module separately.
- On site
- In person or remote
- Price
- Priced module by module
- Stage 03 // 2 weeks
Designs and approval
You and your teams test the main screens before development. This is when the edge cases nobody had mentioned come out.
- Tested by
- Your teams, not management
- Revisions
- Until you approve
- Stage 04 // 8 to 20 weeks
Build by modules
Each module ships as soon as it is usable. You start saving time before the project ends.
- Pace
- A module ships once it helps
- Included
- Data migration · tests
- Stage 05 // 2 weeks
Go-live
Data migration, training, a period of running both systems if needed, then close follow-up through the first month.
- Delivered
- Migration · training · support
- Then
- Both systems if needed
(good to know)
The
answers
The answers
Price, timing, data migration, adoption: the questions asked before starting custom software.
Not always, and I will tell you so. A market tool that covers nearly all of your need is often the right call. Custom pays off when the subscriptions pile up, when your teams spend hours retyping the same data, or when no tool can do the thing that makes you different. We put both figures side by side at scoping.
The price follows the number of modules kept for the first version, and cutting that number down is exactly what the immersion is for. Budget from 15,000 euros for a first scope that is genuinely usable, with its users, its access rights and two or three complete processes. A tool covering a whole organisation, with accounting integrations and your history migrated across, goes beyond 120,000 euros. After the immersion you receive a quote priced module by module, and you are free to push back anything that is not essential on day one.
The first useful module goes into production eight to twelve weeks after kick-off, and your teams use it while I build the rest. A complete first version takes three to six months, depending on how many processes are brought across. You never wait for the end of the project to start saving time.
Yes, in the vast majority of cases: spreadsheets, software exports, databases. I run a test migration before the switchover to spot duplicates and missing information, and you approve the result before go-live.
That is the real risk on an internal project, more than the technical side. Which is why I have the screens tested by the people who will use them, from the design stage, and not only by management. Software designed with its users gets adopted. Software imposed ends up next to the original spreadsheet.
Yes, most of the work happens remotely: first conversation, design sign-off, progress reviews and training all take place over video, and you follow the project on a preview address you can open whenever you want. I travel when the situation calls for it, particularly for time on the ground. Distance has never been the issue; responsiveness is.
Eight years of software development and cloud infrastructure, for large companies and as an independent, on systems that handle serious volume. That is what makes the difference on business software: the hard part is not the screen, it is everything behind it, access rights, data migration, scaling and backups. Devazur has existed since 2022, in Marseille.
The code belongs to you and you have an up-to-date copy from delivery, with its technical documentation. It is written with widely used technologies, which means another developer can take over. No closed formats, no dependency on me alone.
(contact)
Your
project
Your project
Describe what is costing you time today. I tell you whether custom software is the right answer, or whether an off-the-shelf tool would do.
Reply within 24 working hours. Free, no commitment.