Everything useful is on the machine by the window
Your main program was installed on office PCs years ago. It talks to a database on a server in the back room. It works fine for anyone sitting at a desk in the building.
For everyone else it is a problem. Sales staff on the road phone the office to check stock. The manager works from home on Fridays by remote-controlling their office PC, which has to be left switched on. When the one machine that everyone remotes into restarts for updates, half the team is locked out until someone drives in.
You have tried a couple of fixes. Remote desktop tools were slow and clunky. A VPN helped until the program started timing out over home broadband.
Why the obvious fixes disappoint
Most older desktop programs were written assuming a fast, reliable network between the PC and the database. They make many small requests for every screen. Over an office network that is invisible. Over a VPN from a kitchen table it turns every click into a pause, and a dropped connection mid-save can leave a record half written.
Remote control of individual office PCs avoids that, but it ties each remote worker to a physical machine, leaves those machines running and exposed, and scales badly. It was a stopgap that became permanent.
The root cause is that the program was built for one building. The fix has to either bring the building to the user, properly, or bring the data to a browser.
The daily cost of office-only software
- Calls into the office for information staff could look up themselves
- Work that waits until someone is back at their desk
- Office PCs left on and reachable from outside, which is a security worry
- Hiring limited to people who can commute to where the software lives
- Business continuity tied to one building's power and internet
None of these show up as a line on the accounts. They show up as slower quotes, longer days and customers who wait for an answer.
How we open it up
We normally work in two stages, so the immediate pain goes away before any rebuilding starts.
| Stage | What we set up | Good for |
|---|---|---|
| Publish the program | The existing app runs on a hosted server (for example Azure Virtual Desktop or Windows Remote Desktop Services) next to its database, and users open just that app from anywhere | Everyone needing the full program, straight away |
| Add a web layer | An API over the program's database plus a small browser app for the most common tasks | Mobile staff, quick lookups, simple updates |
| Replace in pieces | Rebuild remaining screens as web pages over time, if and when it is worth it | Retiring the desktop program eventually |
- We check licensing first. Some software licences restrict hosted or multi-user use, and that needs clearing with the vendor where one still exists.
- We move the database and program onto the same hosted network, so the chatty traffic stays local and only screen updates travel to the user.
- Access goes through proper sign-in with multi-factor authentication, not open ports on office PCs.
- We then look at which tasks remote staff do most, such as checking stock, looking up a customer or logging a visit, and build those as browser or phone screens reading the same data.
What working day looks like after
A salesperson in a customer's car park opens a browser, checks stock and price, and answers the question there and then. The office manager works from home without leaving their desktop humming. If the office loses power, the business keeps running because the program is no longer in the office.
Nobody had to relearn the main program on day one, because the full version still looks the same. The new web screens simply take the simplest jobs off it.
The office PCs can finally be switched off at night. Remote access runs through one controlled route with proper sign-in, rather than a handful of machines each reachable in its own way, which makes the setup far easier to reason about when someone asks how secure it is.
Checklist: is this you?
- Your main business software only runs on office PCs
- Remote staff remote-control a specific office machine
- The program times out or freezes over a VPN
- People phone the office for information they could look up
- Office PCs are left on so staff can reach them from home
- Losing the office internet would stop the business