Partner onboarding

It depends on the program. Most customers target a time-to-first-deal of thirty to ninety days. Unifyr doesn't enforce a fixed timeline; it enforces a sequence. A partner can't be marked ready-to-sell until the certifications and tasks you've defined are complete. Programs that hold to that sequence typically see consistent ramp times across new partner cohorts.

Yes. Onboarding journeys are configured per partner type, with distinct application forms, required courses, and stage definitions. An MSP sees a different journey than a referral partner or a global SI. Each is calibrated to what that partner type needs to do before they sell.

The journey defines explicit readiness criteria, usually a combination of completed certifications, a finished profile, and a product training completion. Until those are met, the partner sits in onboarding rather than active. Lead distribution, deal registration, and tier placement can all be gated on that state, so partners who haven't completed onboarding aren't treated as if they had.

Stalls surface in two places. The dashboard shows every partner sitting on a stage past its expected duration. Onboarding IQ also runs in the background, sending the partner contextual reminders (an unfinished course, an unfilled profile field) and escalating to the channel manager when there's no response. Human time stays focused on accounts that need a real conversation.

Yes. Application pages, journey stages, and onboarding content all support the same theming and overrides as the rest of the portal, so a distributor's partners can see distributor branding alongside the vendor's. Stages and required tasks can also vary by tier or geography, which matters when local regulation or language requirements differ from the global program.

Contracts are part of the intake flow. The application produces a contract artifact on approval, which routes to e-signature. Once signed, the contract record attaches to the partner record in Unifyr alongside any supporting agreements. Counter-signatures and signed PDFs archive in the partner's record for later retrieval.

Yes. Courses, documents, and journey stages are library objects that can be referenced across multiple onboarding journeys. A product certification that every partner type needs doesn't have to be rebuilt per type; reference the same cert from each journey. When the source material changes, every journey that references it picks up the update.

Partner records sync to the major CRMs, with Salesforce and HubSpot as the out-of-the-box connectors and other CRMs available through extension. Contract artifacts route to e-signature providers, and certification data writes back to the partner record. When onboarding completes, the ready-to-sell state propagates to the systems your sales team uses.

Partners see a progress view inside the portal: the stages of their onboarding, the tasks within each stage, and a completion indicator against each. That view is the same one the channel manager sees in aggregate, so conversations between partner and manager reference the same picture.