Year Two Is What Matters: The Real Timeline (and 3 Decisions) That Take an Outsourcing Relationship From "Delivery" to "Partnership"

The Client's Real Problem

A 12-year-old trading company paid NT$60,000 for a website four years ago. Since then, every time they want to change a price list they re-find a vendor, re-request a quote, and re-explain "what our company does." They weren't unwilling to pay — they started from zero every time, because each vendor only did "this one delivery" and no one accumulated "knowledge of this company." What they actually wanted wasn't a cheaper quote; it was a long-term partner who "remembers who we are so we don't have to re-explain." That's the biggest difference between "delivery" and "partnership" outsourcing.

Myths to Break

Myth 1: "One-off projects are cheaper; retainers lock you in." Truth: the "re-onboarding cost" of repeatedly finding new vendors (re-explaining, re-reading old code, rebuilding trust) often exceeds a retainer — the bill just never gets tallied for you.
Myth 2: "The longer they work with you, the more they slack." Truth: slacking comes from relationships with no renewal incentive; a well-designed long-term relationship ties the vendor's interest to your system's stability.
Myth 3: "Switching vendors is easy." Truth: the hidden cost of switching is "knowledge reset to zero" — every "why" in the old system must be rediscovered, and you're most fragile during that stretch.
Myth 4: "Long-term = spending more." Truth: the real value of long-term is decision continuity, so every dollar builds on last year rather than starting over.

Core Framework: A Three-Stage Maturity Model for Outsourcing Relationships

See the relationship as three stages and you'll know what to decide now:

Stage 1 (months 0–12): Delivery. Goal: build it, launch it, stabilize it. KPIs: on time, accurate, usable.
Stage 2 (months 13–24): The pivot. Goal: move from "done" to "continuous improvement." This year sets the relationship's trajectory.
Stage 3 (month 25+): Partnership. Goal: the vendor participates in your business decisions, not just takes tickets.

Three Typical Companies, Different Conclusions

Small (under 10 people): usually needs "delivery + light maintenance"; in year two a small retainer to keep it working is enough.
Mid-size (10–50): year two should invest in decision continuity — a fixed partner plus quarterly planning to avoid re-onboarding every revamp.
Growth-stage (fast scaling): year two should upgrade outsourcing from "execution" to "advisory," letting the vendor shape the tech roadmap so the system keeps up with scale.

The 3 Key Decisions of Year Two

Decision 1: Institutionalize knowledge? Build shared requirement records, decision records (ADRs) and ops docs so the relationship doesn't depend on one person's memory.
Decision 2: Shift pricing from per-project to monthly? If you have quarterly change requests, a retainer usually costs less — and moves faster — than re-quoting each time.
Decision 3: Bring the vendor to the decision table? Letting outsourcing join planning, not just receive tickets, is the divide between "partner" and "order-taker."

Full Hidden-Cost List (the Real Price of Vendor-Hopping)

Re-onboarding hours: each switch re-explains requirements and re-reads old code, usually dozens of hours.
Knowledge-loss cost: the "why it's built this way" can't be handed over, so a new vendor only re-guesses.
Trust-rebuild period: the run-in phase carries the highest communication cost and error rate.
Opportunity cost: during this stretch you can't advance new features — stagnation.
Maintenance-gap risk: if something breaks mid-handover, no one owns it.

KPI Scorecard for Evaluating an Outsourcing Partner

☐ Do they proactively leave documentation (rather than lock knowledge in their heads)?
☐ Will they honestly say "this isn't right for you"?
☐ Are response times and SLA explicit?
☐ Is pricing transparent, with no hidden monthly fees?
☐ Are source-code and IP ownership clearly written?
☐ Do they understand your industry and business model?
☐ Is there an incident-response mechanism and postmortem when things break?
☐ Do they take tickets, or give you advice?

ScriptWalker's Options + When We're Not a Fit

We offer four collaboration models: one-off project, monthly retainer, quarterly advisory, and full outsourcing. Honestly, we're not a fit when: you only want the lowest price and don't care about quality; you expect "unlimited revisions to satisfaction" without scoping; or you have no internal contact to own decisions. In those cases, a long-term relationship only wears both sides down.

Transition Playbook (From Delivery to Partnership)

Month 1: inventory the current system, build shared docs and decision records, move "knowledge" off people and onto documents.
Months 2–3: pilot quarterly planning, turning "passively receiving tickets" into "proactively offering advice."
Day-90 review: check whether this quarter's changes built on the earlier base and whether communication cost dropped, then decide the pricing model.

Decision Checklist

☐ Do I have system change requests every quarter?
☐ Do I re-explain my background every time I find a new vendor?
☐ Does my system knowledge live only in one person's head?
☐ Do I want the vendor to join planning, or only execute?
☐ Have I tallied the hidden cost of vendor-hopping?
☐ Do I have an internal contact for the long term?

FAQ

Won't a retainer become "paying with nothing to do"?

No — provided scope and SLA are explicit. A good retainer covers maintenance, monitoring, small changes and priority support, i.e. "someone guarding it even when you're away." If you have quarterly change requests, it usually costs less than re-quoting each time.

How do I judge if a vendor is worth a long-term relationship?

Two things: do they proactively leave documentation, and will they honestly say "this isn't right for you." Vendors willing to institutionalize knowledge and decline unreasonable requests won't lock you in over time.

Is year two really more important than year one?

For long-term cost, yes. Year one decides "does it work"; year two decides "can this relationship save your repeat costs later." Most people put all attention on year one and miss the real divide.

What exactly makes switching vendors expensive?

Knowledge reset to zero. Every decision in the old system must be rediscovered by a new vendor, and that handover is when communication cost and error rate peak while you can't advance new features. This bill is usually bigger than a retainer — it just never appears on a quote.

Call to Action

Want to know what stage your outsourcing relationship is at and which year-two decision to make? We offer a free 30-minute consult to tally the hidden cost of vendor-hopping together.