What we can take on, from a blank domain to a business that runs itself
The question we get asked most often is not whether something can be automated. It is a smaller and more awkward question: how much of this do I have to sort out myself before you can help?
The answer is none of it. We can start at the point where a business is an idea and a name someone likes, and we can start at the point where a business has been running for fifteen years and has a spreadsheet nobody is allowed to touch. What follows is the honest list of what that covers, so you can see where you sit on it.
If you are starting from nothing
A new business needs an uncomfortable number of things to exist before it can take a single enquiry. The domain has to be registered. Hosting has to be set up and pointed at it. Email has to work on that domain, which is fiddlier than it sounds and quietly critical, because mail that lands in spam is worse than no mail at all. Then there is the site itself, the copy on it, the logo, the security certificate, the privacy and terms pages, and the plumbing that lets Google find any of it.
We do all of that, and we do it on your accounts, registered in your name. That matters more than it seems. If we ever part ways you keep the domain, the hosting, the site and the logins, and nothing has to be rebuilt or ransomed back.
One decision worth making early is how you want to edit the site afterwards. If you would rather change your own prices and add your own pages without asking anyone, we build it in a visual editor such as Elementor so you can do exactly that. If you would rather never touch it, we build it lighter and faster and look after it. Neither is the correct answer. They are different preferences and the build is different for each.
Once people can find you
A site nobody visits is an expensive business card. The next layer is being found and being followed up: search set up properly, analytics so you can tell what is working, social accounts created and correctly linked to each other, and advertising on Meta or Google when there is something worth spending on.
Most of the ongoing effort here is publishing, and publishing is where businesses quietly give up. It is not hard to post for three weeks. It is hard to post for three years. So we automate it: posts built from your own material, on a schedule, to every channel at once, with a person keeping approval over anything that goes out. The same applies to a newsletter, including the unglamorous part of making sure it actually reaches the whole list rather than the first fraction of it.
The questions your team keeps answering
Look at what arrives in your inbox over a week and a pattern appears fast. Opening hours. Do you deliver to this postcode. How much is it roughly. Can I move my appointment. Is this in stock. Almost none of it needs the person it reaches, and all of it interrupts them.
A chat bot on your site that has been trained on your own content answers those in seconds, at three in the morning, without anyone waking up. It hands over the ones that genuinely need judgement, which are usually the ones you actually want to see. The effect is not that customers get less attention. It is that the customers who need attention get it sooner, and your admin team gets their day back.
If your customers prefer WhatsApp, and in a lot of businesses they do, we set up WhatsApp Business properly and can put the same kind of bot behind it, answering questions and taking details before a person joins the conversation. If bookings are the bottleneck, we set up a booking system that talks to your real calendar, sends the confirmation, sends the reminder, and stops the double booking that costs you an afternoon and a customer.
The work behind the scenes
This is the part with the most hours in it, and the part nobody has ever counted, because it is rarely anybody’s named job. It is the master spreadsheet split into twenty files every Monday. It is the attachment that arrives by email and gets typed into a shared sheet so the rest of the team can see it. It is the statement pack that goes out on the first of the month, the invoice generated by editing last month’s invoice, the report assembled from four systems before a meeting, the timesheets consolidated, the price list that has to be kept in step in two places.
Every one of those is a scheduled job rather than a person’s morning. Where your systems offer a proper connection we use it. Where they do not, and plenty do not, it can still be done through scheduled exports, file drops, or code that works the tools the way a person would. The absence of a neat integration changes how it gets built. It does not change whether the hours come back.
What keeps all of it honest
Anything that runs on a schedule can stop running without telling you. So whatever we build, an agent supervises it afterwards, and it checks outcomes rather than green ticks: the post went out, the file landed, the email reached the whole list, the credentials have not silently expired. One board, one alert, one place to look, whether we built one thing for you or twenty.
Where to start
Not with all of it. Almost every problem we see in automation projects comes from scope rather than technology.
The useful first step is small and you can do part of it yourself this week. Pick the single process in your business that most annoys the person who does it. Time it honestly, from the first click to the last email sent. Multiply that by how often it happens, add the times it has to be redone, and you have a number. That number is what the process costs you every month, and it is almost always larger than people guess.
Bring us that one number and we will tell you straight whether it is worth automating, what it would take, and what it would give back. Sometimes the answer is that it is not worth it, and we would rather say so than sell you a build that never pays for itself.
