Local guides · Post 5
What a small accountancy or letting firm in Ceredigion can safely hand to AI
For accountancy and letting firms in Ceredigion: which parts of the week AI can safely take, where the line sits, and why the line never moves for client money.
It's Monday morning in a small practice, in Cardigan or Aberystwyth or anywhere in between. The same chase list is open: clients who haven't sent records, landlords whose certificates need renewing, replies that all say slightly different versions of the same thing. The work that earns the fee sits behind it, waiting.
The question a small firm asks first is not "what can AI do". It's "what can it safely take". For a practice, the safe line matters more than the speed, because a wrong filing or a wrong answer costs more than an hour ever saved.
The maths (a sketch, not a client figure)
Take the chase-and-type layer of a small practice's week: record chases, routine replies, data entry, deadline reminders.
- × 6 hours a week across the team = the time cost
- × £30 an hour = £180 a week
- × 46 working weeks = £8,280 a year
Now the same work with a draft step. Software prepares the chases, the replies and the entries, and a named person checks and approves:
- About 1.5 hours a week of approving, instead of 6 hours of composing and retyping.
The value isn't only the hours. Chases that go out on rhythm collect records faster, which moves the deadline work earlier and calmer.
Score it: the three checks
- Hours. Four or more hours of someone's week, every week. The record chase alone usually clears it.
- Repeat. Could a new starter run the chase from one written page? Practices that can write the page can automate the chase.
- Risk-if-wrong. This is where the line is drawn. A duplicate reminder is recoverable. A wrong figure in a filing is not. High-risk work stays human.
Try one thing this week (free)
Write the record-chase page. Which clients, what documents, what day of the week the chase goes out, what the reminder says. Run it by hand once, exactly as written. That page is the spec: it shows the hours the chase really takes and proves whether the job is writable. Most firms find the chase is bigger on paper than in their head, which is exactly why it keeps slipping.
Where a person stays
The safe line, stated plainly. Safe to hand over with approval: chasing clients for records, drafting routine replies, typing data from one place to another, reminding about deadlines, assembling the papers for a job. Never handed over: filings and submissions, tax positions and advice, anything touching client money, anything compliance-shaped. Those stay with a qualified human from start to finish. The software may prepare the papers and watch the dates, and a person does the act.
Beyond that line, everything starts as a draft. A named person approves, and nothing sends unchecked. Anything that touches a filing, a payment or a client's money stays approval-only, permanently, in every configuration. The approvals are logged, so the firm can always show who checked what. The judgement stays in the firm. The retyping, the chasing and the remembering leave it.
FAQ
No. Money movement, filings and anything with legal weight stay with a person, always. The software's job is preparing and watching, and the person's job is deciding.
The software watches the calendar and prepares reminders and papers ahead of each date. The submission itself is made by a person. A deadline is the one thing that should never depend on memory.
They'll notice the chases arrive on time, every week, in plain English. The drafts go out in the firm's own words after a person approves them. What clients never see is a message nobody read first.
The design assumes a small team with more work than hands. Start with the one chase that repeats most, watch it for a fortnight, then decide. One job handed over well beats five handed over badly.
The £499 diagnostic. One fixed fee: a one-hour discovery call, a written report ranking what to hand over first, and a follow-up call. 5 hours a week found or a full refund, and every pound credits against any build.