Your catalogue, your brand: real white-label

There are two ways to read the word white-label. In the first it's a settings screen: upload a logo, pick a couple of colours, and the product underneath still belongs to somebody else. In the second it's how the product was built in the first place, and then the question stops being where your brand goes and becomes whose services end up in the proposal.

You won't spot the difference in a demo. You'll spot it at the third renewal, when the customer decides who to call.

The logo is the easy part

Nearly every platform lets you swap the brand, the colours and the domain, and the screen that does it takes about ten minutes to fill in. What almost none of them let you swap is the catalogue. If the services reaching the SME are the platform's services, with the platform's descriptions and the platform's price, you aren't selling your offer. You're reselling somebody else's with your name on the cover sheet.

That holds up as long as the customer takes the package as it comes. Then the customer asks for an exception, a discount in year two, a different bundle because half of it already sits with another supplier, and you find you have no levers at all: you don't govern the thing you're selling. Your reps work this out before finance does, and they quietly stop pitching it.

The services proposed come off your price list

With Cyberangels the catalogue gets defined up front, inside the platform, using your descriptions and your prices. Every risk the signals surface is mapped to the service in your catalogue that closes it, and the proposal your rep carries into the call is assembled from nothing else. The co-worker has no knowledge of services you don't sell and can't promise anything you can't deliver, because there's no price list of ours for it to reach into.

That's also why catalogue co-design is part of going live rather than something to handle later. It sits inside the short stretch between agreement and an active portfolio, alongside the branding and the choice of which group of SMEs the pilot runs on. It isn't a technical setup task; it's a commercial conversation about what you already sell, what you'd like to sell, and what you'd rather not promise.

Picture a partner arriving at that table with twenty line items inherited from three years of different agreements. The catalogue usually comes out of the session shorter than it went in: six of those items genuinely sell, four only ever move through the enterprise team, and nobody could deliver the rest to a fifteen-person company on any sensible timeline. Better to find that out before a customer signs. What survives is a list your reps can recite from memory, and a set of services the co-worker can build proposals from without improvising.

The document that stays on the customer's desk

Every deal has a moment where the rep leaves and the customer is alone with a file open on screen. That file is the most underrated asset you have, and in a half-finished white-label it's where the costume slips: your cover page, somebody else's technical annex.

The white-label report the platform generates holds four things together under your brand:

• that SME's security posture, written so the managing director can read it without a technical translator sitting next to them
• coverage against the frameworks the customer cares about, with no claim that they're compliant: the platform supports the preparation work, it doesn't certify anybody
• the signals behind the assessment, each carrying its own date, so when they push back on a point there's something concrete to look at
• a phased roadmap where every phase is a service from your catalogue that your team delivers and invoices

Documents like that get forwarded. They reach the IT manager, often the accountant, occasionally a customer who sent the questionnaire that started the whole thing. Every copy has your name on it.

Margin follows the price list

Whoever owns the price owns the margin, and this is the part of white-label that shows up in the accounts. You decide how the services are packaged, what rides inside the connectivity subscription and what stays separate, how far you can discount and where you make it back. When the list belongs to someone else, your margin is the gap between two prices you didn't write, and every negotiation squeezes it.

There's a subtler effect on the sales floor too. A rep will happily sell something they recognise as their own, in the vocabulary they already use for the rest of the portfolio. If the proposal speaks a different language, full of service names they've never heard, they treat it as a visiting vendor's product and push it to the end of the day.

At renewal, he calls whoever brought the evidence

For an SME, security is a relationship before it's a product. The supplier who turned up with an exposed port and a date, left behind a document the owner could read, and then closed a few of the gaps becomes the one the owner writes to when a big customer sends a supplier questionnaire, or when somebody in accounts clicks the wrong link.

Put a platform's brand in the middle of that relationship and the relationship is shared, which means the renewal conversation is shared as well. Keep the platform invisible and the relationship is only yours. The rest follows from there: whoever holds the relationship holds the renewal, and whoever holds the renewal holds the recurring revenue the rest of the portfolio gets built on.

There's a flip side, and it's worth looking at squarely: an unhappy customer writes to you, never to the platform. Native white-label means owning that part too, and anyone selling it to you as pure upside has probably never had to. What you get in exchange is control over the response time and the tone, the same way you already have it on connectivity.

Treat white-label as a setting and you get a cover page. Treat it as the architecture of the product and you get the price list, the margin, and the customer who calls you in year two.