The Memo That Gets Outsourced Engineers Approved

You are convinced. Your CFO is not yet. Copy this memo, replace the brackets with your own figures and send it.

Everything outside the [brackets] is a published StepTo term, a published practice, or a cited benchmark. Everything inside the brackets is yours: the need, your cost of delay and your budget. The floors are a starting point, not a quote. For a number to put in the first bracket, use the open seat calculator, and to see how StepTo answers the questions your procurement team will ask, read the due diligence answers.

The vacancy benchmark is from SHRM's recruiting benchmarking. This is a template, not financial advice.

Subject: Request to add [number] engineers through a nearshore partner

1. The need

We need [number] [role] engineers for [project or goal] by [date]. Without them, [what is blocked] stays blocked, which costs us about [your figure] per week.

2. Cost floor

The partner publishes its floors. Staff augmentation starts from $4,500 per developer per month, with a 3-month minimum and weekly billing. A dedicated team of three starts from $13,500 per month, billed monthly. These are floors, not a quote: the final price follows seniority mix, stack and scope. Our budget for [number] engineers is [your figure], to be confirmed against the partner's written quote.

3. The cost of waiting

The in-house alternative is a search. SHRM's recruiting benchmarking puts the median time to fill a nonexecutive position at 39 calendar days. For our own role the estimate is [days] days at [your cost per day] per day, or [your figure] before the engineer starts.

4. Speed

Engineers can typically start within one to two weeks of first contact; a full team usually takes two to four weeks.

5. Commitment and exit

3-month minimum, then 30 days notice to scale down. Replacement: free within the first 30 days.

6. How quality is checked

Every change is reviewed by a second engineer before it is merged. We can verify this ourselves: Open any merged pull request in your repository. It should show an approving review from someone other than the author. A CI pipeline runs automated tests on every pull request. We can verify this ourselves: Look at the checks on any pull request. The test run and its result are listed next to the review. Engineers work in your repository and your tools from day one, and you own the code at all times. We can verify this ourselves: Every commit lands in the repository you control, under a named engineer's own account.

7. Decision requested

Approve a budget of [amount] for [term] starting [date], with [name] as the named owner on our side.

Ready for the next step? Spec the team you want on the team spec page or see the full terms on the pricing page.

Performance-led engineering

Want senior engineers who move work forward, not just tickets?

Work with accountable, English-fluent professionals who communicate clearly, protect quality, and deliver with a steady operating rhythm. Cost efficiency matters, but performance is why clients stay with us.

Delivery signals · senior engineering team
Senior ownership
Lead-level
Delivery rhythm
Weekly
Timezone overlap
CET
1 teamaccountable for outcomes, communication, and execution