Build an it outsourcing business plan for days 30, 60 and 90

What should a busy buyer put in the onboarding plan?

Give the hire a named manager, a working environment and a first assignment before committing that person to a delivery date. Then define what you will review at days 30, 60 and 90.

Treat the schedule below as a proposed plan for an engineer joining your team. Adjust the work to the role and the systems involved. These checkpoints are management targets, not promises about how quickly every hire will become independent.

Keep this plan in a document the hire can edit. Give each task an owner, a due date and a link to its evidence. A checked box labeled "training complete" tells the manager less than a link to the change the engineer shipped.

Prepare the first assignment before the start date

Choose a small task that touches a real part of the product. It should have a known reviewer and a clear way to test success. Avoid making a production incident or an undocumented migration the first test of the hire's ability.

For example, a backend engineer might fix a validation bug, add a regression test and explain the release steps. That is a proposed exercise, not a universal day-30 requirement. A platform engineer may need a different assignment, such as testing a deployment procedure in a safe environment.

Write down what the hire can decide alone and what needs approval. Name the person who can answer product questions. If the manager will be away, assign a backup before the hire arrives.

Prepare a fallback task that uses the same skills but needs fewer permissions. If the main repository is blocked, the hire might review a test case with their buddy or improve setup instructions. Keep the fallback tied to the role. Filling the first week with unrelated reading makes it harder to assess whether the person can do the work.

Use days 1–30 to establish a working routine

Start with the product, the users and the reason the role exists. Show the hire a real customer problem and trace it through the relevant system. Give them enough context to understand why the first task matters.

Set up access through your normal approval process. Use individual accounts, require the team's authentication controls and grant permissions based on the task. Keep production access separate from basic setup.

Ask the hire to record where the setup instructions fail. Have the buddy review those notes and fix the instructions. The manager should resolve blocked access with the account owner rather than asking the hire to keep chasing an unanswered request.

At the first checkpoint, review:

• Whether the hire can run the relevant tests and explain a failure.
• Whether the first change meets its written acceptance criteria.
• How the hire asks for help and responds to review comments.
• Which dependencies still prevent useful work.

Do not grade the engineer on a deadline that depended on an account nobody approved. Record that delay separately and decide what work can proceed.

Use days 31–60 to expand ownership

Assign a bounded feature or maintenance task with a clear business owner. Ask the engineer to propose the approach, identify dependencies and describe how they will test it.

The manager should still review scope before work begins. A new hire should not have to infer which shortcuts the team accepts or which systems require extra review.

Use regular check-ins to discuss actual work. Review a pull request, a design note or a customer issue together. Ask what changed since the estimate and what decision the engineer needs from the team.

By the day-60 review, look for evidence that the hire can move work forward without waiting for every next instruction. That does not require working without help. It requires knowing when help is needed and involving the right person.

For a proposed feature assignment, write the acceptance test before development starts. State the expected user behavior and the failure case the change must handle. Name who approves the result. If the product owner changes the requirement midway through the task, update the review criteria too. Keep the original estimate visible so the discussion reflects the work actually requested.

Use days 61–90 to agree on recurring responsibility

Give the hire ownership of an area that matches the role you hired for. Define its boundaries, the support available and the decisions that still need review.

If support duty is part of the job, arrange shadowing and a supervised handoff. Check that the engineer can find the runbook and contact the backup owner. Keep independent incident duty subject to your team's readiness criteria.

At day 90, compare the agreed scope with the work completed. Discuss quality, judgment and communication using specific examples. Set the next scope in writing, including any coaching that remains necessary.

Ask the hire to walk another teammate through the area they now own. Use the walkthrough to check whether the notes support a real handoff. Have the teammate find the test command, explain the release steps and locate the rollback instructions. Fix gaps before making this engineer the only person responsible for the area.

A calendar date alone should not trigger broader access or less review.

What does the data say about hiring and the start date?

SHRM reports that median time-to-fill in 2025 was roughly a month and a half for both executive and nonexecutive roles. It defines that period as job requisition to offer acceptance. That endpoint does not establish when someone starts work or completes onboarding. SHRM's 2025 recruiting findings.

Use that distinction when building your staffing schedule. Track requisition approval, offer acceptance and the first day worked as separate dates. Begin the onboarding clock on the first day worked.

The SHRM benchmark is broad. Do not turn it into a promised hiring time for a particular engineering role, country or seniority level. Ask the provider to define its own timing measure before comparing it with another quote.

For your own plan, record the dates that affect delivery:

These are proposed tracking fields. They help distinguish hiring delays from setup problems and gaps in the work itself.

Avoid putting an assumed productivity percentage into the budget. Estimate the manager and buddy time required for the actual onboarding tasks. Revise that estimate after reviewing what the hire can complete and where support is still needed.

If finance needs a delivery assumption before hiring starts, state the dependency plainly: the planned work begins after the start date, approved access and manager availability. Keep the person who owns each dependency visible.

Review those assumptions when the start date changes. Move welcome sessions and reviewer time together, then check the assignment still fits the team's current priorities. Do not leave the hire attached to a deadline that was set for an earlier arrival. Record the revised commitment in the same document finance and engineering use.

How should hiring models change your nearshore onboarding plan?

Choose a model based on the work you want another party to own. Then write the handoff into the agreement.

The table below is a way to assign responsibilities during buying discussions. Confirm the actual scope in the contract.

For a direct hire, name the internal owner of every step between offer acceptance and the first working day. Ask the agency what remains in its scope after the placement.

For an EOR arrangement, confirm who answers payroll and employment questions. Keep the technical manager visible in the welcome plan. The hire should know where to take a pay question and where to take a blocked code review.

For staff augmentation, agree on how the provider and your manager will handle a performance concern. Decide who records feedback and who gives it to the person doing the work. Avoid separate review processes that produce conflicting instructions.

For an outsourced project, write acceptance criteria for the deliverable. Your plan should identify who can approve a scope change and who signs off on the result. If you want to manage an individual engineer's daily tasks, make that expectation explicit before signing.

Agree on overlap for Latin American hires

Put both time zones and the shared working window in the onboarding document. Include the hours when the manager or buddy will be available.

Mexico City uses UTC-6 without daylight saving time. Tijuana follows a different schedule and observes daylight saving time. A country name alone is therefore too broad for a working-hours agreement. IANA's North America time-zone records.

Bogotá uses UTC-5 without daylight saving time. Buenos Aires and São Paulo use UTC-3 without daylight saving time. Check meeting times against the US team's daylight saving changes before booking recurring sessions. IANA's South America time-zone records.

Ask the hire to confirm the calendar invitations in local time. Put review sessions inside the agreed overlap and define how questions will be handed off outside it. Add planned leave and local holidays to the shared calendar before assigning deadlines.

Budget for the work around the hire

Separate the provider's charge from your internal onboarding costs. Include equipment, software licenses and the time existing staff will spend on setup and review.

Ask who pays for a replacement device and who owns it when the engagement ends. Confirm whether any setup charge, deposit or notice payment belongs in the first-quarter budget.

Keep these items in the same approval document as the monthly cost. That gives finance a plan it can review without guessing which expenses sit outside the quote.

What should you ask a provider before day one?

Ask the provider to walk through the handoff using your proposed start date and first assignment. General statements about support are less useful than a named owner and a defined next step.

Use these questions during the buying call:

1. Who confirms the first day worked, and what must happen before that date?
2. Who owns equipment delivery, setup and replacement?
3. What candidate assessment evidence can the hiring manager review?
4. Which working hours has the candidate agreed to?
5. Who answers employment questions, and who handles technical blockers?
6. What happens if the hire cannot begin the agreed work?
7. How are performance concerns recorded and escalated?
8. What costs and duties apply if the engagement ends?

Ask for the answers in writing. Add the relevant names and contact details to the hire's welcome document.

When comparing IT recruiting agencies, use the same scenario for each: the hire has started, but the development account is blocked. Ask who receives the issue, who can resolve it and how your manager gets an update.

Repeat the exercise with a role-fit concern. Describe a concrete problem, such as repeated failure to apply review feedback after coaching. Ask what evidence the provider needs and what the next step would be.

The best IT recruiting agencies for your team should fit the responsibilities you want to delegate. Compare those responsibilities directly. A search service and a delivery team should not receive the same score simply because both can introduce engineers.

Keep the review fair and specific

Agree on acceptance criteria before each assignment starts. Save review comments and record changes in scope. Give feedback while the hire still has time to act on it.

If a checkpoint slips, separate the cause from the outcome. A missed delivery might involve unclear requirements, delayed access or a skill gap. Each needs a different response.

Write the next action in terms the hire can use: revise the test, explain the design choice or break the task into smaller work. Assign someone to provide the promised support.

For example, if a change fails review because it lacks a test, point to the behavior the test must cover. Arrange a pairing session if the test framework is unfamiliar. At the next review, inspect the revised work against that same requirement. Avoid replacing a concrete concern with a broad label such as "not proactive."

Avoid collecting activity counts that do not answer the hiring decision. Messages sent and hours online do not show whether the engineer can own the agreed work.

For a discussion tied to your role and start date, talk to Opus about a role. This site is an Opus-owned reference; recommendations are editorial.

Where does Opus fit in this onboarding plan?

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

For your onboarding plan, that means assigning an internal manager before the hire starts. That person should own the first assignment, review the work and decide when to expand responsibility.

Opus describes its pricing this way: "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."

Published dollar rates: Not published. Ask for a written quote for the role, seniority and location you are considering. Add your own equipment, software and management costs before approving the budget.

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

Ask how a replacement request would work for your engagement. Agree on the contact, the evidence needed and the handoff duties. Keep your own plan for unfinished work and access removal.

Before the call, prepare the role scope, the intended start date and a sample first assignment. Include the shared hours your team needs. Bring the proposed day-30 outcome so both sides can discuss what the hire will actually do.

Your manager should leave the discussion knowing which tasks belong to the client and which belong to the provider. Put those decisions beside the onboarding schedule, with names and dates.

Talk to Opus about a role.

<!-- Not saved to disk because filesystem access is read-only. Page rendering was not checked. -->