Strategic Alliance

There was a stretch where needing another company's strength left two options: buy them, or do nothing and build it yourself. Buying costs a great deal of money and time, and a failed acquisition cannot be undone.

The meeting between Grace and the head of a video-call company shows the gap between those two. About a third of the two customer lists overlapped and the products did not overlap at all. Teams meeting over a document were opening both products separately and switching between windows. Connecting them would obviously get both used more, there was no money for an acquisition, and building the equivalent separately would cost each side two quarters.

A strategic alliance fills that gap. Writing down a relationship that cooperates without owning lets each side use the other's strength without paying the price of an acquisition.

Both companies stay independent. No equity changes hands and neither gets a say in the other's decisions. What gets exchanged is settled case by case, and in practice it is usually one of four things.

1. Technology — connecting the products, or building a feature together. Opening a video call directly inside a document comes out of this kind of work.
2. Customers — introducing each other to your own base. Running a joint webinar and sending the same invitation to both lists is the common form.
3. Brand — co-hosting events or producing material together. Both names stay as they are and appear side by side.
4. Distribution — taking your product into a region or industry the other side already reaches.

Two conditions have to hold. The customers overlap and the products do not: overlap on both and it is competition, overlap on neither and there is nothing to do together. And what each side gains has to be roughly the same size. A structure where only one side benefits stops in the quarter that becomes obvious.

Because the arrangement is loose, a lot has to be written down: who does what by when, how joint results get divided, how far each side may use customer information the other passed over, and under what conditions it ends. That last item is the one most often skipped. Leave the ending unwritten at the start and a relationship producing nothing runs for three years because nobody is responsible for closing it.

The ways these break are fairly predictable. The most common is both contacts changing roles: once the two people who had the original conversation move on, the document survives and the work stops. Slipping down the priority list produces the same outcome. So a quarterly session to look at numbers together gets scheduled from the beginning, and the numbers are new customers arriving through the alliance and what those customers paid.

This is the form to pick when the market will not grow on its own. Pagedeck and a video-call tool can each build well and neither grows much if the practice of editing a document during a meeting never spreads. When the missing piece is a route to customers, a reseller who sells your product for you is the answer; when it is a feature the product lacks, an integration partner connecting the two products is. When neither is missing and the market still will not grow, this form is what's left.

It also stands in for an acquisition — when the other side's technology is needed and the money is not there, or the ownership is not wanted. Without ownership, though, a change of direction on their side shakes you too. Unlike an OEM arrangement, where one side supplies under the other's brand, both names survive here and both sets of decisions are required.

Enterprise bids bring the two sides in together. When a customer wants to adopt a document tool and a meeting tool at once, the companies enter one proposal. Who signs the contract and how the money splits has to be settled before the bid goes in, not after it is won.

The poor fit is a large size gap. A relationship between a 45-person company and a 5,000-person one is an alliance in name while one side works to the other's calendar. Writing it up as a transaction with stated terms tends to cause less trouble later than calling it a partnership.

"An acquisition is out of reach. Let's connect through an alliance and revisit in six months."

Testing the relationship through cooperation rather than ownership.

"The agreement is signed and both contacts have changed. It's effectively stopped."

The document survived and the work did not.

"This isn't an alliance. We're just working to their schedule."

The size gap means the relationship is not between equals.

Pagedeck signed an alliance with a video-call company last year. What Grace settled in the first meeting was not a statement of shared direction but three pieces of work to finish within four months and an owner for each: opening a call inside a document, one joint webinar to both customer lists, and a quarterly session over the numbers.

Six months later, eleven new contracts had come through the alliance. That was fewer than expected, and the reason Grace did not end it was that eight of the eleven came from industries Pagedeck had never reached. What changed instead was the next half-year's list: the joint webinar came off it and refining the integration went on, because the three contracts the webinar produced were customers Pagedeck could have reached anyway.

The most common conflation is reading an alliance as the signing of an agreement, because alliance news usually arrives with a photo of a signing. An agreement is a document confirming intent; the alliance is the work that actually moves between the two. With no owners and no dates set after the signature, what remains is the photo and the press release, and six months later each side says it assumed the other would move first. What gets settled at the start is not a direction but two or three pieces of work due within four months.

The other one is that a bigger partner is a better partner, since a large name suggests a large gain. What sets the speed of the work is not the other company's size but where this sits on their priority list. Something that is first for you and thirtieth for them takes three weeks to get a meeting scheduled, and one person leaving their team pushes it out by half a year. That is why alliances between companies of similar size often move faster.