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
Information Technology and Software · Business automation and RPA companies
HR for Business Automation and RPA Companies: Bot Developers, Process Analysts and Client Support
An RPA firm builds software robots that take over repetitive office tasks for clients. Here is how to manage the analysts, developers and support staff who must understand a client's work before they can automate it.
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 business automation or RPA company studies how a client's staff do repeated tasks, such as entering invoices or reconciling reports, and builds software robots to do them. The firm is staffed by business analysts who map the process, developers who build and test the bots, support engineers who watch them after launch, and project managers who deal with the client. People often spend weeks at client offices, learning someone else's rules, and then support bots that break whenever the client changes a screen. Staff must be part analyst, part coder and part diplomat, because the people whose work is being automated may feel threatened. That mix is hard to hire, hard to grade and easy to lose to larger firms. See also HR for IT and software.
- Plan
- Hire
- Onboard
- Manage
- Develop
- Perform
- Engage
- Retain
- Exit
- Improve
When HR is weak in business automation and RPA companies, you may see
- Analysts and developers see the work differently
- Support never ends after go-live
- Staff sit at client sites for weeks
- Certifications drive pay and exits
- Client staff fear being replaced
- Bot knowledge sits with the builder
- Project end brings a gap
- Pre-sales promises outrun delivery
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 business automation and RPA companies
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.
- Process analysts
- RPA developers
- Solution architects
- Testers and quality analysts
- Bot support and monitoring engineers
- Project and delivery managers
- Client success executives
Roles we help you hire in business automation and RPA companies
GullyHR runs talent acquisition for permanent roles in business automation and RPA companies. 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.
Job descriptions for this sector
Share a hiring requirementTalent acquisition services →IT and specialised recruitment →Role design and job descriptions →
We recruit permanent employees. We do not supply contract or temporary staff.
We set up the interview and hiring process for business automation and RPA companies
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.
1. Role brief and scorecard
We agree what the role must deliver, the must-have and nice-to-have skills, and how each will be scored.
2. Stages and sequence
Screening call, assessment, interview rounds and decision points, sized to the role and the number of people you hire.
3. Question bank and scoring
Structured questions for each role family and a rating guide, so two interviewers judge the same answer the same way.
4. Interviewer readiness
A short briefing for your managers on what to ask, what to avoid and how to give a clear yes or no.
5. Offer and follow-up
Who approves, how the offer is made, and how candidates are kept informed from first call to joining.
Where HR strains in business automation and RPA companies
Analysts and developers see the work differently
Analysts promise what the client wants, developers find it hard to build, and the gap shows up late in the project.
Support never ends after go-live
Bots break when client screens or rules change, so support engineers face alerts at odd hours with no clear rota.
Staff sit at client sites for weeks
They work under the client's rules and out of sight of their own manager, so appraisal and welfare are easily missed.
Certifications drive pay and exits
Staff with vendor certificates are quickly poached, while others feel their experience is not counted.
Client staff fear being replaced
Analysts hear resistance during process study, and without guidance they handle it badly or take it personally.
Bot knowledge sits with the builder
If the developer leaves, nobody else understands how a particular bot behaves or why it was built that way.
Project end brings a gap
When a build finishes, people wait to be placed on the next client, and idle bench time weakens morale.
Pre-sales promises outrun delivery
Sales staff commit dates and scope that the team then has to meet, leading to overtime and blame.
HR topics for business automation and RPA companies
Start with the topics that matter most here: Organisation Design; Learning and Development; HR Technology and Automation. Then work through the rest. Each topic is written for information technology and software, not in general.
Organisation Design
Structure, reporting lines and who is allowed to decide what.
Learning and Development
Training planned from need rather than from the calendar.
HR Technology and Automation
Records that survive people, and approvals that do not queue.
HR Strategy and Workforce Planning
How many people, in which roles, by when — and what they will cost.
Recruitment and Talent Acquisition
Requisition to joining, the same way every time.
Onboarding and Probation
A first day that is the same for the fifth joiner as the first.
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.
Retention and Attrition Management
Who leaves, when, why — and which of them mattered.
Exit and Alumni Management
Resignation to relieving letter, in a defined order.
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 business automation and RPA companies business puts in place, in an order that makes each easier. Open any card for the detail.
Document every bot and process
A standard design note and run book for each bot, stored centrally, so another person can support it.
What this coversHide
Document every bot and process
A standard design note and run book for each bot, stored centrally, so another person can support it.
What this coversHide
A standard design note and run book for each bot, stored centrally, so another person can support it. See the HR documentation process for keeping such records current.
Create a support rota with fair cover
Named on-call people, a clear allowance and handover notes, using the attendance and shift process.
What this coversHide
Create a support rota with fair cover
Named on-call people, a clear allowance and handover notes, using the attendance and shift process.
What this coversHide
Named on-call people, a clear allowance and handover notes, using the attendance and shift process.
Plan client-site working
A visit checklist, regular check-ins from the firm's manager and a clear route to raise a client-site concern.
What this coversHide
Plan client-site working
A visit checklist, regular check-ins from the firm's manager and a clear route to raise a client-site concern.
What this coversHide
A visit checklist, regular check-ins from the firm's manager and a clear route to raise a client-site concern.
Grade analysts, developers and support separately
Different ladders and expectations for each, so a good analyst is not forced into coding to progress.
What this coversHide
Grade analysts, developers and support separately
Different ladders and expectations for each, so a good analyst is not forced into coding to progress.
What this coversHide
Different ladders and expectations for each, so a good analyst is not forced into coding to progress.
Plan the bench time
Use gaps between projects for training, internal tools and certification, so waiting time adds skill.
What this coversHide
Plan the bench time
Use gaps between projects for training, internal tools and certification, so waiting time adds skill.
What this coversHide
Use gaps between projects for training, internal tools and certification, so waiting time adds skill. The learning and development process can structure this.
Make pre-sales and delivery sit together
A scoping review with the delivery lead before any date or price is promised.
What this coversHide
Make pre-sales and delivery sit together
A scoping review with the delivery lead before any date or price is promised.
What this coversHide
A scoping review with the delivery lead before any date or price is promised.
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- List which bots only one developer understands.
- Check who is on call this week and whether they know it.
- Ask one consultant at a client site how often their manager has spoken to them.
- Review the last go-live and ask what pre-sales promised that delivery had to absorb.
- Count how many staff are currently without a project and what they are doing.
- Ask analysts how they handle client staff who resist the change.
- Confirm with a qualified professional the employment rules that apply to staff you send to client sites.
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.
- Learning and development
Planned certification and skill paths, and a use for bench time between projects.
- Attendance, shift and leave
A fair support rota with records that feed pay accurately, including after-hours alerts.
- Performance management
Appraisal that covers staff working at client sites and measures delivery, not only hours.
- Recruitment process
A clearer way to find analysts and developers with the mix of process and technical skill you need.
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
Grades, titles and billing levels: building a structure a growing services firm can keep
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
Industries
Fresher hiring and a first-year training programme for a small IT services company
A founder's guide to hiring freshers and running a first-year programme: campus or open drives, a screening round, a training plan by quarter, mentors and checkpoints.
6 min readRead article
Industries
Timesheets that people actually fill in: a simple routine for services teams
A simple timesheet routine for IT services teams: a short form, daily entry, light approval and a month-end lock that finance can bill from.
6 min readRead articleMore on the GullyHR blog.
Questions owners ask
Keep regular contact with their own manager, collect feedback from the client lead and set clear targets. Make sure they know how to raise concerns without going through the client.
Name an on-call person each week, give them notes on each bot and pay an agreed allowance. Review alert volume monthly, since repeated breakages may point to a design fault.
It helps with client trust and skills, but it also makes staff easier to hire away. Pair it with a retention understanding or a service period, and have the terms checked by a qualified professional.
Plan it. Use gaps for training, internal accelerators, documentation and certification. Unplanned waiting weakens morale and makes people look elsewhere.
HR cannot fix pricing, but it can help set a joint scoping step and link part of sales incentives to delivered, not just signed, work. Review project overruns together.
We would ask about support rota fairness, client-site welfare, bench use and grading across analyst, developer and support roles. A sensible first project is a role ladder with a support rota. Scope goes into writing before you decide.
More on HR for information technology and software
All 61 business types in information technology and software · Find another business type
Managed service providersIT support firmsSoftware testing companies3D printing companiesCloud computing companiesCybersecurity firmsOrganisation Design in information technology and softwareLearning and Development in information technology and softwareHR Technology and Automation in information technology and software
See all HR topics for information technology and software, or another industry.