Operations
Operations Command Centre: is the site up and what broke?
The Operations Command Centre is a private dashboard that shows whether your site is up, what came in and what broke, on six screens and a Monday email. £799 to set up, then £49 a month. Live in 10 working days.
Why do small businesses find out about outages from customers?
Most small firms run on five or six tools, each with its own login and its own idea of what matters. Nobody opens them all, so the outage, the halved sign-ups or the tripled bill go unseen until it costs money.
So nobody looks until something goes wrong. The site was down on Saturday, sign-ups halved last month, the cloud bill tripled - and you learn it from a customer or an invoice.
I built a single console to stop that happening on GigXchange. You get the same idea, cut down to the six screens a small business actually opens.
How does one dashboard compare with a big monitoring platform?
Logging into each tool means five or six logins and nobody telling you. A big monitoring platform is built for engineers. The Operations Command Centre is one private screen in plain words, with costs against your caps and a weekly email.
| Logging into each tool | A big monitoring platform | Operations Command Centre | |
|---|---|---|---|
| Where the numbers live | Five or six separate logins | One tool, built for engineers | One private screen |
| Site up or down | You notice, or a customer does | Yes, once set up | Checked all day, every day |
| Errors | Buried in a hosting log | Yes, in developer terms | In plain words, by page |
| Costs | The bill at month end | Usually not | Against your caps, red/amber/green |
| Who tells you | Nobody | Alerts you have to tune | A weekly email, plus alerts when red |
What is on the Operations Command Centre dashboard?
The Operations Command Centre gives you six screens - health, sign-ups, sales, errors, search and costs - read from your own systems with test accounts filtered out, plus a Monday email with the one thing that needs you at the top.
- 01
Six screens, not sixty
Health, sign-ups, sales, errors, search and costs. Anything you will not look at is left out.
- 02
Site health
Is the site up, is the login working, which pages are slow on phones - checked all day.
- 03
Sign-ups and sales
Read straight from your own systems, with test accounts and staff filtered out so the numbers are real.
- 04
Errors in plain words
What broke, on which page, and how many people hit it - not a wall of developer logs.
- 05
Search figures
Google and Bing clicks, views and position, pulled in daily so you stop logging into two consoles.
- 06
Costs against caps
Each cloud and AI bill shown green, amber or red against the limit you set.
- 07
A weekly email
Monday morning, one page, with the one thing that needs you at the top.
- 08
Private by default
Behind a login only you and the people you name can pass.
What does the weekly summary email look like?
The Operations Command Centre sends one page every Monday at 08:00: site uptime, sign-ups against last week, orders, login tests passed, new errors by page, Google clicks, the cloud bill against its cap and what needs you.
Monday 08:00 - weekly summary
- Site: up all week
- Sign-ups: 41 (last week 33)
- Sales: 18 orders
- Login test: 84 of 84 passed
- Errors: 2 new, both on checkout
- Google clicks: 1,120 (28 days)
- Cloud bill: green, 31% of cap
- Slowest page: /book (3.1s on phones)
- Needs you: 1 thing
- 65pages in the GigXchange console
- 102back-end functions behind it
- 12login journey tests a day
Source GigXchange's own figures, as of 25 October 2026
How long does the Operations Command Centre take to set up?
The Operations Command Centre takes 10 working days from the first call. Days 1-3 connect your tools read-only, days 4-5 agree the screens and what counts as red, days 6-9 build them from live data, and day 10 is handover.
- 01
Days 1-3
Connect
We list your tools - host, payments, email, search - and connect read-only access to each.
- 02
Days 4-5
Choose
We agree which six screens matter and what counts as red for each number.
- 03
Days 6-9
Build
Screens built and filled from your live data. You check the numbers against what you already know.
- 04
Day 10
Hand over
Logins set up, the first weekly email sent, alerts switched on.
Is a business dashboard worth it for a small firm?
The Operations Command Centre suits a business that takes money or sign-ups online, uses three or more tools to run the site and has been caught out before. It is the wrong buy for a brochure site, or if you will not open it weekly.
A good fit if
- You take money or sign-ups online
- You use 3+ tools to run the site
- You have been caught out by an outage or a bill
Not for you if
- You have a brochure site and no online sales
- You want a full engineering monitoring stack
- You will not open it once a week
Questions
07Asked and answered
It costs £799 to set up and £49 a month after that. The setup covers connecting your tools, building the six screens and sending the first weekly email. The monthly fee covers hosting, keeping the connections working when a provider changes something, the alerts and the weekly email. There are no per-user charges, so you can add a business partner or a bookkeeper without the price moving.
Health, sign-ups, sales, errors, search and costs. Health shows whether the site and login are up. Sign-ups and sales come from your own systems with test accounts removed. Errors lists what broke and where. Search shows Google and Bing figures. Costs shows each bill against a cap. If you want login tests every two hours on top, add Synthetic Monitoring.
Most of the common ones a UK small business uses: Stripe for payments, Google Search Console and Bing for search, Cloudflare and the main hosting providers, Supabase or Postgres databases, and email senders such as Resend. If you use something unusual, ask first and we check it in writing before you pay. Anything without a way to read its data is left off rather than faked.
It is the same system, cut down. The GigXchange console has 65 pages because a marketplace has a lot of moving parts - directories, moderation, GDPR requests, a price index. A small business does not need most of that. I keep the parts that earn their place and rebuild them around your tools, which is why each client version is built rather than switched on.
Only you and the people you name. The dashboard sits behind a login that blocks everyone else before the page even loads. Connections to your tools are read-only, so it can show your numbers but cannot change them. We never copy customer names or card details into it. The NCSC small business guide is a good plain-English check on the rest of your setup.
10 working days from the first call. Days 1-3 connect your tools, days 4-5 agree the screens and what counts as red, days 6-9 build them from your live data, and day 10 is handover with the first weekly email. The slowest part is usually waiting for access to a provider account, so having those logins ready saves days. Nothing goes live until you have checked the numbers against figures you already trust.
Yes, any month, with no notice period. When you cancel, the dashboard, alerts and weekly email stop, and we remove our read-only access from your tools. Your own systems are untouched because the console only ever read from them. If you later want a one-off check instead, Cloud Cost Controls runs on its own with no monthly fee. Your data stays exactly where it always was, in your own accounts.
No, a dashboard tells you something is wrong, not what to do next. That is the job of a written plan: who to call, what to switch off, what to tell customers. The Incident & Continuity Plan is the other half, and the alerts on this screen point straight to the matching page in it. Together they cover the two questions that matter on a bad day: what is wrong, and what do I do about it.