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 computer repair shop earns from technicians' time and customers' trust in their data. Here is how to run a small team that does both well.

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 computer repair shop fixes laptops, desktops, printers and sometimes phones for walk-in customers, homes and small offices. Many also sell parts, accessories and service contracts, and some send technicians out on visits. The team is small: technicians, a counter or reception person, a person for parts and billing, and the owner, who is often the best technician. Customers leave devices that hold their photos, accounts and business files, so honesty and carefulness are the real product. Workload is uneven, with a rush after exams, launches or a virus wave, and technicians learn mostly by doing. See also HR for IT and software.
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.
The hardest repairs go to the owner or one senior technician, which caps how many jobs the shop can take.
A trained technician who knows the customers and suppliers opens a rival nearby, and the shop trains the competition.
Devices are opened, backed up and tested with little rule on what staff may look at, copy or keep.
Devices sit on shelves with no clear record of who has them or what was promised, so customers call and staff scramble.
The person at the counter delivers bad news about cost and time with no training in how to say it.
Fixed pay, incentives per repair and shares on parts get mixed, and technicians argue over who earned what.
New models and fault types appear constantly, and technicians pick things up only if they happen to meet the job.
Start with the topics that matter most here: Compensation, Payroll and Benefits; Learning and Development; Employee Administration. 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.
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.
A first day that is the same for the fifth joiner as the first.
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 computer repair shops business puts in place, in an order that makes each easier. Open any card for the detail.
What technicians may open, copy or keep, how data is handled in recovery work and what happens if the rule is broken, explained to every new person.
What this coversHideWhat technicians may open, copy or keep, how data is handled in recovery work and what happens if the rule is broken, explained to every new person. The HR policies service helps frame it.
A simple record of who received it, the fault, the estimate, the technician and the promised date, so any staff member can answer a customer.
What this coversHideA simple record of who received it, the fault, the estimate, the technician and the promised date, so any staff member can answer a customer.
Levels from basic repairs to board-level work, with a pay structure and a repair incentive that is written and checked.
What this coversHideLevels from basic repairs to board-level work, with a pay structure and a repair incentive that is written and checked. Compensation rewards covers the options.
Short practice on explaining cost, delay and unrepairable faults.
What this coversHideShort practice on explaining cost, delay and unrepairable faults. The customer-service skills programme fits this.
A short slot where technicians share a tricky fault and the fix, and a plan to teach the next person, tracked in the learning and development process.
What this coversHideA short slot where technicians share a tricky fault and the fix, and a plan to teach the next person, tracked in the learning and development process.
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 short written rule on customer data and device handling that every technician and counter person knows.
A clear mix of fixed pay and repair incentive that technicians accept as fair.
Practice for counter staff on explaining cost, delay and bad news to customers.
A simple way to build technician skills so the owner is not the only expert.
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
Most salary structures grew one negotiation at a time. How to build grades and bands from what you already pay, without repricing everybody at once.
8 min readRead article
A calendar of courses, a budget spent by March and no record of what any of it changed. What a learning and development process contains when it starts from need rather than from the catalogue.
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 cannot always, but you can lower the chance. Give a real path in pay and responsibility, share some credit with customers, and consider fair written terms on what they may do after leaving, checked by a qualified professional.
Many shops mix a fixed salary with an incentive per completed repair. Keep the formula simple, written and tied to quality, such as repeat faults, so speed alone is not rewarded.
That files and accounts are the customer's, that nothing is opened or copied without need, and that any breach has consequences. Write it down and explain it on the first day.
Pick one or two technicians, teach them the next level of work in stages and record the fixes. Give them the added pay and title that go with it.
You need the basics: clear roles, written pay terms, leave and attendance records, and a way to deal with problems. These are small tasks that prevent large disputes.
We would ask which repairs only you or one technician can do, whether every device on the shelf has a job card, and what technicians may do with a customer's files. A good first piece of work is a customer data rule and a job card habit, both small enough for a team of a few people. Scope is agreed in writing afterwards.
All 5 business types in information technology and software · Find another business type
See all HR topics for information technology and software, or another industry.
Identify payroll leaks, record gaps and hiring bottlenecks in a free first conversation, and leave knowing what to fix first.
Know what you need? Share your requirements in four short steps.
Want the full picture? See the paid HR Diagnostic.
Prefer a quick message? Chat on WhatsApp