Skip to content
Spark
Writing

Security and data

A bespoke system is as secure as its builder’s answers to eight questions

A bespoke system can be as secure as anything you buy, but only if the people building it can answer eight plain questions well. Here they are, from where your data lives to what happens with AI, with what a good answer sounds like.

By Seb Lawson · 6 November 2026 · 5 min read

A bespoke system can be every bit as secure as software you buy off the shelf, and often more so, because it holds only the data you need and only your people can get in. But that depends entirely on how it’s built and run. Before you let anyone build yours, ask them the eight questions below. A careful builder will answer each one plainly, in writing, and won’t mind being asked.

Know exactly where your data will live

Ask: where will the system be hosted, and where will our data be stored?

A good answer names names: the provider, the country or region, and every other service that sees any of your data. Often the best place for your documents and records is the Microsoft 365 or Google Workspace account you already have, under controls you already run. Anything the builder hosts for you should sit with an established cloud provider in a location you’ve agreed, written down before building starts.

For Jersey businesses this ties into data protection. If personal data leaves the island, you need to know where it goes and on what terms. We cover that in the Data Protection (Jersey) Law and your systems. A vague answer, such as “it’s in the cloud”, is a warning sign.

Backups only count if someone has tested a restore

Ask: how is it backed up, and when did you last restore a backup to check it worked?

A backup nobody has ever restored is only a hope. You want to hear how often the data is backed up, how long copies are kept, that they’re stored separately from the live system, and that restores are tested on a schedule. Also ask how long it would take to get you working again if the live system were lost. A good answer gives a frequency, a retention period and a date, and those details belong in your agreement.

Each person should see only what their job needs

Ask: who can see and change what inside the system?

Your engineers need their jobs and their customers’ addresses. They have no reason to see payroll or the partners’ notes. A good system gives each person a role that decides what they can see and change, set up to match how your team actually works, and you decide who has which role. Ask what happens when someone leaves. The answer you want is that switching off one account removes their access to everything, the same day.

Your team should sign in with the accounts they already have

Ask: can we use single sign-on with our Microsoft or Google accounts, with multi-factor sign-in?

Your team shouldn’t need yet another password. A well-built system lets people sign in with the work accounts you already manage, through Microsoft Entra ID for Microsoft 365 or through Google Workspace, so your existing multi-factor sign-in applies. Stolen and reused passwords are one of the commonest ways into a business’s systems. With multi-factor sign-in on, a password alone won’t get anyone in, and with single sign-on there’s one account to switch off when someone leaves.

Data should be encrypted while it moves and where it’s stored

Ask: is our data encrypted in transit and at rest, including the backups?

Encryption in transit scrambles data as it travels between your browser and the system, so it can’t be read along the way. Encryption at rest scrambles it where it’s stored, so a copied disk or backup is useless to whoever has it. Both should be a straight yes. Also ask where the passwords and keys for your connected tools, such as your Xero connection, are kept. They should sit in a secure store that only the system can read, never in a spreadsheet or an email.

Every important change should leave a trail

Ask: can we see who did what, and when?

An audit trail records the changes that matter: who created a record, who changed a price, who approved an invoice, who deleted a file. Ask what gets logged, how long logs are kept, and whether you can search and export them yourselves. For regulated firms, this is how you show an auditor or reviewer how the work was done. For everyone else, it settles “who changed this?” in a minute.

You should know who at the builder can see your data

Ask: who at your company can see our data, and how do we know?

People forget this one. The builder needs some access to build, fix and support the system. A good answer names a small number of people, explains why each needs access, confirms that every access is logged, and says access is removed when they no longer need it. They should sign a confidentiality agreement before seeing anything sensitive, and you should have a data processing agreement setting out what they can do with personal data on your behalf. We sign both before we see anything sensitive.

Ask too what happens to that access if you part company. It should end, and you should be able to end it yourself. There’s more on that in owning your system.

You should know what the AI sees and who checks it

Ask: where does the system use AI, what data does it see, and is that data used to train anyone’s model?

If the system uses AI to draft, summarise or sort, the builder should tell you which provider, which data each step can see and what the provider’s terms say about training. Business terms from the major AI providers generally don’t use your inputs to train their models, but the builder should have checked the specific terms for each tool and written down what they found. Very sensitive data can be kept out of AI steps altogether.

Then ask who checks the output. The answer you want is that a named person in your team approves anything that matters before it reaches a client.

Ask about practices as well as certificates

Some builders hold certifications such as Cyber Essentials or ISO 27001, and they’re worth asking about. A certificate tells you a process was in place when someone checked. The eight answers above tell you how your system will be built and run day to day. If your risk calls for it, you can also have an independent specialist test the system before it goes live and give you the report.

Our recommendation: get the answers in writing before you sign

Put these eight questions to anyone who wants to build your system, including us. Ask for the answers in writing, and make the important ones, such as backups, access and where data lives, part of the agreement. A builder who answers clearly and specifically is far more likely to build carefully.

If you’d like to ask us the eight questions directly, book a review. It’s a free 30-minute call with Mark, our CTO, or me, and we’ll answer each one for the system you have in mind.

Let’s map how your business works

A free 30-minute call with Seb or Mark. Bring the spreadsheet you hate most and we’ll tell you honestly whether a system would fix it.