7 minutes read

Integrated software and the challenge of keeping your own name

Your product is good, and customers are happy with it. But they don't remember your name, only the name of the distribution platform.

Sinh Vũ · Creative DirectorTechnology sector

Quick summary

When software is sold through a partner platform, the logo shrinks and the interface is renamed, and the original brand fades with each integrated version. To protect brand assets, a software company needs to define which identity elements are non-negotiable, write them into the partner contract, and keep at least one direct touchpoint with end users.

In this article · 6 sections

Your product runs reliably, and customers use it every day. But they call it by the name of the distribution platform, not the name you gave it.

This is not a rare situation. It is the natural result of distributing through partners without a brand protection strategy in place beforehand.

Why a brand fades away

When software is integrated into a partner platform, three things usually happen at once.

The logo is shrunk or moved to the bottom corner, where users look least.

The product name is replaced by the partner's relabel, for example "Inventory management feature" instead of the original brand name.

Notifications, emails and welcome screens all carry the platform's identity. End users have no reason to remember who is behind it.

Technically, the product still runs. In brand terms, you are building a house on rented land.

A brand is how users perceive you, not the logo on your homepage.

Marty Neumeier, The Brand Gap

Which brand assets get lost

Brand equity is not just visual identity. It is the sum of the awareness, associations, and trust that users attach to the name of the product.

In an integrated environment, these three layers of assets erode in this order:

  • Recognition (who you are): users don't know the original product name, can't search for it, and can't recommend it to others.
  • Association (what you do well): every good experience is credited to the platform, while bad experiences sometimes land on you when something goes wrong.
  • Trust (why choose you): when the platform switches providers, users have no reason to look for you again, because they never knew you existed.
85%of organizations have brand guidelines, but only about 30% apply them consistently in practice. Source: Marq / Demand Metric, Brand Consistency Report, 2021.
The 85%/30% figures come from a self-reported Marq survey (now Brandfolder), with the sample size n not clearly disclosed. The trend matches what is observed in the industry, but it should not be used as an absolute constant.

Four touchpoints worth keeping

Not every touchpoint is negotiable. But the four below are the most valuable ones, and they are often overlooked when the contract is signed:

  • First login screen: this is where users pay the most attention, because everything is still new. A line like “Powered by [Product name]” placed in the right spot is enough to leave an impression.
  • Notification emails and invoices: these are moments when users read on purpose, not skim. A small logo and your product name in the footer are enough to keep your presence.
  • Settings screen and vendor information: there is usually a dedicated area with information about the integrated app. This is where the name, version, and link back to the homepage go.
  • Error messages and support screens: when something goes wrong, users want to know who to contact. This is a chance to show up as the responsible party behind the product, rather than hiding.

Put it in the contract before signing

Most brand losses in integrations can be prevented at the contract negotiation stage.

The problem is that software companies tend to focus on technical terms and revenue, and overlook the terms on brand visibility.

Points to set out clearly in the contract with the partner platform:

  • Minimum size and logo placement in the integrated interface.
  • The display name in the app list and settings.
  • The right to communicate directly with end users by email or in-app notifications.
  • The right to collect feedback and reviews from end users under the original product name.
  • Terms for when the contract ends: are you allowed to notify users so they know where to find you?
+32 points%the revenue of companies in the top design group compared with the average group, based on a study of 300 companies over 5 years. Source: McKinsey, The Business Value of Design, 2018.

Keep at least one direct channel

No matter how well you negotiate, a distribution channel through a partner is still a channel you do not fully control.

The partner can change the terms, switch to another provider, or simply shut down.

The safe strategy is to maintain, in parallel, at least one channel that reaches end users directly. It doesn't need to be big, it needs to be consistent:

  • A separate documentation page under the original product name, which users can find through search engines (SEO: Search Engine Optimization, optimizing to appear on search engines).
  • A technical newsletter or feature updates sent directly to users who have opted in.
  • A user community, however small, where the original product name is the primary name.

These channels don't compete with the partner platform. They are a safety net for your brand.

A brand is the sum of product, environment, communication and behavior. Miss one layer, and the whole system weakens.

Wally Olins, On Brand

Once you've already integrated: where to start

If your product is already integrated and the brand is fading, you do not need to start over. Check three questions:

One: in the current integrated interface, where do end users see your product name, and how many times in a typical working session?

Two: if the partner platform shut down tomorrow, would you have a list of end users to contact?

Three: does your current contract include any clause on brand visibility, and when is the next renewal?

These three questions show the real level of risk. Only then do you know where to set your priorities.

The first unicornNubank (Brazil) built an independent brand from the start, even while distributing through many partner channels. Its purple color and distinct name helped it keep its identity as it expanded into Mexico and Colombia. Source: Nubank brand report, public data.

References

Marty Neumeier, The Brand Gap. Byron Sharp, How Brands Grow (Ehrenberg-Bass Institute). Jenni Romaniuk, Building Distinctive Brand Assets. McKinsey, The Business Value of Design, 2018. Marq / Demand Metric, Brand Consistency Report, 2021.

Frequently asked questions

Does integrating through a partner platform require you to use their name and interface?

Not entirely. The extent depends on the contract terms and each side's negotiating leverage. Many platforms allow a small logo or a vendor information area if the software company asks for it clearly from the start. A common problem is that software companies don't raise brand protection when signing the contract, and only see their name disappear after the product has been integrated.

If end users do not know the original product name, does it actually cause harm?

It does harm in two ways. First, when the partner platform changes vendors or ends the partnership, you lose your entire relationship with end users, because they don't know where to find you. Second, when you want to upsell features, upgrade plans, or move users to a direct channel, you have to start from scratch as a completely new brand.

Does a small business have enough leverage to negotiate brand terms with a large platform?

You have less leverage, but not none. Small terms, such as keeping your name on the settings screen, sending notification emails with your own logo, or placing a link back to your homepage, usually don't affect the platform's interests. The hardest thing to negotiate is changing the display name on the main interface. The practical approach is to list which touchpoints matter most to end users, then negotiate each one rather than demanding everything.