12 admin processes Claude can run for you now, from chasing invoices to closing the month.
Each one below comes with a prompt you can copy, fill in the [brackets], and run today. These aren't the tricks you've read a hundred times. These are the jobs that used to eat your Sunday.
36%of the working week goes on admin, 15 to 20 hours. Xero calls it the time tax.
56%of owners say admin is the first thing they'd hand off.
$17,700average sitting in invoices more than 30 days overdue (QuickBooks).
379 hrsa year on regulatory paperwork. Ten full working weeks.
So why hasn't it happened? Because until this year, AI could write. It couldn't do. It could draft the reminder email but it couldn't see which invoices were overdue. It could summarise a contract you pasted in but it couldn't open the contract.
That changed. Claude can now open your files, read your QuickBooks, your Stripe, your Gmail, your calendar, your DocuSign, and run on a schedule while you're not there. It went from a writer to a worker.
One rule
Claude drafts, sorts, flags and files. It doesn't send, post or pay. You approve. Every time.
59% of small businesses carry invoices more than 30 days overdue; the average outstanding is $17,700.
Claude pulls every open invoice, ranks it by how late it is and how that customer has paid before, and drafts a reminder in the right tone. You read the drafts over coffee and send the ones you agree with.
Prompt · fill in the [brackets]
Connect to my QuickBooks (or Stripe) and pull every open invoice.
For each one, work out how many days overdue it is and look at that customer's payment history over the last 12 months (average days to pay, how often they've been late).
Then draft a reminder email for every overdue invoice, matching the tone to the situation:
- 1 to 7 days late: friendly nudge, assume it slipped their mind.
- 8 to 21 days late: firm and specific, quote the invoice number, amount and original due date, and ask for a payment date.
- 22 to 29 days late: firm, mention the next step if unpaid.
- 30+ days late: don't draft to the customer. Write me a short note summarising the account so I can call them.
A customer who is always a few days late gets a lighter touch than one who has never been late before.
Give me a table: customer, invoice number, amount, days overdue, payment history, recommended tone, then the drafts below it. Do not send anything. I will review and send myself.
Ten minutes a week and the overdue pile stops growing.
02
Knowing whether payroll clears
FinanceRuns: Every Monday, 7amConnects: Bank feed, QuickBooks, Stripe
Not 'are we profitable' but 'is there enough in the account on the 28th'.
Claude pulls your cash position, open invoices, bills due and incoming settlements and builds a 30-day forecast with payroll dates marked. If the 28th looks thin, you find out on the 12th.
Prompt · fill in the [brackets]
Every Monday at 7am, build me a 30-day cash forecast and save it as a spreadsheet in [Finance folder]/forecasts/.
Start from my current bank balance(s) from [bank feed / QuickBooks].
Add expected receipts: every open invoice, dated using that customer's average days-to-pay rather than the due date.
Add scheduled payouts from Stripe.
Subtract bills due, recurring subscriptions, loan repayments, tax set-asides, and payroll on [the 28th] at [amount].
Show a running daily balance for the 30 days with payroll dates marked.
If any day drops below [minimum buffer, e.g. $10,000], flag it at the top of the sheet in red: the date, how far below, what's driving it, and 2 or 3 things I could do about it (chase a specific invoice, delay a specific bill).
Finish with a five-line plain-English summary I can read on my phone.
A forecast that rebuilds itself every Monday without being asked.
03
Closing the month
FinanceRuns: MonthlyConnects: QuickBooks, bank feed, Stripe
Owners who do this cut close time by about a third. The accountant stops emailing questions in week two.
Claude reconciles QuickBooks against your bank and payment feeds, flags every mismatch, missing category and duplicate, and puts them in one list of yes/no questions. You answer, it updates the books and writes the summary for your accountant.
Prompt · fill in the [brackets]
It's month-end for [Month YYYY]. Reconcile QuickBooks against my bank feed and Stripe for that period.
Find and list every:
1. Bank deposit or Stripe payout that doesn't match a recorded transaction (show both sides and the difference).
2. Uncategorised transaction, with your best-guess category based on the merchant and my past categorisation.
3. Expense with no receipt attached.
4. Likely duplicate.
Put them in ONE numbered list. For each item, give me your best guess and a question I can answer in one word or a short phrase (e.g. "Uncategorised: $49 to Notion Labs. Software subscription? Y/N").
Wait for my answers. Then apply the categories, mark items as resolved, and write a one-page plain-English summary of the month for my accountant: revenue, cost of sales, major expenses, anything unusual compared with last month, and the open questions that still need a human.
Month-end becomes a list you work through, not a weekend.
04
Writing quotes and proposals
SalesRuns: Per dealConnects: A folder of your price list and best proposals
45 minutes becomes 6, and the quote goes out the same day. Same-day quotes close more.
Give Claude a folder with your price list and your five best proposals that closed. It writes the new one in your structure, priced from your list, in the words the client used on the call.
Prompt · fill in the [brackets]
In [Proposals folder] you'll find price-list.md and five past proposals that closed. Treat them as the template for structure, tone and pricing.
Write a proposal for [Client name] based on these call notes:
[paste notes or attach transcript]
Rules:
- Follow the same section structure as the past proposals.
- Price every line item from price-list.md. Never go below the floor prices listed there, and never invent a service that isn't on the list.
- Describe their problem in the client's own words from the call, not mine.
- Include scope, what's excluded, timeline, price, payment terms and validity period ([14 days]).
- At the end, list every assumption you had to make and anything I should check before sending.
Output as a document I can send today.
Put your price floor in writing or it will discount for you. That's the only real mistake people make with this.
05
Replying to a new lead in the first hour
SalesRuns: ContinuousConnects: Web form or inbox, CRM
A lead answered within the hour is roughly twice as likely to book a meeting as one that waits until tomorrow.
Claude watches the form or the inbox, checks the lead against who your good customers actually are, and drafts the first reply with the right next step already in it. You approve from your phone.
Prompt · fill in the [brackets]
Watch [contact form inbox / leads@ mailbox]. When a new lead arrives:
1. Compare it against my ideal customer profile in [ICP file] and my best current customers in the CRM. Score it High / Medium / Low fit and say why in one line.
2. Draft a first reply in my voice (use [voice examples file]) within 20 minutes of arrival:
- High fit: acknowledge exactly what they asked, answer the one question you can from my FAQ, and include my booking link [link] with two suggested times.
- Medium fit: acknowledge, ask the two qualifying questions that matter most, give a price range from the price list.
- Low fit: polite, warm decline with a referral to [alternative] if appropriate.
3. Create the CRM contact with source, fit score and the lead's original message.
Put the draft in my approval queue and notify me on my phone. Never send it yourself.
A real answer in 20 minutes instead of 'thanks, we'll be in touch' the next morning.
06
The follow-up after a sales call
SalesRuns: Per callConnects: Fathom / Otter transcript, CRM
It's not a time-saver. It's the reason nothing slips.
Paste the notes or the transcript and Claude produces three things: the follow-up email in your voice, the CRM entry with the deal terms filled in, and the task list for your side.
Prompt · fill in the [brackets]
Here is the transcript/notes from my call today with [Name] at [Company]:
[paste or attach]
Produce three things:
1. FOLLOW-UP EMAIL in my voice (see [voice examples]): thank them, recap what we agreed in their words, confirm next steps with owners and dates, and end with the single action I need from them. Under 200 words.
2. CRM ENTRY, ready to paste: company, contact and role, deal value, stage, expected close date, key requirements, objections raised and how I answered them, competitors mentioned, decision process and who else is involved.
3. MY TASK LIST: everything I promised, with due dates. Flag anything I committed to that isn't already in my calendar.
Also tell me in one line: what's the biggest risk to this deal based on the call?
A 30-minute job becomes a 5-minute edit, and the summary actually gets sent.
07
Contracts: reading and signing
Legal & adminRuns: Per contractConnects: DocuSign, contract template, CRM
Contracts that used to take five days to come back take two, and the invoice goes out three days earlier.
Reading: Claude flags the clauses that matter, the auto-renewal, payment terms, liability line, the thing on page 9 you'd have missed. Signing: it generates the contract from your template with the deal terms from the CRM, sends for signature, and reminds on day 1, 3 and 8.
Prompt · fill in the [brackets]
PART A: Read the attached contract [or DocuSign envelope: link].
Give me a first-read summary in this order: parties and term; payment terms; auto-renewal and notice periods; liability, indemnity and caps; termination rights on each side; IP and confidentiality; anything unusual, one-sided or missing. Quote the clause and give the page number for each. Rate each item green / amber / red for a business of my size, and list the three questions I should ask before signing. Say clearly where I need a lawyer rather than you.
PART B: When I say "go", generate our standard agreement from [contract template] using the deal terms from the CRM record for [Company]. Show me the completed draft for approval. Once I approve, send it for signature via DocuSign and remind the signer on day 1, day 3 and day 8 if unsigned. When it's signed, file it in the client folder and start the onboarding checklist.
A very good first read, and a signature chase that runs itself. It isn't a lawyer and it will say so.
08
Onboarding a new client
OperationsRuns: Per new clientConnects: Templates folder, CRM, task list
Every new client gets the same 40 minutes of setup. Now a signed contract triggers all of it.
Claude writes the welcome email in your voice, builds the kickoff doc from your template, creates the client folder with the right structure, and drops the first three tasks in your list.
Prompt · fill in the [brackets]
[Client name] has just signed. Using my templates in [Templates folder] and their details from the CRM and the signed contract:
1. Write the WELCOME EMAIL in my voice: what happens next, who they'll hear from, what I need from them, and the kickoff call link.
2. Build the KICKOFF DOCUMENT from kickoff-template.md: goals as stated in the proposal, scope, timeline, contacts on both sides, and my standard discovery questions.
3. Create the CLIENT FOLDER at [Clients folder]/[Client name]/ with subfolders: 01 Contract, 02 Briefs, 03 Deliverables, 04 Invoices, 05 Notes. File the signed contract and the proposal in it.
4. Add the first three tasks to my task list with due dates: send welcome email, hold kickoff, deliver [first deliverable].
Show me everything for review before anything goes out.
The client folder is the important part. Every later job for that client reads from it.
09
Friday client updates
OperationsRuns: Every Friday, 3pmConnects: Client folders, task list
The most-skipped task in the business, and the one that decides whether they renew.
Claude reads each client's folder, sees what got done this week, and writes the update: what shipped, what's next, what you need from them. Two minutes per client to check.
Prompt · fill in the [brackets]
Every Friday at 3pm, for each active client in [Clients folder]:
Read this week's notes, files added to 03 Deliverables, completed tasks, and any emails from them this week.
Draft a client update email in my voice, under 150 words, with four short sections:
- Done this week
- Next week
- We need from you (or "nothing needed")
- Status: on track / at risk / blocked, with one line of why
Skip any client with no activity this week and tell me instead of drafting something empty.
Put all the drafts in one document, one client per page, in [Clients folder]/updates/YYYY-MM-DD.md so I can review and send in one sitting.
It runs on a Friday schedule so you don't have to remember.
10
The support inbox
Customer serviceRuns: ContinuousConnects: Support mailbox, help docs, customer history
At 25 tickets a day, an 8-minute ticket becoming a 2-minute check is two and a half hours back, every day.
Claude watches the support inbox, reads your help docs and the customer's history, and drafts the reply in your voice. Half your replies are the same six answers; now you check them instead of retyping them.
Prompt · fill in the [brackets]
Watch [support@ mailbox]. For every new ticket:
1. Read the customer's history (past tickets, plan, recent orders) and search my help docs in [Help docs folder].
2. Draft a reply in my voice (see [voice examples]) that answers the question directly in the first sentence, gives the steps if there are any, and links the relevant help article.
3. If it's a bug report, add an internal note with the customer's account details, what they tried, and the steps to reproduce.
4. If it's a refund or cancellation request, add an internal note with their account value and your recommendation against my refund policy in [policy file].
5. If you can't answer confidently from the docs, tag it "needs human" and say what's missing.
Save all drafts for my review. Never send a reply yourself.
At the end of each day, tell me which questions came up more than twice so I can add them to the help docs.
It never sends. You do.
11
The Monday brief
LeadershipRuns: Every Monday, 7amConnects: QuickBooks, Stripe, CRM, calendar, inbox
Build this one first. It's where you notice the shift.
Before you're up, Claude reads QuickBooks, Stripe, your CRM, your calendar and your inbox, and writes one page: cash position, what's overdue, deals that stalled, what's on this week, and the three things that most need you.
Prompt · fill in the [brackets]
Every Monday at 7am, read QuickBooks, Stripe, my CRM, my calendar and my inbox, and write a one-page brief. Save it to [Briefs folder]/YYYY-MM-DD.md.
Sections, in this order, plain language, no filler, under 400 words total:
CASH: current balance, expected in and out this week, and the date of the next tight spot if there is one.
OVERDUE: who owes what and how late, biggest first.
PIPELINE: deals that moved last week, deals that have gone quiet for more than 10 days, and anything due to close this month.
THIS WEEK: meetings, deadlines and deliverables from the calendar and task list, by day.
NEEDS ME: the three things that most need my attention this week, and one line each on why. Exactly three.
If anything is genuinely urgent (payroll at risk, a client escalation, a contract expiring), put it in a single line at the very top before the sections.
In your folder by 7:05. The week is sorted before the first coffee is finished.
Small businesses spend around 379 hours a year on regulatory paperwork. Ten full working weeks.
Claude keeps a folder of every document that matters, answers your own questions from your own policies, and at tax time builds the organiser: what's in, what's missing, what the accountant will ask for.
Prompt · fill in the [brackets]
Maintain an index of the key business documents in [Documents folder]: contracts, staff agreements, policies, licences and permits, insurance, leases, loan agreements, and receipts.
Ongoing:
- Keep index.md up to date: document, what it is, key dates (start, renewal, expiry), where it lives.
- Answer my questions from the documents with a citation to the source file and clause, e.g. "How many holiday days did we agree with Sam?" or "When does our insurance renew?"
- 30 days before any renewal or expiry date, add a reminder to my task list.
Tax time (starting [two months before deadline]):
- Build the tax organiser: everything in the folder that the accountant will need, grouped by the categories in [accountant's checklist].
- List what's MISSING against that checklist, with where it probably is (which bank statement, which supplier).
- List the questions the accountant is likely to ask based on last year's, with draft answers where the documents already contain the answer.
You're not filing my taxes. You're making sure I never spend a Saturday looking for a receipt.
It won't file your taxes. It will mean you're not spending a Saturday in February looking for a receipt from May.
Connect the tools it needs (in Claude: Settings › Connectors) and point it at a folder it can read and write.
Paste the prompt, replace the [brackets], and read the first result critically. It does exactly what you wrote, so adjust the prompt rather than the output.
Once it's reliable, put it on a schedule and keep the approval step. Claude drafts. You send.
Figures cited from Xero's research on the small-business "time tax" and QuickBooks' small-business late-payment survey. Prompts are starting points; adapt the tone, thresholds and folder names to your business. Claude is not a lawyer or accountant and will tell you when you need one.
Prompt copied
Begin your AI transformation.
Book a call with our founders. They'll take the time to understand your needs and how StackAI Lab can help.