nine services
What we run for you.
Most of these we run for you month to month, and some can also be bought as a scoped piece of work. We report on each of them every month, including what we got wrong.
What running each service involves.
Each service has a page of its own, and this is the short version: what the work covers and what we report on every month.
AI Adoption & Data Strategy
We look at the data underneath first, then build one thing with AI and measure whether it works.
- Runs on
- What we take on
- We turn the AI question into one task somebody does every week.
- We check whether the data behind it exists, has an owner and agrees across systems.
- We build the platform in your own tenant, on Databricks.
- We set who may read which table, and trace every figure to its source.
- Your board pack and any assistant read the same governed figures.
- We fix permissions before anything is allowed to retrieve on your behalf.
- We measure answers on questions we did not choose.
- Every month
- We report the task before and after, measured against its baseline.
Data Platform & Analytics
We build the place your figures live, with one catalogue deciding who may read them and reporting built on the same tables.
- Runs on
- What we take on
- We deploy Databricks into your own network, not a default workspace.
- Unity Catalog decides what each person and each tool may read.
- We record lineage, so every figure can be traced to its source.
- We get each key definition agreed once and attach it to the table.
- Power BI reads the same governed tables as everything else.
- Rules that reject a bad row are written where everybody can see them.
- The same pattern runs on Azure, AWS or Google Cloud.
- Every month
- We report platform spend by team and any change to the catalogue.
Cloud Strategy & Design
We work out what should move, decide which platform each workload belongs on, and write the design you keep.
- Runs on
- What we take on
- We map your estate from the live platforms, because old diagrams are rarely current.
- Some workloads stay exactly where they are, and we say which and why.
- We assess an AWS or Google Cloud estate you inherited on its merits.
- We lay out accounts, networking and identity so every cost traces to a team.
- We agree how much data you can afford to lose, and design to it.
- We work out what it will cost to run while it is still a design.
- You can edit every document yourself, whether or not we build it.
- Every month
- We report the decisions taken and the ones still waiting on you.
Migration & Modernisation
We move servers, files and line-of-business systems on a written plan, rehearse it before a dated cutover and keep a way back.
- Runs on
- A migration runs on both platforms at once, the one you are leaving and the one you are moving to.
- What we take on
- We move servers and the systems your people use every day.
- Shared drives keep their permissions when they move.
- Mailboxes can move between tenants as well, after a merger or a sale.
- Where a platform service can replace a server, we say so before the move.
- Some things should not move yet, and we will tell you which.
- Every month
- We report what has moved and what is still to go.
Managed IT & Cloud Operations
We run the estate day to day, from the laptops to the cloud, with an assigned Solutions Architect and support staff.
- Runs on
- What we take on
- One support route connects you with the staff assigned to your account.
- We enrol your Windows and macOS devices in Intune and encrypt them, and you can reach the recovery keys yourself.
- We patch on a ring schedule and report on each device separately.
- We open and close accounts on a written joiners, movers and leavers process.
- We monitor and patch whatever still runs on your premises.
- We write your estate down and keep the documents current.
- Every change is logged and approved by someone named on your side.
- Every month
- Each month we report every ticket, and we list the ones we missed.
Cloud Cost Control
We read the bill line by line, and most of the saving comes from what gets switched off.
- Runs on
- What we take on
- We tag every resource to a team, so the bill can be split by who caused it.
- We find resources with no owner, such as disks with no machine attached and projects that have finished.
- We resize machines to match the load they carry today.
- We schedule test environments to switch off outside working hours.
- We set retention periods, so old backups and logs are deleted on a schedule.
- We use the licences you already own before buying any commitment.
- Every saving we report can be checked on your own invoice the following month.
- Every month
- Each month we report every rise in spend and what we switched off.
Automation & Platform Engineering
When somebody does the same job every week, we write it down once and have it run, so nobody types it again.
- Runs on
- What we take on
- A new starter gets their account, groups, mailbox and licence from one request.
- Leavers lose access on the day, with what they held recorded first.
- We run changes across hundreds of accounts from one checked list.
- Approvals go to a named person, and each decision is recorded.
- We define environments in Bicep or Terraform, so they can be rebuilt from the same files.
- Every deployment goes through a reviewed pipeline in Azure DevOps or GitHub.
- We give each Power Platform flow a named owner and bring it under a written policy.
- Every month
- We report what ran, what it changed and where it stopped.
Cyber Security & Resilience
We harden and patch your systems, review who has access, and run restores and write each one up.
- Runs on
- What we take on
- We put multi-factor authentication on every account and turn off the older sign-in methods that get round it.
- We install endpoint protection and make sure a person reads its alerts.
- We find any machine that is not managed, then report patching for every device.
- We restore a real file and mailbox item on a schedule, and report the result.
- We review who has access to what, and record the date of every change.
- We set up phishing filters, block automatic forwarding to outside addresses, and publish the domain records that make your email harder to spoof.
- We work through the Cyber Essentials questions with you before an assessor does.
- We write an incident plan with you that says who does what and who gets called.
- Every month
- We report patch status for every device and every change to who has access.
Microsoft 365 & Devices
We take your tenancy, identity and licensing past the defaults, and look after the laptops people work on.
- Runs on
- What we take on
- We review every tenant setting and change the defaults that do not suit you.
- We write access policies that name what they block, with a documented emergency account.
- We match each licence to what the person uses, and take it back when they leave.
- We lock down mail flow and remove rules that forward your mail outside the business.
- We agree the sharing rules, and name an owner for every team and site before they multiply.
- We back up your data separately, and test the restore.
- The tenant and its admin credentials stay registered to you.
- Every month
- We check the licences you pay for against the people using them, leavers included.
A service or a solution? They are different purchases.
A service is something we run for you from month to month. A solution is a piece of work with an end date. They are priced and reported differently, so it is worth knowing which one you are asking for.
A service
It carries on until you decide to stop it.
- You are retaining us to run something, month after month.
- It is charged monthly and it appears in every monthly report.
- Stopping it means going back to whatever you did before.
Most of what is listed above is bought this way.
A solution
It has a start, an end and a written list of what it needs.
- You are paying for a change, and at the end you keep what was built.
- It is scoped and quoted once, against a written dependency list.
- When the work is finished, we say so and the engagement ends.
Most people who come to us need one of each: a solution for the thing that prompted the call, and a service so it does not happen again. We will tell you which to start with.
Not sure which of these you actually need?
Most people are not sure when they first get in touch. Working it out with you is what the first half hour of the conversation is for.
Contact us