Cloud & Managed Technology
The part nobody thinks about until the day it matters.
Secure hosting, backups that get tested, sensible security, and ongoing care after launch — plus a human to call when something breaks.
No obligation. No jargon. Plain English.
Sound familiar?
- You are not entirely sure where your website lives, or who holds the login.
- The backup is a drive under someone's desk, and nobody has ever tried restoring from it.
- The person who set all of this up moved on, and nothing has been updated since.
- When something goes down at nine at night, you are searching the internet instead of calling someone.
- One password gets shared for the important account, including with the person who left last year.
Do I actually need this, or is my setup fine?
Quite possibly fine. This is the service we talk people out of most often.
If your site is simple, the hosting account is in your name, the software behind it still gets security updates, and you could genuinely restore everything from a backup this afternoon, then you do not have a problem and you should spend the money on something that brings in work.
The trouble usually shows up as one of four things. Nobody at the business can log in to the place the website actually lives. The backup exists in theory and has never been tested. The system has not had an update in a long time because the person who used to do it is gone. Or there is no answer to the question of who you call at nine at night when it stops working.
Those are not urgent right up until the moment they are the only thing that matters, which is the awkward thing about insurance.
What does “in the cloud” actually mean here?
Renting a slice of somebody else’s very good data centre instead of owning a machine.
The big platforms — the ones run by Amazon and Microsoft — are the same infrastructure large companies run on, and you can rent a small corner of it. The current way of doing that is called serverless, which is a misleading name for something straightforward: you rent servers by the sip instead of the barrel. You are not paying for a machine that sits idle overnight, and the morning your ad runs does not knock the site over.
That said, big platform does not mean better for everyone. A brochure site and a booking page do not need an enterprise architecture, and we are not going to build one so the diagram looks impressive. We size it to your actual traffic and tell you when something simpler is the right call.
What does the ongoing part actually cover?
The things that go wrong slowly.
Monitoring, so an outage produces an alert to us rather than a phone call from a customer. Updates applied on a schedule instead of in a panic. Backups taken, stored separately, and restored on purpose from time to time — because a backup nobody has tested is a hope with a file extension. Renewals and certificates watched, since the most common reason a small business site suddenly goes dark is that something expired and nobody was tracking it.
And a person. Named, reachable, with agreed expectations about how quickly you hear back and what happens next. We cannot promise nothing will ever break. We can promise you will not be alone at nine at night working out who to call.
Who owns all of it?
You do, deliberately and completely.
Accounts opened in your name with your billing details. Credentials in your password manager, not ours. A written runbook covering where every system lives, how to restore it, and who to contact at each vendor. Hand that to another provider tomorrow and they can pick it up without speaking to us.
Being easy to leave is part of the design. It is also the only honest way to sell a monthly plan — we would rather earn next month than have you trapped in it.
What's included?
Done-for-you. We build it, connect it to what you already use, and stay until it's running the way you'd run it yourself.
- A written inventory of every system, domain, and account the business depends on — and who holds the keys to each
- Hosting on mainstream cloud platforms, sized for the traffic you actually have rather than the traffic in a brochure
- Migration from whatever you are on today, done out of hours, with a tested way back if it goes wrong
- Backups on a schedule, stored somewhere separate, and restored on purpose from time to time to prove they work
- Security basics done properly: updates applied, one account per person, multi-factor sign-in, a shared password manager
- Monitoring that tells us a system is down before a customer does
- A named person to call when something breaks, with response expectations agreed in writing beforehand
- Every account opened in your name, on your billing, with documentation you keep
How does it work under the hood?
The short version: real, named mechanisms doing specific jobs — no magic. Open this up if you're the skeptic, or if you have a technical friend who's going to ask.
Show me how it actually works
Cloud hosting means renting a slice of somebody else's very large, very well-run data centre instead of owning a machine. The platforms most people have heard of — the ones run by Amazon and Microsoft — are the same infrastructure large companies use, and small businesses can rent a corner of it. The modern version of this is usually described as serverless, which is a confusing name for a simple idea: you rent servers by the sip instead of the barrel. Nothing sits idle waiting for you. A quiet Tuesday costs almost nothing, and the busy morning after your ad runs is handled without anyone being woken up.
The right size is smaller than most vendors will tell you. A brochure site, a booking page, and a small internal tool do not need an enterprise architecture, and building one is a way to spend money on a diagram. We start by looking at what you are on now, and a fair share of the time the honest answer is that your current hosting is fine and the money is better spent elsewhere. When it isn't fine, the usual reasons are concrete rather than dramatic: nobody can log in, the site falls over exactly when you are busiest, the platform has stopped receiving security updates, or the whole thing is registered to somebody who no longer works with you.
Backups are the part everyone claims to have and few people have tested. A backup is not a backup until it has been restored. We keep more than one copy, keep at least one of them somewhere separate from the live system, and periodically restore from it on purpose to prove the file is real and the process works. Before any of that we ask two plain questions and write the answers down: how much work can you afford to lose, and how long can you afford to be down? An hour of lost bookings and a week of lost records are very different problems, and the answers decide what the backup schedule has to be. Ransomware, a bad update, and somebody deleting the wrong folder all get solved by the same boring discipline.
Security for a small business is mostly hygiene, not hardware. Keep software current, because most trouble arrives through a known hole that was patched months ago. Give each person their own account with only the access their job needs, so leaving the business is a checklist rather than an archaeology project. Turn on multi-factor sign-in — the code on your phone — for anything that touches money, customer records, or your domain name. Put shared credentials in a password manager instead of a spreadsheet or a group chat. None of this is exciting and all of it matters, and most attempts on a business your size are automated and indiscriminate rather than personal. We do not sell alarm systems for problems you do not have, and we will not put a compliance program on a four-person practice that needs a password manager and a patch schedule.
Managed care is what happens after launch, which is where most small-business technology quietly falls apart. Systems get monitored so an outage produces an alert rather than a phone call from an annoyed customer. Updates get applied on a schedule rather than in a panic. Certificates and domain renewals get watched, because the most common cause of a site suddenly going dark is something expiring that nobody was tracking. You get a short note about what happened and what needs attention, and a named person to reach when something breaks. We will not promise nothing ever will. We will tell you who picks up, how fast, and what happens next.
Everything is built to be left. Accounts are opened in your name with your billing details, credentials live in your password manager, and the written runbook — where things live, how to restore them, who to call at each vendor — belongs to you. If you hand it to another provider tomorrow, they can pick it up without ringing us. Being easy to leave is a design decision, not a courtesy, and it keeps us honest about earning the next month.
What's the return?
We measure every engagement in the same three currencies — dollars, customers, and hours of your day. Here's what this one pays back.
Outages and lost data stop being emergencies you absorb personally, and hosting spend matches what you actually use rather than what you were sold.
Dollars
Customers meet a site and systems that are up, current, and quick — including on the days you are busiest.
Customers
The evening you would have spent on hold with a hosting company belongs to somebody whose job it is.
Hours of your day
What changes, in practice?
One ordinary moment in your week, before and after. Illustrative, not a client case study.
Before
Your three-person practice runs a website and a client booking page set up years ago by a contractor, under his email address, on a hosting plan you cannot access. The backup is an external drive someone remembers to plug in most Fridays. When the site went blank last spring, the first hour was spent working out who to even call.
After
Everything sits in accounts in your name, on your card, with the logins in a password manager the whole team uses. Backups run nightly to a separate location and get test-restored on a schedule. The last outage was caught by monitoring before opening, and you found out by text that it was already being dealt with.
Questions owners ask us
My hosting is cheap and it has never given me trouble. Why would I change it?
Often you should not, and we will say so. Cheap shared hosting is genuinely fine for a simple site with modest traffic. The questions worth asking are whether the account is in your name, whether the platform still receives security updates, and whether you could restore the site from a backup this afternoon if you had to. If those three answers are good, keep what you have.
Isn't a platform like AWS or Azure overkill for a business my size?
It can be, and plenty of small businesses are better off on something simpler. What those platforms are genuinely good at for a small business is paying for what you use and not falling over on your busiest day. We size the setup to your actual traffic, and where a simpler host does the job, that is what we recommend.
We are small and boring. Who would bother attacking us?
Nobody is picking you out, and that is rather the point — most of what reaches a small business is automated, scanning everything it can reach for something out of date and taking whatever it finds. The more common losses are duller still: a departed employee's account nobody closed, a folder deleted by accident, an attachment somebody opened. All of them are handled by the same unglamorous basics rather than by anything you would need a budget for.
Isn't a monthly managed plan just paying for someone to do nothing?
Some months, very little happens, and that is what you are buying. What is actually running is monitoring, updates, backup checks, restore tests, and renewals nobody else is tracking. If you would rather handle it yourself, we will hand over the runbook and the checklist and you can. The plan is for owners who know they will not get to it.
What happens if I want to leave, or if you go away?
Everything is already yours. The accounts are in your name, the credentials are in your password manager, and the documentation describes where each system lives and how to restore it. Another competent provider can take over without our involvement. We would rather be kept than relied on.
Who does this work best for?
It fits most businesses that sell time or appointments — but here's where it pays back fastest.