Build an it outsourcing business plan for the first 90 days

# Build an it outsourcing business plan for the first 90 days

What should you put in the plan before day one?

Start the onboarding clock on the first day worked. Record offer acceptance and the confirmed start date separately. Your manager needs a schedule built around when the person can join the team and access its tools.

Choose a useful outcome for the role before assigning training. For a developer, that might be ownership of a small service change. For an IT support hire, it might be resolving a defined class of requests within your review process.

The schedule below is a proposed operating plan. Adapt its targets to the person's role, seniority, and system access. A senior engineer joining an unfamiliar platform may need a different first assignment from a support specialist joining an established queue.

Prepare the team before the start date

Assign one manager who owns the outcome and one buddy who can answer daily questions. Give the buddy time for that work. Confirm who covers each person during leave.

Send the hire a short welcome document with the first week's meetings, working hours, and contact details. Include a route for reporting login problems that does not require access to your internal chat.

Prepare access through your normal approval process. Give the person only the permissions needed for the initial assignment. Separate development access from production access, and name the person who approves each change.

Confirm equipment delivery, device setup, and authentication requirements. Have the hire test the approved setup before the first technical session when the contract and start arrangements permit it. Do not make unpaid work a condition of being ready.

Choose a first task with limited scope and a clear reviewer. Explain what a successful result looks like. Avoid assigning a neglected incident or an unclear backlog item simply because nobody else wants it.

Put the plan somewhere the hire and manager can both update. Each task needs an owner, a due date, and a link to the work. Keep access requests there as status updates without copying passwords or other secrets into the document.

Before confirming the start, ask the manager to walk through the first morning. Who welcomes the person? What can they do if the device arrives late? Which approved task can proceed while an access request is pending? Resolve those questions before filling the calendar with training.

Use days 1–30 to complete a small work cycle

During the first week, walk through the system the person will actually use. Show how a request becomes a task, how work gets reviewed, and how a change reaches users.

For a developer, that walkthrough should include the local environment, tests, code review, and release process. For support, cover ticket ownership, escalation, customer communication, and closure rules.

Ask the hire to complete a small task through the full process. A code change sitting in an unreviewed branch does not demonstrate the same progress as an accepted change. Record where the work stalled and who can remove the blocker.

Keep early check-ins focused on decisions:

• What can the person now do without help?
• Which access request or unanswered question is holding up work?
• Who will review the current task?
• Does the next assignment still fit the agreed role?

At the day-30 review, inspect the work together. Ask the hire to explain the relevant system and the choices made. Use their questions to repair setup instructions that assume knowledge a new person would not have.

If the task slipped because access arrived late, record that cause. Do not score an internal approval delay as a skill failure.

For example, a developer's first assignment could be correcting a validation error in an existing form. Write down the expected behavior, the test needed, and who accepts the change. Ask the developer to describe how they checked that nearby behavior still works. This gives the reviewer something more useful than a count of training sessions attended.

Keep the first review narrow. Decide whether the person can repeat that work cycle with less help and which support they still need.

Use days 31–60 to assign a defined responsibility

Give the hire a piece of work with a named stakeholder and written acceptance criteria. Keep it small enough for the manager to review the result during this period.

The person should propose an approach, identify dependencies, and raise problems while there is still time to act. The manager should make decisions and arrange reviews within the working schedule.

For an application engineer, the assignment might be a modest feature with tests and release notes. For an infrastructure hire, it might be a reviewed change with a rollback plan. A support hire could own a defined queue category with an escalation contact.

At day 60, compare the result with the agreed scope. Discuss rework, judgment, and communication using actual examples. Counting tickets alone can hide differences in task size or difficulty.

When progress falls short, write down the cause and the next step. A missing skill needs a different response from unclear requirements or a reviewer who was never available.

Use a short review record that both sides can inspect:

Discuss the record with the hire before sending a performance concern to the provider. Give them room to correct a factual error or explain a dependency. Keep the agreed next step specific enough to review at the next meeting.

Use days 61–90 to confirm ongoing ownership

Expand responsibility only where the completed work supports it. Define which decisions the person can make alone and which still require approval.

Ask for a handoff document that another teammate can use. Depending on the role, this could be a runbook, a support procedure, or notes explaining a service change. Have someone follow it and flag unclear steps.

Treat production access and on-call duties as separate approval decisions. Set readiness criteria for each. Reaching day 90 should not automatically grant broader permissions.

At the final review, decide whether to continue the scope, expand it, or address a specific performance issue. Record the next work outcome and its owner. Give the hire a copy so expectations remain visible after the formal onboarding period ends.

Check whether the team can sustain the arrangement. If every task still waits for the same senior engineer, decide whether the cause is training, unclear boundaries, or limited review capacity. Assign the fix to the person who controls it.

Close out temporary permissions and remove meetings that no longer help. Keep the regular feedback meeting and the escalation route. The end of onboarding should leave the person with clear responsibilities and a manager who still reviews their work.

What does the hiring data tell you about the schedule?

SHRM reports that median time to fill in 2025 was roughly a month and a half for executive and nonexecutive positions. It defines that interval as job requisition to offer acceptance. That measure ends before the person's first day. SHRM's 2025 recruiting analysis.

Use that distinction when setting a delivery date. A recruiting estimate cannot tell you when a hire will have working equipment, approved access, or enough context to own a release.

Keep these dates separate in your plan:

Ask IT staffing companies how they define each hiring milestone. Check whether an estimate ends at candidate presentation, offer acceptance, or the first day worked. Compare estimates only after those definitions match.

Build your own onboarding record from the actual start date. Track access delays, time waiting for review, and accepted work. These observations help distinguish a hiring issue from a slow internal process.

Budget for the manager and buddy as well as the hire. Include equipment, approved software, and any training the role requires. Use your team's costs and planned hours rather than assuming a new hire will deliver at full capacity immediately.

For a fixed launch date, work backward from the ownership needed at launch. If the first assignment requires a security review, put that review on the calendar before promising delivery.

Write down what happens if the start date moves. You may need to reduce launch scope, move a task to an existing employee, or change the delivery date. Name who can approve that choice. Avoid compressing the same training and work into fewer days without checking what the hire can reasonably complete.

How should nearshore hiring models change your onboarding plan?

Choose the model based on who will manage the work and who will handle the employment arrangement. Ask providers to confirm the division in the contract. Similar service labels can hide different duties.

If you want a person embedded in your team, reserve management time for that person. Include them in the meetings where requirements change and decisions get made.

If you want a project delivered, organize onboarding around the project agreement. Set up access, technical discovery, acceptance reviews, and handoff requirements. Do not assume the provider's team will follow every internal employee routine unless that is agreed.

For a Latin American hire, define shared working hours with the actual manager and reviewer. The word "nearshore" does not set a meeting schedule.

Bogotá stays on UTC-5 and does not observe daylight saving time. Its difference from a US team's clock can therefore change when that US location changes clocks. Use named time zones in invitations and review recurring meetings around those changes. IANA's South America time zone data.

Ask the hire and provider to confirm local holidays and planned leave before setting milestone dates. Record who covers reviews when either side is away. A task should not wait several days because its only reviewer is on leave.

Agree on how work passes between people outside shared hours. A useful handoff states what changed, where the work sits, and what decision is needed next. Put the request in the agreed channel and name its owner. Do not make the new hire guess whether silence means approval or a blocked task.

What should you ask a provider before approving the hire?

Ask for answers tied to your role and start date. A general service description will not tell you who fixes a failed login on the first morning.

When comparing IT staffing agencies, use the same proposed first assignment and review schedule. Ask each provider to identify its duties against that plan. This makes it easier to see where your own team must supply time or support.

Who owns the first-week handoff?

Request a named contact for scheduling, equipment coordination, and employment questions. Assign separate client owners for system access and technical work.

Ask what the provider will send before the start date. Specify the details your team needs, such as the agreed schedule, role scope, and any setup dependencies. Keep personal information limited to what the relevant owner needs.

Confirm how a delayed start affects the schedule and billing. Put the answer in writing before your team blocks out onboarding time.

What evidence comes with the candidate?

Ask how the assessment relates to your first assignment. If the role requires debugging an existing service, discuss how the interview assessed that skill.

Request a handoff on the candidate's demonstrated strengths and areas that need support. Give the manager enough context to choose a suitable first task without treating an interview score as proof of production readiness.

Confirm your own rules for AI tools before the person starts. State which tools are approved and what code or data may be entered. Apply the same review requirements to work produced with those tools.

What happens when progress stalls?

Agree on an escalation route before a problem occurs. Distinguish employment or scheduling issues from technical feedback that belongs with your manager.

Bring concrete evidence to a performance discussion: the assignment, acceptance criteria, work produced, and feedback already given. Ask the hire for their account before deciding on a remedy.

If you need a corrective plan, specify the next task, the support available, and the review date. Avoid a vague instruction to "be more proactive" when the actual issue is a missed escalation.

What does a replacement involve?

Ask who restarts the search, what charges apply, and how the handoff works. Confirm whether billing continues during a vacancy and what the agreement requires from your team.

Keep access removal within your own security process. Assign an owner to recover equipment, transfer work, and revoke credentials when someone leaves. Do not wait for a new candidate to be chosen.

What will the first months cost?

Request the recurring rate and any separate charges in writing. Ask how equipment, software, overtime, leave, and changes in scope are handled.

Then add the internal cost of interviews, pairing, and review time. Compare IT staffing services using the same role scope and billing assumptions.

If you are considering Opus, bring these questions and a proposed first assignment to the discussion. This site is an Opus-owned reference; recommendations are editorial.

Talk to Opus about a role.

Where does Opus fit in this onboarding plan?

Opus states: "The client chooses the finalist and manages day-to-day work."

That division puts the technical onboarding plan with your manager. Assign someone who can set priorities, review work, and decide whether the person is ready for broader responsibility.

For pricing, Opus states: "Opus charges one flat monthly rate per hire. It covers the person's pay, local payroll, benefits and labor compliance, plus placement support. There is no separate recruiting fee. The rate depends on role, seniority and location."

Ask for a written quote for the role, seniority, and location under consideration. Add your internal onboarding costs before approving the budget.

Opus also states: "Every placement carries a lifetime replacement guarantee with no cap and no time limit."

Discuss how that guarantee would work for your team, including the handoff and billing terms. Keep the first assignment and review criteria in place even when a replacement guarantee applies.

Before proceeding, prepare a short role document with the intended outcome, manager, agreed working hours, and first task. Include the day-30, day-60, and day-90 review criteria. Send the same document to the finalist and your internal reviewers so everyone starts with the same expectations.

Talk to Opus about a role.

Not saved to disk: filesystem access is read-only. Live links were not checked.