Platform access level: Org Admins
Arist builds and maintains each integration for you, so your team confirms credentials and reviews results rather than writing integration code. This guide explains the broker model behind every connection, the implementation timeline, the security posture, and what happens after go-live. It is written for Org Admins and IT stakeholders who sponsor an integration.
1. Broker model
Arist connects through a managed integration platform that brokers each connection, so your systems and Arist never connect directly. Arist's solutions engineering team builds and maintains the connection on that platform for the life of the contract.
Your IT team's role is limited to confirming credentials for each connected system.
The integration platform Arist uses today is Workato.
2. Six phases from SOW to cutover
Every integration runs on a fixed six-phase methodology with an eight-week clock that starts when the SOW is signed. Pre-sales discovery feeds the plan but sits outside this clock.
Phase | Timing | Milestone |
Scoping and planning | Week 0 | SOW signed and systems inventoried |
Kickoff and discovery | Weeks 1 to 3 | Configuration spec signed off |
Build and configure | Weeks 4 to 5 | Configuration working in staging |
UAT and pilot | Weeks 6 to 7 | UAT signed and cutover scheduled |
Cutover and go-live | Week 8 | Production stable |
Steady state | 90+ days | Project closed |
3. Fast track and full track
Two tracks run inside that timeline, depending on which systems you connect.
Fast track: SSO and delivery methods are plug-and-play, so you can begin sending lessons by around week 3.
Full track: HRIS and LMS run the full schedule and go live together at the week 8 cutover, where HRIS brings learners in and LMS sends completions back.
4. Security posture
Arist keeps credentials and data contained through the broker model rather than direct system access.
Brokered connection: Your systems and Arist never connect directly, since the platform sits between them.
One credential per organization: Arist authenticates through a single key scoped to your organization.
Enterprise-grade platform: Monitoring, logging, and reliability run on a vendor-backed integration platform rather than one-off code.
Maintained for the contract term: Schema changes, vendor API updates, and error resolution are included.
Important: Your IT team's only required task is confirming credentials for each connected system.
5. Ninety-day handoff
After go-live, the integration moves from the implementation team to Customer Success over 90 days.
Milestone | Timing | Focus |
Go-live | Day 0 | Production deploy and cutover |
Hyper-care | Week 1 | Bi-weekly check-ins, IM leads |
Retro | Day 14 | Hyper-care closes, CSM takes lead |
Adoption check | Day 30 | First NPS and Org Admin enablement |
Mid-point review | Day 60 | Friction surfaced early |
Closure | Day 90 | Project closed |
Related articles
Arist Integrations Guide
HRIS and LMS Integration - Technical Guide
Note: Need help at any point? Reach out to your Arist Customer Success contact, or email [email protected].