/ partners · models
Don't build the infrastructure.Build your business on it.
Four ways to work with Inferrex, separated by one question: how far into the customer relationship do you go? Refer an introduction, sell it in your offering, deliver on it, or embed it in your product.
/ the models
Refer · Sell · Deliver · Embed.
These are not tiers, and a partner is usually more than one of them. They describe how far you go into the customer relationship, and therefore what Inferrex does and what you do.
Refer
You introduce, Inferrex sells and delivers. Qualification, solution design, agreement, implementation and support are ours. The lowest-friction path: no delivery capability required and nothing to learn deeply. For advisers, independent consultants and anyone with strong relationships they would rather not complicate.
Sell
You own the sale. You find the customer, position Inferrex, package it into your offering and may keep the relationship afterwards. Inferrex provides the product, enablement, technical support and deployment help. The distinction from Refer is the whole of it: **Refer introduces the opportunity, Sell owns it.**
Deliver
You build customer solutions on Inferrex infrastructure. You already deliver integration, migration, modernisation, ERP and CRM programmes, data work and automation — and you already rebuild the comprehension layer inside each one. Stop rebuilding it. Your revenue stays consulting, implementation and transformation; the infrastructure underneath stops being your cost.
Embed
Inferrex becomes part of your product's architecture, and your customers may never see the name. This is the one that is structurally different from the other three, which is why software vendors have
their own branchTwo more, and neither is a fifth column
/ the distinction
What your business is, and how you work with us, are different questions.
A partner type describes who you are. A partner model describes how you work with Inferrex. One company has one type and usually several models, and keeping them separate is what stops a partner programme becoming seven near-identical tracks that all mean "we would like to work together".
Systems Integrator
Deliver, often with Sell and Co-sell. Delivery-led, customer by customer, with the infrastructure underneath rather than rebuilt inside each engagement.
Consultancy
Deliver or Refer, depending on whether the engagement ends in advice or in something running.
Software Vendor
Embed, often with Co-sell. Its own branch:
Software Vendor PartnersManaged Service Provider
Sell and Operate. You run it; your customer consumes the outcome.
Reseller
Sell, sometimes with Operate. You own the sale and may keep the relationship.
Cloud / Technology Partner
Co-sell, marketplace distribution, joint solutions and reference architectures. You are not necessarily selling Inferrex; Inferrex is part of a larger solution.
Referral Partner
Refer. An introduction, and no delivery obligation.
/ the economics
A system understood once is understood for every customer you have.
Integration work has historically been per-customer: each deployment is a project, and the project does not make the next one cheaper. That is a poor shape for a partner business, because revenue scales with delivery capacity rather than with customer count.
Comprehension inverts it. A provider Inferrex has understood is understood across every workspace, so a connector your first customer needed is already there for your fiftieth. The work that stays per-customer is the part that should be — the design, the judgement and the outcome.
The progression across the four paths follows the same logic: Refer → Sell → Deliver → Operate → Embed. As capability and strategic weight increase, so does what each side gets out of it. Nothing requires you to move along it.
Tell us which of the four you already are.
Most partner conversations stall because the model was assumed rather than agreed. It is a short conversation once it is named.