Block one hour a week, ideally Friday afternoon, and split it into ten minutes to gather loose ends, fifteen on quotes, fifteen on invoices, fifteen on customer messages and five to plan next week. AI drafts follow-ups, invoice wording and replies from your notes, and you send nothing until you have read it.
The hour works because the pile is processed in one pass, with the same instructions every time, instead of in scraps at ten at night. It also puts a ceiling on the job: when the hour ends, leftovers move to next week's list instead of into your evening. The first ten minutes decide the rest, because AI can only sort what you have gathered in one place.
The hour as five blocks, each with one output
| Minutes | Block | You do | AI does | Output |
|---|---|---|---|---|
| 0 to 10 | Dump | Gather voice notes, job-sheet photos, open quotes, unbilled jobs, unpaid invoices and unanswered messages in one note | Sorts them into one table | One sorted list |
| 10 to 25 | Quotes | Decide which quotes to chase, close or leave | Drafts follow-ups matched to each quote's age | Messages ready to send |
| 25 to 40 | Invoices | Confirm amounts and customer details | Writes line descriptions and overdue reminders | Invoices raised, reminders sent |
| 40 to 55 | Messages | Make the decisions the AI flags | Drafts replies in your voice | Replies sent, callbacks booked |
| 55 to 60 | Close | Note mistakes and plan next week | Turns the log into a rule or two | A short list for next Friday |
Two rules hold the hour together. First, AI drafts and you decide: it never sends, never confirms a date and never quotes a price you have not given it. Second, every prompt starts from the same short rules block (it comes later on this page), so the output does not drift from one Friday to the next. The examples that follow all come from one illustrative week for a sole-trader electrician.
Minutes 0 to 10: one dump of the week's loose ends
Keep a single note on your phone called "Admin dump" and drop things into it all week: a dictated line after each job, a photo of the job sheet, a customer's text you cannot answer from the van. On Friday add whatever is missing, then paste the lot into the assistant. The point of the dump is that sorting is cheap for AI and expensive for you, because your head holds twenty half-finished things at once.
Sort this into five buckets: quotes to chase, invoices to raise, invoices overdue, messages to answer, decisions only I can make. One table, one row per item, a short note on each. Do not invent anything; if a detail is missing write MISSING.
Raise invoices: L switchboard done 1,420; G fan fitted 860; M outdoor sockets 2,150; N rewire second fix 1,770.
Quotes out: A switchboard upgrade 1,850 (9 days); B garden lighting 2,400 (4 days); C two-room rewire 3,200 (16 days); D extractor fan 380 (2 days); E EV charger 1,150 (12 days).
Unpaid: H 640, 14 days over; J 1,100, 30 days over.
Messages: F says lights flickering since Tuesday, wants a visit; B asks if the lighting quote includes the trench; K wants a price for three sockets; P wants to move Tuesday's visit; Q wants a copy of her invoice; R asks if I can start a week early.
The reply comes back as a tidy table of 17 items: five quotes, four invoices to raise, two overdue, six messages. It will also make a few mistakes, which is why you read it. In this illustrative run, the sort put F's flickering lights under "messages", when it is a callback that needs a booking and a decision from you, so it moves to the decisions bucket. It filed B's trench question under "quotes", where the question is really a message that needs a look at the quote itself. And it left a MISSING marker on the date for invoice N, which is correct, because you never gave one. The marker is the rule paying for itself: without it, the tool tends to invent a date that looks plausible.

The Complete Excel Course with AI Integration
From formulas and pivot tables to Power Query, DAX, VBA and AI with Copilot, ChatGPT and Claude — hands-on from the first lesson.
By Sagnik Bhattacharya and Virginia Thorn, Primetime Emmy Award winner
Buy nowMinutes 10 to 25: open quotes, chased and closed
Chase by age, not by feel. A fixed rule means you stop deciding which quote deserves a message and start working down a list.
| Days since sent | Action |
|---|---|
| 0 to 2 | Leave it alone |
| 3 to 6 | First follow-up: check it arrived and offer to talk through the scope |
| 7 to 13 | Second follow-up: ask what is holding the decision up |
| 14 to 20 | Last call: say when the quote will be closed |
| 21 or more | Close it in your records and send a short "closed, happy to reopen" note |
Apply it to this week's five quotes. A at 9 days gets a second follow-up, B at 4 days a first follow-up, C at 16 days a last call, E at 12 days a second follow-up, and D at 2 days is left alone. Four messages, covering 8,600 of the 8,980 in open quotes. Hand the assistant the table and the action for each row:
Draft one text per quote below, matched to the action in the last column. Under 50 words each, in my voice from the rules. No discounts, no offers to hold a date, no pressure. First names only.
A | switchboard upgrade | second follow-up
B | garden lighting | first follow-up
C | two-room rewire | last call, quote closes next Friday
E | EV charger | second follow-up
A typical draft for B reads: "Hi [first name], just checking the lighting quote reached you. Happy to talk through the trenching or the fittings if that helps. I can hold a slot for you next week if you want to go ahead. [your name]". Two things need changing. "I can hold a slot" is a promise that your diary may not keep, and the rules say no offers to hold anything, so cut it. And the trenching mention is useful only if the quote covers trenching, so check it against the quote before the text goes. For C, expect a last-call text that is polite and clear about the closing date; make sure it names the real date rather than "soon".
Follow-ups sometimes draw a reply you did not want, such as "a bit more than I was expecting". This is where an unchecked draft costs real money, because the easy answer is a discount. Suppose the assistant offers: "No problem, I can knock 10% off if you can confirm today." Delete it. A better reply asks what budget the customer had in mind, offers a smaller scope with the price that goes with it, and leaves the full quote standing: "Understood. If it helps, I can price a version without the garden section, which would bring the total down. What budget were you hoping to stay within?" The assistant can write that if the rules block says "never discount; offer a reduced scope or ask for the budget".
The quote-template tutorial on GST lines, validity and acceptance wording covers writing the quote itself, and ten ChatGPT prompts for quotes and follow-ups offers variations when a customer goes quiet in a particular way.
Minutes 25 to 40: invoices out, overdue ones nudged
Invoicing software, not the chatbot, should do the sums and the tax lines. AI earns its place on the words: the line descriptions a customer reads, and the reminder when a payment is late. For the four jobs to bill, paste your short notes and ask for descriptions only.
Write invoice line descriptions from these job notes, one block per customer letter. Do not calculate or mention any amounts or tax; my invoicing app adds those. Plain English a customer would follow. If a job note is vague, write MISSING instead of guessing.
L: old board out, new board in, tested circuits, labelled
G: bathroom fan, new switch, made good
M: two outdoor sockets, trench, cable, weatherproof boxes
N: second fix, sockets and switches, 6 rooms
Compare the before and after for G. The note says "bathroom fan, new switch, made good". The description worth sending says: "Supply and fit bathroom extractor fan with new switch; make good plaster and paint around the fitting." The second version lets a customer who queries the total see what they paid for, and "made good" is the sort of phrase that starts arguments. Check that each description matches what you actually did; if the tool added "paint" and you never painted, delete it.
Then raise the invoices in your app and run the same four checks every time: the customer is right, the amount matches your job sheet, the tax line is the one your accountant gave you, and the due date matches your terms. The tutorial on tax invoice wording and reminders lists the fields an invoice needs and the reminder sequence in full.
For the two overdue invoices the draft depends on age. H is 14 days over and gets a firm, friendly reminder with the invoice attached. J is 30 days over and gets a short email followed by a call. Here is what an assistant might offer for J, and the part to change:
Hi [first name], invoice for 1,100 is now 30 days past due. Please pay by Friday or I will pass this to a debt collector. [your name]
The threat is the problem. You may not intend to use a collector, and a threat you will not carry out costs you credibility. A better version asks for a date: "I'd like to agree a payment date this week. If something is holding it up, tell me and we'll find a way." Save the formal wording for a letter you have checked with an adviser.
Minutes 40 to 55: replies to customer messages in one batch
Replying to six messages one at a time costs six context switches; replying to all six in a row costs one. Paste the messages with first names, and ask the assistant for a numbered list in which every reply sits next to a "Decision for me" line wherever the answer is not in your rules. Here is how three of this week's six might look.
| Customer message | Illustrative draft | What to change |
|---|---|---|
| F: lights flickering since Tuesday, can you come? | "Sorry about that, it was clearly our work. I'll be there first thing tomorrow." | Cut "clearly our work", since you have not looked yet. Cut "first thing tomorrow", a promise. Offer two slots you choose, and ring first if flickering could mean a safety problem. |
| B: does the lighting quote include the trench? | "Decision for me: MISSING, check the quote for trenching." | Nothing: the rules block made the tool flag the gap. Reply once you have read the quote. |
| K: how much for three sockets? | "Happy to help. I'd need to see where they go first. Could you send a photo of the wall, or shall I pop round for a quick look?" | Fine. It asked for information instead of inventing a price, which is what the rules say. |
The first row shows the most expensive kind of error: an apology that admits fault before anyone has examined the problem. Customers screenshot messages. A draft that says "our work" is a draft that you edit to "I'm sorry you're having trouble; I'll take a look", and it gets edited every time, which is why you read every draft. The second row shows the opposite: a gap that the tool surfaced instead of covering. The five customer messages to draft and check tutorial goes through more cases, including complaints and delays.
Minutes 55 to 60: log the misses and set next Friday
Use the last five minutes to turn the week's mistakes into rules. Keep a three-column note: what the AI got wrong, how you spotted it, and the rule that would stop it. This week's log might read as follows.
| What went wrong | How I spotted it | Rule to add |
|---|---|---|
| Offered to hold a slot for quote B | Read the draft against my diary | Never offer to hold a date or slot |
| Called a flicker "our work" | Read before sending | Never admit fault; offer to inspect |
| Filed F's callback as a message | The sorted table looked wrong | Callbacks and visits go under decisions |
Paste the new rules into the rules block, then end the hour by writing next Friday's list: the quote that closes, the invoice that needs a call, and anything you could not decide. Two weeks of this log is worth more than any prompt library, because it is built from your own near misses.
The rules block that starts every prompt
Save this in a ChatGPT Project or a Claude Project, which both keep instructions between chats, and not in a custom GPT, because OpenAI stopped custom GPT creation in late September 2026. Edit the first line to your trade and the voice to yours.
You are my admin assistant. I am a sole-trader electrician. Write short, friendly, plain messages in my voice: direct, no jargon, no exclamation marks.
Rules: never promise a date or time; never quote a price unless I give it; never admit fault or offer refunds; never offer to hold a slot; never invent job details; if something is missing, write MISSING; if a message mentions burning smells, sparks, heat or water near electrics, write URGENT and draft nothing; use first names or letters only; texts under 50 words, emails under 120.
Format: a numbered list, one item per customer, with a line "Decision for me:" wherever I must choose.
Paste three real messages of yours under the rules as voice samples and tell the assistant to match their length. Keep surnames, addresses and phone numbers out of everything you paste: the assistant needs the job and the question, not the identity.
Setting the hour up once: a 30-minute job for a quiet evening
- Put a repeating block in your phone calendar, Friday 3pm, called "Admin hour", with the dump note linked. A calendar event nudges you better than any AI tool.
- Create the "Admin dump" note and pin it to your home screen so adding to it takes two taps.
- Create the Project, paste in the rules block and three samples of your own messages, and write the quote validity period and your invoice terms into the rules so the assistant never has to guess either.
- In your job or invoicing app, find the three lists you need: open quotes, finished jobs not yet invoiced, and unpaid invoices. Write down where each one lives, so exporting or copying them takes a minute rather than a hunt.
- Run a dry run on last week's paperwork. Note what the assistant gets wrong and add a rule for each miss before the first live Friday.
Thirty minutes of set-up is what lets the real hour run in an hour. Skip it and the first Friday spends twenty minutes on hunting and instruction, and a routine that starts badly is easy to drop.
One electrician's Friday in numbers
Here is the same week in one table, with illustrative figures.
| Block | Minutes | What passed through | Value in front of customers |
|---|---|---|---|
| Dump | 10 | 17 items sorted | Not counted |
| Quotes | 15 | 5 reviewed, 4 messages | 8,600 of quotes chased |
| Invoices | 15 | 4 raised, 2 reminders | 6,200 billed and 1,740 overdue |
| Messages | 15 | 6 replies, 2 flagged | Not counted |
| Close | 5 | 3 rules logged | Not counted |
| Total | 60 | About 17 items, 12 messages | 16,540 |
The sum behind the last column: 8,600 of quotes chased, 6,200 of invoices raised and 1,740 of overdue invoices nudged add up to 16,540. If the same work normally takes you two to three hours spread across the week, the routine could hand one or two of them back. Time it for three Fridays and use your own numbers, because the saving depends on how scattered your admin is today. The money is the better reason to keep the hour: unsent invoices and unchased quotes are the cheapest cash you will ever collect.
Changing the split for your kind of week
The 10, 15, 15, 15, 5 split fits a mixed week. Move the minutes when your work has a different shape, and keep the total at 60.
| Shape of your week | Dump | Quotes | Invoices | Messages | Close |
|---|---|---|---|---|---|
| Many small call-outs, such as a plumber's day of repairs | 10 | 5 | 25 | 15 | 5 |
| A few big quotes, such as a kitchen fitter's | 5 | 25 | 10 | 15 | 5 |
| Staged jobs, such as a renovation with deposits | 10 | 15 | 20 | 10 | 5 |
With many small call-outs, invoicing is the block that overflows, so the better fix is to raise each invoice in the van at the end of the job and let Friday handle only the exceptions. With a few big quotes, spend the extra minutes on the follow-up, since each quote is worth a lot more than one call-out. For staged work, the invoice block checks that each stage invoice matches the milestone you agreed.
How to tell after four weeks that the hour is working
Count four things at the start of each hour and write them in the dump note. They take two minutes and show whether the routine is changing anything.
| Count | Week 1 (illustrative) | Week 4 (illustrative) |
|---|---|---|
| Finished jobs not invoiced for over 7 days | 4 | 0 |
| Open quotes older than 21 days | 3 | 0 (closed or chased) |
| Invoices more than 14 days overdue | 2 | 1 |
| Customer messages unanswered for over 48 hours | 6 | 1 |
If a number does not move, change the block behind it rather than the whole routine. Overdue invoices stuck at two usually mean the reminders are too gentle or too late, so tighten the wording. Messages still piling up usually mean the rules block forces too many "Decision for me" lines, so move the safe ones into the rules. A routine you adjust once a week for a month ends up fitted to your trade in a way no template can be.
What to automate later, and what stays in your hands
Automate a step only when you have done it by hand at least twenty times with near-identical wording, you rarely edit the draft, and a wrong send costs little. That sorts your Friday hour into candidates and keepers.
| Task | Automate when | Keep in your hands |
|---|---|---|
| Quote follow-ups at days 3 and 10 | The wording has stopped changing and your job app can send them | Quotes above your usual size, or with open scope questions |
| Invoice reminders at days 1 and 7 | Your invoicing software can send them from the due date | Anything from day 14, which needs a call |
| Appointment confirmations and "on my way" texts | Straight away, since the risk is low | Changes caused by a problem on site |
| Review requests after a finished job | You have a run of jobs with no complaints | Any customer who raised an issue |
| The Friday dump itself | You have a stable shared inbox for voice notes and photos | The decisions bucket, always |
Complaints, price changes, safety concerns and anything involving fault never go on that automation list. The tutorial on quote follow-ups that run themselves shows one automation worth adding first, and whether a once-a-week task is worth automating at all gives a rule for deciding. Run the manual hour for a month first: you cannot automate a routine whose wording and rules you have not yet found.
Questions about the weekly admin hour
What if I cannot spare a full hour a week?
Start with 25 minutes: the dump and the invoices, because money owed and work not yet billed matter most. Add the quote block in week two and the message block in week three. A short routine you keep doing beats a long one you skip, and the full hour usually settles by itself once the instruction note is in place.
Which AI should I use for this?
Any mainstream chat assistant works, including ChatGPT, Claude, Gemini and Copilot, and each has a free plan good enough to start. Paid plans mostly buy higher limits. Keep the rules block in a ChatGPT Project or a Claude Project so every Friday begins from the same instructions, and keep surnames, addresses and phone numbers out of the chat.
How do I stop the replies sounding robotic?
Paste three real messages you have sent and tell the assistant to match their length and tone. Ban the words you never use, such as exclamation marks or 'kindly', in the rules block. Then edit every draft, even lightly, because customers can tell when nobody has read the message, and your edits are also how you catch promises you cannot keep.
Is it safe to paste customer messages into a chatbot?
Strip names down to first names or letters, and leave out addresses, phone numbers and anything about access to the property. The assistant needs the question and the job, not the identity. Business plans from ChatGPT and Claude do not train on workspace content by default, but a free or personal plan may, so check the data setting first.
Further reads
- AI for Tradies: Eight Admin Jobs to Hand Over Before You Hire Help — Eight admin jobs ranked by how safely AI can take them.
- AI App for Tradies: ServiceM8, Tradify or Fergus by Business Size — Job apps compared by business size, when you outgrow the routine.
- Tradie Apps: Quote, Schedule and Invoice Tools Compared, With AI Features — Quote, schedule and invoice apps with their AI features.
- Best AI for Tradies: Seven Tools by Job, Price and Setup Effort — Seven tools with prices, if you want to pay for help.
- Can an AI Agent Run a Tradie Office? What It Handles Now — What an AI agent can run in a tradie office today.
- How Can AI Help Plumbers? Start With Calls, Quotes or Follow-Up — Whether to start with calls, quotes or follow-up.
- Hourly Rate for a Tradesman: Work Out Yours Without Guessing — Work out what an hour of your time is worth.
- AI Tools and AI Development: The Complete 2026 Guide — the AI hub, including every tutorial in the AI-for-business series.
Sources: vendor plan pages for ChatGPT and Claude on free-plan and Projects availability and on the data defaults of business plans.