The Cost of Staying: Why YCG Group Left Its Legacy ATS

Every firm considering a new system builds a careful model of what moving will cost. Days of disruption, the migration quote, the fortnight where nobody trusts the numbers.

Almost nobody models the other side. Staying has a price too, and it is paid in amounts small enough that no one ever adds them up.

YCG Group did add them up. What follows is what they found, why the thing that actually trapped them was not the data, and the questions worth asking before your next renewal.

This is the decision half of an ATS change. If you have already made the decision, what a migration does and does not carry across covers the mechanics.

The firm

Joshua and Seon started YourCode in technical recruiting with a deliberately unfussy proposition: get good candidates in front of clients fast.

It worked well enough that they turned the method into a business of its own. YCG is the group they built to invest in and acquire other recruitment businesses, then install the playbook that had worked for YourCode. Today that spans construction, medical, automotive and hospitality.

The model shapes everything about their software requirements. YCG either takes a stake in an established business or funds one that is still an idea, with a seasoned operator on the ground running it locally. Head office does not manage those desks day to day. It reads them.

That makes consistency a structural requirement rather than a preference. Every business in the group has to produce comparable numbers, and the teams are remote, so the system is the only place that picture exists.

Why they left

Their previous platform was not broken. That is the point, and it is why firms stay in this situation for years.

Everything took too many clicks

Their own summary of the decision was that they had to press too many buttons to achieve what they wanted to do.

That sounds like a small complaint and it is the most expensive item on the list. A task that takes four extra actions and runs forty times a day is not a minor irritation, it is a headcount decision nobody made deliberately. It also decides whether the system gets used properly at all, which is the failure mode that quietly hollows out a database.

The missing pieces had become the actual job

Two absences mattered: no browser extension, and no serious email campaign capability.

Both of those describe where recruitment work moved over the last decade. Sourcing happens in the browser, on profiles, and outbound happens in sequences rather than one message at a time. A platform designed before that shift can be entirely competent at everything it was built for and still force your team to work outside it every day.

The test is not whether a system has gaps. It is whether the gaps sit on the path your team walks most often.

The contracts were rigid

This is the one almost nobody screens for, and it is what turns a manageable problem into a stuck one.

Flexibility in commercial terms is invisible while things are going well and decisive the moment they are not. A firm that has outgrown its platform but cannot move for another eighteen months does not get to make a decision. It gets to wait.

For a group whose whole model is adding businesses at unpredictable intervals, that rigidity was disqualifying on its own.

Why the cost of staying stays invisible

The two costs are not comparable in the way they present themselves.

Migration arrives as a single number, on a specific date, with someone accountable for it. It is easy to fear precisely because it is easy to see.

The cost of staying arrives as four extra clicks, a follow-up that did not happen, a note that went into a personal file, a report that had to be rebuilt in a spreadsheet. None of it is ever invoiced. It does not appear in any budget line, and no one is accountable for it, because it is distributed across everybody’s afternoon.

So firms systematically overweight one and underweight the other. The useful correction is to make the invisible cost concrete: count the actions, multiply by frequency, and put a number on it before comparing it to a migration quote.

What the change actually bought

Automated follow-up is the piece YCG point to first, and it maps directly onto the sales problem their model creates. Selling into many different businesses means tracking a lot of partly finished conversations across email, phone and social. Remembering them is the work that fails first.

Once follow-up ran on its own, their team could spend its attention on new business rather than on chasing the last round of it. They describe roughly doubling the new business they generate this way, and put the overall saving at the equivalent of a full-time salary each year.

Leads captured from a profile now go straight into a nurture sequence in a few clicks, and the team can see who opened what, which changes follow-up from guesswork into a queue.

“With Recruiterflow on our side, it’s like having another member on the team, working tirelessly to help us bring in new business and deepen our relationships with existing clients.”

YCG Group

Four questions before you sign or renew

What are the notice period and the auto-renewal date? Ask this about your current contract today, not when you want to leave. Most firms discover the answer at the worst possible moment.

How many actions does the thing you do fifty times a day take? Not the impressive workflow in the demo. The ordinary one. Count them, then multiply.

Has the roadmap shipped? Every vendor has a roadmap. The question is what arrived in the last twelve months, and whether anything on it came from a customer request rather than an internal plan.

What does leaving cost, in writing? Export formats, what comes with the data, how long you retain access afterwards. A vendor confident in the product will answer this quickly.

Work out what staying is costing you

Pick the three actions your recruiters repeat most and count the clicks in each. Multiply by how often they happen across the team in a week. That number is your annual cost of staying, and it is usually larger than the migration quote you are comparing it to.

Bring those three workflows to a demo and we will run them side by side against what you do today.

You can read the full YCG Group case study for the rest of their story.

FAQs

When should a recruitment firm switch ATS?

When the cost of staying exceeds the cost of moving, which is usually earlier than it feels. Practical triggers are workflows that take more actions than they should, capability gaps on the path your team walks daily, and a team that has started working outside the system.

What should you check in an ATS contract?

Notice period, auto-renewal date, what happens to your data on exit, and which export formats are included. Commercial rigidity is the factor most often missed at signing and the one most likely to trap you later.

Is it worth switching ATS if the current one works?

Working is a low bar. A system can be entirely functional and still charge your team several extra actions on every task, which compounds into real cost. The question is not whether it works but what it costs per day to keep using it.

How do you calculate the cost of staying on the wrong system?

Count the actions in your most repeated workflows, multiply by weekly frequency across the team, and convert to hours. Add the work that happens outside the system entirely, since that represents capability you are paying for and not receiving.

What usually goes wrong when firms delay an ATS decision?

The delay is rarely a decision. It is a contract term discovered late, so the firm waits out a renewal cycle it did not plan for. Meanwhile the team builds workarounds that are then expensive to unwind whenever the move does happen.