Before automating,
know where the time goes.
For one week, your team logs what they do on a platform I built. At the end, I show you how many hours go into repetitive tasks and which ones make sense to automate first.
Estimating gives one number. Logging gives another.
Ask someone how long they spend copying orders from email into Excel and you get a guess. After a week of logging, you know how many orders there are and how many minutes each one takes.
“Orders? Half an hour a day, tops.”Said in a meeting
From log to report.
The team logs and I cross-check the logs with the tools the company already uses. Out the other side comes a list of what to automate and in what order.
One-line log
What they did, how long it took and with which tool. It takes a few seconds.
Separate data
Login with email and password. Each company only sees its own logs.
A full week
A single day misses tasks that happen two or three times a week.
In-person meeting
The first one is at your premises, to get to know the story and the team before looking at numbers.
Three moments, a week in between.
The first meeting is in person. I want to hear the company's story and what's going wrong from you, before looking at numbers.
In-person meeting
The company's story, who does what and what weighs most day to day.
Platform access
Each person gets a login and I explain how to log. It takes a few minutes.
Logging week
Five working days of logs, plus a survey of the tools and files in use. During the week I watch the logs come in and answer the team's questions.
Analysis
I group the logs by task, person and tool and see what repeats.
Report and meeting
Where the time goes, what to automate first and why, presented in a meeting.
Where the time goes, in order.
At the end of the week, the logs are grouped and ranked by the time they take. The figures are an example.
Repetitive tasks
ExampleBuilt by me for these diagnoses, at diagnostico.starmountainflash.pt.
You get the report and a presentation meeting, so you can ask anything before deciding.
The report says what makes sense to automate and why. You're not obliged to go ahead with me.
What people ask me most.
Will my team waste a lot of time logging?+
Each log is one line: what they did, how long it took and with which tool. Over a day, it adds up to a few minutes.
Why a week and not a day?+
A single day misses tasks that happen two or three times a week, such as invoices, supplier orders or reports.
Who sees the logs?+
Your company and me. The platform keeps each company's data separate and access is by email and password.
Does the meeting have to be in person?+
The first one, yes. That's where I get to know the company, the team and how you work.
After the diagnosis, do I have to automate with you?+
The report says what makes sense to automate and why. What happens next is your decision.
Which companies is it for?+
For teams with admin work that repeats every week: orders, invoices, bookings, quotes, reports.
What takes up the most time in your company?
Tell me in two or three lines. I'll reply with how I'd run the diagnosis in your case.