Integrators, OEMs and channel partners

In short: in emerging tech the buyer already trusts someone else's hands; your job is to make those hands want to carry you, one partner at a time.

Key points

• Utilities, ports, hospitals and mines buy from whoever holds the relationship, procurement vehicle and liability.
• Partners want margin, differentiation and no support burden, not the same belief as the customer.
• Do first deployments yourself, then productise the playbook into documents you hand a partner.
• OEM and embedded deals are slow, often eighteen months or more, but sticky once live.
• The trap is ten signed partners who do nothing; a logo slide of integrators is not a channel.

The buyer already has suppliers

Part 8 made the case that platforms are closed and distribution has to be built. In emerging tech the platforms are people. A utility, a port operator, a hospital group or a mine does not buy a robot, a sensor network or a verification layer from a startup. It buys from whoever already holds three things.

The relationship: an integrator or engineering firm that has been on site for years. The procurement vehicle: a framework agreement, an approved vendor list, a distributor already in the system. The liability: a managed service provider who answers the call at 3am and carries the insurance.

You can fight that structure or use it. Fighting it means two-year sales cycles against a buyer who wants to say no. Using it means selling once to the partner and letting the partner sell many times.

What the partner believes

Part 2 asked for a belief per audience. The partner's belief is not your customer's belief. The customer wants risk retired. The partner wants three plainer things.

Margin: a deal that pays better than reselling what they already resell. Differentiation: something to say in a tender that the next integrator cannot say. No support burden: confidence that your product will not turn their engineers into your unpaid support desk.

If your pitch to a partner is the same deck you show customers, you have not done the work. Write the partner's belief as one sentence and put it in the claims register.

What a channel partner needs from you

Partners are not evaluating your technology. They are evaluating the cost of carrying it. Five things lower that cost.

A reference deployment, live, with a customer who will take their call. A certified integration with whatever the partner already installs, tested and documented, not roadmap. Training that their field and sales teams can complete, with a pass mark. A partner margin that survives their cost of sale, which is usually higher than yours because they carry travel, site time and bid cost. A support path with a service level, an escalation route and a named person on your side.

Miss any one and the partner will sign your agreement and sell what they already know.

Direct first, channel second

The temptation is to recruit partners before the product is stable, because partners look like leverage. They are leverage only once there is something repeatable to lever.

Do the first deployments yourself. Part 33's design partners are where the playbook comes from. You learn the site survey questions, the installation sequence, the failure modes, the commissioning test, and what the customer calls the thing you sell. Write all of it down as you go.

Then productise the playbook. Installation guide, commissioning checklist, training module, support runbook, pricing sheet with partner margin. That document set is what you hand a partner. Without it you are asking them to learn at their own cost.

OEM, embedded and platform programmes

Two other routes sit beside the channel.

OEM or embedded deals put your technology inside someone else's product. A perception module in a robotics platform, a verification layer in an identity product, a control algorithm in a battery system. These are slow to close, often eighteen months or more, sticky once live, lower margin than direct, and the reach can be larger than anything you could build. Price them as licences or per-unit royalties. Protect your right to sell direct and to serve other OEMs.

Ecosystem and platform programmes are distribution with a badge. Cloud marketplaces, chip vendor partner programmes, robotics platform ecosystems, standards body member lists. They open procurement vehicles, co-marketing and sometimes co-selling. They rarely close deals on their own. Treat them as a channel to partners, not a channel to customers.

The trap, and the measure

The trap is ten signed partners who do nothing. The partner agreement costs nothing to sign and nothing to ignore. A logo slide of integrators is not a channel.

Pick one partner with a live deal in front of them and a named owner inside their business who is paid on that deal. Work that deal with them to paid pilot. Then do it again with the same partner before you add a second.

Measure partner-sourced pipeline that reaches paid pilot. Not partners signed, not partner-registered leads, not joint webinars. One number, reported monthly alongside the direct equivalent.

The checklist

• [ ] The partner's belief is written as one sentence and sits in the claims register
• [ ] The first deployments were done direct and the playbook exists as a document set
• [ ] One partner has a live deal, a named owner and a commission on it
• [ ] Partner margin has been tested against the partner's real cost of sale
• [ ] A support path with service levels and an escalation route is in place
• [ ] Partner-sourced pipeline to paid pilot is the only channel metric reported

Common questions

How do emerging tech startups sell through channel partners?

Sell once to the partner and let the partner sell many times. Give them a live reference deployment, a certified integration, training with a pass mark, a margin that survives their cost of sale, and a support path with a service level.

When should a startup start recruiting channel partners?

Only once there is something repeatable to lever. Do the first deployments yourself, write the playbook down, then productise it before handing it to a partner.

What metric should I use to measure channel partner performance?

Partner-sourced pipeline that reaches paid pilot, reported monthly alongside the direct equivalent. Not partners signed, partner-registered leads or joint webinars.

How should OEM or embedded technology deals be priced?

Price them as licences or per-unit royalties, and protect your right to sell direct and to serve other OEMs.