Implementation Timeline
AI Gateway:
Prerequisite: DNS record
Expected time: 30 days post implementation kickoff call
Includes:
Gateway deployed
Models accessible
Observability configured
DNS name configured and certificate applied
Single sign-on configured
Users able to login
Data Connectors:
Prerequisite: AI Gateway deployed
Expected time: 1-4 weeks (depends on connector complexity)
Initial Setup
Domain Hosting
Will your organization host the chat subdomain?
If YES:
Please consider your preferred subdomain (e.g., chat.company.com).
If NO:
Expedient can provide hosting for the subdomain (e.g., yourcompany.expedient.cloud).
Why we ask:
This helps us determine network setup requirements and ensures your AI Chat Gateway is accessible under a domain structure that fits your organization.
Single Sign-On (SSO)
Does your organization have a cloud-hosted SSO solution either Azure Entra or Okta?
If YES:
Expedient will coordinate with your team to enable SSO integration for the AI Chat Gateway.
If NO:
Please identify your current identity management system (cloud or on-premises).
Why we ask:
Understanding your identity management approach allows us to plan for secure user access and anticipate any integration needs or additional services, such as SSO licensing implications (e.g., Expedient SSO user count).
AI Document Search
Data Sources
Is SharePoint Online (cloud-hosted) your primary document repository? What other data sources do you want to integrate?
If YES:
We will prepare for a high-level discussion on creating the integration during the ‘Walk’ Phase.
If NO:
Please consider which document repository you plan to use and be ready to discuss its capabilities.
Why we ask:
Identifying the data source early streamlines connection setup and gives us time to research and address custom integration requirements for non-standard platforms.
Rollout Plan
POC / Post-POC User Groups
Will there be a designated focus group during the trial phase?
If YES:
Please identify the involved groups or departments at a high level.
If NO:
Think about which groups should begin, and how you may want to expand rollout post-trial.
Why we ask:
This informs the development of training resources and enables us to support your unique onboarding and enablement needs. Early identification of user groups also helps frame your internal communication and adoption strategy.
Use Case Planning
Business Needs & Success Measurement
Have you identified specific business pain points or desired outcomes for the AI Chat Gateway/Document Search? Do you have a plan to measure trial success?
If YES:
Please provide a high-level mapping of goals for discussion during our kickoff call.
If NO:
Start considering a short list of measurable trial goals or use cases you want to validate.
Why we ask:
Clear objectives help focus the project, define what success looks like, and ensure the solution fits your business needs. This early assessment also enables us to design the trial to maximize value for your organization.
Success Criteria and Timeline
Expectations Of Timeline
What is your desired timeline for rollout, and are there any critical dates or milestones to be aware of?
Why we ask:
Aligning on timing and success metrics ensures expectations are clear and the project stays on track.
Prioritization
Are there any factors, deadlines, or organizational priorities that may impact the POC or production timeline (e.g., levels of urgency, potential delays, or competing initiatives) during the expected implementaion period?
Why we ask:
Understanding your internal priorities and possible scheduling constraints allows us to proactively address any challenges that could extend the trial or shift critical milestones. This helps ensure we deliver within your ideal timeframe and adjust plans as needed to stay aligned with your organizational goals.