Why software employees leave and how to understand why
Engineers and product staff leave for many reasons beyond salary. How to run an exit conversation in a software company, read the pattern and act on it.
6 min readRead articleAn accounting software provider sells to accountants, traders and small businesses who expect the product to be right at filing time. Here is how to organise developers, domain experts and support teams around year-end pressure.

Not sure what you need? Tell us about your business in six short steps and we will come to the first meeting prepared.
Share your requirementsAn accounting software provider builds and sells products for bookkeeping, invoicing, GST-style tax returns, inventory, payroll and reports, used by accountants, shopkeepers, traders and small firms. Its people include developers, testers, accountants who act as domain experts, implementation consultants, support agents, trainers, a sales and partner team and sometimes reseller managers in several cities. Customers rely on the product at moments with no room for error: month-end, quarter-end, tax filing dates and year-end closing. When the rules change, a release must reach customers on time, so engineering, domain and support teams go into crunch together. Support agents answer calls and chats from users who may be anxious accountants. Knowledge of accounting practice, not only code, decides the quality of work. Resellers and partners hold customer relationships and need training. Product knowledge is held by a few long-serving staff. See also HR for IT and software companies.
These are the places the people side of this kind of business tends to give way. The rest of this page works through them.
HR here has to work for each of these groups, not only the office. The set-up below is written with all of them in mind.
GullyHR runs talent acquisition for permanent roles in accounting software providers. For each role we agree the job description with you, find and screen candidates against it, and support the offer through to joining. Tell us the role and the number of people, and we start there.
We recruit permanent employees. We do not supply contract or temporary staff.
Every business interviews, but few have a written process that works the same way for every role and every interviewer. GullyHR designs yours, from the role brief to the offer, trains your managers to run it, and can run it for you on the roles you hand us.
We agree what the role must deliver, the must-have and nice-to-have skills, and how each will be scored.
Screening call, assessment, interview rounds and decision points, sized to the role and the number of people you hire.
Structured questions for each role family and a rating guide, so two interviewers judge the same answer the same way.
A short briefing for your managers on what to ask, what to avoid and how to give a clear yes or no.
Who approves, how the offer is made, and how candidates are kept informed from first call to joining.
A regulatory change arrives with a deadline, and developers, testers and domain staff work nights and weekends with no plan for rest or recognition.
One or two accountants know how the tax rules map to the product, and the team is stuck when they are away or leave.
Call volumes jump at filing time, and agents face upset users, long queues and targets that ignore the complexity of calls.
Requirements are lost between accountants who describe a rule and developers who build it, leading to defects found by customers.
Qualified accountants joining a software company struggle with agile ways of working, and developers undervalue their input.
Resellers sell and set up the product but are poorly trained, and the provider is blamed for their mistakes.
Staff see customers' financial data during support, and rules on access, remote sessions and confidentiality are loose.
The same people carry each crunch, and after the season the best ones start looking at other companies.
Start with the topics that matter most here: HR Analytics and Management Reporting; Learning and Development; Retention and Attrition Management. Then work through the rest. Each topic is written for information technology and software, not in general.
A short monthly pack management actually reads.
Training planned from need rather than from the calendar.
Who leaves, when, why — and which of them mattered.
How many people, in which roles, by when — and what they will cost.
Structure, reporting lines and who is allowed to decide what.
Requisition to joining, the same way every time.
A first day that is the same for the fifth joiner as the first.
Records, attendance, leave and the day-to-day HR that must simply work.
Salary structure, payroll inputs and a month that closes on time.
Goals, reviews and ratings that hold up in a conversation.
Named backups for the roles that cannot be vacant.
Communication, recognition and the conditions people actually work in.
Two routes — one for complaints, one for conduct — kept separate.
Policies a manager can apply, and obligations with owners and dates.
Induction, records, incident reporting and follow-through.
Resignation to relieving letter, in a defined order.
Records that survive people, and approvals that do not queue.
An HR function that runs the same way every month.
The pieces a accounting software providers business puts in place, in an order that makes each easier. Open any card for the detail.
A calendar of known tax and regulatory dates, staffing plan, rest rules and compensation for extra hours.
A calendar of known tax and regulatory dates, staffing plan, rest rules and compensation for extra hours. See the attendance, shift and leave process.
Documented rules, pairing between accountants and developers and a bench of cross-trained staff.
Documented rules, pairing between accountants and developers and a bench of cross-trained staff. The learning and development process can guide this.
Temporary agents, triage by issue type, scripts for common questions and fair targets in peak weeks.
Temporary agents, triage by issue type, scripts for common questions and fair targets in peak weeks.
A short template and review meeting between domain and engineering for every rule change.
A short template and review meeting between domain and engineering for every rule change.
A certification path for resellers and implementers, with feedback to the provider.
A certification path for resellers and implementers, with feedback to the provider.
Access limits, session recording where lawful, confidentiality undertakings and clear exit steps.
Access limits, session recording where lawful, confidentiality undertakings and clear exit steps. See the employee information management guidance and confirm with a qualified professional.
Before changing anything, find out what is true today. These checks take an afternoon and tell you which of the topics above to start with.
Share your requirementsConfirm with a qualified professional. What applies to you depends on your business, your state and your arrangements, and it changes. This page describes practice. It does not state a legal position.
The services below fit this kind of business best. Each starts by recording where you stand, and every later report compares against that. We do not promise outcomes.
Release crunch rotas with rest and fair extra-hours handling.
Cross-training between domain experts, developers and support.
Targets for support and engineering that reflect seasonal peaks.
Controlled access to staff and customer-related data.
Start with a free conversation, or see the paid HR Diagnostic.
Understand the business, its workforce, current processes and HR challenges.
Find the missing, weak, inconsistent or person-dependent processes.
Create the structure, processes, policies, SOPs, dashboards and systems needed.
Help HR and department managers actually adopt the new system.
Digitise repetitive and approval-based workflows where it is worth doing.
Track hiring, attendance, employee cost, performance, training and attrition.
Strengthen the people-management system continuously, not once.
From the GullyHR blog: one on HR in information technology and software, and one on each of the topics this page points to.

Engineers and product staff leave for many reasons beyond salary. How to run an exit conversation in a software company, read the pattern and act on it.
6 min readRead article
Six numbers, one page, same format each month. What they are, how to define them so they mean the same thing twice, and what each one tells you.
8 min readRead article
A founder's guide to hiring freshers and running a first-year programme: campus or open drives, a screening round, a training plan by quarter, mentors and checkpoints.
6 min readRead article
What really keeps mobile app and web developers in a small firm: stay conversations, growth paths, fair release rules and a risk sheet an owner can use this month.
6 min readRead articleMore on the GullyHR blog.
Plan ahead, add temporary help, set rest after peaks and spread the work among more people than the usual few.
Document rules, pair people on changes, rotate tasks and recognise the experts in role and pay.
Adjust targets for volume and complexity, and measure resolution quality as well as speed.
Give them a seat in product planning, share the language of agile work and respect their domain judgement.
Set expectations in the partner agreement, train and test their staff, and track recurring issues together. Ask a qualified professional about contract terms.
We would ask how release crunch is handled, who holds the accounting rules and how support copes at filing time. A sensible first piece of work is a seasonal staffing plan, a cross-training plan and fairer peak-season targets. Scope and fees are agreed in writing afterwards.
All 61 business types in information technology and software · Find another business type
See all HR topics for information technology and software, or another industry.
Tell us what is slowing your team down. We’ll help you find a practical way forward, starting with a conversation.