Look
Read anything on the board — figures, history, alerts, the morning brief. Happens instantly. Changes nothing.
PushButton Ops · The control room
Every login you have. One question.
Money in, ads, traffic, who visited, what's broken, what needs you today. It's all on one board — and you don't read the board, you ask it. Out loud, if you want. It answers out loud too.
In practice
Things people ask it on a Monday.
No dashboard to learn. No filters to set. You ask the way you'd ask a person who happens to have read everything.
- “How much came in yesterday?”
- get_today_metrics
$1,240 across the storefront and two subscriptions. Up $180 on the Monday before.
Spoken aloud: “About twelve hundred yesterday, mostly the storefront.” - “What's broken right now?”
- get_alerts · list_sources
Two things. The quotes site has been down 41 minutes. The search data feed hasn't refreshed since Friday.
Spoken aloud: “Two things. Quotes site is down, and search data is stale since Friday.” - “How did last week's ads do?”
- get_metric_history · ads_fleet
$318 spent, 94 clicks, 11 enquiries. The roofing ad is doing the work; the other two are flat.
Spoken aloud: “Three eighteen spent, eleven enquiries. The roofing one's carrying it.”
It also tells you things you didn't ask. If a site is down or a feed has gone quiet, that comes up first, before it answers whatever you actually typed.
Voice
Hold the key and talk. Get an answer you can listen to.
Press and hold to speak — from any page, or with a keyboard shortcut from anywhere in the system. The answer comes back on screen in full, and out loud in a shorter version written to be heard rather than read.
To askHold the mic key and talk. Let go and it goes.
From anywhere⌥Space opens it over whatever you're looking at.
To listenNumbers get rounded the way a person would say them.
The spoken version isn't the written one read aloud. It's written separately, at the same moment, for the ear — "about twelve hundred" instead of "$1,240.00". You can turn the voice off and it behaves like an ordinary chat.
Where the numbers come from
It reads the record. It never reads your mind.
This is the part that matters most and gets talked about least. Every figure it gives you was pulled from the actual source, stored with a timestamp, and read back when you asked. It is not allowed to produce a number from memory, and it can't estimate one to be helpful.
- If a feed is down, it says so. It won't quietly answer with last week's figure and let you think it's today's.
- It shows its working. Every answer lists where it looked —
⚙ get_today_metrics · get_alerts— so you can check. - It knows the difference between "yesterday" and "ever." Sounds obvious. It's the single most common way these systems mislead people, and it's designed out rather than hoped away.
A tool that's confidently wrong about your revenue is worse than no tool. So it's built to say "I don't have that" more readily than most people would like.
The interlock
It can spend your money. It cannot spend your money without asking.
It can pause an ad, change a budget, extend a campaign, or launch a new one. Every single one of those stops dead at a gate and waits for you.
How an ad launch actually goes
You say"Run £10 a day on the roofing page for a week."
It buildsThe actual advert. Real headline, real words, real picture, real button.
It shows youAll of it, plus £10 × 7 days = £70 maximum. Nothing has been spent. Nothing exists yet.
You say yesOnly now does it go live — with exactly the advert you looked at, word for word.
The block isn't an instruction telling it to behave. It's in the wiring. A request to change something arrives without your approval attached and it is refused before it gets anywhere near your accounts — not because the model chose well, but because there's no path through.
And "yes" means yes to that — the exact advert you were shown, not a fresh one written after you agreed.
The feeds
Fourteen places, checked on a schedule.
You don't connect anything by hand. It's already wired to what you're running.
- Money in
- Website visitors
- Advert spend and clicks
- What people searched to find you
- Whether sites are up
- Your CRM activity
- How fast pages load
- Storefront orders
- Search rankings
- New sign-ups
- Failed deployments
- Audience sizes
- Database load
- Each of your own apps
If you add something later, it gets added to the board. Nothing on this list needed you to learn an API.
Three tiers
Look, tidy, or change. Only one of those needs you.
Tidy
Refresh every feed on demand, or rebuild today's morning brief and email it out. Happens instantly, gets written down, still changes nothing outside.
Change
Pause, resume, re-budget, extend or launch an advert. Held at the gate every time. Never happens without you.
Most days you'll only use the first one.
Record
Everything it did, and everything it asked to do.
Every action is written down — including the ones you said no to, and the ones still waiting on you. Who asked, what was asked, what came back, and whether it went through. Changes to your adverts are logged twice: once here, once in the advertising system itself.
You should be able to answer "what changed and who let it" without phoning anyone. That's the whole point of a log.
The stack
Underneath is the OS. Outside are the platforms. This is where you stand.
The OS is what your business runs on — your information organized, your decisions written down, software that acts. The platforms are where the work happens. Ops is the room you watch it all from, and the only place anything gets approved.
Next
Come and see the board.
Easiest way to understand this one is to watch someone ask it something. Fifteen minutes, your numbers or ours, no deck.
Book a call
Ops sits on top of the OS, so it's worth a conversation about what you've already got before anyone talks about buying it.