"We need more people" is usually the symptom. Name the gap before you bring anyone in.
Co-sourcing earns its cost when the need is specific and has a real end date.
When it is not that kind of need, a different kind of help usually is: a scoping sprint, interim coverage, or work on the process itself.
Most requests for co-source support start with a sentence about capacity.
The plan is behind. Someone left. Testing season overlaps with an implementation. The audit committee wants a review nobody on the team has done before.
Those are real problems. But "we need more people" is usually the symptom, not the diagnosis. Before bringing in outside help, it is worth being clear about what the help is supposed to change.
Co-sourcing works well when the gap is specific: a skill, a period of time, a level of judgment, or a piece of independence the team does not have right now. When the gap is less clear, the right first step is usually a different kind of help.
The Question Behind the Request
A useful way to start is to finish this sentence: If this goes well, in six months we will have...
A tested set of key controls ahead of year end. A completed IT general controls review the committee can rely on. A remediation backlog that is actually closed, not just updated. A team member who now knows how to run the work alone.
If the sentence is hard to finish, that is worth knowing early. It means the first piece of work is defining the need, not staffing it.
When It Makes Sense

Co-source support tends to earn its cost in a handful of situations.
A skill the team does not have, and does not need every day. IT general controls, a system implementation review, a data analytics test, a first look at a new regulation. Hiring for a skill used three months a year rarely makes sense. Borrowing it often does.
A peak that will pass. Year-end testing, a first-year SOX program, a backlog after a reorganization. The work is known and the end date is real.
A gap that cannot wait for a hire. A manager leaves in the middle of the plan. Recruiting will take months, and the work cannot pause. Senior interim support keeps the plan moving and gives the new hire something stable to step into.
A need for distance. Sometimes the team is too close to the area under review. An outside reviewer can ask the questions an insider cannot ask comfortably.
A second opinion before a hard conversation. A finding is about to go to the audit committee. Someone wants a careful, independent read before the call is made.
A company preparing for its first year of SOX compliance had a capable controller and a small internal audit team, but no one who had walked a program from scoping through testing. Senior support for the first cycle gave the team a working program, and gave the controller a model to run the second year without help.
In each case, the need has edges. You can say what the work is, when it ends, and what should be different afterward.
When It Needs a Different Kind of Help
Sometimes the help a company asks for is not the help it needs. More hands will not fix these situations, but the right kind of support often will.
The problem is permanent capacity. If the plan has been behind for three years running, this is not a peak. It is a staffing question. Outside support can cover the gap while you recruit, help define the role, and leave a program the new hire can run. It should not quietly become the answer to a decision no one has made.
No one owns the outcome. Outside support needs someone inside who sets priorities, reviews the work, and acts on what comes back. Settle that first, or make it part of the first conversation.
The real issue is in the business. If control owners are not performing their controls, adding testers will produce more findings about the same problem. What helps is different work: understanding why controls are being skipped and redesigning the process so they can be performed.
The scope keeps moving. "Help us with SOX" is not a scope yet. The answer is not to avoid help. It is to start with a short, defined piece of work that turns the request into a scope.
The goal is to hand off judgment. A good partner brings judgment, explains it, and helps the team build its own. It should not become the place every hard call goes so no one inside has to make it.
A team brought in support to clear a backlog of overdue control testing. The testing was completed on time. Six months later, the backlog was back, because control owners were not producing evidence on schedule. A short look at why evidence was late would have been the better first step.
Two questions sort most requests.
How clearly can you name the gap, and does the need have an end date? Select any situation to see where it lands and what kind of help fits.
- Co-source fitCo-sourced audit or controls support
- Bridge to a hireInterim senior support
- Scope it firstA focused advisory sprint
- Fix the processRemediation and process work
Questions to Ask Before You Bring Someone In
A few questions, answered honestly, will usually tell you what kind of help fits and where to start. They are not equal.
- What exactly is the gap? Skill, time, independence, or judgment. If the answer is "all of them," start with a short scoping conversation.
- What does done look like? A deliverable, a date, or a capability the team will have afterward.
- Who on our side owns it? Name the person who will set priorities, review the work, and decide what to do with it.
- Who will actually do the work? The people in the proposal meeting should be the people doing the work. Senior judgment is easy to lose in a handoff.
- What should our team know afterward? Good support leaves something behind: a method, a template, a person who now knows how.
- What would make us stop? Decide in advance what would tell you the arrangement is not working.
The first two define the scope. Without them, nothing else holds, and the right first step is a conversation to build it. The third decides whether the work sticks once it is done. The last three are worth settling with whoever you bring in, usually in the first conversation.
Are you ready to bring someone in?
The six questions above, in three groups. They are not equal. The first two decide where you start.
Start with scope.
Answer the first three questions to see where you would start.
The Short Version
Co-sourcing is a good answer to a specific question.
When the gap has edges, outside support can move the work, add judgment the team does not have yet, and leave the function stronger than it found it. When the gap is unclear, or the real problem sits somewhere else, the better first step is usually a different kind of help: a short scoping exercise, interim coverage, or work on the process itself.
The most useful conversation before any engagement is not about rates or headcount. It is about what should be different when the work is done.
