Somewhere around the point where the owner is answering enquiries at 10pm and doing invoices on Sunday, it becomes obvious the business needs help. Lately a second thought follows close behind: maybe that help does not have to be a person.
Software vendors will tell you it does not. Recruitment agencies will tell you it does. Both are describing their own product.
The honest answer to ai employee vs hiring depends almost entirely on what the hours are being spent on, and most owners have not measured that. So this piece starts there, then gives you a way to decide.
What a part-time admin actually does all week
Ask a small firm to describe its admin role and you get "answering enquiries". Watch the role for a fortnight and it looks quite different. A typical part-time admin in a service business spends time on things like:
- Phone calls, including suppliers, existing customers and the occasional wrong number.
- Email and website enquiries, answering questions and passing on new work.
- Diary management, confirming appointments and rearranging them.
- Chasing, whether that is unpaid invoices, missing paperwork or a customer who never confirmed.
- Data entry, updating job sheets, the CRM or the accounts package.
- Judgement calls, like spotting that a customer is upset, or that a job is outside what you do.
A website assistant can take only one of those rows properly, and part of another. That is not a criticism. It is a different shape of job.
Where they overlap, and where they do not
| Task | Website assistant | Part-time admin |
|---|---|---|
| Answering website questions at 9pm on a Saturday | Yes, instantly | No, unless you pay for those hours |
| Answering the phone | No | Yes |
| Taking details of a new enquiry from the website | Yes | Yes, during working hours |
| Capturing a booking request with details attached | Yes, for someone to confirm | Yes, and can confirm it in the diary |
| Chasing unpaid invoices | No | Yes |
| Entering data into your systems | Only by passing lead data on via a webhook | Yes |
| Handling an upset customer | Can take details and hand over | Yes, with judgement |
| Answering the same pricing question for the tenth time today | Yes, without tiring of it | Yes, less cheerfully |
The overlap is the middle of the table: website enquiries during office hours. Everything above it is the assistant's advantage (hours and speed), and everything below it belongs to a person.
A point of accuracy that matters here. SpideyChat works on your website only. It does not answer calls. If your enquiries mostly arrive by phone, a website assistant will not solve that, and you should look at phone answering options separately. AI receptionist vs phone answering service compares those.
The questions that decide it
Run through these with your own numbers.
- Where do new enquiries arrive? Mostly website and forms points towards the assistant. Mostly phone points towards a person.
- When do they arrive? A large share outside office hours favours the assistant, because a part-time hire will not be there either.
- How repetitive are they? If most questions are the same dozen, an assistant handles them well. If every enquiry is a bespoke conversation, less so.
- What else is piling up? If invoices, paperwork and diary management are the real burden, no website assistant will touch them.
A worked example you can redo with your figures
This is illustrative. Replace every number with your own.
Say a kitchen fitting firm logs its admin for two weeks and finds 20 hours a week of admin work. Of that, 6 hours is answering website and email enquiries, 5 hours is phone calls, 4 hours is diary juggling and 5 hours is invoicing and paperwork. It also notices that around a third of website enquiries arrive in the evening and wait until the next morning.
A website assistant could plausibly absorb a good share of the 6 enquiry hours and cover the evening gap, at a flat software cost. Starter on SpideyChat, for instance, is $20 a month, and current plans are on the pricing page. It would do nothing for the other 14 hours.
A part-time admin at your local hourly rate for 20 hours would cover all of it during working hours, but none of the evening enquiries.
So the firm's real choice is not either/or. It is: hire someone for around 14 to 16 hours, and let the assistant cover website enquiries and evenings. The chatbot ROI calculator is a quick way to run your own version.
When you need both
Many firms end up here, and it is a good outcome rather than a compromise. The assistant handles the repetitive website questions and captures enquiries at any hour. The admin starts the morning with a clean list of named leads with details attached, instead of a stack of half-finished contact forms, and spends their time on calls, chasing and the judgement calls software should not make.
It also makes the human role better to hold. Nobody takes a job hoping to type out opening hours thirty times a week.
There is one order-of-operations point worth making. If you hire first, the new person will spend their early weeks absorbing the repetitive website questions, and the job will be shaped around them. If you add the assistant first, you find out how much of that work was ever really a person's job, and you can write a tighter advert for the rest. Neither order is wrong, but the second tends to produce a clearer role and fewer surprises about how many hours you actually need.
What to do this week
Before talking to a recruiter or signing up for anything, keep a simple log for ten working days. Every admin task, roughly how long it took, and whether it came from the website, the phone or elsewhere. Also note how many website enquiries arrived out of hours.
At the end, sort the log into the rows of the table above. If the website rows dominate, test an assistant first; the free plan is enough to see how it handles your real questions. If the phone and paperwork rows dominate, write the job advert. If both are heavy, you already know the answer, and the cheapest way to cover after-hours enquiries is worth reading before you decide how to handle evenings.