Business platforms
From desktop to web: three generations of one system
One Qatar manpower company has run its quoting, billing and deployment on the same application through two technology generations, and is scoping a third. The workflows stayed the same. Each move changed something else.
By itmarkerz Technologies. Updated 30 October 2026.
The system
The client supplies skilled trade workers, such as masons, plumbers and electricians, to businesses that need them for a period. It bills by worker, trade and duration. The application holds customer quotes, trade-based price lists, billing and invoicing, employee records, and who is deployed to which customer. Off-the-shelf HR software rarely describes this work well, because the workforce is the product being sold.
The three generations
| First | Second | Third | |
|---|---|---|---|
| Technology | C#/.NET desktop | Electron | Web application |
| Status | Built and used | Built and used | In discussion and scoping |
| Reason | The company needed one in-house system | The environment moved on, and it had to run on current machines | Being worked through with the client |
| Workflows | Established here | Kept the same | To be reviewed in scoping |
What the Electron rebuild changed, and what it didn’t
The Electron move was a technical one with a clear purpose: the same workflows on current machines. Staff didn’t need to learn a new way of working, and that was the point. A rebuild like this is easier to judge, since “does it do what the old one did?” has a definite answer.
It also didn’t change the shape of the system. It remained an installed application. If what you want from a migration is remote access from any site, Electron alone won’t give you that. Be clear which problem you have before choosing the technology.
What moving to the web would change
This stage hasn’t been built, so these are the questions we would bring to any desktop-to-web scoping, this one included.
| Topic | On the desktop | On the web |
|---|---|---|
| Access | Where it is installed | Anywhere you allow, so sign-in and permissions become central |
| Updates | Each machine, or an updater | One release for everyone |
| Hosting and backups | Often an office server or machine | Someone must run, back up and monitor a server |
| Internet outage | May keep working on the local network | Stops, unless you design for it |
| Printing | Direct to office printers | Through the browser, so check quotes and invoice layouts early |
| Security exposure | Mostly inside the building | On the internet, so employee records need more care |
| Concurrent use | Often assumes a small, known group | Must handle two people editing one quote |
What outlasts the technology
- The data. Customers, price lists, employees and deployment history carry on through each generation. Plan the move around them, and check them for gaps early.
- The rules. How a quote is priced by trade, and how a deployment becomes an invoice, are the system’s real value. Write them down and turn them into tests during the move.
- The relationship. We have worked with this client across generations of the system, and knowing why it behaves as it does makes scoping far more reliable.
If you are comparing a replacement with a product, the reasoning in custom ERP or off-the-shelf applies here too.
The system described here
Labour-supply quoting, trade-based pricing, billing, employee records and deployment tracking for a Qatar manpower company placing skilled trade workers with clients. Built in C#/.NET, rebuilt in Electron, now being scoped for the web.
- Sector
- HR, staffing & manpower
- Region
- Qatar
- Stack
- C#/.NET, Electron
- Engagement
- Long-term client, two generations of one system
Questions
Has the web version been built?
No. We built the C#/.NET application and the Electron rebuild. The web move is being scoped with the client, so what follows on that stage is our thinking about the decision, not a report of the result.
Is Electron a good step, or should we go straight to web?
It depends on why you are moving. Electron suits a business that needs the same desktop workflow on current machines. If you need access from several sites, or want to stop managing installations, the web answers that and Electron doesn't.
Could you take over a desktop application we didn't build?
Yes, if the source code and a copy of the data are available. The first step would be reading both and listing what the application really does, because old desktop systems often hold rules nobody has written down.
More on business platforms
- Rental software: build or buy? What two custom builds taught usA decision table and a requirements checklist you can brief anyone with.
- Rate cards, availability and utilisation: the hard parts of rental softwareThe three calculations that decide whether a rental system can be trusted.
- Vehicle rental software: deposits, fines and handoverWhere vehicle hire differs from equipment hire, and what to build for it.
- Custom ERP or off-the-shelf for a wholesaler?How to decide, from a two-year ERP we built, including how old that build is.
Still running the business on a desktop application?
Tell us what it does, what it runs on and why you are thinking of moving it. We will help you work out which move, if any, solves the problem.
We reply within one business day (IST).