Whalebone did not set out to make telecom operators its main route to market. The route emerged as operators told the company what they would, and would not, buy.
Richard Malovic, Whalebone’s CEO and co-founder, started with a broad set of options for the company’s threat-intelligence capability: sell intelligence, consult, build a firewall or endpoint agent, or secure DNS traffic. Early conversations with small internet service providers narrowed that field. They did not want a feed to operate themselves. They wanted Whalebone to apply the intelligence to DNS traffic and run the DNS resolution.
The next conversations changed the business. Large mobile operators, including Telefónica and América Móvil, were not searching for another security cost. They asked whether the architecture could become a service provisioned per SIM card or per home, inside the telco network. Whalebone could remain the operator’s supplier while the operator could offer protection to its own customers.
From network security to a subscriber service
That request gave Whalebone a much larger role than protecting a carrier’s infrastructure. The product had to work at the point where the operator serves its customers: a mobile line, a home connection, or a business account. It also had to be simple enough for the operator to package and activate without turning every subscriber into a security administrator.
Whalebone’s DNS-level model suited that task. Its protection is delivered through the network rather than software installed on each device, allowing the service to follow the customer’s connectivity. A carrier can make the service available across the base it already manages rather than asking each customer to deploy and maintain a separate security product.
That does not turn every telco integration into a channel. The product still has to fit the operator’s commercial unit, fulfilment flow, and service promise. A vendor that can only sell a complex enterprise deployment has a very different starting point from one that can provision protection across SIM cards or household connections.
The questions are concrete:
- What can the operator offer its customers that it could not offer before?
- At what unit can the service be activated, measured, and billed?
- Can the vendor run the service reliably at the volume the operator already serves?
The commercial model followed the product
Whalebone entered those operator discussions expecting a conventional software transaction: a perpetual licence or a lump-sum fee. The operator proposition pushed the model toward consumption. As more customers activate the service, both the operator’s customer offer and Whalebone’s opportunity grow.
That alignment is central to the model. A product bought as a one-time infrastructure expense can be technically sound and commercially invisible. A service tied to subscriber adoption gives the operator a reason to launch, promote, and improve it over time.
Malovic describes the company’s direction in plain language: “we are not selling cybersecurity, we are selling business.” The security capability remains essential, but it becomes part of a broader offer that has to earn a place in the operator’s portfolio.
Launch support is part of the product
Availability inside the network is only the beginning. Whalebone’s operators roll cybersecurity out progressively, rather than switching protection on for every potential customer at once. The work moves quickly from integration to penetration: who is activated, how the offer is presented, and where the rollout slows down.
Whalebone complements its technology with a GTM package to help telcos bring the service to market, drawing on its experience with operator launches. The partnership therefore extends beyond making the technology work inside the network. It helps the operator turn that capability into a service it can sell.
Customer and operator questions drove Whalebone to extend its service around the product. Malovic describes the shift from product excellence to service excellence: an excellent product can create far more value when the vendor also helps customers put it to work. He estimates that the resulting impact can be “10 times bigger” or even “100 times bigger” than delivering the product alone.
For a carrier partnership, that means preparing for rollout as carefully as integration. The vendor needs to help the operator shape the customer proposition, prepare launch and activation paths, and deal with the barriers that appear after the service goes live. A channel partner should not be left with a functioning technical capability and no practical way to build demand for it.
Penetration is the proof of the channel
Whalebone’s ambition is built around connectivity at scale. Access to a very large operator base does not mean every person in that base is protected on day one. Malovic calls the next phase an “execution mission”: the service has to move through the operator’s customer base step by step.
That changes how a cybersecurity company should judge an operator relationship. A signed logo demonstrates access. Penetration shows whether the service has become part of the partner’s business. The useful measures sit on both sides of the relationship: active customer units, rollout progress, service quality, and the commercial performance of the offer.
Whalebone’s path shows how a channel can reshape a company. The operators did not just create a larger sales opportunity. Their requirements pushed the company to redesign delivery, pricing, and post-launch support around a shared customer proposition. That is how a telco becomes more than a buyer, and becomes a distribution channel that can scale.
This insight comes from Scaling Cyber, a podcast hosted by Ignacio Sbampato featuring cybersecurity founders and leaders from around the world. Watch the full episode: Richard Malovic on Whalebone →
