Skip to content

Guides / 8 min read

Working with a client's Windows-only tools.

It is a familiar moment. A new client sends a welcome pack, and somewhere on page three is the line: you will need access to our system, which runs on Windows. If you work on a Mac, a tablet or a lightweight laptop, you now have a small logistics problem. Handled well, it takes an afternoon. Handled badly, it eats the first week of the engagement.

Start by asking the right questions

Resist the urge to say yes and figure it out later. A few questions at the start save a great deal of trouble. Which programs exactly, and which versions? Do they hold the licence, or do I need my own? Will I connect to their network, and if so, how? Where may their files be stored?

Often the real need is smaller than the first email suggests. You might need one reporting tool and a spreadsheet, not the whole stack. Knowing that opens up lighter options.

The three ways it usually gets solved

Clients tend to offer one of these, and it helps to recognise them.

  • They give you a laptop. Simple for them, awkward for you: another device, another set of updates, and a machine to return.
  • They give you remote access to a machine on their side. Clean for them, but you depend on their setup and their support.
  • You bring your own solution. Most flexible, but you need to show it is secure enough for their data.

Why a remote Windows machine is often the easiest yes

From a client's point of view, the risk in an outside contractor is data landing on a personal device. If the program and its files live on a Windows machine that is not your laptop, much of that worry goes away. The picture reaches you, but the files stay where they are.

That makes the conversation easier. You are not asking to copy their data to your laptop. You are asking to use a tool in a way that keeps data off it, which is usually what their security person wanted anyway.

Licences and who pays for what

Settle early who holds the licence for their software. If it is theirs, they may need to add you as a user or approve remote use. If it is yours, check that its terms allow the way you plan to run it. Put the answer in your statement of work so nobody is surprised at invoice time.

Do not forget Windows itself, which your remote machine needs a valid licence for. A service that provides the machine handles that for you.

A one-page checklist

Before you start, write down the answers to these and share them with the client.

  • The programs and versions you will use.
  • Who holds each licence.
  • How you will connect, and whether a VPN is required.
  • Where client files will live, and where they will not.
  • How access ends when the engagement does.

Handing back cleanly

When the work finishes, close the loop. Remove your access, confirm no client files remain on any device you own, and tell the client in writing. It is a small courtesy that makes clients remember you well and call you again.

The Compass

Check whether the client's program is likely to work remotely before you promise it.

Written with consultants in mind.

Questions people ask.

Do I have to install the client's software on my laptop?

Not necessarily. If the program can run on a remote Windows machine and you reach it in a browser, nothing needs installing on your own device.

Will clients accept a remote machine?

Often they prefer it, because their data stays off your personal device. It is worth asking early and explaining how it works.

Who is responsible for the security of client data?

You and the client share it. Agree the rules up front: where files live, who can access them and how access ends.

The quickest answer is to try your own program.