Before you email
Before you email
Send the same role scope to each provider so the replies are easier to compare.
- What would you include in week 1, and what would you leave out until the role is cleaner?
- Can you separate first-month cost, ongoing cost, setup fees, tools, management fees, and replacement fees?
- Which SOPs, examples, scripts, or sample outputs do you need before day one?
- What would make this role a poor fit for your team or candidate pool?
Build the quote briefOn the sales call
On the sales call
Use the call to test how the provider handles scope, review, access, price, and backup coverage.
- Who does the work, who manages it, and who checks the first week of output?
- What does a bad output trigger: rewrite, manager review, retraining, or replacement?
- Which actions should stay with our manager until the provider proves fit?
- What answer would change your quote after this call?
Score the provider callWhen the quote comes back
When the quote comes back
A polished quote can still hide vague scope, extra fees, broad access, or weak quality checks.
- Which tasks are included, which are excluded, and which are still assumptions?
- What fees are outside the headline rate?
- What proof will we see in week 1 that the role is working?
- What happens if the assigned person is not a fit?
Check quote red flagsWhen you compare proposals
When you compare proposals
Put each proposal into the same fields before you decide who moves forward.
- Are all providers pricing the same first 30 days of work?
- Which proposal gives the clearest review plan for weeks 1, 2, and 4?
- Which proposal asks for the least access needed to start safely?
- Which assumptions need a written answer before we sign?
Compare proposalsBefore you shortlist
Before you shortlist
Choose providers based on fit, scope, ownership, quality checks, access risk, and backup plan, not pitch polish.
- Can this provider explain the first week without turning it into a broad sales story?
- Who owns SOPs, examples, training notes, and handoff docs after work starts?
- What should the hire never touch without written approval?
- What visible output should we expect by day 30?
Build the shortlistBefore you share access
Before you share access
Tool access should be named, limited, reviewed, and easy to remove before the first task starts.
- Which named accounts, MFA rules, and permission levels will the worker use?
- Which actions are blocked unless our manager approves them in writing?
- Who reviews access after seven days, and what gets removed if the scope changes?
- How will offboarding work if the provider, seat, or contractor changes?
Plan access handoffBefore you sign replacement terms
Before you sign replacement terms
Replacement included only helps when timing, handoff notes, retraining, and coverage are clear.
- What counts as a replacement trigger?
- How fast does replacement start, and who covers open work while the seat changes?
- Who pays for retraining, repeated onboarding, or duplicated manager review time?
- Which notes, SOPs, and account access move to the replacement worker?
Write replacement rulesIn the first week
In the first week
The first week should prove access, scope, quality, and owner review before the role expands.
- What worked on day one, and what blocked the worker?
- Which mistakes repeated by day three?
- What should stay blocked until the SOP or review rule is better?
- What can expand next week without adding too much manager cleanup?
Run the first-week review