We are roasting at the limit of one person, and I have been thinking about a second roaster for months. The hourly rate is easy to quote.
Story · Solution
The owner catches every payroll mistake before the run goes out
I own a small coffee roaster, and I approve payroll twice a month. I used to approve it on trust.
Sound familiar?
I approve payroll on trust and hear about a missed clock-out or missing paperwork only when someone calls about their pay.
Why it hurts
I own a small coffee roaster, and I approve payroll twice a month. I used to approve it on trust. If someone forgot to clock out, or a new person had shifts but no paperwork, I found out when they called me about their pay. By then the money had gone out, and the fix meant another run, an apology and lost time.
How it is solved
Find and explain every problem in the coming run a few days before each pay date, so that the run I approve is right the first time.
- The owner sees the run prepared from the timesheets. For the open pay period, the app reads every shift and pay rate and lists each person in the run, with the questions it cannot answer on its own and anything that would stop the payroll system from paying.
- The owner sees each person checked against their own history. The app compares this run with the last few pay periods and with the records behind it. It looks for hours it cannot know, overtime from someone who never works overtime, a rate that has changed, a person with shifts but no hire record, leave beyond the balance, and a payment the payroll system will refuse.
- The owner reads the problems written up in plain words, without pay being exposed. An AI agent writes each flag as a short explanation. It is given hours and placeholders only, never a name, a pay rate or a dollar figure. The app adds the names and amounts afterwards. Per-person pay never appears in a brief, a dashboard or a chat.
- The owner finds the run waiting for approval, staged with its flags beside it. Nothing is paid until the owner approves it, and each decision on a flag is recorded with who made it and when.
The result
A run sheet for the coming payroll with every problem flagged, each with its reason. It flags a missing clock-out (the hours are unknown, so the app asks instead of guessing), overtime from someone who has worked none in recent pay periods, a change of role at a different rate (both rates shown), a person with shifts but no hire record (flagged as a new person to set up), leave requested beyond the person's balance, and a payment method the payroll system will refuse, such as a paper cheque, explained in plain English with the run sheet still built. The owner fixes what needs fixing, then approves a run that can be stood behind.
- If no problems are found, the run is approved as it stands.
- If problems are found, each is fixed before approval, so no one is paid wrongly and no correcting run is needed.
- If the payroll system will refuse a payment, the blocker is explained in plain words, and the owner resolves it before the pay date.
Try it
The demo runs on WidgetCo Coffee Roasters, an example business: a coffee roaster with an online store and a wholesale side. You will see it as Dana, the owner.
Connected to this story
The app
Read next
Why: Now possible, also about people and payroll, with an example app you can try today