Industries
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 article
SaaS & Product Companies · Subscription software businesses
HR for Subscription software businesses: Renewals, Support Queues and Steady Growth
A 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 often 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.
- Plan
- Hire
- Onboard
- Manage
- Develop
- Perform
- Engage
- Retain
- Exit
- Improve
When HR is weak in subscription software businesses, you may see
- Support agents carry the queue and the blame
- Renewal targets are set without context
- New joiners take months to be useful
- Incentive plans cause quarrels
- Good support staff have nowhere to go
- Handovers between sales and success lose detail
- Quiet months hide slow resignations
These are the places the people side of this kind of business tends to give way. The rest of this page works through them.
Who does the work in subscription software businesses
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.
- Customer support agents
- Support team leads
- Customer success managers
- Onboarding and implementation specialists
- Account executives and renewals managers
- Product engineers and quality testers
- Product managers
- Billing and collections staff
- Community and documentation writers
Where HR strains in subscription software businesses
Support agents carry the queue and the blame
Ticket volume rises after every release, and agents absorb frustration from customers while engineers sit far from it.
Renewal targets are set without context
A customer success manager is given a list of accounts, some of which were lost the day they signed, and judged on the whole.
New joiners take months to be useful
Product knowledge, customer history and internal tools take time to learn, and a poor first month shows in churn.
Incentive plans cause quarrels
Upgrades, renewals and referrals are credited in different ways, and people argue over who earned a result.
Good support staff have nowhere to go
An agent who is excellent has no clear step to lead, success or product roles, so the best ones leave.
Handovers between sales and success lose detail
What the customer was promised is not passed on, and the first service call begins with an argument.
Quiet months hide slow resignations
Because the business is steady, small signs of unhappiness go unnoticed until several people leave together.
HR topics for subscription software businesses
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.
Onboarding and Probation
A first day that is the same for the fifth joiner as the first.
Retention and Attrition Management
Who leaves, when, why — and which of them mattered.
Learning and Development
Training planned from need rather than from the calendar.
HR Strategy and Workforce Planning
How many people, in which roles, by when — and what they will cost.
Organisation Design
Structure, reporting lines and who is allowed to decide what.
Recruitment and Talent Acquisition
Requisition to joining, the same way every time.
Employee Administration
Records, attendance, leave and the day-to-day HR that must simply work.
Compensation, Payroll and Benefits
Salary structure, payroll inputs and a month that closes on time.
Performance Management
Goals, reviews and ratings that hold up in a conversation.
Career and Succession Management
Named backups for the roles that cannot be vacant.
Employee Engagement and Experience
Communication, recognition and the conditions people actually work in.
Employee Relations
Two routes — one for complaints, one for conduct — kept separate.
Policies, Compliance and Governance
Policies a manager can apply, and obligations with owners and dates.
Health, Safety and Wellbeing
Induction, records, incident reporting and follow-through.
Exit and Alumni Management
Resignation to relieving letter, in a defined order.
HR Technology and Automation
Records that survive people, and approvals that do not queue.
HR Analytics and Management Reporting
A short monthly pack management actually reads.
HR Operations and Governance
An HR function that runs the same way every month.
What a working HR set-up looks like
The pieces a subscription software businesses business puts in place, in an order that makes each easier. Open any card for the detail.
Write role descriptions that match the queue
For support, success and onboarding roles, state what each owns, the response times expected and who they hand to.
What this coversHide
Write role descriptions that match the queue
For support, success and onboarding roles, state what each owns, the response times expected and who they hand to.
What this coversHideFor support, success and onboarding roles, state what each owns, the response times expected and who they hand to. See role design.
Run a two-week product induction
A structured first fortnight covering the product, the customers, the tools and shadowing, with a check at the end.
What this coversHide
Run a two-week product induction
A structured first fortnight covering the product, the customers, the tools and shadowing, with a check at the end.
What this coversHideA structured first fortnight covering the product, the customers, the tools and shadowing, with a check at the end. The onboarding process sets it out.
Split accounts by realistic health
Assign accounts with their history noted, so goals reflect the starting point and not only the final count.
What this coversHide
Split accounts by realistic health
Assign accounts with their history noted, so goals reflect the starting point and not only the final count.
What this coversHideAssign accounts with their history noted, so goals reflect the starting point and not only the final count.
Write incentive rules in plain words
Who gets credit for a renewal or upgrade, how ties are settled and when payment is made, on one page.
What this coversHide
Write incentive rules in plain words
Who gets credit for a renewal or upgrade, how ties are settled and when payment is made, on one page.
What this coversHideWho gets credit for a renewal or upgrade, how ties are settled and when payment is made, on one page.
Build a visible ladder from support
A path from agent to senior agent, lead, success manager or product specialist, with skills at each step.
What this coversHide
Build a visible ladder from support
A path from agent to senior agent, lead, success manager or product specialist, with skills at each step.
What this coversHideA path from agent to senior agent, lead, success manager or product specialist, with skills at each step.
Hold a sales-to-success handover
A short note and a call for every new account on promises made and the customer's goals.
What this coversHide
Hold a sales-to-success handover
A short note and a call for every new account on promises made and the customer's goals.
What this coversHideA short note and a call for every new account on promises made and the customer's goals.
Start by checking where you stand
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 requirements- Count how many support agents and success managers joined in the last year and how many are still here.
- Read the incentive rules and ask two staff to explain them back to you.
- Pick five lost accounts and trace whether the handover note existed.
- Ask your best support agent where they see themselves in two years.
- Check how long a new agent takes to handle tickets alone.
- Confirm with a qualified professional the rules on incentive pay, employment terms and records that apply to a software company like yours.
Confirm 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.
How GullyHR helps
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.
- Employee onboarding process
A first-fortnight route for support, success and implementation staff to reach useful work sooner.
- Role design and job descriptions
Clear roles for support, customer success and onboarding, so handovers stop dropping detail.
- Customer-service skills
Practical training for agents and success managers on handling frustrated customers and renewals.
- HR reporting and analytics
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.
Our HR transformation approach
- 1
Assess
Understand the business, its workforce, current processes and HR challenges.
- 2
Identify gaps
Find the missing, weak, inconsistent or person-dependent processes.
- 3
Design
Create the structure, processes, policies, SOPs, dashboards and systems needed.
- 4
Implement
Help HR and department managers actually adopt the new system.
- 5
Automate
Digitise repetitive and approval-based workflows where it is worth doing.
- 6
Measure
Track hiring, attendance, employee cost, performance, training and attrition.
- 7
Improve
Strengthen the people-management system continuously, not once.
Blogs worth reading first
From the GullyHR blog: one on HR in information technology and software, and one on each of the topics this page points to.
Industries
Onboarding a new joiner on the production floor in solar and renewable energy equipment makers: the first 30 days
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
HR Management
How to recognise and address employee workload problems
How to spot an unmanageable workload before it becomes an exit or an error, what to look at, how to talk about it and what to change, without guessing.
5 min readRead article
Industries
Skill-building in plastic moulding and extrusion units: a training plan that survives a busy production schedule
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 articleMore on the GullyHR blog.
Questions owners ask
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.
Often 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. Many 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.
More on HR for information technology and software
All 6 business types in SaaS & product companies · Find another business type
B2C SaaSB2B SaaSVertical SaaSAI product startupsEnterprise SaaSOnboarding and Probation in information technology and softwareRetention and Attrition Management in information technology and softwareLearning and Development in information technology and software
See all HR topics for information technology and software, or another industry.