Zoho won't buy Trengo - it wired into it instead

There is a whole genre of technology news that reads like a scoreboard. Company A bought Company B. Company C is in talks to be swallowed by Company D. The headline is the deal, and the deal is the story. Zoho has spent thirty years being the awkward exception to that genre - a software company that keeps building instead of buying, that never took a dollar of venture money, and that once put its philosophy in a blog title as blunt as a door slam: "They Acquire, Acquire, Acquire While We Build, Build, Build."

So when a company like Zoho starts working closely with a smaller, sharper outfit like Trengo, the interesting question is not "who bought whom." Nobody bought anybody. The interesting question is how two very different companies decided to talk to each other without merging - and what that quiet choice says about where useful software is actually heading.

Two companies that both hate asking for money

Start with the odd-couple framing, because it is real. Zoho was founded in 1996 as AdventNet by Sridhar Vembu and two co-founders, run out of Chennai, and grown into one of the largest fully bootstrapped software companies on the planet. In February 2026, on its 30th anniversary, it passed a million paying customers and roughly 150 million users across a suite that spans CRM, mail, accounting, and dozens of other tools. It has more than 19,000 employees and has never raised outside capital. The whole identity is self-reliance taken to an almost stubborn extreme.

Trengo is younger and smaller and Dutch. Founded in Utrecht in 2017 by Patrick Meutzner, Marcel van de Weerd and Igo Trampe, it started with a specific, unglamorous bet: local businesses wanted to reach customers on WhatsApp, and nobody was making that easy. The team bootstrapped for its first three years with about fifteen people before taking a $36M Series A in 2021. What it built is an omnichannel inbox - WhatsApp, email, live chat, Instagram, Facebook, SMS and voice, all landing in one shared workspace, with AI agents handling the repetitive questions.

Different sizes, different countries, different decades. But the same instinct: get the product right first, ask for outside money late or never. That shared temperament is part of why the connection between them is worth a look. Neither one needs the other to survive. They connect because it makes the day better for the person doing the work.

The swivel chair problem

Here is the small daily frustration this whole thing is built to kill. A customer messages a business on WhatsApp. Then, a day later, they email. Then they open live chat. To the customer it is one continuous relationship. To most support desks it is three disconnected tickets, handled by three different people, none of whom can see the other two.

Trengo solves the first half of that: it pulls every channel into one thread so an agent sees the whole conversation regardless of where it happened. But a unified conversation is only half a memory. The agent can see what was said and still have no idea who is saying it - are they a first-time buyer or a ten-year account, did they just get refunded, do they have three open orders. That context does not live in the inbox. It lives in the CRM.

A shared inbox tells you what was said. A CRM tells you who is saying it. Neither is enough on its own.

This is where the Zoho connection earns its keep. The Zoho CRM integration surfaces a customer's Zoho contact details and interaction history directly alongside the Trengo conversation. The agent stops swivelling between two screens. The message, the person, and their history sit together. As one Trengo customer put it plainly: "Trengo was able to provide the API that we needed, efficiently - now we have one interface for all of our touch points."

Why "build and connect" beats "acquire"

The tech default, when two products would be better together, is to buy one and bolt it on. It looks decisive. It generates a headline. And it very often produces years of painful integration work, a re-platformed product, and customers who liked the original thing wondering where it went. Zoho's whole history is an argument against that reflex. Its blog post about rivals who "acquire, acquire, acquire" was not a cheap shot - it was a thesis. Build the pieces yourself, keep control, and let the seams be clean.

An integration is the humbler cousin of an acquisition, and in a lot of cases the smarter one. Trengo keeps being the best version of an omnichannel inbox. Zoho keeps being the CRM that a million companies already run. Nobody has to absorb anyone's roadmap. If the relationship stops being useful, the API can be swapped for another. The customer, meanwhile, gets the benefit of both without paying the tax of either company's reorganization.

There is a lesson here that any operator can lift for free: decide which single system owns the customer record, then make every channel read from it. You do not need to own the channels. You need them to agree on who the customer is.

It also changes the risk math. An acquisition is a bet made once, at a fixed price, that two roadmaps will still make sense together in five years. An integration is a bet you can re-make every quarter. If Trengo ships a better AI voice agent, Zoho customers get it without Zoho lifting a finger. If a Zoho team wants to expose a new field on the contact record, Trengo reads it the next day. The dependency is real, but it is loose - and loose dependencies are the ones that survive contact with a changing market. That is not a knock on acquisitions, which sometimes are the only way to buy talent or time. It is an argument for reaching for the smaller tool first.

The channels, ranked by where customers actually are

Part of why the CRM context matters so much is the sheer spread of places a modern customer might turn up. Trengo's own framing puts messaging channels - led by WhatsApp - at the center, which is exactly the shift most legacy CRMs were slow to make.

Notice the top of that list. WhatsApp is where Trengo started, and it is still where a striking share of customer conversations begin - Trengo reports a 98% open rate there. A CRM built in an era of web forms and phone queues was never going to keep up with that on its own. Bolting a messaging inbox to the customer record is how a thirty-year-old suite stays relevant to a customer who would rather text than call.

What you can actually do with it

Strip away the philosophy and the practical version is short. If your company already runs Zoho CRM and your customers already message you across a mess of channels, the pairing lets a support or sales agent open a single conversation and see, right there, who the person is and what has happened before. Routine questions - booking changes, refunds, order tracking - get handled by Trengo's AI agents, which the company says clear roughly 84% of repetitive conversations. The ones that need a human land in front of someone who already has the context to answer well.

That is the whole promise, and it is enough: fewer tabs, faster answers, and a customer who does not have to explain themselves three times. No acquisition was required to deliver it. Just two companies that would rather build and connect than buy and absorb.