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 B2B SaaS company sells subscription software to other businesses. Sales, customer success and engineering grow together, and people leave when pay bands, goals and equity records are unclear, or when promotions look arbitrary.

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 B2B SaaS company sells subscription software to other businesses, through a sales team, onboarding specialists and a customer success group, with engineers, designers and product managers building behind them. Headcount can double in a year after a funding round, and every new team brings its own habits. Sales carries a quota, customer success carries renewals and engineers carry the roadmap, so each group wants a different kind of pay and recognition. Equity grants are common and need careful records. 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.
GullyHR runs talent acquisition for permanent roles in B2B SaaS. 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.
Offers are made quickly to different people in different ways, so two colleagues at one level find they have very different pay and titles.
Quota-driven incentives sit beside salary-only engineering roles, and each side questions the fairness of the other's pay.
Goals set at company level are not clear at team level, and reviews fall back on opinion at the end of the period.
Employees do not know what they hold, when it vests or what happens if they leave, and records sit in a few spreadsheets.
Strong individual contributors become managers without help, and their teams feel the gaps in feedback and fairness.
Renewals, escalations and onboarding pile on the same people, and attrition starts before leadership sees it in the data.
People ask what comes next and receive vague answers, so ambitious staff move to larger companies.
Start with the topics that matter most here: Compensation, Payroll and Benefits; Performance Management; HR Analytics and Management Reporting. Then work through the rest. Each topic is written for information technology and software, not in general.
Salary structure, payroll inputs and a month that closes on time.
Goals, reviews and ratings that hold up in a conversation.
A short monthly pack management actually reads.
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.
Training planned from need rather than from the calendar.
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.
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.
An HR function that runs the same way every month.
The pieces a B2B SaaS business puts in place, in an order that makes each easier. Open any card for the detail.
Define bands for sales, success, engineering and product, with clear rules for placing offers.
Define bands for sales, success, engineering and product, with clear rules for placing offers. Compensation benchmarking sets them against the market.
One register of grants, dates and conditions, shared in plain words with each holder.
One register of grants, dates and conditions, shared in plain words with each holder. Confirm the rules with a qualified professional before you finalise it.
Company goals broken down to teams, with five or fewer per team and a monthly look.
Company goals broken down to teams, with five or fewer per team and a monthly look. Performance management ties reviews to them.
A short programme on feedback, one-to-ones and fair reviews for those about to manage.
A short programme on feedback, one-to-ones and fair reviews for those about to manage. See manager development.
A monthly view of who leaves, after how long and from which team, so action is based on patterns and not a feeling.
A monthly view of who leaves, after how long and from which team, so action is based on patterns and not a feeling.
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.
Bands and incentive mixes that make sense across sales, success and engineering.
Goals, reviews and rewards connected so ratings rest on evidence.
Monthly retention and hiring views by team and tenure.
A practical start for new managers before their teams grow.
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
Simple variable pay structures for product and engineering teams: four options, why individual metrics backfire, a build plan and a one page outline to adapt.
6 min readRead article
A practical design for an IT services appraisal cycle: when to run it, how to rate fairly across projects, and how to explain hikes so they hold.
7 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 articleMore on the GullyHR blog.
Start with a simple band per role family and level, based on market data, and place each offer inside it with a written reason. This keeps early hires and later hires within a fair range.
Not exactly. Sales will have variable pay linked to targets, engineering mostly fixed pay. What can be shared is the grade structure, the review rhythm and the way promotions are decided.
There are too many, they are too vague, or no one looks at them after the first month. Keep a few clear goals, review them monthly and separate them from salary discussions.
In one register with grant date, number, schedule and conditions, plus a plain summary for each holder. Ask a qualified professional to confirm the legal side, and keep HR and finance records aligned.
Measure accounts per person, spread escalations, give rest after renewal peaks and ask for monthly feedback. A visible career step into senior or leadership roles also helps.
First we would compare recent offers at the same level, list who holds equity and ask team heads to state their goals. Pay bands with a goal-setting rhythm are 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 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.