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 enterprise SaaS company sells to large organisations through long deals, deep onboarding and named account teams. Its pay, hiring and succession choices rest on a few people whom big customers know and trust.

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 enterprise SaaS company sells subscription software to large organisations, where a deal takes many months and many meetings. A sales lead is supported by solution consultants, a customer success owner and implementation staff who spend weeks inside the customer's premises or calls. Engineers handle security reviews, integrations and custom requests. Customers often know the people by name and ask for them when renewals approach. Losing one senior seller, solution architect or account owner can put an account at risk. The wider IT and software hub and the SaaS and product hub cover what these firms share.
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.
A seller can go many months without closing, and managers cannot tell if the deal is slow or the person is struggling.
Large accounts ask for a certain solution architect or owner, which creates dependence and makes any transfer delicate.
Proposal weeks and go-live weeks bring long hours, then a lull, and credit goes to the seller who closed.
Quotas, accelerators, splits and territory changes create disputes, and each year's plan seems to leave someone unhappy.
Weeks at a customer's office strain families, and the firm's rules on travel, rest and leave vary from project to project.
No one knows who would cover a regional head or a lead architect, and the answer emerges only after a resignation.
Work behind the scenes, such as security answers and integration fixes, is overlooked when ratings are set.
Start with the topics that matter most here: Career and Succession Management; Compensation, Payroll and Benefits; Employee Relations. Then work through the rest. Each topic is written for information technology and software, not in general.
Named backups for the roles that cannot be vacant.
Salary structure, payroll inputs and a month that closes on time.
Two routes — one for complaints, one for conduct — kept separate.
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.
Goals, reviews and ratings that hold up in a conversation.
Training planned from need rather than from the calendar.
Communication, recognition and the conditions people actually work in.
Policies a manager can apply, and obligations with owners and dates.
Induction, records, incident reporting and follow-through.
Who leaves, when, why — and which of them mattered.
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 enterprise SaaS business puts in place, in an order that makes each easier. Open any card for the detail.
Compare structure, mix of fixed and variable pay and ranges for each senior role.
What this coversHideCompare structure, mix of fixed and variable pay and ranges for each senior role. Compensation benchmarking gives a method.
For each critical role, name a ready successor, a possible one in a year and the risk if the person left.
What this coversHideFor each critical role, name a ready successor, a possible one in a year and the risk if the person left. Succession planning sets out the steps.
Travel days, rest, allowances and leave around go-live, written once and applied the same way across projects.
What this coversHideTravel days, rest, allowances and leave around go-live, written once and applied the same way across projects.
Pair each large account with a second named person, so relationships do not rest on one individual.
What this coversHidePair each large account with a second named person, so relationships do not rest on one individual.
Add security, integration and escalation work to the review format.
What this coversHideAdd security, integration and escalation work to the review format. See performance management.
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.
Training for account owners and support staff who handle senior customer contacts.
Senior sales, solution and delivery pay set against comparable firms.
Named cover for key roles, so large accounts do not depend on one person.
Reviews that credit the work customers never see.
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
A two-hour exercise that names the roles you could not fill quickly, who could cover them, and what readiness would actually require.
7 min readRead article
How to design incentives for operators, setters and inspectors in fastener, gear, spring and valve units so that accepted lots, not piece counts, earn the bonus.
7 min readRead article
An employee brings you a complaint about their supervisor. What happens next should not depend on who is in the room. A grievance procedure a small company can actually run.
8 min readRead articleMore on the GullyHR blog.
Name a second person on each large account, share meetings and notes, and make relationship building part of the owner's goals. The owner should feel it extends their reach, not threatens their position.
Look at stage progress, quality of customer meetings and pipeline hygiene alongside closed deals. Agree these measures in advance so the wait for a close does not become a mystery.
Write travel and rest rules, plan breaks between go-lives and ask for monthly feedback. Respect for family time shows in small details, such as advance notice of site moves.
Leadership owns it with HR as the facilitator. Start with the few roles that matter most and update the map twice a year. Tell the people involved what the plan means for them.
Use real scenarios: a delayed go-live, a security question, a price challenge. Practise listening, clear answers and honest follow-up. Short sessions repeated each quarter work better than a single course.
First we would list the roles whose loss would hurt a large account, ask senior sellers about the incentive plan and count site weeks for delivery staff. A succession map for key roles is a natural first job, and scope goes into writing for your sign-off.
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 what is slowing your team down. We’ll help you find a practical way forward, starting with a conversation.