When an internal project is a credible alternative to your offer, help the customer compare both options on consistent terms.
A useful comparison starts with the outcome the customer needs. It includes the work required to achieve that outcome and the responsibilities that continue afterward.
Use this worksheet to make assumptions visible, identify uncertainties and establish what would make either option a sensible choice.
1. Define the outcome before comparing solutions
Complete this statement:
We need to accomplish ______ for ______, within ______, while meeting ______.
Specify the users, essential requirements, timing and constraints. Separate what is necessary from what would be useful later.
For a fictional customer evaluating a support assistant, the initial outcome might be:
Help the support team handle a defined set of routine questions, escalate cases outside that scope and retain enough information to investigate mistakes.
That is a narrower requirement than automating the entire support operation. An internal project should not be assessed against capabilities the customer does not need. A purchased product should not receive credit for features that add little value to this decision.
2. Describe the actual alternatives
Record what “build” and “buy” mean in this situation.
An internal solution may use purchased models, platforms and components. A purchased solution may require substantial configuration, integration and ongoing oversight.
For each option, write down:
- What the customer would create, configure or purchase.
- Which systems, services and people it would depend on.
- What is included in the initial scope.
- What would remain outside that scope.
If a hybrid approach is credible, add it as another option. Keep the current process visible too: continuing as things are may be the customer’s preferred alternative.
3. Compare on consistent terms
Choose the same scope, operating period and expected level of service for each option.
Use estimates or ranges where necessary. Record their sources and avoid treating an untested assumption as a known cost.
| Comparison | Internal project | Purchased solution |
|---|---|---|
| Required outcome | What can it reasonably deliver within the agreed scope? | What can it reasonably deliver within the agreed scope? |
| Initial work | Development, integration, evaluation and rollout | Configuration, integration, evaluation and rollout |
| Time to useful operation | When could it meet the acceptance requirements, and what could delay it? | When could it meet the acceptance requirements, and what could delay it? |
| Ongoing costs | People, platforms, usage, maintenance and support | Fees, usage, administration, oversight and support |
| Ownership | Who investigates problems, maintains the system and approves changes? | Which responsibilities belong to the supplier, and which remain with the customer? |
| Dependencies and risk | Reliance on platforms, components and internal expertise | Reliance on the supplier, platforms and customer-side capabilities |
| Control and flexibility | What can the team change, and at what cost? | What can the customer configure or extend, and what requires the supplier? |
| Exit or replacement | What would migration, retirement or replacement require? | What would migration, retirement or replacement require? |
| Opportunity cost | Which other work would the team defer? | What other uses of budget and implementation time would be displaced? |
| Uncertainty | Which estimates and assumptions need testing? | Which claims and assumptions need verification? |
Account for opportunity cost explicitly, but avoid counting the same cost twice. For example, record staff effort and the work it displaces without automatically adding both as separate financial expenses.
4. Make ownership concrete
In the support-assistant example, both options need an account of what happens when an answer is wrong or a case needs escalation.
The internal team might own the application while relying on an external AI platform. The purchased product might provide the escalation mechanism while requiring the customer to configure rules and maintain its documentation.
“Build” and “buy” do not tell you how those responsibilities are divided.
Complete a responsibility map for the tasks that matter:
| Task | Internal-project owner | Purchased-solution owner | What needs clarification? |
|---|---|---|---|
| Maintain source documentation | |||
| Configure escalation behaviour | |||
| Investigate incorrect answers | |||
| Manage access and permissions | |||
| Evaluate changes before rollout | |||
| Monitor operating costs |
Use role or team names. Where responsibility is shared, describe the handoff. Leave unknowns visible rather than assigning ownership by assumption.
5. Test the uncertainties that could change the decision
You do not need equal detail about every feature. Prioritize the assumptions that could make a preferred option unsuitable.
For each important uncertainty, record:
Assumption: What are we relying on?
Evidence needed: What would help us assess it?
Evaluation: What can we inspect, test or confirm?
Owner: Who will investigate?
Decision consequence: What would change if the assumption proves wrong?
In the fictional example, both options could be evaluated against the same representative support cases and agreed escalation requirements.
A prototype demonstration would not establish every aspect of ongoing reliability. A supplier demonstration would have the same limitation. Record what an evaluation establishes and what remains unknown.
6. Make the conclusion conditional
Avoid forcing every consideration into a single score. Some requirements may be essential; other differences are trade-offs the customer can reasonably accept.
Write:
Buying appears preferable if ______.
Building appears preferable if ______.
A hybrid approach or the current process deserves consideration if ______.
The decision depends most on verifying ______.
We should revisit the decision if ______ changes.
The result may be a choice, a focused evaluation or a decision to defer. State which one the available evidence supports.
Use the comparison to improve your marketing
For marketers and founders, this worksheet can reveal why an otherwise attractive offer struggles to win.
Perhaps the customer’s requirements are narrower than your proposition assumes. Perhaps your integration advantage is real but poorly evidenced. Perhaps the customer values control more than you expected. Or perhaps your product creates responsibilities that your marketing has not explained.
Those findings can inform the offer, positioning and evaluation materials.
If you prepare the comparison as a supplier, make that perspective clear. Invite the customer to correct assumptions and include alternatives that could reasonably serve them better.
A fair comparison should explain where your offer is strong and where it is not.
Use Matrix to identify who needs to assess the trade-offs. Use IMPACT to coordinate the evidence and examine whether a clearer comparison improves understanding and evaluation.
Read “When your competitor is an internal project” →
Try the Matrix exercise →