Four different businesses, one system. Follow each job from what comes in to what the owner decides.
Starky OS is one system, built in layers.
Construction supplies merchant
Live since July
What comes in
Customer messages on WhatsApp, and supplier invoices.
The rules it follows
Quote from past buys and sells, plus his margin.
What the AI does
Drafts the quote from the price history.
Where the work lands
The draft waits in front of the owner.
What you decide
The owner sends every quote. Nothing goes automatically.
Plumbing firm
Built, and the owner is testing it
What comes in
A customer WhatsApps the firm, with photos and a video.
The rules it follows
The firm’s own questions. Never a promise of a time or price.
What the AI does
Reads the chat, sorts the job, checks the details back.
Where the work lands
A booking request in the firm’s own job system.
What you decide
The firm taps to offer a visit. Nothing becomes a job until it says.
Contract cleaning firm
Built and ready to switch on
What comes in
Check ins from the cleaners at each site.
The rules it follows
A set wait for each site before anyone is alerted.
What the AI does
Spots a missed check in. Messages the cleaner first.
Where the work lands
A cover list goes to the manager.
What you decide
The manager approves the cover with a tap.
Tyre and MOT centre
Built and tested
What comes in
Calls after hours.
The rules it follows
The centre’s own diary rules.
What the AI does
Set up so a voice answers and pre books the job.
Where the work lands
A pre booking for the morning.
What you decide
The team approves each booking.
The layers, and the brain at the centre
It isn't a chatbot, a bundle of automations, or a subscription to someone else's product. It's the system I run my own companies on, and every business gets its own copy.
The rings read from the brain before they act, and what you decide is written back into it.
How it learns
It learns the plain way, by writing down what you teach it, and by reading that back before it acts. This is how it works in my own businesses today.
It reads first. Before it drafts anything to a person, it reads what happened last time with that person, on that channel. What you changed, what you sent as written, what you left.
It guesses your pick. Every draft and every decision put to you carries its guess at what you'll choose. Your choice is kept against the guess, and the guesses are scored every week.
Your edits are the lesson. When they shrink, it's learning you. When they don't, that shows too, in the same weekly score.
It shows you yourself. The threads you've left quiet, the things you said you'd do and haven't, how long you take to reply, each yours to keep or drop. One question a day, with your answer kept in your own words as a rule for you to confirm.
It earns, it isn't given. Today every send is your tap. A kind of message only ever goes on its own after a run of right guesses and your word by name.
A wrong lesson comes out. Because every lesson is written down, it can be found and taken back out.
For the merchant it works like this today. Every tap that links a line to a product is kept, so the same wording prices itself next time. Every supplier invoice he gets is read, so the next quote knows more. Every customer he types on a quote is remembered and offered back.
You own it.
Your records. You get them in plain files, on a machine you own or a server in your name. If your build starts on my kit, the move to yours is planned from the start.
Open standard tools. It's built on tools anyone can run. SQLite holds each database in a single file, and its makers intend to support it through 2050. The US Library of Congress lists it as a recommended format for keeping digital content. Around it sit Python, plain files, a full history of every change, and the scheduler already built into your computer or server.
What leaves the machine, honestly.
The AI reads the words it's working on, through Claude, an AI made by Anthropic.
WhatsApp messages travel through Meta, as they always do.
Where a build answers the phone, the call goes through the voice service that carries it.
A web page's data sits with the company that hosts the page.
How it's guarded
Nothing reaches a customer without your yes, or a kind of message you've approved to go on its own.
The read only WhatsApp link has no way to send at all.
Every change is checked by a second reviewer before it goes live.
Every running build checks itself every day, the parts and the results.
A copy is kept every day.
The worst case, said out loud. If it stops, your WhatsApp and your phones carry on exactly as before, and you're back to doing it by hand until it's fixed. You don't lose your messages.
Mac Mini or cloud
It is one system either way, and where it runs is your choice. The system and your records are yours.
Mac Mini
On a Mac Mini that you own.
Cloud
On a server set up for your business alone.
If you want to see where it would fit in your business, tell me a bit about it.