Two files you hand to your team. Each person spends 10 to 25 minutes being interviewed by ChatGPT or Claude about what they actually do all day, and gets a written record of their own job out of it. You get every one of those, plus a read on where the hours really go and what is worth automating first.
Built by Raghave at SideKick Studio. I kept running AI audits for Australian businesses that stalled in week one, because no owner could tell me what their team's week actually looked like. This is the thing I built to fix that, and it is free.
Fill this in and both files land in your inbox within a couple of minutes, along with instructions for running the exercise with your team.
One email with the files and the instructions. No sequence, no drip, and your details never get sold on.
Would rather just talk it through? Book a 30-minute call with Raghave
The email is on its way to . It has the download plus a short guide on running this with your team. If nothing has shown up in five minutes, check spam or the promotions tab.
Or grab it right now:
Stuck on any of it? Book a 30-minute call with Raghave or email raghave@sidekickstudio.com.au
A job description gets written once, when the role goes up on Seek. Then the person in the seat quietly reshapes the job around whatever needs doing that month. Three years on they are spending Tuesday mornings on a reconciliation nobody asked for, because that is how the last person did it.
The wasted hours live in that drift. Ask an owner where their bookkeeper's week goes and the answer is usually about 60% right. Ask the bookkeeper and you get the reconciliation, the chasing, a spreadsheet kept in step with Xero by hand, and the four times a week somebody asks her the same question about invoice terms.
Nobody has ever sat down and asked her properly. That is the entire idea here.
The interview spends a whole section on this, because people under-report all of it. It does not feel like real work to the person doing it, so it never makes a job description and never comes up in a review.
Five minutes here and there spent asking someone for a file, an approval or a number. It never feels like work, so nobody counts it. It is often the single biggest line in a finished Role Map.
The same detail typed into two systems. Or a spreadsheet somebody keeps in step with the software by hand, every Friday, because the two were never connected.
Logging in to confirm something happened. The report ran, the payment cleared, the job got assigned to someone. Pure overhead, and invisible until you ask.
Repairing things that should not have broken. Usually caused by one of the three above, and usually the reason a Tuesday disappears.
The question that turns up every week and gets answered from scratch every time, because the answer was never written down anywhere the asker could find it.
They arrive a minute or so after you fill in the form. Plain markdown files plus a page of instructions covering how to introduce this to your team and what to say when someone asks why.
Each person uploads the first file into ChatGPT or Claude and gets asked about their job, one question at a time. Quick mode is 12 questions and runs about 10 minutes. Full mode is 23 questions and runs about 25. They choose which.
The AI writes it up in their own words. Where the week goes, what happens daily and weekly and at month end, what breaks, what they would delete tomorrow, and what would fall over if they took a fortnight off.
Upload the second file along with every completed Role Map. Out comes the whole-business read: hours by activity, duplicated work, single points of failure, and a prioritised list of what to automate first.
Ten minutes a person on quick mode, twenty-five on full. For a team of eight that is under three hours of company time in total, and none of those hours are yours. Reading the Role Maps and running the analysis costs you about fifteen minutes once they are all back.
Worth having even if you never automate a thing. Handovers, hiring, restructures and performance conversations all get easier when the work is on paper.