Let the repeat work run on its own.

We automate the steps your team repeats each week by connecting the tools you already have, such as Excel and Microsoft 365, Google Workspace, Airtable and your CRM. A form entry lands in the right record, the monthly report assembles itself for a person to check, and the owner hears before a due date slips. We build these for teams in London and across the UK as part of our workflow and automation work.

Who are automation builds for?

They suit a team that already knows which jobs it repeats and is tired of doing them by hand:

  • Someone copies figures from one file to another every week or every month.
  • The monthly report is rebuilt by hand, and checking it takes as long as building it.
  • Enquiries arrive by email or through your website and wait until someone notices them.
  • People chase each other for updates that a reminder could ask for.

What you get

  • The repeated steps, built to run on their own inside the tools you already pay for.

  • Reports that assemble themselves from your records, ready for a person to check and send.

  • Reminders that reach the owner before a date slips, and an alert when something needs a person.

  • A clear line between what runs itself and what stays with a person, drawn on the process map.

  • Automations built to stop and say so when a step fails, instead of carrying on quietly.

  • Written instructions for each automation: what it does, when it runs and what to do when it stops.

  • Every file we make is yours: the automations, their settings, any code and the instructions.

How it runs

  1. A call about the work your team repeats. We ask what exists today, how often each job comes round, who decides, and what a good result would look like. We do not talk price on the call.

  2. The process comes first. We automate a process once it is clear, so if it is not, we start from a process map. Where the figures are spread across several spreadsheets, we put them in one database first.

  3. A written scope before any work starts: which steps will run themselves, which stay with a person, the dates and the price.

  4. Built in your own accounts and tested on invented data, then run on your real records with you before it goes live.

  5. A weekly look at real progress, with each automation shown working.

  6. Handover. Your team gets the instructions and short training, and runs it from there. If you would rather we looked after it, that is a monthly arrangement, offered only when there is something to keep.

What to bring

  • The jobs your team repeats, and how often each one comes round.
  • Access to the tools involved, from your own accounts and under your own permissions.
  • An example of the report or result you want, even a rough one.
  • The person who will own the automations once they are live.

An example

This one is real, and it was built by Rron Imami for his own product and sites, not for a client. A small always-on computer reads the business inbox and the site's comments on a timer, and checks that the sites are up. Each new item is sorted by plain rules, with no AI, labelled with a next step and sent to the owner's phone and project board. Marketing mail is logged and never rings. It never replies, deletes or publishes: replies stay with the owner.

The site checks have run since August 2026, and the inbox and comment watchers since September 2026. For a team whose enquiries arrive by email and through its website, the same pattern means nothing waits unseen. You can see the inbox and site watcher on the Work page, drawn from its real structure.

Automation and your website

If enquiries reach you through your website, the form is where the automation starts. The same studio offers website design and build, so the form and the record it lands in are designed together, by the same people. Owners who want their brand, site and admin from one studio will find more on working with growing businesses.

Questions about automation builds

Can you automate our Excel reports?

Yes, if the figures already live in spreadsheets or a database, the report can assemble itself from them, ready for a person to check before it goes out. Where the figures are scattered across several files, we put them in one place first.

Do we need to buy an automation tool?

Not usually: we start with the tools you already pay for, before anyone buys anything new. If something new is needed, the written scope says what it is and why, before you buy it.

What happens when an automation goes wrong?

It stops and says so, so a fault does not pass unseen and the person who owns it can step in. Each automation is tested before it goes live, and its written instructions say what to do when it stops.

Does it use AI?

Only where AI is reliable and you agree. Plain rules are enough for many repeat steps, such as moving a form entry into the right record. We use AI tools where they are reliable, people decide and check everything, and your data stays out of them unless you agree. There is more on AI assistants for teams.

Who looks after the automations once they are live?

Your team does, with written instructions and short training from us. If you would rather we looked after them, that is a monthly arrangement, offered only when there is something to keep.

Book a call

Tell us which jobs your team repeats. A call with Dorotea and Rron about which steps could run themselves. Before any work starts, you get a written scope.

Book a call

Not sure which? Plan your project