Clay Tech

"clay-works make things real"

translated from clazytech.com

Large companies and startups fail to collaborate for clear reasons

This is another consultation I get often.

This kind of consultation only ever comes from large companies. That’s because in most cases startups know exactly what they want, and the moment they realize they won’t get it, they pull out quickly. There’s not much room for them to agonize over it.

Large companies, on the other hand, very often move forward into collaboration on a vague feeling, without having made clear even one or two things — or in the worst case, anything at all — about what they want to get out of the startup, how much they should reasonably expect, and what they themselves should be offering in return.

Let’s unpack these issues one by one.

First, what you want to get out of it. A typical pattern of collaboration is “helping the startup get into the market.” The story goes something like this: the large company has an established position across the industry, and by having the startup’s product or service adopted early by itself or its affiliated companies, it can be the first to bring that advanced service to market ahead of others, turning the move into promotion for its own users or into tangible profit.

Here, I want you to be honest with yourself.

Isn’t what you actually want to recover the detailed know-how behind the product or service the startup is working on? Even if it’s not overt, haven’t you thought even a little about converting that into your own company’s products or services? You need to get clear on this dividing line, because how you engage with the startup changes depending on the answer.

Next, how much you should expect. It’s quite common for a startup’s technical details or know-how, of the kind mentioned above, to turn out to be completely unusable in practice. In other words, excessive expectations are something to avoid. Have you drawn that line clearly for yourself? Are you talking up only the rosy scenarios internally? If you’re entering into a capital relationship, the conversation changes again, so that boundary needs to be made clear too.

Finally, what you should be offering in return. This one is simple, because in most cases what startups clearly need is already known, so just keep it in mind. As I touched on in another section, the top priorities are QA and CS. Production lines come next. QA and CS are areas where the period of need tends to be relatively short, and the resources required can swing wildly depending on the situation. For a startup that’s chronically short on resources and has no realistic way to temporarily backfill from other departments, this is a notoriously difficult area. On top of that, these areas demand a wide range of experience and disciplined, organized behavior. At the same time, though, they don’t require especially deep understanding of the underlying technology that makes up the product. In that sense, this is an ideal area for outside support, particularly from large companies. Startups obviously don’t have money, but when it comes to funding specifically, a number of other sensitive factors come into play, so the startup isn’t necessarily obligated to take money from you no matter what.

If you’re on the large-company side, I hope this has given you at least some concrete sense of what collaboration looks like.

From my point of view, you need to take a clear-cut strategic stance. If your ultimate aim is to bring the startup itself into your fold, you should build a foundation of shared fate based on a capital and business alliance, and on top of that, take the strategy of simply giving the startup whatever it asks for. Alternatively, if you’re merely trying to find out whether the startup is promising or whether the market is promising, the strategy becomes one of managing risk to minimize your own burden and sacrifice, while giving the startup enough of what it needs to extract as much information as possible from it.

In the former case, it becomes clear early on whether the startup will accept your offer or not. If it moves forward, it moves forward; if not, it ends there. Either way, neither side wastes time or effort. In the latter case, both sides establish a shared understanding that the relationship will be conducted in a way that minimizes risk as much as possible. Neither side expects much from the other, so there’s no need to get worked up over a lull in communication or a lack of progress from either party. The relationship may simply fade away naturally. In a sense, this too minimizes time and effort.

I’ve seen confusion arise in all sorts of places from companies bringing up collaboration vaguely, without even settling on this minimal a stance. In the end, it’s an unproductive outcome for both sides: the startup wastes effort and time that could otherwise have gone toward something else, while the large company ends up disappointed, having had excessive expectations but failing to recover sufficient results.


Originally published in Japanese at https://clazytech.com/2021/08/568/. Translated with LLM assistance and reviewed before publication.