A foundation wants to retire its legacy system and move to Microsoft 365. An association with 30 staff needs someone to pick up the phone when the printer jams or an account is locked. A company has a website nobody wants to touch any more. And an organisation has heard from all sides that it now has to “do something with AI”, without knowing what.
These are four different jobs. They still share a cause: there is no IT department, or it consists of one person whose actual job is something else. That is why we solve them with the same pattern.
Advise: understand first, then recommend
We start by taking stock. Which systems exist, who uses them for what, and which of them work fine and are merely unloved? For the foundation with the legacy system this means reviewing the data, settling access rights per project and deciding what moves across and what gets archived.
With AI this step matters even more. Most organisations do not need a twenty-page strategy but two or three concrete places where a tool noticeably takes work off people’s hands: drafting grant applications, answering recurring enquiries, summarising minutes. Which of these pays off, and what the legal requirements are, we settle before anyone buys a licence.
Sometimes the recommendation is to buy nothing new and set up what is already there properly.
Implement: fitted, not off the shelf
Implementation follows from what the assessment found, not from a standard package. A Microsoft 365 environment for a foundation with changing project teams and volunteers looks different from one for an office with permanent staff. A website for an organisation that mainly raises donations needs different priorities from one that explains advisory services.
The same goes for AI. Often it is enough to introduce an existing tool properly and train the team. Where that falls short, we build our own assistants that draw on the organisation’s knowledge. How such a system is put together is described in Three parts of an AI assistant.
Operate: after the project comes everyday work
This is where a project proves itself. A freshly migrated environment without patch management, backups and a named contact is a legacy system again within a year.
So we stay after the rollout: with updates, backup routines, user management and first-level support that takes requests, documents them and resolves them. Which ticket system we use for that, and why, is covered in Four ticket systems in practice.
The benefit for you: whoever runs the environment also built it and knows its quirks. Nobody has to get up to speed while something is on fire.
Why it all comes from one team
You can buy advice, implementation and operations from three different providers. Then someone advises who does not have to live with the consequences, and someone runs the systems who did not make the decisions. The knowledge of why something was set up the way it was erodes a little at every handover.
With us it stays in one team. That makes recommendations more careful, because we will be supporting them later, and operations cheaper, because there is no handover to pay for.
When you do not need us
If you have an IT department of your own that does its job well, we complement it on specialist topics at most. If you just want a single device set up once, the computer shop around the corner is faster. And if you need a three-page website that will never change again, a site builder is the more honest answer.
We fit best with organisations that need IT but have no people of their own for it. Whether that applies to you can be settled in a short, no-obligation call.