Nothing here is a surprise on purpose.
Most staffing goes wrong in the first three weeks, and almost never because of skill. It goes wrong because nobody agreed on who gives direction, nobody provisioned access, and everyone expected week one to look like month three.
So here is the whole thing, written down before you buy it.
30 minutes. One question does most of the work.
"Walk me through last week. What did you personally do that somebody else could have done?"
That is the question. You answer it, we write down what you say, and that becomes a scope document you read before any money changes hands.
We are also listening for the things a co-laborer should not touch. Pastoral conversations. Anything requiring a body in the building. Banking. We name those on the first call rather than letting you find them in month four.
By the end of the call you know two things: whether this fits, and what the first 90 days would cover.
You meet your co-laborer before we place them.
For a generalist, we work from co-laborers who have already cleared our standard: faith and character interview, paid work simulation, background check, pastoral reference. We interview them against your specific list, not against a generic profile, then we introduce you.
For a specialist, we recruit to order. When you ask for a bookkeeper, a paid ads manager, a video editor, or a senior executive assistant, we run a three to four week search against that exact role. We do not keep a bench, which means we are never trying to place the person we already have instead of the person you need.
You meet the candidate. If the fit is wrong, we say so first, and we go again.
Week one is not the test.
Access comes first. In the first week you provision named accounts through your own administrator, at the least privilege each task requires. A co-laborer without access is a co-laborer who cannot work, and this is the single most common reason a good first month turns into a slow one.
Then we set the shift. Fixed days, fixed hours, a minimum of five hours overlapping your business hours, written into your scope attachment. It does not float.
Then they start learning your organization, and the arc below begins.
We rewrite the document against what actually happened.
At day 30 you and your account manager go back through the scope attachment line by line. Work that turned out to be bigger than expected gets more room. Work you thought you wanted turns out to be nobody's priority and comes off. New work you did not think of on the first call goes on. Then quarterly after that.
Scope grows in every good engagement. The only question is whether it grows on paper where both parties can see it, or silently, until somebody feels taken advantage of.
Week by week, honestly.
-
Week 1: Shadowing
They are learning your tools, your people, your calendar, and your voice. Be honest with yourself about this week: you might get three hours back, and you will spend some of your own time answering questions.
~3 hours back
-
Weeks 2 to 4: They own the recurring work
The bulletin. The volunteer schedule. The weekly email. Guest follow-up. Data cleanup. The work that happens every single week and takes the same shape every single time.
10 to 15 hours a week back
-
Month 2: They start catching what you forgot
The co-laborer stops waiting for assignments and starts flagging the thing nobody assigned. The gift that failed to process. The guest from three weeks ago who never got a second contact. The room double-booked for Thursday.
-
Month 3: They run processes they wrote down themselves
Part of the job from day one is documenting your processes as they learn them. By month three those documents exist, and your co-laborer runs from them. If the person ever changes, the knowledge does not walk out with them.
This part is not optional, and we would rather say so now.
The engagement is mutual. These are your commitments, and they belong in the conversation before the contract instead of after the first problem.
- Name one point of contact and keep it stable. Others can submit requests; those requests route through one person. A remote team member taking direction from five people cannot prioritize and produces less than half of what they are capable of. Placements fail on this more than on skill. If you take one thing from this page, take this one.
- Give 20 to 30 minutes of direction a week. That is the real number. A short standing check-in where you say what matters this week and answer what got flagged last week.
- Provision access in the first week. Named accounts, issued by your administrator through a password manager, at least privilege. Never a shared login, never sent by email or chat.
- Raise concerns early, while they are still small. A correction in week two is a five-minute conversation. The same correction in month four is a replacement.
- Give it the first 30 days. Week one is shadowing. Real output starts in week two. Judging the placement on week one is like judging a hire on their orientation day.
You will never get a surprise invoice.
Here is exactly what happens when you ask your co-laborer for something the scope attachment does not cover. They acknowledge the request. They do not start the work. They flag it to their CoLabor account manager the same day. Your account manager comes back to you within two business days with one of three answers:
- In scope. Proceed.
- That is specialist work. Here is the rate, and here is the timeline.
- That is not something we do. Here is what we suggest instead.
Nothing gets billed to you that you did not approve first. Ever.
This routing also protects the co-laborer. A dedicated person who wants to be helpful, working across a cultural distance, for a client they respect, will say yes to almost anything. Scope protection has to route around that instinct instead of depending on one person to resist it at 4pm on a Friday.