What is white label?

Sometimes they do, from technical clues and resemblance to other instances, and usually it does not matter — on one condition: that you deliver real value on top of the engine, through service, support, expertise and integration into your own offer. Customers buy the problem being solved by a supplier they trust, not authorship of the code. What does matter is honesty when asked directly, because a claim of fully in-house development dismantled during due diligence costs exactly the trust it was protecting.

The ones governing dependence and separation: portability of customer data on exit, with format, deadline and cost negotiated now rather than in a crisis; ownership of the end-customer relationship, meaning whose accounts and contracts these are; the availability commitment on the engine, since its outages are your brand’s outages; price predictability with a cap on increases, because a supplier able to double your cost controls your margin; customisation limits and exclusivity; and the scenario where the supplier is sold or fails.

Realistic only with written discipline. Using it as validation works — you learn the market and gather real requirements, which makes later development precise — provided migration is planned from day one: a contract securing data portability, avoidance of deep dependence on the engine’s peculiarities, a defined threshold at which building starts, and a real budget for the transition. The self-deception is the default version, where every successful year on somebody else’s engine makes moving more expensive until the mortgage becomes permanent.