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 articleLegaltech startups build software for contract drafting, case tracking, research and compliance. This is how to run engineers, lawyer-advisers, customer success staff and sales teams where client confidentiality and professional trust shape every hire.

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 legaltech startup builds software for lawyers, in-house legal teams or businesses: contract drafting and review tools, case and matter tracking, document search, e-signing, compliance calendars or tools that help people reach legal help. The team has engineers, data and AI specialists, product managers, designers, lawyers or former lawyers who shape content and check accuracy, customer success staff and sales executives who sell to law firms and company legal departments. Customers are careful, slow to buy and quick to complain about errors. Their documents are confidential. A wrong clause suggested by the tool or a leak of client files could end a contract. Lawyer-advisers and engineers speak different languages, and founders must bridge them. For the wider sector, read 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.
GullyHR runs talent acquisition for permanent roles in legaltech startups. 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.
A legal adviser's rule becomes a vague ticket, and the shipped feature misses the point.
A wrong clause or missed date in the output damages trust, and no one is sure who checks what.
Support staff and engineers handle documents from law firms, and loose access is a serious risk.
Law firms take months to decide, and sales staff on short targets lose heart.
Part-time legal experts are busy with practice, reply slowly and leave when the work becomes routine.
Support agents face careful, sharp questions that need precise answers.
Marketing says the tool replaces hours of work and the team scrambles to match it.
Engineers handle support and founders handle sales, and nobody has a clear job.
Start with the topics that matter most here: Organisation Design; Policies, Compliance and Governance; Compensation, Payroll and Benefits. Then work through the rest. Each topic is written for information technology and software, not in general.
Structure, reporting lines and who is allowed to decide what.
Policies a manager can apply, and obligations with owners and dates.
Salary structure, payroll inputs and a month that closes on time.
How many people, in which roles, by when — and what they will cost.
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.
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 legaltech startups business puts in place, in an order that makes each easier. Open any card for the detail.
A short template that turns a legal rule into inputs, outputs and tests, written by adviser and engineer together.
A short template that turns a legal rule into inputs, outputs and tests, written by adviser and engineer together. Keep it with documentation.
Who reviews legal content, how errors are logged and what stops a release.
Who reviews legal content, how errors are logged and what stops a release. See performance management.
Role-based access, an audit of who opened what and a rule for support staff.
Role-based access, an audit of who opened what and a rule for support staff. Use HR policy packages.
Measures for meetings, pilots and pipeline stage as well as closed deals.
Measures for meetings, pilots and pipeline stage as well as closed deals. See compensation benchmarking.
Hours, availability, fees, response times and review cycles agreed in writing.
Hours, availability, fees, response times and review cycles agreed in writing.
A glossary, sample replies and a check before sending anything that sounds like legal advice.
A glossary, sample replies and a check before sending anything that sounds like legal advice. See learning and development.
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.
Specs, review logs and adviser agreements on record.
Confidentiality and data access rules for client files.
Sales pay that fits long legal-buyer cycles.
Precise-language training for support staff.
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
A founder's guide to building job grades, titles and billing levels for a growing IT services firm, with a step-by-step method and a grade description outline.
6 min readRead article
How an India head can sort a global parent's HR policies into apply, adapt or replace, write an India addendum with advisers, and keep headquarters on side.
7 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 articleMore on the GullyHR blog.
Use a short spec template, joint reviews and examples. Pair them on small features first.
Limit access by role, log who opened what and teach support staff the rules. Confirm legal duties with a qualified professional.
Reward pilots and pipeline progress as well as closed deals. Pure commission loses good people.
Agree clear hours, give meaningful work and acknowledge their input in the product.
Check each claim with product before it goes out, and keep a list of what the tool can and cannot do.
We would sit in on a product review and a support session, then draft a spec template, access rules and a sales measure. We do not do legal advice or payroll filings, and scope is written down after we talk.
All 61 business types in information technology and software · 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.