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 vertical SaaS company builds software for one industry, such as clinics, schools or logistics. Its value rests on people who know the trade and the code, so onboarding and learning paths matter more than in generic product firms.

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 vertical SaaS company builds software for a single industry, such as school administration, restaurant billing or fleet operations. The best people often combine knowledge of the trade with a technical skill, and they are hard to find. Product teams speak to customers constantly. Implementation staff visit customer sites to set up and train users, and support staff answer questions in the language of the trade. A new joiner must learn two worlds: the product and the customer's daily work. Because the market is narrow, the same few customers and rivals know everyone. 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.
One former practitioner knows how a school or clinic really works, and the product, sales and support teams all depend on that person.
Engineers do not know the trade and trade experts do not know the code, so the first months go slowly without a plan.
They spend weeks setting up and training at customer sites, and rules on travel, rest and workload vary between teams.
A support agent who cannot speak the customer's vocabulary loses trust, and hiring from the trade is slow and costly.
Consultants, implementers and support staff share tasks, and titles do not show who does what, so growth steps are unclear.
Customer guides and internal notes fall behind as the product changes, and new joiners learn old habits.
A person strong in one module of the trade is stuck there, since no record shows what else they could learn.
Start with the topics that matter most here: Onboarding and Probation; Learning and Development; Employee Administration. 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.
Training planned from need rather than from the calendar.
Records, attendance, leave and the day-to-day HR that must simply work.
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.
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.
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 vertical SaaS business puts in place, in an order that makes each easier. Open any card for the detail.
One track for the trade and one for the product, with a buddy for each in the first months.
What this coversHideOne track for the trade and one for the product, with a buddy for each in the first months. Employee onboarding gives the format.
For implementers, support and engineers, list what must be learned in trade terms and in product terms.
What this coversHideFor implementers, support and engineers, list what must be learned in trade terms and in product terms. Learning and development shapes the steps.
One page per role with duties and who it hands work to, so overlaps and gaps are visible.
What this coversHideOne page per role with duties and who it hands work to, so overlaps and gaps are visible. See HR documentation.
List who knows which part of the trade and who is learning it, using competency and talent management.
What this coversHideList who knows which part of the trade and who is learning it, using competency and talent management.
Travel days, rest and workload caps written once and applied to every customer project.
What this coversHideTravel days, rest and workload caps written once and applied to every customer project.
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 first month that teaches both the trade and the product.
Paths for implementers, support staff and engineers in trade and product terms.
Role pages and handoffs written once and kept current.
A skill map of who knows which part of the trade.
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
Hour by hour, then week by week, for a recruit's first month at a module, inverter, pack or junction box line: safety and handling first, a practice bench, a buddy, a sign-off and a day-30 review.
7 min readRead article
Plastics training dies when it waits for a free Saturday. Tie it to mould changes, purges and cold starts, use one-point lessons and a visible skill ladder, and protect it in peak months.
7 min readRead article
Payroll says one joining date, the personal file says another and the manager remembers a third. How to establish a single trustworthy employee record and keep it that way.
7 min readRead articleMore on the GullyHR blog.
You need both. Hire engineers who are curious about the trade and trade experts who can work with product teams. Pair them early so each learns the other's world.
Plan for the first quarter, with checkpoints at the end of the first week, month and quarter. The trade side often takes longer than the technical side, so set expectations early.
Arrange customer visits, shadow sessions with support and implementers, and a short glossary. Let engineers sit in on training calls. Seeing a user struggle teaches more than a document.
Record it in short guides, run monthly sharing sessions and pair each expert with a learner. A skill map shows where knowledge is thin, so you can act before a resignation.
Write travel, rest and workload rules, plan breaks between projects and check in monthly. Customers value stable faces, so keeping implementers well helps retention of accounts too.
First we would ask domain experts what newcomers must know, count implementation days on the road and check which roles lack a written page. A two-track onboarding plan 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.