English
Log inGet a demo

Run several partner programs as one.

Unifyr handles enterprise partner management where partner types, regions and funded budgets all operate together.

Get a demoPricing

What is partner ecosystem management?

Partner ecosystem management is governing every company that sells, services or integrates with your product as one connected program instead of unrelated relationships. What makes it hard is rarely the number of companies but the number of kinds.

A program becomes structurally difficult at its second partner type, its second region or its first funded marketing budget, and each of those arrives long before the roster looks large.

Full definition

A region gets its own view

Each custom view is targeted at a partner group and held in priority order, so a partner who qualifies for more than one is given the highest. A view can also sit inactive until the region is ready for it.

A funded budget arrives with a rate attached

A fund type carries the percentage of qualified spend you reimburse, which is what makes a fund co-op rather than discretionary. One type can be the default, and each decides whether partners request against it or you allocate it.

Your own forms and approvals

Custom objects hold the forms and approvals a mature program has accumulated, on the partner record beside the deals and the training. One customer models warranty registration, invoice submission and demo unit requests without a second system.

Where a new partner type lands

It lands in a partner group, and the group is what the rest of the program is aimed at.

Membership is a rule, not a list. A partner qualifies on its profile, on fields you define and on what it has done in marketing, and the rule is re-run on a ninety-minute cycle and at sign-in.

A tier program is scoped to its groups, and so is the onboarding plan a partner meets at first sign-in. The new type becomes one group with structures pointed at it, not a new condition inside every module.

See three partner types run at once

Security and access control

You are giving hundreds of outside companies a login. The controls matter more than in most software you buy.

Configured separately for the partner portal and the admin console, each with its own client and fallback handling.
Auth0, on your own tenant. You supply the application and hold the keys.
Scoped by partner group. Membership rules re-evaluate on a schedule and again when a partner signs in.
Assigned per user rather than per partner account, so seniority inside a partner matters.
Impersonation opens a partner's exact portal view, so a reported issue is reproduced rather than described.

The questions that arrive with the second partner type

Can we run more than one tier program?
Yes, concurrently, each scoped to its own partner groups. A reseller ladder, a regional push and a compliance tracker coexist rather than competing for one global set of levels. See partner management.
Will our existing processes survive the migration?
Eleven custom objects sit on the partner record in one live tenant, each one a process that program had already accumulated before it arrived. You define them in the admin console under Partner Management, so a process that works is carried over rather than rewritten.
What about single sign-on?
Single sign-on is configured separately for the partner portal and for the admin console, each with its own client identifier and its own handling for a user who arrives without a match. The identity provider is Auth0 on your own tenant, so you supply the application and hold the keys.
Which edition does a program this size need?
The editions differ by how much structure you can run at once: concurrent tier programs, more partner types, deeper fund accounting. Compare Activate, Grow and Scale.

Tier programs, funds and portal views

Bring your most awkward program requirement

Describe it in full, however specific to your program, and we will show you where it lives here.

Get a demo