Why software employees leave and how to understand why
Engineers and product staff leave for reasons beyond salary. How to run an exit conversation in a software company, read the pattern and act on it.
6 min readRead articleA subscription software business lives on renewals. Support, customer success and engineering staff are judged by whether customers stay, so how the team is hired, paid and kept shows up directly in churn.

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 requirementsA subscription software business sells access by the month or year and earns by keeping customers. The team splits into engineers who build and fix, support staff who answer tickets, customer success managers who guard renewals, sales staff who bring new accounts and a small back office. Work arrives in a steady stream rather than a project, so the same people deal with the same customers for years. A good support lead knows which accounts are restless. A new customer success manager takes months to learn the product and the accounts. Pay mixes a fixed part with incentives tied to renewals or upgrades, which makes goals and fairness matter. See the IT and software hub and the SaaS and product hub for the wider picture.
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 subscription software businesses. 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.
Ticket volume rises after every release, and agents absorb frustration from customers while engineers sit far from it.
A customer success manager is given a list of accounts, some of which were lost the day they signed, and judged on the whole.
Product knowledge, customer history and internal tools take time to learn, and a poor first month shows in churn.
Upgrades, renewals and referrals are credited in different ways, and people argue over who earned a result.
An agent who is excellent has no clear step to lead, success or product roles, so the best ones leave.
What the customer was promised is not passed on, and the first service call begins with an argument.
Because the business is steady, small signs of unhappiness go unnoticed until several people leave together.
Start with the topics that matter most here: Onboarding and Probation; Retention and Attrition Management; Learning and Development. Then work through the rest. Each topic is written for information technology and software, not in general.
A first day that is the same for the fifth joiner as the first.
Who leaves, when, why, and which of them mattered.
Training planned from need rather than from the calendar.
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.
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.
A short monthly pack management actually reads.
An HR function that runs the same way every month.
The pieces a subscription software businesses business puts in place, in an order that makes each easier. Open any card for the detail.
For support, success and onboarding roles, state what each owns, the response times expected and who they hand to.
For support, success and onboarding roles, state what each owns, the response times expected and who they hand to. See role design.
A structured first fortnight covering the product, the customers, the tools and shadowing, with a check at the end.
A structured first fortnight covering the product, the customers, the tools and shadowing, with a check at the end. The onboarding process sets it out.
Assign accounts with their history noted, so goals reflect the starting point and not only the final count.
Assign accounts with their history noted, so goals reflect the starting point and not only the final count.
Who gets credit for a renewal or upgrade, how ties are settled and when payment is made, on one page.
Who gets credit for a renewal or upgrade, how ties are settled and when payment is made, on one page.
A path from agent to senior agent, lead, success manager or product specialist, with skills at each step.
A path from agent to senior agent, lead, success manager or product specialist, with skills at each step.
A short note and a call for every new account on promises made and the customer's goals.
A short note and a call for every new account on promises made and the customer's goals.
Before changing anything, find out what is true today. Work through the checks using a recent operating period. The time needed depends on the records you hold; note missing evidence and use the findings to choose a priority.
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.
A first-fortnight route for support, success and implementation staff to reach useful work sooner.
Clear roles for support, customer success and onboarding, so handovers stop dropping detail.
Practical training for agents and success managers on handling frustrated customers and renewals.
Simple people numbers that show where staff leave and how long new joiners take to settle.
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 reasons beyond salary. How to run an exit conversation in a software company, read the pattern and act on it.
6 min readRead article
A first-week plan for bringing in an outside specialist: what access to give, how to protect client data, and the confidentiality steps to settle on day one.
7 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 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 articleMore on the GullyHR blog.
There is no fixed number. It depends on account size, how hands-on each customer is and the mix of renewal and upgrade work. Look at your own time records, then test a figure with one team before rolling it out.
They work better with a clear line between them and a good handover. Support solves problems now, success guards the long-term outcome. Either way, agree who owns the customer when both are involved.
Start from account health and history, not only the total. Give people a mix of safe and difficult accounts, and review goals when a major customer leaves for reasons outside the person's control.
A week of product learning, a week of shadowing, supervised tickets with feedback and a review at the end. Give a named buddy. The aim is confidence with real customers, not speed on day ten.
Show a path upward, pay fairly for skill and recognise the work in front of the team. Some leave because the next step is invisible. A written ladder and honest talk about it help more than a small raise.
We would count how many support and success staff joined and left last year, read the incentive rules with two people and trace five lost accounts for handover gaps. A role ladder plus a first-fortnight programme is a natural start, with scope written down for your approval.
All 6 business types in SaaS & product companies · Find another business type
See all HR topics for information technology and software, or another industry.
Tell us your industry, team size and the issue you want to address. Bring one example of where work gets delayed or ownership is unclear, and the deadline or decision you are working towards.