Case and job tracking
Every file with its status, history and documents. Everyone sees the same thing at the same time.
A shared file that has become unmanageable, software that does not quite do the job: I build the tool that matches how you actually work — case tracking, scheduling, orders, client portals, back-office.
Applications that run in a browser, reachable from any machine, with nothing to install.
Every file with its status, history and documents. Everyone sees the same thing at the same time.
Who does what, when and where — with last-minute changes handled without rebuilding the table.
From request to final document, with the prices, discounts and approvals that follow your rules.
Your clients check their own information instead of calling. Each one sees only their own data.
The screen your team runs the business from: search, edit, and access rights per role.
Your data carried over as-is, into a tool that prevents entry mistakes and handles several users at once.
Your invoicing software, your shop, your files: the tool plugs into them rather than replacing them.
An application someone else built, now fragile or unmaintained? I can take it over.
A spreadsheet is an excellent starting point. Here is how you know it has hit its limit.
Several people work on the same file and you have already lost changes.
There is an "up to date" version of the file that not everyone actually has.
An entry mistake can go unnoticed and reach a client.
You would like to give clients access to part of the information, but not to the whole file.
You cannot easily tell who changed what, or when.
Your current software does 80% of the job, and the remaining 20% happens by hand alongside it.
What the tool does, what it does not, who for, and in what order we build it.
The first version covers the heart of the need, not the full list of ideas.
You use the tool before the project ends, with your real data.
Setup, a walkthrough, then changes driven by real day-to-day use.
Three projects where a specific business need became a tool people use daily.
A platform where each hotel gets its own space, colours and rules, from a single application.
An extranet giving every partner access to their own files, without ever seeing anyone else’s.
A client portal that makes each client’s equipment status readable at a glance.
A first genuinely usable version starts around €5,000. The budget then varies with the number of screens, the number of users and the connections to your existing tools. Anything larger gets a quote after scoping — I do not give a figure before understanding what the tool has to do.
Expect several weeks for a first usable version. I would rather ship a tool that covers the core well and grow it, than make you wait six months for a complete one.
Yes, and that is nearly always the starting point. Your existing data is carried over as it is: you do not start from an empty database.
Yes, and it is a common use. Each person sees only what concerns them: your team sees everything, each client sees only their own information.
No. The tool opens in a browser, on a computer, tablet or phone. Nothing to install on machines and nothing to update by hand.
You own the code, the accounts and the data. The tool is documented so another developer can pick it up. Your business must not depend on my availability.
Describe how you work today and what slows you down. I reply personally, usually within 24 hours.