From signature to partners logging in inside a day. Here is what we need from you at the start, what arrives already populated, and the order the rest of it runs in.
The first question is not what you want to build. It is what you already have. Airstride reads your existing system and works out the shape of your program from it: who your partners are, what tier they sit on, which deals they have brought you and what collateral they have been sent.
Any of three sources works. A CRM connection is the richest, and Attio, folk, Zoho, HubSpot, Salesforce, Pipedrive and Dynamics 365 are all supported. An export from an existing PRM works. So does a spreadsheet, which is what most programs are actually running on.
This is the part that changes what your first session looks like. The standard PRM implementation hands you an empty portal and a services invoice, and the first three months go on filling it in. Airstride arrives with your partners, their tiers, their deals, their history and your collateral already in place.
The practical consequence is that your first session is a review rather than data entry. You are checking whether a tier looks right and whether a partner should still be listed, on a screen that already has something on it.
The rest of the setup runs without you. Partner data is migrated, collateral is connected from Google Drive and your other content sources, the portal is white-labelled to your brand, SSO is configured against your identity provider, the Partner Activation Agent is trained on your program, and your partners are invited.
You get told when each piece lands. Nothing waits on a ticket queue and nothing needs a professional services engagement to unblock it.
Three things, and none of them takes long. Everything else on the setup list is ours.
Once the portal is live, the two things most programs do first are connecting the CRM properly so sync runs both ways, and deciding what each partner role is allowed to read.
It is the real one, and it is measured from signature rather than from kick-off. The reason it holds is that almost none of the work is yours. Your data is already in a system we can read, so the setup is a migration and a configuration pass, not a build.
That is the normal case, and it is better handled inside Airstride than before you arrive. Duplicates, dead partners and half-filled records all migrate. You review them on a populated screen, which is a far faster job than reconstructing the list in an empty one.
No. A spreadsheet is a perfectly good starting point and plenty of programs begin there. The CRM connection can come later without redoing anything, and when it does the records reconcile rather than duplicate. See connecting your CRM for what that step looks like.
Not during the migration. The initial read is read-only, so nothing in your CRM changes while we are populating the portal. Two-way sync is switched on once you have signed off the field map.
When you decide. Invitations are the last step of the setup and they are held until you release them, so you can review a fully populated portal under your own brand before a single partner sees it.
Bring the spreadsheet or the CRM you run on today and we will show you the populated portal rather than a demo tenant.
