Choose the business outcome
Identify the system you want to connect, the recurring question you need answered, or the JobBOSS task you want to automate. Name the person who owns the result.
TRIDENT · GETTING STARTED
Start with one useful result.
Build from there.
A clear business outcome makes package selection, implementation and adoption much easier.
TRI-GDE-001 · v1.0.0 · Revised 2026-10-16
Confirm the environment
Review your JobBOSS version, company databases, Windows and SQL Server environment, hosting arrangement, installation permissions and the applications or AI client involved.
Install and establish the first workflow
Installation establishes the Trident software and connectivity. Onboarding establishes user context, package access and a first practical scenario. Customer-specific connectors and workflow development are scoped around the actual requirement.
Verify, train and expand
Verify the results against JobBOSS, agree how consequential changes are reviewed, and train the people who will use the workflow. Expand once the first use case works as intended.
WHAT IS BEING SCOPED?
The product, the setup and your workflow.
Software subscription
The licensed Trident capabilities for the selected package and agreed site scope. Integration and Insights serve different needs; Automation combines their capabilities with transactional AI access.
Installation & onboarding
Establish the software, connectivity, user context and initial use. The environment and package determine the work required.
Integration, workflows & training
Customer-specific connectors, workflow design, additional training and wider rollout are scoped separately rather than assumed to be included in a subscription.
AI platforms, third-party software and hosting are separate services. Confirm hosted-environment requirements before scheduling installation.
PREPARE FOR THE FIRST CONVERSATION
Bring the process, not a technical specification.
Tell Neptune which JobBOSS environment you use, who owns the process, what happens today, the expected result, and which other systems or AI tools are involved.
For integration projects
Identify your developer or software partner, the information that must move, the trigger and the system responsible for each step.
For AI workflows
Identify the recurring question or task, the users involved, and where an approval or result check belongs.