Essay

When your competitor is an internal project

Your customer may agree that your product is useful and still decide not to buy it.

Their team may believe it can build something adequate. It may already have a prototype. Or it may be considering a smaller internal project that solves only the part of the problem that matters most.

That project belongs in your competitive analysis.

AI makes the question more pressing. If customers believe they can now create a workable alternative with less effort, their reasons for buying may change—even before that belief has been tested.

For marketers and founders, the implications reach beyond messaging. You need to understand what customers could reasonably create, what they would need to operate it and where your business provides value worth paying for.

Start with the outcome the customer needs

Consider a fictional company evaluating a support assistant.

A supplier offers a product that answers routine questions and escalates harder cases. The customer’s engineering team proposes an internal version using an AI platform, existing documentation and a connection to its support system.

The supplier sees a mature product competing with an unfinished project. The customer sees two possible ways to reduce repetitive support work.

The customer may not need the supplier’s full feature set. Its internal version might serve one product, one language and a limited group of users. That narrower scope could make building a sensible choice.

A comparison against other vendors would miss part of the decision. The marketer needs to understand the outcome the customer considers worthwhile and what each alternative requires to achieve it.

That includes the current process. The customer may decide that neither a purchase nor an internal project justifies the effort yet.

AI can change both sides of the comparison

AI-assisted development may reduce the effort required to create an internal solution. It can also help suppliers develop, configure and support their products.

Neither possibility settles the decision for a particular customer.

A faster prototype does not establish that operating the system will be easy. Equally, a supplier’s historical development investment is not, by itself, a reason to pay. The customer is choosing between the alternatives available now.

In the support-assistant example, an internal prototype might answer a selection of common questions convincingly. Further evaluation needs to examine what happens when documentation is incomplete, an answer is wrong or a case requires escalation.

Who investigates problems? Who maintains the source material? What happens when an underlying service changes?

The purchased product deserves the same scrutiny. Buying can transfer some responsibilities to a supplier, but it does not automatically remove integration work, oversight or operational risk.

Apply consistent standards to both options.

Compare ownership as well as acquisition

“Build versus buy” sounds like a choice between a development project and a purchase. Both create an operating commitment.

An internal system needs people responsible for its performance and upkeep. A purchased system needs people responsible for configuration, supplier management and the parts of the workflow that remain inside the business.

A useful comparison therefore considers:

  • The outcome each option can deliver within the required scope.
  • The work and time needed to reach an acceptable operating state.
  • The costs and responsibilities that continue afterward.
  • The control, flexibility and dependencies each option creates.
  • The other work displaced by choosing it.
  • The effort required to change course later.

The comparison should use the same scope, operating period and expected level of service. Estimates need visible assumptions, particularly when a prototype is being compared with a product already in use elsewhere.

An internal project can be technically feasible and still be a poor use of a team’s time. A subscription can save development effort and still be poor value if the customer needs little of what it provides.

Marketing can help make these trade-offs understandable.

A credible argument for buying needs evidence

A supplier might respond by emphasizing speed, reliability or reduced maintenance.

Those can be valuable advantages. Buyers need a way to examine them.

In our example, “easy integration” becomes more useful when accompanied by an account of supported configurations, required permissions, customer tasks and ongoing responsibilities.

“Reliable escalation” needs an explanation of the behaviour, its limits and how the customer can evaluate it. A demonstration can establish something useful without proving performance under every operating condition.

The purpose of evidence is to help the buyer assess the purchased option against a plausible alternative. That might require an evaluation task, documented requirements or an ownership worksheet whose assumptions the customer can change.

Sometimes the comparison will favour building. Recognizing those situations helps the supplier understand where its offer is strongest and which prospects are unlikely to benefit from it.

It may also reveal a need the business could serve better.

Sometimes the offer needs to change

Clearer explanations have limits.

If customers can create an adequate solution at an acceptable cost, and the supplier’s advantages matter little to them, the offer may need attention.

A business could concentrate on harder operating requirements, reduce adoption effort or serve customers with a different balance of capability and resources. It might provide a component that internal teams can incorporate rather than asking them to replace their project.

These choices affect product, pricing and delivery as well as promotion.

Marketing contributes by identifying what customers are comparing, which differences they value and where their objections reveal a substantive weakness.

A recurring “we could build this” response should prompt investigation. It might reflect an optimistic estimate, a poorly explained advantage or an accurate assessment that the customer can meet its needs another way.

The response depends on which explanation the evidence supports.

Measure whether the decision becomes better informed

Suppose the support-assistant supplier creates a technical evaluation guide and an ownership worksheet.

Downloads would show interest. To assess marketing effectiveness, the business also needs to examine what happens during evaluation.

Can engineering teams reach a clearer conclusion about fit? Are responsibilities understood earlier? Can the business owner compare costs using consistent assumptions? Which questions remain unresolved?

Commercial outcomes matter too: progression among suitable customers, the effort required to support evaluations and the misunderstandings that surface after purchase.

Interpret those outcomes carefully. An evaluation may take longer because the customer is examining it more thoroughly. A poor-fit prospect may leave earlier because a requirement has become clear.

Neither result is automatically good or bad. Investigate the reason and connect it to the intended improvement.

Establish what happens before the change, then compare subsequent experience while considering other factors that could explain the difference. Where the evidence is limited, say so.

Ask what they would build—and why

This is one reason I’m developing B2E—Business to Engineers as a specialist marketing motion within Adaptive Marketing.

Engineering buyers may be able to create an alternative and may inherit responsibility for whichever option is chosen. Supporting that evaluation requires an account of technical fit, ownership and business value that they can examine.

Matrix helps identify those responsibilities and the evidence missing from the decision. IMPACT helps coordinate a response and assess what happens.

Begin with one customer and one practical question:

If this customer did not buy from us, what would they build—and why would that seem like a good decision?

A serious answer can change your positioning, your evidence and sometimes your product.

It can also help you make a more credible case for buying.

Use the buy-versus-build comparison worksheet →
Try the Matrix exercise →