Short answer: it depends on whether knowledge lives in people or in the system. Score the project on eight items worth 16 points; at 9 or more, name 2–3 key people in the contract, require 10 working days’ notice and a 5-day paired handover at the vendor’s cost, or expect 2–4 extra weeks of delay.
A 45-person skincare chain paid NT$800K to outsource a membership and order system. In week 10 the vendor wrote: “Our back-end engineer leaves next week; a colleague will take over.” The new engineer needed three weeks to understand the code, two deployments failed, and launch slipped from June to late July, missing the anniversary sale. The contract never mentioned people.
Myths to drop
- “Big vendors have spare people.” Headcount isn’t a handover process; big shops often move seniors to new deals.
- “We have the code, so we’re safe.” Deployment steps, credentials and third-party settings often live in one head.
- “Ban staff changes in the contract.” You can’t stop resignations; specify notice and handover instead.
- “Handover is the vendor’s cost.” Your schedule pays for the learning curve.
The framework: a staff-change risk score (8 items, 16 points)
Score each 0–2; at 9 or more, put people clauses in the contract.
| Item | 0 | 1 | 2 |
|---|---|---|---|
| Engineers on the project | 3+ | 2 | 1 |
| Code review | Every merge | Sometimes | None |
| Repository owner | Client | Vendor, transferable | Engineer’s personal account |
| Deployment docs | Current and usable | Outdated | None |
| Automated tests | Core flows covered | A few | None |
| Task records | All in a PM tool | Partly in LINE | Verbal |
| Service accounts | Client-owned | Mixed | Engineer-owned |
| Remaining schedule | Under 1 month | 1–3 months | 3+ months |
Google’s DORA research lists documentation quality as a capability that affects delivery performance, which is why docs and task records carry four points.
Three scenarios
- 15-person design firm, NT$250K website: about 7 points; just confirm domain and hosting are in your name.
- 45-person retail chain, NT$800K member system: about 12 points; add key-person and handover clauses and move the repo to your organization.
- 120-person manufacturer, NT$2M ERP extension: about 5 points; review docs quarterly.
Hidden costs: one swap adds roughly 5–10% of the contract
- Learning curve: 2–4 weeks at about half productivity.
- Delay losses: a missed season often costs more than the build.
- Rework: 20–40 hours fixing new mistakes.
- Your time: 8–16 hours re-explaining requirements.
- Access risk: recovering accounts held by a departed engineer.
Vendor scorecard: ten questions
| Dimension | Ask |
|---|---|
| Team | How many engineers, and who is backup? |
| Turnover | Average engineer tenure? |
| Handover | How many days, and who pays? |
| Code review | Is every merge reviewed? |
| Repo ownership | Can it live in our GitHub organization? |
| Docs | Can we see a past deployment doc? |
| Tests | Are core flows tested automatically? |
| PM tool | Where are tasks tracked, and can we see them? |
| Notice | How early are key-person changes announced? |
| Track record | How did past mid-project swaps go? |
Repos can start in the client’s organization, and GitHub supports transferring repository ownership.
ScriptWalker’s options and poor-fit cases
At ScriptWalker (a Taiwan custom Laravel/Flutter development studio), at least two people know every codebase, and repos and accounts default to the client’s name.
- Project: from NT$150K, with a key-person and 5-day handover annex.
- Maintenance retainer: from NT$2,000 a month, including doc updates.
- Advisory review: NT$15K–30K to assess your current vendor’s staffing risk.
- Dedicated team: 2–3 fixed people, monthly fee.
Not a fit:
- One named engineer on-site full time, no team model
- A one-person budget for a large system in three months
- Refusing to hold repos and accounts in your own name
- 24-hour on-site shift support
Transition playbook: 90 days after a swap
- Weeks 1–2: five paired days; the new engineer deploys one small change to staging.
- Weeks 3–4: update docs; confirm all accounts are yours.
- Months 2–3: if weekly output drops 30%+, ask for extra help.
- Day 90: re-score and update the contract annex.
Decision checklist: five or more yeses means fix the contract now
- ☐ One engineer on the project
- ☐ More than three months left
- ☐ Repo not in your name
- ☐ Never seen a deployment doc
- ☐ No key-person clause
- ☐ No notice period for changes
- ☐ Tasks mostly in LINE
- ☐ Hosting and service accounts under an engineer’s name
- ☐ A fixed launch date
- ☐ Unknown vendor turnover
- ☐ No automated tests
FAQ
Can the contract ban engineer changes?
Not usefully. Specify notice, handover days and who pays instead.
How long should handover last?
At least five paired working days, ending with one deployment by the new engineer.
Can I hold the vendor responsible for delays?
Yes, if the contract has key-person and handover clauses and a delay remedy.
How do I spot an unannounced swap?
Check commit authors in the repo and require named staff in weekly reports.
Next step: score your project
If you land at 9 or more, we’ll spend a free 30 minutes on which clauses to add:
- Email: [email protected]
- Phone: 0916-224-047
- LINE: @ufv9089p