What buyers ask AI before choosing a payroll provider

Buyers usually arrive with a statutory question rather than a vendor question: a professional tax slab, a provident fund rule, a Form 16 deadline. Then they ask whether to buy software or outsource, what it costs per employee, and who is responsible if a filing is late.

The questions, in the words buyers use

The statutory questions that bring them

• "Professional tax deduction for salaries in this state"
• "Is PF applicable above the wage ceiling, and what is voluntary coverage"
• "ESIC applicability, which employees are covered"
• "Gratuity eligibility and how it is calculated"
• "Form 16 and Form 24Q deadlines"
• "Employee joined mid year with two Form 16s, how is tax computed"
• "Leave encashment and notice pay, how are they taxed"

Software or service

• "Payroll software or outsourced payroll, which is better for us"
• "Can our chartered accountant just do payroll"
• "What does a payroll bureau actually do each month"
• "Does it integrate with our accounting and attendance systems"

Cost

• "Payroll processing cost per employee per month"
• "Is there a minimum billing for a small team"
• "Setup and implementation charges"
• "What is extra: full and final settlements, reimbursements, multiple states"

Risk and special cases

• "Who pays the penalty for a late PF challan"
• "What if the provider makes a tax error"
• "Is our salary data safe and where is it stored"
• "Paying employees in India with no local entity"
• "Employees across several states, what changes"
• "Contractors versus employees, how do we classify them"

What a good answer looks like

Answer each statutory question as its own page, with the rule, the section or notification it comes from, the official link and the date you checked. Then, at the end, say what you do. A page that answers the question properly earns the citation; a page that turns the question into a sales pitch does not.

On cost, publish the price with its conditions. On responsibility, be honest: the employer remains liable to the department, and what you offer is accuracy, review, and whatever indemnity your contract actually provides. State the indemnity rather than implying it.

On the employer of record question, say plainly who the legal employer is, who signs the employment contract, and what happens to the employee if the client ends the arrangement. Buyers looking for this are usually foreign and are entirely dependent on your explanation.

Where you are probably missing

• No statutory content, so every query in the first group goes to a software vendor's blog.
• No pricing, in a category where the competition publishes it.
• No scope boundary, so buyers cannot tell what you will not do.
• Nothing about data protection, although salary data is the most sensitive file in the company.
• Undated pages, which is serious here because rates and thresholds change and a stale page is worse than none.
• Nothing for the employer of record buyer, a growing and well paid query.

What to publish first

• One page per statutory question above, dated, with the official source linked.
• A price page per employee per month, with minimums and extras.
• A scope page listing what you file and what you do not.
• A data protection page: storage, access, retention, exit.
• A state by state compliance calendar, updated on a fixed day each month.

The compliance calendar is the page HR teams will return to every month, and a page people return to is a page that keeps being cited.

A worked example of a statutory page

Take the question of a mid year joiner with two Form 16 documents, which is asked every year and answered badly. Here is the complete shape.

State the situation: an employee leaves one employer in the middle of the financial year and joins another, so two employers have each deducted tax on the salary they paid. Then explain the mechanism: unless the employee declares the previous salary to the new employer, the new employer computes tax only on the salary it pays, applies the exemption limit and the deductions a second time, and the employee ends the year with a shortfall.

Then give the steps. The employee declares previous employment income to the new employer using the prescribed declaration. The new employer includes that income and the tax already deducted when computing tax for the rest of the year. If the declaration is not made, the shortfall must be paid at the time of filing the return, with interest. Name what the employee should collect from the previous employer: the Form 16, the full and final settlement statement, and the provident fund details.

Finish with what the employer should do: ask for the declaration at joining, not in January, and explain why to the employee in one line. Add the caution that the choice of tax regime and the treatment of specific allowances need checking for the individual, and that this page is a process explanation rather than personal tax advice.

That page is short, it is correct, it is dated, and it answers a question that brings a stressed HR executive to your website at exactly the moment they are wondering whether to outsource payroll.

What these questions do not include

They do not include software feature comparisons early on. Buyers get there, but only after they have decided between buying a tool and buying a service.

They also do not include anything you can guarantee away. Accuracy, review and indemnity are real offers. Removing the employer's own liability to the department is not, and stating the limit plainly is what makes the rest of your promises credible.

And they do not include advice to individual employees. Your client is the employer. Questions about a single employee's tax position belong with that employee's own adviser, and saying so is a professional boundary rather than an evasion.

Common questions

Which statutory page should we write first?

The professional tax page for the states your clients operate in, because it changes by state, it is looked up constantly, and the existing answers are often wrong or out of date.

Should we answer the question about whether a chartered accountant can do payroll?

Yes, honestly. Many accountants do it well for small headcounts. Say where a bureau adds something: a system of record, payslips employees can access, statutory filings on a calendar, and cover when one person is on leave. That comparison is the buyer's real decision.

How do we answer the question about who pays a penalty?

Plainly. The employer is liable to the department. Then state what your contract provides if the error was yours, what evidence is kept, and how quickly a correction is filed. A stated position is trusted; silence is assumed to be unfavourable.

Buyers keep asking about data security. What convinces them?

Specifics: where the data is hosted, whether access to salary figures is restricted by role, who inside your team can see it, whether actions are logged, what certification you hold and its scope, how long you keep data after a client leaves, and how a client gets an export on exit.

Is the employer of record question worth building pages for?

If you actually offer it, yes, and it is one of the better paid enquiries available. If you do not offer it, write one page explaining the options honestly, because the buyer who reads it may still need ordinary payroll next year.

What to do first

Write the professional tax page for your largest client state, dated and sourced, and publish your price beside it. One answers the query that brings buyers in, and the other decides whether they stay.