How an automation comes together, step by step

We start from the work you really do every day, and from there we build a system that runs on the programs you already have installed

The first step costs nothing and commits you to nothing, you show us the process and we tell you whether it makes sense

A hand writing steps by hand in a notebook next to a whiteboard

You show us the process

Even just a screen recording of you doing it, with a couple of sample files

We work out the gain

Hours, errors and the checks needed, if it isn't worth it we tell you

We put it all in writing

What the system will do, what it won't do and how much it costs per month

We build it

On your programs and your rules, tested on controlled cases

We start out assisted

More checks and more confirmations at first, then it widens little by little

The first step is just a chat

There is nothing formal to prepare, we only need to understand how you work today. The quickest way is for you to show us the process while you do it

A screen recording is fine, shot on your phone or with the Windows tool, with no editing, and your own voice explaining the steps as you click

We watch the video and ask you a few questions, then we give you our opinion

We tell you whether it's worth it, even when the answer is no

Together we count the hours you spend on it, what they cost and how many would be left, and we also take into account the checks the system will have to run

If the process changes too often, or the volumes are low, or the saving doesn't pay back the monthly fee, we tell you and we stop there. We would rather have a client who stays than a monthly fee that makes no sense after three months

What it will do and what it won't, written down before we start

Before you decide you get a document in plain language, with no technical jargon, listing the steps the system will handle on its own, the ones that stay with a person, the cases it won't cover, the monthly fee and what support includes

We agree the monthly fee right there, and it stays that way, if something more is needed later we explain it and you approve it before it becomes a cost

We build it and test it on controlled cases

We develop the process and run it on real documents without touching anything final, so you see what it gets up to before it touches your data

This is usually where the exceptions nobody remembered come out, the supplier who sends the PDF laid out differently, the case that follows a rule of its own, we sort them out now, while they can't do any harm

We start slowly, with more checks than needed

In the early days the system works on a short leash, it asks for confirmation before sensitive operations, it stops if a value doesn't add up instead of carrying on, and it leaves a log of what it did

Once you have seen enough runs go well, you decide how much autonomy to give it, the brake stays in your hands

After the rollout we are the ones who keep it running

Programs change, a portal moves a button, the business software gets an update, these things are covered by maintenance under the plan you chose and it's one of the reasons the service is a subscription and not a one-off project

When you write, Antonio answers, and he's the one who wrote the automation, with no call center in between

Every process is different, so we set the cost and how much work the system can take on only after we have seen how you really work, before that any figure would be made up

What people usually ask us

Not much, Muffin Suite asks for a screen recording of you doing the process, even shot on your phone and with no editing, one or two sample files and an idea of how many times a month you repeat it, if something is missing write to us anyway and we'll talk it over
No, the first assessment from Muffin Suite costs nothing and doesn't commit you to going on, we look at the process you show us, we ask you a few questions and we give you an opinion, then you decide whether to carry on or stop there
It happens, and Muffin Suite tells you so, if the process keeps changing, if the volumes are low or if the saving doesn't pay back the monthly fee the assessment ends there, at no cost and with no pushing
No, the business software you use stays as it is, Muffin Suite builds the automation on top of the programs already installed and on the rules you follow, even when there is no direct integration with the outside
Antonio Fuccillo, the same person who wrote the automation, with no call center in between, changes to the programs and the portals are covered by maintenance under the plan you chose and it's one of the reasons the service is a subscription
No, at the rollout the Muffin Suite automation works with more checks than it needs, it asks for confirmation before sensitive operations, it stops when a value doesn't add up and it leaves a log, then you decide how much autonomy to give it

Show us what you still do by hand

Describe the process or send a short screen recording and we will work out what can be automated

WA