A business owner knows the payroll service is poor. Payslips arrive late, questions go unanswered and a mistake last year took three months to unwind. She has not changed provider because the thought of staff not being paid correctly is worse than the current situation.
Payroll is bought on fear, and the enquiry is really asking whether the change will be safe.
What businesses ask
They usually ask how the transfer works, when they can switch, whether data is moved across, who handles the changeover month, what happens to year-to-date figures, whether staff will notice, what it costs per employee, whether pension submissions are included, how payslips are delivered and who they contact when something is wrong.
Explain the transfer plainly
Employee records, year-to-date figures, pension details and submission credentials move across. Explaining that the outgoing provider is contacted, that a parallel check is run and that nothing goes live until figures match is what removes the fear.
Timing is less restrictive than people think
Many businesses believe they must wait for the tax year. Explaining that mid-year transfers are routine, with the right data, converts businesses that were prepared to endure another nine months.
Example conversations
These scripts use information a provider might publish. Your answers should come from your own pages.
Owner: I want to switch but I am terrified of a mistake with staff pay. Assistant: That is the most common concern. The transfer page explains how employee and year-to-date data are moved, the parallel check run before the first live pay run and who handles submissions in the changeover month. Could you tell me how many employees you have and whether you pay weekly or monthly?
Owner: What does it cost? Assistant: The pricing page shows the monthly charge per employee, with the minimum charge for smaller teams and what is included, such as payslips, submissions and pension filing.
Owner: Who do we contact when there is a problem? Assistant: The page explains that each client has a named contact, with the response times shown, and how urgent pay run issues are handled.
A named person matters more than software
Payroll problems are urgent and specific. Businesses want to know who answers, not which system is used. Publishing a named contact arrangement and response times is a stronger selling point than any feature list.
Parallel running removes the last doubt
Running one pay period through both the old and new system, and comparing the figures line by line before anything goes live, is what turns a frightening switch into an administrative task. Explaining that you do this, and that the business sees the comparison before approving it, answers the fear directly rather than asking an owner to trust a promise.
What is included and what is not
Starters and leavers, statutory payments, pension submissions, year-end documents, holiday calculations and any charge for additional pay runs. Unclear inclusions are where payroll relationships sour.
Never advise on employment matters
Questions about entitlements, dismissals, holiday disputes and contracts are employment advice, as described in HR help enquiries from small employers with a problem today and retainer and project questions for HR consultancies.
Switching generally
Buyers fear transitions in every service, which is the pattern in switching and new connection questions for providers, and capture at any hour matters for busy owners, as in AI receptionist for childcare and nurseries.
Getting started
Publish your transfer process, per-employee pricing, inclusions and contact arrangements, then capture headcount at any hour. SpideyChat for consultancies answers from your published pages. Try SpideyChat on your own site, or read about answers on the features page.