The Outsourcing Readiness Checklist: 12 Questions Before You Start [Part 2]
6 more questions to assess outsourcing readiness: management bandwidth and realistic expectations. Part 2 of the readiness checklist.
Most companies decide to outsource when they're under pressure.
Hiring is slow. The roadmap is slipping. Stakeholders are asking why features are taking so long. Outsourcing seems like the fastest way to add capacity.
So they start evaluating vendors. Compare portfolios. Negotiate rates. Sign contracts.
Then, three months in, the partnership stalls. Requirements were unclear. Expectations misaligned. The outsourced team delivers code that doesn't fit the architecture. Internal engineers spend more time reviewing and fixing than they would have spent building themselves.
The problem wasn't the vendor. The problem was starting before the company was ready.
This two-part checklist helps you assess readiness before you commit. Part 1 covers Scope Clarity and Internal Ownership. Part 2 covers Management Bandwidth and Realistic Expectations.
Answer each question honestly. "Partially" counts as "No."
Here's the uncomfortable truth: even a great outsourcing partner can't save a poorly-prepared client.
The best vendors have processes, experience, and engineering talent. But they can't:
Outsourcing amplifies what you already have. Clear scope, defined ownership, and realistic expectations become efficient delivery. Unclear scope, contested ownership, and unrealistic expectations become expensive friction.
Before evaluating vendors, evaluate yourself.
Not a paragraph. Not a vision document. One sentence that anyone on your team would agree with.
Example of clear scope:
"Build a patient intake form that collects medical history, validates insurance eligibility, and stores data in HIPAA-compliant infrastructure."
Example of unclear scope:
"Improve our patient experience and modernize the onboarding flow."
The second example sounds reasonable in a strategy meeting. It's a disaster for an outsourcing engagement. "Improve patient experience" means different things to different stakeholders. The outsourced team will guess - and guess wrong.
If you can't answer this: Don't outsource yet. Run a scoping workshop internally first. Get alignment on exactly what "done" looks like.

Outsourcing works when requirements can be transferred. If your product vision exists only in the founder's head or in scattered Slack conversations, the outsourced team will spend half their time trying to extract what you need.
This doesn't mean you need a 50-page PRD. But you need:
If you can't answer this: Write requirements first. Even a 2-page document is better than nothing. The act of writing forces clarity.

Requirements evolve. That's normal. But there's a difference between "we'll refine details as we build" and "we're still figuring out what product we're building."
Outsourcing works poorly when:
If scope changes significantly after the contract is signed, you'll either pay for rework or get something that doesn't match what you now want.
If you can't answer this: Wait until product direction stabilizes. Use internal resources for exploration. Outsource execution, not discovery.

Not a committee. Not "the engineering team." One person.
This owner is responsible for:
Without a clear owner, the outsourced team sends questions to Slack channels that go unanswered. Decisions get delayed. Small ambiguities become large misalignments.
If you can't answer this: Assign an owner before signing any contracts. If no one has bandwidth to own this, you don't have bandwidth to outsource.

Having an owner isn't enough. That person needs authority.
If every decision needs approval from the CEO, or requires consensus from three departments, the outsourced team will wait. And wait. And their timeline estimates will mean nothing.
Questions to test decision authority:
If you can't answer this: Clarify decision rights before starting. Document what the owner can decide alone and what requires escalation.

Outsourcing doesn't eliminate the need for internal engineering. Someone needs to:
If your internal engineers are already at 100% capacity, adding an outsourced team won't help. They'll produce code that sits in review queues, or gets merged without proper validation.
Rule of thumb: Plan for 15-25% of internal engineering capacity to support outsourced work. If you don't have that bandwidth, either free it up or don't outsource yet.

Count your clear answers for Questions 1-6:
5-6 clear answers: You have scope clarity and ownership in place. Move to Part 2.
3-4 clear answers: Address gaps before continuing. Most can be fixed in 1-2 weeks.
0-2 clear answers: Stop here. These fundamentals need work before outsourcing makes sense.
Continue to Part 2: Management Bandwidth & Realistic Expectations
In Part 2, we cover the remaining 6 questions: regular sync capacity, onboarding materials, time zone planning, capacity vs capability decisions, true cost calculation, and success metrics.