A company can have a budget, support from HR and a willingness to discuss the PFRON mandate. And still, the project may never get off the ground. All it takes is for nobody to be able to name the work the new team is supposed to do, or the person responsible for accepting its results.
Imagine a company where HR is given a task: “Let’s hire ten people with disabilities.” The recruitment team can find candidates and take care of the formalities. But it cannot, on its own, invent an operational process, allocate a budget to its owner or take responsibility for the quality of the work delivered. This is not a gap in HR’s competence. It is how the task has been set up.
So the first question should not be “How many people can you supply?” but “What work does the company want to hand over?” That small change in the order of decisions determines whether the company builds a team or merely promises to build one.
Before we start looking for people, we need answers to four questions. Who owns the process? Which tasks can be separated out without compromising the work delivered to the internal customer? How will we measure accuracy, timeliness and volume? Who will accept the output, and what will they do when performance starts to drift?
Only then can we determine the number of people needed, their skills, access to tools and how the team will be managed. Reversing that order looks convenient in a presentation. Operations send the bill later.
Remote work does not remove the need for management. You still need instructions, quality standards, access to systems, an escalation process and someone authorised to make a decision when something goes wrong. In the Innothink model, managing the work is part of the project. It is not an add-on to be written into the plan after the contract is signed.
There must still be a business owner on the client’s side. They can delegate execution, but they should not delegate responsibility for deciding whether the process is needed in the first place.
A sensible starting point is a paid pilot with a clearly defined scope: a task list, baseline volume, acceptance criteria, named owners and a review date. If the process cannot be described in those terms, recruitment is not yet the problem. The problem is that the company has not decided what it wants to achieve.
The PFRON mandate can be an important part of the business case. But it cannot replace work that the client is prepared to take responsibility for. Savings without a process are a financial plan with no operations behind it.
Before launching recruitment, bring finance and the process owner into one meeting. Leave it with a named sponsor, a list of tasks and three measures of success. If those things are in place, you can discuss team size and launch. If they are not, another meeting about the organisation’s “openness” will not solve the problem.