How we work.

The first meeting is usually a conversation, not a presentation. Masroor will be in the room. We want to understand the business before we understand the infrastructure — who depends on what, what's business-critical, where the real pain is.

We ask about the last thing that broke and how long it took to fix. We ask about vendors currently in the relationship and whether there's a reason they're there. We ask about the team — who calls IT when something goes wrong, and whether anyone is currently carrying undocumented tribal knowledge about how the systems actually run.

We don't bring a deck. We bring questions. The difference matters: a deck is a pitch, a conversation is a diagnosis. You can't do good work without a diagnosis.

Sometimes the conversation ends with us recommending a different firm or telling a client they don't actually need what they think they need. That's a feature, not a bug.

If the first conversation goes well, we propose a structured assessment. This is a paid engagement, typically two to four weeks depending on the size and complexity of the organisation. At the end, you receive a written document — usually fifteen to twenty pages — that describes what you have, what's working, what isn't, and what we'd recommend and in what order.

The assessment is not a sales document. We don't include pricing, and we don't include urgency that isn't real. We've delivered assessments that told clients their current setup was mostly fine and needed targeted improvement, not replacement. That's frequently disappointing for clients who came expecting a big project. We don't manufacture urgency.

The document is yours regardless of whether you proceed with us. If you take it to another firm, we consider that a fair outcome. The goal is to give you accurate information, and accurate information is useful whoever acts on it.

Most clients who commission an assessment proceed to an engagement. But the assessment stands alone. That's by design.

We work on annual maintenance contracts. Not because it's the most profitable structure for us — in many cases it isn't — but because it's the right structure for what we actually do. Reactive IT is expensive for the client and exhausting for the provider. Annual contracts let us plan, maintain, and improve rather than respond and invoice.

The AMC covers a defined scope: on-site support, remote monitoring and response, patch management, backup validation, vendor coordination, and a fixed number of engineer hours per month. Everything else is quoted separately, transparently, and with your sign-off before we start.

We don't have hidden charges. We don't charge for travel. We don't invoice for phone calls. We don't have a 'minimum billable' for a two-minute fix. These aren't generous terms — they're what a relationship-based business looks like when it's working correctly.

Most AMCs are twelve-month agreements with a thirty-day wind-down clause. We've never needed to invoke one.

The first ninety days of any engagement are the most intensive. We're learning the environment — not just the hardware and software, but the people, the workflows, the things that break on Sundays before a Monday trading day.

During this period we document everything. Network diagrams, vendor contacts, license keys, renewal dates, escalation paths. Most SMBs have this information spread across email threads, old staff laptops, and memory. We consolidate it into a structured runbook that lives in a format we can hand back to you if the relationship ever ends.

We also start the process of vendor consolidation — not by replacing everything with our preferred vendors, but by identifying where unnecessary complexity is adding cost and risk, and proposing simplification where it makes sense.

Year one is when most of the heavy lifting happens. By year two the relationship has compounded into something different — fewer fires, more strategy.

Our longest client relationship is now approaching fifteen years. When we ask ourselves what we've delivered in that time, the honest answer is: mostly invisible work. The servers that didn't go down. The ransomware attack that didn't succeed because the credentials were rotated three months before it was tried. The migration that happened over a long weekend without anyone losing a file.

We meet with each long-term client quarterly — not to justify the engagement, but to review the roadmap. What's coming in the next twelve months? Hardware that will need refreshing. Software that will reach end-of-life. New regulations that touch data handling. Hiring that implies infrastructure change. These conversations happen before they become emergencies.

There's a type of client that moves between IT providers every two to three years, always chasing a lower price or a new relationship. We've had those conversations. The economics rarely work out as planned: the transition costs, the knowledge loss, the period of instability during handover — they tend to exceed whatever the rate saving was. We're not the right firm for clients who want to optimise on unit cost.

We don't have a sales pipeline made of one-off projects. We have a small portfolio of long relationships. That's a deliberate choice.