Inside fully managed and co-managed IT
Boutique means you get known, not processed.
It is the part of how we work that does not fit neatly on a list of services, so it gets its own page. Every client is looked after by the same small pod of technicians, which means nobody starts a support call by explaining who you are.
The call this replaces
You spend longer describing the problem than it takes to fix it.
You ring about the printer at the front desk. Whoever answers has never heard of your front desk, so first you describe the printer, then the network it sits on, then the fact that nobody can take a payment while it is down. By the time all of that is out, the morning has gone.
Next week a different person answers and you do the whole thing again. Not because anyone is careless, but because the model is built to move tickets rather than to know businesses.
Boutique support is the decision not to run that way.
What it means here
Three things your pod already knows before you call.
Your people
Who is asking, and what that costs
They learn your staff by name and by habit. Who travels, who needs a hand, who will have already tried three things before picking up the phone.
That is the difference between a ticket marked normal and one that quietly stops your business taking money.
Your systems
How the pieces actually fit together
They know your setup because they documented it, not because they are working it out live while you wait on the line.
No rediscovery, no guessing which of your four things is the one that broke.
Your history
What happened last time
They remember the thing that went wrong in March. When something similar starts in September, somebody recognises the pattern.
Recurring problems get asked about rather than fixed four times.
Personal, without being fragile
One person who knows you is a risk. A pod that knows you is not.
A single IT person, whether yours or ours, is a wonderful thing right up until they are on holiday, on another call, or looking at something outside what they do best. That is the trap most small providers fall into, and it is why familiar support has a reputation for being thin.
Your pod is a group rather than a name, and the wider team sits behind it. The relationship holds when somebody is away, and the depth is there when a problem turns out to be bigger than a printer.
- The same familiar faces on the day to day
- Cover through holidays, illness and busy weeks
- Specialist help when a problem needs it
- A tool stack no single person could licence alone
Where you actually notice it
Four moments, and what changes in each.
Familiarity is hard to sell and easy to feel. These are the points where the difference shows up.
When something breaks
Nobody asks you to describe your setup. The answer starts from what is already known, which is why the average wait to reach a technician is measured in seconds rather than menus.
When you are deciding something
Replace the server room now, or budget for it next year? The honest answer depends on your business, your cash flow and your risk. Advice from someone who knows all three is worth more than advice that is technically correct.
When security comes up
Multi-factor prompts, email filtering and training all land differently depending on how your people work. A generic rollout is the one staff quietly find a way around, and a control nobody follows is not a control.
When you are planning
The quarterly review is short because nobody has to establish the facts first. You spend the time on decisions instead of on background.
Straight answers
What boutique does not mean.
The word gets used loosely, so here is what we are not claiming.
“It means small.”
It means deliberate. Being personal is a decision about how support is organised, not a side effect of not having enough people.
“It means expensive.”
It means fewer repeat problems. Most of what makes support costly is the same issue coming back, and context is the thing that stops it.
“It means one person you hope does not quit.”
It means a pod, with the wider team behind it. Continuity that survives a holiday is the entire point.
“It means light on tools and process.”
It means the same tooling, pointed at your business. Monitoring, patching, backup testing and security run exactly as they would anywhere. What changes is who reads the results.
What it produces
Numbers, rather than adjectives.
Those are measured averages from our own phone and ticket systems, not targets we aim at. We publish feedback from every ticket on the same basis.
“As usual, I caused myself some grief trying to fix something myself, and completely messed up my Mac’s performance and I was in danger of missing a critical client deadline. When I called, Ian calmed me down and quickly found the issue and fixed my problem.”
HR executive, a client since 2016
Questions we get asked
The things owners want to know about this.
The ones that come up most, answered in one place so the answer here and the answer anywhere else on the site are the same words. All questions and answers →
Are you locally owned?
Yes. Robertson Technology Group is locally owned and operated in Victoria, British Columbia, and has been since 2013. Decisions about your account are made here, by people you can meet, rather than at a head office in another province or another country.
Is your support offshored?
No. There is no offshore call centre. In business hours you reach our own team. After hours, or if every technician is already on a call, the line overflows to a Canadian support desk in Ontario. They take the details and pass them to one of our technicians. The call never leaves Canada.
Who actually answers when we call?
A technician, not a receptionist taking a message and not an automated menu. Wherever possible it is somebody from the pod assigned to your business, who already knows your systems and your history. You will not be asked to explain your setup from scratch, and you will not be handed between departments.
Will the technician who comes out have been here before?
Usually, yes. That is the point of assigning a pod rather than dispatching whoever happens to be free. Somebody who has already been in your server room knows where things are, what changed last time, and why. If a visit needs a specialist you have not met, we tell you who is coming and why.
Will we get the same technicians each time?
Yes. Every client is assigned a pod, a small group who learn your people, your systems and your history. You never explain your setup from scratch, and the wider team sits behind them for busy days and specialist work. More on how the pod model works.
Is boutique just a nicer word for small?
No. It describes how support is organised, not how many people do it. Work is assigned to a pod that stays with your business rather than to whoever happens to be free, and the wider team sits behind that pod for the busy days and the specialist problems.
Is this only for fully managed clients?
No. Fully managed and co-managed clients both get a pod. On co-managed the pod works alongside your own IT person rather than instead of them, and your person stays in charge.
What happens when my pod is busy or away?
Somebody else picks it up, and they can, because your environment is documented rather than carried around in one person’s head. You get a name you do not recognise far less often than you would elsewhere, and when you do, they are not starting from nothing.
Do I still get proper monitoring, patching and security?
Yes, all of it, running the same way it would at a much larger provider. See what is included in fully managed for the full list. Familiarity is about who interprets the results and how the advice is delivered, not about doing less of the work.
Related
Where this applies.
See whether it holds up.
Half an hour, no charge, no obligation. Ask us about your last bad support experience and what we would have done differently.
Would rather write?
Send this and we will reply, usually the same business day. No call unless you want one.
Protected by reCAPTCHA.