Build a staff augmentation business plan for the first 90 days

What should your staff augmentation business plan settle first?

Approve the work the hire will own, the manager who will support them, and the budget for getting them started. Then build the onboarding schedule around those decisions.

For this plan, use a practical staff augmentation definition: an outside professional joins your existing team, while your manager directs their daily work. The onboarding plan should show how that person becomes able to deliver within your systems.

A job title is too broad to guide the first month. "Back-end engineer" describes a role. "Own fixes to the billing API, with a senior engineer reviewing releases" gives the hire a starting point.

Use the following schedule as a planning template. These are proposed checkpoints, not promises about how quickly every person should become productive.

Prepare the work before the person arrives

Write a short role charter. Name the business problem, the work in scope, and the decisions the hire may make. Include work that needs approval, such as changing a customer-facing API or accessing production data.

Pick an initial task with a clear finish. For an engineer, that might be fixing a reproducible bug with an existing test. Avoid a task that depends on an unresolved architecture decision.

Assign an onboarding teammate and reserve time for questions and reviews. Put that time on the calendar before you promise a delivery date.

Prepare access through your usual approval process. Request only what the role needs. Record who can approve extra access, and give the hire a way to report a setup problem without sharing credentials.

Keep a readiness checklist with an owner for every open item. If equipment is late, the manager should know what work can proceed and what must wait.

Use days 1–30 to test the working setup

Start with the product and the people who use it. Walk through a real customer task, then show how the team's work supports it.

For engineering roles, trace a small change from ticket to release. Explain who reviews code, what checks must pass, and how the team handles a failed deployment. Let the hire follow the process with a low-risk task.

Agree on how to raise a blocker. A useful message states what the person tried, what happened, and whose decision or access they need. Name a backup contact for days when the manager is absent.

At day 30, review actual work. Ask whether the hire can explain the task, use the team's tools, and act on feedback. Check whether your team provided timely answers and reviews.

If the first task remains unfinished, record the cause. A delayed account approval calls for a different response than repeated mistakes after clear coaching.

Use days 31–60 to expand responsibility

Choose a bounded deliverable that requires the hire to plan and complete work. For example, assign an API change with agreed behavior and a named reviewer.

Ask the hire to identify dependencies before starting. Which decision needs a product owner? Which change needs another team? Who can approve release?

Keep the team's normal quality checks. Reduce hands-on guidance when the work supports that decision, while retaining peer review and required approvals.

At day 60, compare the result with the agreed scope. Review rework and unresolved questions alongside completion. Ask the teammate where help was still needed.

Use those findings to set the next month's scope. If the hire can complete routine changes but struggles with unfamiliar systems, plan a supported task in that area.

Use days 61–90 to decide what the hire can own

Give the hire an area with clear boundaries. Ownership might include routine fixes, documentation, and estimates for a small service. State which decisions still belong to the internal team.

Test the handoff. Ask another teammate to use the hire's notes to understand an open task or repeat a routine procedure. Correct gaps while both people are available.

At day 90, decide whether to continue the current scope, change it, or address a persistent fit problem. Record the reason and the next owner.

Check contract deadlines before this meeting. Schedule the decision early enough for the person responsible for renewal or notice to act.

What does recruiting data tell you about the schedule?

SHRM's 2025 recruiting benchmark puts median time to fill at roughly a month and a half for executive and nonexecutive roles. It defines that period as job requisition to offer acceptance. That is a recruiting measure, not an onboarding deadline. SHRM's recruiting benchmark.

Keep separate dates for role approval, offer acceptance, and the first working day. Begin your onboarding checkpoints from the first working day.

A candidate accepting an offer does not confirm that equipment, access, and manager time are ready. Ask each owner to confirm their part before treating the start date as firm.

Do not turn a broad recruiting benchmark into a forecast for a specific role. Your interview availability and approval steps belong in your own hiring schedule.

Measure progress with work you can inspect

Build a small scorecard around the role's actual tasks. Agree on the evidence before the hire starts.

Avoid using ticket count as the sole measure. Record what the tasks involved and whether they were ready to start. A small bug fix and a cross-team migration need different judgments.

Track delays caused by your own process. Note when a ticket waited for review or a decision. That gives the manager a concrete problem to fix.

Keep the scorecard short enough to discuss in a regular check-in. Link to work records instead of asking the hire to duplicate them in a separate report.

Budget for the team's onboarding time

Your staff augmentation plan should include more than the provider invoice. Assign budget owners for equipment, software access, and any approved setup costs.

Reserve internal capacity for onboarding and code review. A senior engineer who is helping a new teammate needs room in their own workload.

Use the written quote to build the external cost line. Separately list costs your company pays directly. Ask about billing start dates and how approved changes to the role affect the price.

Do not assume the hire will carry a full workload immediately. Use the phased scope to plan capacity, then revise it from observed delivery.

How do hiring models change a nearshore onboarding plan?

Choose the model by the work your team will manage and the responsibilities it wants a provider to take. Put those responsibilities in the agreement.

A nearshore or Latin American hiring plan still needs an internal owner for access and work priorities. Geography does not assign those tasks.

These are planning distinctions. Ask each provider to name the party responsible for every task instead of relying on the service label.

If your team cannot assign work or review it, resolve that gap before adding a person. A hire needs someone authorized to settle priorities.

If you need a supplier to own a complete deliverable, write that expectation explicitly. Discuss how acceptance works and who handles changes to scope.

Agree on hours by location

Record the hire's city and the team's working location. State when both sides need to be available and which work can proceed without a live meeting.

Bogotá stays on UTC-5 without daylight saving time. Buenos Aires stays on UTC-3 without daylight saving time. Those fixed offsets do not mean every US team's meeting time stays the same throughout the year. IANA time-zone records.

Use calendar time zones for recurring meetings. Assign someone to check shared hours when clocks change. Confirm that the proposed schedule works for the hire before treating it as a requirement.

Add local holidays and planned leave to the team's calendar. Ask the provider to explain the applicable schedule and how absences should be reported. Name the person who will cover urgent work.

Make the handoff rules visible

Write down where decisions live. If a task changes during a call, update its ticket so the hire can work from the same instructions as everyone else.

Set a response expectation for blockers during shared hours. Avoid making every question urgent. Distinguish a production incident from a request that can wait for the next review.

Choose the working language for meetings and written handoffs. Test job-specific communication during interviews with a realistic task, such as explaining a bug or clarifying an incomplete request.

What should you ask a provider before day one?

Give the provider your role charter and proposed milestones. Ask them to review the start-date assumptions and identify tasks that need action from your team.

Request named owners and written answers to questions that affect the schedule or cost.

Who handles each pre-start task?

Ask who confirms equipment delivery, handles employment paperwork, and answers payroll questions. Your IT team should name its own access approver.

Create a shared checklist with due dates. Keep sensitive personal details in the approved system rather than copying them into a general project document.

Ask what happens if a pre-start task slips. Confirm who contacts the hire and who decides whether to move the start date.

What does the quoted price include?

Ask for a role-specific written quote. Confirm the billing currency, invoice schedule, and the event that starts billing.

List equipment and software separately unless the agreement includes them. Ask how leave, overtime requests, or a change in scope affect the arrangement.

Have the budget owner review the quote against the planned engagement. Record any approval needed before costs can change.

How will we handle weak performance?

Agree on an escalation contact before a problem occurs. Ask how the provider expects you to document concerns and what support follows.

Use specific examples when raising an issue. Include the task, the agreed standard, the feedback given, and the result after feedback.

Set a recovery task and review date when improvement is realistic. If the role was poorly scoped, revise it with the hire and provider.

Ask about replacement terms separately. Confirm what happens to billing and ongoing work during a transition, along with any steps your team must take.

What happens when the engagement changes or ends?

Assign an owner for access removal and equipment return. Keep work records in company-controlled systems throughout the engagement.

Ask who coordinates the final handoff and which contract deadlines apply. Plan how another person will take over open tasks.

Keep the onboarding plan and exit checklist together. Both should identify the systems, decisions, and work the person owns.

Opus is an option to discuss against this checklist. This site is an Opus-owned reference; recommendations are editorial.

Talk to Opus about a role.

Where does Opus fit in the onboarding plan?

Opus states: "The client chooses the finalist and manages day-to-day work." Assign your own manager to priorities, feedback, and acceptance of completed work.

Use that division of responsibility when preparing the first assignment. Your manager should choose the task and arrange access to the people who can review it.

Opus states: "Every Opus placement works with US timezone overlap." Before hiring, agree on the actual shared hours and the meetings the role must attend.

Separate the provider's coverage from your team's work

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."

Published dollar rates: Not published.

Ask for the written quote for your role. Use it to confirm the external cost, then budget separately for your manager's time and any direct setup costs.

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

Ask how a replacement would work during an active project. Confirm the handoff steps and the responsibilities your team would retain. Keep documentation current so another person can understand the work.

Bring a role that is ready to start

Take the proposed scope and onboarding schedule into the conversation. Include the first working date you want, the manager's name, and the initial task.

Explain what success would look like at each review. Use examples your team can assess, such as an accepted production change or ownership of routine fixes.

Identify any dependencies that could delay the start. Access approval, equipment delivery, and reviewer availability should each have an owner.

Before committing, have the hiring manager and budget owner review the same plan. The manager confirms the work and support. The budget owner confirms the spend.

Talk to Opus about a role.

<!-- File save skipped: the workspace is read-only. The page has not been checked in the site renderer. -->