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 articleA B2C SaaS company sells subscriptions to individual users, so growth, product and support teams chase numbers daily. Its people face shifting priorities, thin support rosters and the pull of larger consumer brands.

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 B2C SaaS company sells subscriptions to individuals, so a small team serves thousands of users it will never meet. Product managers, growth marketers, engineers and designers run weekly experiments, and the plan changes when a number moves. Support agents answer users through chat and email, often in shifts that cover evenings and weekends. Attention flips between acquisition, conversion and churn, and teams can feel every change in direction. Headcount is lean and one resignation leaves a visible gap. 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 fall in sign-ups reshapes the week, and teams feel their work is thrown away before it ships.
One designer or analyst leaving stalls an experiment cycle, so hiring feels urgent and decisions are rushed.
Evenings, weekends and festival days bring spikes in user queries, and agents hold the line with little rest.
A marketer may be praised one month and doubted the next because a channel changed, with no agreed way to read results.
Offers to engineers and data staff stretch the structure, and existing employees learn of it by accident.
Leave, work-from-home and conduct rules are borrowed, and they clash with how the team really works.
As headcount rises, norms of speed and candour fade, and newer people feel excluded from how decisions are made.
Start with the topics that matter most here: HR Strategy and Workforce Planning; Organisation Design; Policies, Compliance and Governance. Then work through the rest. Each topic is written for information technology and software, not in general.
How many people, in which roles, by when — and what they will cost.
Structure, reporting lines and who is allowed to decide what.
Policies a manager can apply, and obligations with owners and dates.
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.
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.
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 B2C SaaS business puts in place, in an order that makes each easier. Open any card for the detail.
Link hiring to a six-month view of what the product must deliver, so roles open for a reason.
What this coversHideLink hiring to a six-month view of what the product must deliver, so roles open for a reason. HR strategy and workforce planning gives the format.
Describe what one person decides alone and what they share, so overlaps and gaps are visible.
What this coversHideDescribe what one person decides alone and what they share, so overlaps and gaps are visible. See role design.
A rota that spreads evenings and weekends, with named backup and clear handover rules between shifts.
What this coversHideA rota that spreads evenings and weekends, with named backup and clear handover rules between shifts.
Set the measures, the time window and who decides, so a bad week does not become a verdict on a person.
What this coversHideSet the measures, the time window and who decides, so a bad week does not become a verdict on a person.
Leave, hybrid work, conduct and expenses in plain language that matches practice.
What this coversHideLeave, hybrid work, conduct and expenses in plain language that matches practice. HR policies and governance shows the layout.
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.
A hiring plan tied to the roadmap, so lean teams grow in the right order.
Clear roles in small teams without overlap fights.
Plain policies that fit a fast consumer team.
Early reading of why product, growth and support staff leave.
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
Hiring decisions made one request at a time, in the month the pain is worst. What a workforce plan contains and why a twelve-month view changes what you hire.
7 min readRead article
A flat structure works until the founder becomes the only route to a decision. How to tell when you have passed that point, and how to redesign without a reorganisation.
8 min readRead article
A practical contents list for an employee handbook in a growing Indian business: what to cover, what to leave to policies, and how to keep it usable and current.
5 min readRead articleMore on the GullyHR blog.
Hire for strong fundamentals in roles that stay needed, like engineering and design, and use short project help for peaks. A six-month roadmap view helps you tell which hires are lasting needs.
Rotate evenings and weekends fairly, cap consecutive late shifts, give clear breaks and allow quiet time after spikes. Leads should check workload weekly and flag patterns before agents resign.
Agree measures and a time window up front, and look at learning from experiments, not just one number. Give them a say in what is measured, as channels change quickly.
Set bands that include scarce skills, place the offer within them with a written reason and review existing staff at the same level. Hidden gaps cause more trouble than open rules.
Write down how decisions are made, what is expected in feedback and how people are recognised. Let managers practise these. Culture fades when only founders carry it.
First we would map hiring against your roadmap, ask support agents about their hardest shifts and check how growth roles are judged. A hiring plan with clear 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.