Sooner or later a larger company proposes selling your product as theirs. For a small software business that is genuinely attractive — distribution you could not buy, a customer base you could not reach, and revenue without a sales team. It is also a structural decision rather than a cosmetic one, and the version that goes badly is the one agreed as though it were a branding exercise.
The technical work is more than a logo and less than a rebuild, and it is worth scoping honestly. Theming — colours, logos, typography, email templates, document headers. Custom domains with certificates you must provision and renew. Terminology, because their industry may call the same object something different. Feature visibility, because they will want some things hidden. And configuration per partner, held as data rather than as branches in the code, or your second partner costs as much as your first.
The harder questions are commercial. Who owns the customer relationship — do you know who the end users are, can you contact them, and what happens to them if the partnership ends? Who provides support, and if it is the partner, what happens when their first-line cannot resolve something? Who sets the price, and do you see it? A white-label arrangement where the partner owns the relationship entirely means you have exchanged distribution for the possibility of being replaced once they understand the product well enough to commission their own.
Support is where these arrangements most often strain. Under the partner's brand, the end user contacts the partner, whose staff did not build the product and cannot diagnose it. That produces a slow escalation path with an angry customer at the end of it, and your engineers receive problem descriptions filtered through two people who do not understand the system. Investing early in partner-facing diagnostics and a good escalation channel is what keeps this workable.
Be careful about roadmap capture. A large partner with a substantial share of your revenue will ask for features, and those requests arrive with commercial weight behind them. Over two years that can quietly turn your product into a bespoke system for one company, which is the outcome white-labelling was supposed to avoid. Deciding in advance what proportion of the roadmap is available to partner requests, and holding it, is the discipline that preserves the product.
The version of this that works well is usually narrower than the version first proposed. A defined product, a defined configuration surface, a defined support boundary, a price you set, and visibility of the end customer. Partners who want more than that are often really asking you to build them a product, which is a legitimate business to be in — but it is a services business with a licence attached, and it should be priced and staffed as one rather than as a channel.
