Build a 30/60/90-day staff augmentation business plan

What should your 30/60/90-day plan achieve?

Give the new hire a defined area of work and a manager who has time to review it. Then set checkpoints that show whether the person can take on more responsibility.

Start the onboarding clock on the first day worked. Keep recruiting, offer acceptance, and start-date planning on a separate schedule. Otherwise, a delay before someone joins can look like a failure during their first month.

Use this proposed operating schedule and adjust it to the role. These milestones are planning choices, not promises about how quickly every hire will perform.

Write the business case before the task list

Name the work the team cannot complete with its current capacity. "Add an engineer" is a headcount request. "Give the billing team capacity to finish the export backlog" is a need you can discuss and test.

Record what happens if you do not hire. You might defer a release, narrow its scope, or move someone from another team. Put the proposed hire beside those choices so the budget owner can judge the tradeoff.

Keep the plan in a shared document that the hire can read. Goals in a budget presentation will not guide someone who never sees them.

Before day one: make the first task possible

Choose a manager and a teammate who can answer day-to-day questions. Reserve their time before confirming the start date.

List each system the hire needs, the access level, and the approver. Use individual accounts and grant access based on assigned work. Keep production access subject to your normal approval process.

Choose the first task while you can still check its dependencies. An engineer could fix a small defect with a known reproduction path. An operations hire could prepare a recurring report with documented inputs.

Write acceptance criteria a reviewer can use. "Understand the product" is hard to assess. "Explain the export flow and complete a reviewed fix" gives the manager something to inspect.

Prepare a fallback task in case access is delayed. Reviewing a runbook with approved sample data may work. Do not use shared credentials to work around an approval.

Days 1–30: complete a small piece of real work

Connect product context to the actual work queue. Show the hire who uses the system, what failures affect customers, and how the team approves changes.

Have the hire run through the workflow with their teammate. For an engineer, this includes setting up the environment, running tests, and submitting a change. Ask them to document unclear setup steps.

Keep the initial task small enough for close review. Avoid using a neglected, high-risk project as the first test of someone's ability.

During check-ins, ask what is blocked and who can resolve it. Assign an owner to pending internal approvals. Do not leave the hire chasing an unfamiliar approval chain alone.

At the checkpoint, ask the hire to explain a completed task from request through review. Compare that account with the review notes. Record where they needed help and which decisions they made themselves.

Days 31–60: increase ownership within a clear boundary

Give the hire a larger task with a defined outcome. Ask them to propose the work steps, identify dependencies, and explain what could delay delivery.

The manager should still review scope before work begins. Less guidance does not mean leaving the person without a decision-maker.

An engineer who fixed an export defect might next own a small improvement to that flow. They could draft the approach, implement it, and prepare release notes. Keep the team's normal review and release controls.

Watch how the person handles uncertainty. Do they request a decision before making a costly assumption? Do they flag dependencies while there is time to respond?

Compare the result with the agreed scope. If the task changed, record that change before judging the outcome.

Days 61–90: decide what the person should own next

Assign an area with repeat work and a clear boundary. This could be a service component, reporting process, or defined part of the support queue.

Ask the hire to document how another teammate could cover the work. Test the handoff by having that teammate use the notes.

Use the final review to continue the scope, expand it, or set a focused support plan. If the fit is poor, discuss next steps with the provider using feedback already shared.

Write down which decisions the person can make without approval. Routine export fixes might sit within their scope while changes to customer data still need review. "Take more ownership" leaves that boundary unclear.

What does hiring data tell you about the schedule?

SHRM puts median time to fill at roughly a month and a half for executive and nonexecutive roles in 2025. It measures job requisition to offer acceptance. Your onboarding plan begins after that endpoint. SHRM's recruiting benchmark.

SHRM also reports screening and interviewing averaging 8–9 days each. Its benchmarking announcement describes responses from 2,371 members. Reserve interviewer time early, but do not treat those averages as deadlines for a particular role. SHRM's benchmarking announcement.

For budget context, BLS reports a May 2025 median annual wage of $135,980 for US software developers. The corresponding figure for software quality assurance analysts and testers is $104,300. These are occupational wage figures, not provider quotes or fully loaded employment costs. BLS occupational pay data.

Use the wage benchmark for the role you need. Do not substitute a developer median for a testing role or infer a nearshore savings percentage from US wages alone.

Measure work your team can inspect

Track accepted work, review feedback, and unresolved blockers. For an operations hire, check whether the agreed process runs correctly and exceptions reach the right owner.

Record the support time your team spends. A person may finish every task while needing more review than the manager can sustain. Resolve that mismatch before increasing scope.

Keep definitions consistent. If "complete" means reviewed and released at an early checkpoint, do not count unreviewed work as complete later. Link to the actual work so another manager can understand the decision.

Keep a record of delays

A missed milestone needs a cause and an action.

This record helps you judge the hire without hiding problems inside a general "still ramping up" label.

How should onboarding differ by hiring model?

Choose the model around the work and your management capacity. Confirm responsibilities in writing. A service label alone does not establish who coaches the hire or approves output.

For augmentation, include the person in planning and reviews relevant to their role. Give them the written acceptance criteria you would give an internal teammate.

For project outsourcing, focus on agreed outputs and acceptance. Confirm who assigns the supplier's internal work before building a plan around managing individuals.

Budget for the manager as well as the hire

Put the provider quote beside internal costs. Confirm when billing starts, what sits outside the rate, and which contract terms affect the total.

Separate purchases from recurring charges. If review work exceeds the plan, reduce scope or reserve more reviewer capacity before approving another assignment.

What should you ask a provider before onboarding a nearshore hire?

Ask for answers that name an owner, an event, or a contract term. "We support onboarding" leaves too much room for different expectations.

Confirm who owns each handoff

Identify who confirms readiness and who handles equipment issues. Separate the contact for employment questions from the person who discusses performance.

Ask these questions before choosing a finalist:

• Who confirms the start date with the hire?
• What must be complete before work begins?
• Who resolves payroll or benefits questions?
• What support continues after placement?
• How do we raise a performance concern?
• What happens to work and billing during a replacement?

Keep the answers with the onboarding plan. The manager using them may not have attended the sales call.

Agree on actual working hours

Write the schedule in both locations. Name shared hours reserved for reviews and decisions, and explain how to raise a blocker outside that window.

Bogotá stays at UTC-5 without daylight saving time. Its relationship to a US team's clock can change when that team changes clocks. Check recurring meetings at those transitions. IANA time-zone data.

Ask about the person's actual city and agreed schedule. A country name does not establish availability. Confirm holiday coverage and planned leave before committing the hire to a release.

Check how remote work happens in practice

For remote first companies hiring across borders, onboarding needs written routes to help. Give the hire a place for product questions and a separate route for urgent access issues.

Use a realistic blocked task in the candidate discussion. Ask how they would explain the problem and when they would seek help.

State which AI tools are approved and what data may enter them. Apply the team's normal review requirements to AI-assisted work.

Review replacement and exit procedures

Ask what triggers a replacement search, which charges apply, and what happens during the gap. Confirm how access and work handoffs will be handled.

A replacement still needs onboarding time. Keep task notes current, identify who revokes access, and arrange equipment returns before the departing person's final working day.

Where does Opus fit in this plan?

This site is an Opus-owned reference; recommendations are editorial.

Opus states: "The client chooses the finalist and manages day-to-day work." Your manager needs to own the work queue, give feedback, and decide when the hire can take on more scope.

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 rate: Not published. Request a written role-specific quote and include your equipment and management costs alongside it.

Opus also states: "Every placement carries a lifetime replacement guarantee with no cap and no time limit." Ask how the process applies to your engagement, including billing and handoffs during a change.

Bring the role scope, working hours, and proposed first task to the discussion. Explain who will review the work and what the hire should own at the final checkpoint.

Talk to Opus about a role.

What should a staffing plan look like?

Use a shared plan that connects the hiring decision to accepted work. The following example is a planning template, not a reported client result.

Replace the example with actual owners and links to work. Keep sensitive commercial terms in a restricted budget record when necessary.

Update the plan when priorities change. If a release is cancelled, reassess the assignment instead of judging the hire against obsolete work. Record who approved the change and what replaces the original goal.

What are the different types of staff augmentation?

Describe the assignment by duration, skill need, and location. These are separate choices that can overlap.

Temporary capacity suits a defined backlog or coverage gap. Set an end condition and plan the handoff before the assignment starts.

An ongoing embedded role suits recurring work under your manager. Give the person a maintained backlog and review their scope during normal planning.

Specialist augmentation targets a particular skill gap. Define the technical decision or deliverable, and require knowledge transfer to someone who will maintain the result.

Onshore, nearshore, and offshore describe location relative to the buyer. Choose working arrangements around the actual schedule, access requirements, and review process. Location alone does not establish experience or communication quality.

Avoid choosing a type solely by its hourly or monthly price. Compare the work you expect, the support it needs, and the contract's end conditions.

What are the 7 important functions of staffing?

For this onboarding plan, use the following practical grouping. Assign each function explicitly so work does not fall between your team and the provider.

1. Workforce planning: define the capacity gap and decide whether hiring is the right response.
2. Recruitment: turn the role scope into a search and keep candidate expectations consistent.
3. Selection: assess relevant skills and reserve time for a final hiring decision.
4. Placement and orientation: confirm the assignment, start conditions, team contacts, and first task.
5. Training and development: teach company-specific systems and address observed skill gaps.
6. Performance appraisal: compare accepted work with agreed expectations and give timely feedback.
7. Compensation and retention: assign pay and employment questions, then review whether the role remains workable for the person.

The provider may handle parts of this work. Your manager still needs to know who owns each function and when to escalate a problem.

How quickly can companies scale with staff augmentation?

Set the schedule from the next hire's dependencies and your team's capacity to absorb the work. Candidate selection, the first day worked, and useful delivery are different events.

Ask the provider for a role-specific schedule with clear endpoints. Then add your interview availability, access approvals, equipment delivery, and review capacity. Confirm which steps can happen in parallel.

Use these gates before adding more people:

Start the next search when demand is clear, but confirm the start date against readiness. Stagger arrivals when the same teammate must support everyone.

If completed work is waiting for review, adding engineers can enlarge that queue. Assign reviewer capacity before treating more headcount as the answer.

What should a buyer know about conclusion?

Close the onboarding period with a written decision about the assignment. State whether the person will keep the current scope, own more work, receive focused support, or enter a replacement process.

Compare accepted work with the original business need. Check actual spending and manager time. Separate delays caused by the hire from delays caused by access, changing priorities, or slow internal reviews.

Agree on the next scope with the person doing the work. Name the decisions they can make, the reviewer for higher-risk changes, and the teammate who can provide cover.

Before approving another hire, confirm that the same plan can support them. Put their first review on the calendar and assign their access requests.

Talk to Opus about a role.

<!-- File not saved: the workspace is read-only. Build and rendering checks were not run. -->