Stage 5: Integrations
A short, flexible stage. Decide which third-party and Trimble integrations matter for this company, capture what each one needs, and keep that work trackable in Company Tracker.
Integrations matter more than they used to. Many SaaS products connect through the Vista / Trimble API and similar patterns. This stage does not pretend to be an expert how-to for every vendor. It gives the client room to name integrations and track what they need.
phase_key: integrations
What this stage accomplishes
- The team agrees which integrations are in scope for go-live versus later.
- Each selected integration can carry its own item / action list of whatever the client wants to track.
- Those items sync to Company Tracker, and the stage can refresh from Tracker so the views stay aligned.
Typical work / artifacts
Common / example integrations
Trimble / Viewpoint-related
- ProjectSight (spelling: SIGHT). Commonly purchased; project management / operations focused. List it when in scope.
- Trimble Pay. Include it when in scope. It often needs little dedicated setup of its own and leans heavily on Vista setup. Subcontractors log in, enter monthly amounts to be paid, and the product handles that payment workflow. It strongly enhances the process.
- Viewpoint HR Management (commonly known as the employee portal)
- Vista Field Service
- Tekla and PowerFab
Payroll providers (examples)
- ADP, Paychex
HR-related (examples)
- Bamboo, UKG
Other project management
- Procore
Other
- The client can add whatever else they need. Keep the list open and flexible.
This stage tracks ownership and work items. Detailed vendor setup still happens in the relevant systems and product how-tos, not as exhaustive third-party procedures here.
Tracking integrations
For each selected integration, create an item / action list of whatever needs tracking for that connection. Those items sync to Company Tracker. Use sync / refresh so Tracker changes come back into the stage view.
Connection to Company Tracker / Vista
Sync creates or updates Tracker items for integration setup. Refresh pulls Tracker changes back into this stage. Vista / product configuration for each integration still happens in the relevant systems; Tracker holds the work items for this stage.
Exit / moves to next stage
Integrations is complete when in-scope integrations are identified and Tracker actions exist for the setup work. The implementation then moves to Testing & Training.
In the product
In Mission Control, complete the Integrations workspace (scope list and milestone sync). For step-by-step UI, see Complete the Integrations Stage. For shell navigation and exports, see Run the Implementation Playbook.