The work that eats your week,
handed over.

Takes a signed enquiry through the whole set-up: welcome email, contract and intake form out, details filed in the right folder, the job created in your tracker, and the kick-off booked.

You approve · The welcome email and contract before they go out.

Reads new enquiries, phone notes and email threads, then updates the record in one place — so the next person to reply is not starting from nothing.

You approve · Nothing routine; corrections to a record it flags as ambiguous.

Reads a folder of invoices, receipts and delivery notes, names each one consistently, files it where it belongs and lists anything it could not identify.

You approve · The naming convention, once — then it applies it.

Checks stock levels against the reorder points you set, drafts the purchase order to each supplier, and holds it for you to confirm quantities.

You approve · Every purchase order before it is sent.

Reads the enquiry, checks your price list and past jobs for anything comparable, and drafts a reply that answers the actual question rather than acknowledging receipt.

You approve · The reply, before it sends.

Prices the job from your rate card, writes the quote with the scope spelled out, attaches the terms, and sends it once you approve — then logs it as outstanding.

You approve · The price and the scope on every quote.

Finds every quote sent more than a week ago with no answer, drafts a short follow-up appropriate to each one, and stops chasing the moment someone replies.

You approve · The follow-up schedule, and each first message in a new sequence.

Before a call, pulls together who they are, what they have bought, what is outstanding and what was last said — one page, in your inbox, in time to read it.

You approve · Nothing — it only reads and reports.

Sorts overnight mail into what needs you, what needs an answer it can write, and what needs filing — with the routine answers already drafted in your tone.

You approve · Every drafted reply. Kaer never sends as you without approval.

Reads your returns policy, warranty terms and past decisions before answering, so the customer gets the answer your business actually gives.

You approve · Any reply that departs from a documented policy.

Looks the order up in your storefront or system, checks the shipping status, and answers with a real date instead of a holding message.

You approve · Replies that carry a delay, a refund or an apology with money attached.

Spots the complaint, the cancellation risk and the enquiry that has been waiting too long, and puts them in front of a person with the history attached.

You approve · Nothing — escalation is the output.

Works the aged debt list from the top: a reminder at seven days, a firmer one at thirty, a note to you before anything harder — each one matched to the customer relationship.

You approve · The tone ladder, and any message past the second reminder.

Finds the jobs marked done that have not been billed, raises each invoice against the right rates, and queues them for you to release.

You approve · Every invoice before it is issued.

Matches payments against outstanding invoices across your payment tools and accounts, and gives you a short list of what did not match.

You approve · Nothing to reconcile; write-offs and adjustments stay with you.

Assembles the numbers your accountant asks for every month — takings, outstanding, spend by category, anything unusual — into the same format each time.

You approve · The pack before it goes to your accountant.

Works the list of customers due a visit, offers times that fit the existing route and your working hours, and books what gets accepted.

You approve · The available hours and the booking rules; then it books.

Sends the reminder at the interval that works for your customers, handles the reschedules that come back, and tells you what freed up.

You approve · Cancellations that carry a charge.

When a slot falls out, finds who is on the waiting list or overdue a visit, offers it to them in order, and confirms the first to accept.

You approve · Nothing, within the rules you set.

Reads what comparable suppliers are charging and how they package it, and comes back with a summary and the sources — not a confident guess.

You approve · Nothing — it reads and reports.

Takes a list of company names and fills in what is publicly known — size, sector, who to contact, whether they are a fit — flagging the ones it could not verify.

You approve · Nothing to gather; any outreach is a separate approval.

Searches for suppliers, tenders or funding that match your criteria, checks the deadlines, and gives you the shortlist with what each one requires.

You approve · Nothing — applications and enquiries need your sign-off.

Pulls the same numbers from the same places every week, writes the commentary on what changed, and has it in the right inbox before the meeting.

You approve · The first run. After that it runs on schedule.

Runs through the checklist your industry requires, gathers the evidence, records what passed, and raises what did not with the detail attached.

You approve · Any exception it records as a failure.

Watches contracts, insurance, certifications and subscriptions, and gives you notice far enough ahead to do something about it.

You approve · Nothing to watch; every renewal decision is yours.

Collects the timesheets, chases the missing ones, checks them against the rota, and puts the file together for whoever runs payroll.

You approve · The final file, and any timesheet it had to correct.

Describe the tracker your team keeps re-creating and get a working internal tool, with the right people able to use it, on the same day.

You approve · The tool before you share it with the team.

Adds the form, wires it to your calendar and your inbox, and tests the whole path end to end before it goes anywhere near your live site.

You approve · The change before it is published.

Moves the data between the tools you already pay for — orders into the tracker, enquiries into the customer record — on a schedule, with failures reported.

You approve · The mapping, once; then the sync runs.

For teams that write software: reads the repository, makes the change, runs your tests, and opens a pull request a person reviews and merges.

You approve · The pull request. Nothing merges without a human.

Dependency bumps, test coverage on the untested module, the migration everyone keeps deferring — done as reviewable pull requests, not as a sprint.

You approve · Every pull request, and anything touching production data.