AI coworker

Clear the admin bottleneck in a small firm

In a small firm, the skilled work is not usually what fills the week. What fills it is the admin around that work: a quote that has not been followed up, a client who has not sent the records, a customer who has not had an update, a certificate or letter that is ready but has not gone out.

None of those messages is difficult. Together they keep the person who should be on the tools, or on the file, on the chase instead.

Lorework is an AI coworker for that work. It works through the web systems you already use, on its own computer. The wider coworker model is set out on the AI coworker page. If you want a step-by-step way to pick a first job and write the procedure down, use the AI-native checklist. This page is about the bottleneck itself — the repetitive admin that shows up in the same shape across different kinds of firm.

Book a 30-minute demo

The bottleneck is the same shape, even when the documents are different

A practice chasing a client for year-end records, a solicitor updating a buyer on missives, a property factor keeping homeowners informed about a communal repair, or a plumbing or electrical firm following up a quote: the official backdrop is different in each case, and it lives on the industry pages. The office work is recognisably the same.

Someone has to send the first request, notice that nothing has come back, send the reminder, and tell the customer or the client where things have got to — in the firm's usual words, without inventing a deadline the official rules do not set.

That is the work that stacks up. Clearing it does not replace the accountant, the solicitor, the factor or the engineer. It gives that person the time back to do the work only they can do.

What that looks like in practice

In an accountancy practice, the pile is often an unsigned engagement letter at the start of a relationship, or the bank statements and records that later block a return. Those two jobs are spelled out on client onboarding and chasing clients for records.

In a Scottish solicitors' firm, it is the identity documents that hold up a new matter, or the status update a conveyancing client is waiting for — a survey still outstanding, missives still unconcluded, or an application that has gone to Registers of Scotland. See client intake and conveyancing updates.

In a property factor business, it is the homeowner who has not been told where a communal repair has got to, or the file that has to be kept in order if a complaint may later go to the Housing and Property Chamber. See communal repairs and complaints and the written statement of services.

In a plumbing or electrical firm, it is the quote that sits in the sent folder, the on-the-day job update, or the certificate that has been completed but not yet sent to the customer.

The official rules behind each of those jobs — HMRC and ICAS, the Law Society of Scotland and Registers of Scotland, the Property Factors Code of Conduct, Gas Safe, Water Byelaws, BS 7671 and Scottish Building Standards — are on those pages, paraphrased from the primary sources. This page does not repeat them. It is the pattern that is shared: a follow-up, a missing document, a status note, a reminder when something is due again.

What an AI coworker does with that pattern

Your team works with Lorework in chat. You can require approval before it writes or submits anything. Follow-ups, checks and reminders can run as scheduled, recurring tasks.

Typical starting bottlenecks, whatever the trade, are:

A first request or a quote that has gone out, and a follow-up if nothing has come back.
A missing document, access or signature that is blocking the next step on a file.
A short status update to the customer or the client, in the firm's usual words.
A reminder when a service, an inspection or a recurring compliance job is due again, following the timetable the firm already uses.
Recurring checks, such as a weekly sweep of open jobs with no recent update, or of files that are still waiting on someone else.

Lorework does not give legal, tax, health-and-safety or building-standards advice, complete a professional or statutory document, or replace the person who does the underlying work. Those stay with the firm. It takes on the repetitive admin around that work. The limits that apply in each industry are set out on the industry pages above.

How you teach it the way your firm works

You do not have to write a technical specification. Your team teaches Lorework your procedures and templates, in chat, the way you would brief a new starter. You can ask it in chat, or set recurring work on a schedule.

It works in the web systems you already use, on its own computer. There is no need to rip out the diary, practice or job systems you already run.

The AI-native checklist is a practical way to choose that first job, write down how you do it, and decide what still needs a person. This page is the commercial case for clearing the bottleneck; the checklist is the how-to.

How a firm starts

Start with one routine job — one follow-up, one records chase, or one status update — not a wholesale change of tools. Add the procedures and templates Lorework should follow. A 30-minute demo is enough to walk through that job and see how Lorework would take it on.

Book a 30-minute demo

Questions

What admin can an AI coworker take on in a small firm?

It takes on repetitive admin such as following up a quote or a request, chasing a missing document or signature, sending a short status update, and reminding a customer or a client when something is due again. Your team teaches it those processes by chat. It does not replace the professional work, and it does not give legal or tax advice.

Is this the same as the AI-native checklist?

No. The checklist is a how-to: how to pick one routine job, write the procedure down, and decide what still needs a person. This page is the commercial page for the bottleneck itself — the follow-ups and updates that stack up around the skilled work.

Does every kind of firm have the same first job?

No. The documents and the official rules are different. An accountant chasing records, a solicitor updating a conveyancing client, a factor reporting on a communal repair, and a plumber or electrician following up a quote are not the same job. They are the same shape of admin, and that is what Lorework takes on. The industry pages linked above set out the official backdrop for each one.

Will it send messages without anyone checking them?

Your team works with Lorework in chat, and you can require approval before it writes or submits anything. Follow-ups and reminders can run as scheduled, recurring tasks, on the procedures you teach it.

Does it replace the firm's existing software?

No. It works in the web systems you already use, on its own computer. There is no need to rip out the diary, practice or job systems you already run.

How does a firm start?

Start with one routine job, such as a follow-up, a records chase or a status update, not a change of systems. A 30-minute demo is enough to walk through that job and see how Lorework would take it on.