PremisIQ

Founding Pilot Program

Test private AI on one internal-data workflow

PremisIQ’s Founding Pilot is a narrowly scoped on-premise implementation for companies ready to validate one valuable internal-data workflow before moving toward production.

Apply for a Founding Pilot See what is included
  • Paid pilot
  • On-premise only
  • Clear validation criteria

Qualification

Who the pilot is for

The Founding Pilot is designed for companies with a real internal-data problem, a narrow workflow to validate, and the internal support needed to test private AI in a controlled on-premise environment.

Clear business problem

  • One identifiable business problem
  • Realistic expectations
  • A potential path to production

Accessible internal sources

  • One or two accessible sources
  • IT support or technical access

Committed validation

  • An internal project owner
  • Willingness to validate results

Scope guardrail

If the use case is too broad, the pilot should be narrowed before implementation begins.

Typical Setup

Example pilot scope

A founding pilot is intentionally narrow. The goal is not to replace company systems, but to validate one valuable internal-data workflow with clear test criteria.

Always on-premise

The pilot is always deployed on-premise. During assessment, PremisIQ determines whether compatible customer hardware can be used or whether a dedicated pilot server should be specified and provided.

  • Customer hardware assessed
  • Pilot server specified only if needed

Both are hardware arrangements within the same on-premise deployment model, not separate deployment options.

Delivery Scope

Pilot scope: what is included and where it ends

The Founding Pilot is a focused paid engagement. It includes the core work needed to define, install, connect, test, and evaluate one private AI workflow — while keeping broader rollout, automation, and custom expansion outside the initial scope.

Included in the pilot

  1. Define the pilot

    • Discovery workshop
    • Use-case definition
    • Test criteria

  2. Review access and infrastructure

    • Source review
    • Permission review
    • Hardware assessment
    • On-premise architecture

  3. Install and connect

    • Server setup
    • Initial data connection
    • Focused RAG/search workflow

  4. Validate and recommend

    • Validation session
    • Production recommendation

Timeline

Pilot timeline

A typical Founding Pilot targets four to six weeks.

  1. Week 1

    Discovery and criteria

    Discovery, use case, infrastructure, data access, and test criteria.

  2. Week 2

    Environment preparation

    Server preparation, environment installation, and source connection.

  3. Weeks 3–4

    Workflow setup and testing

    Indexing, retrieval configuration, workflow setup, and internal testing.

  4. Weeks 5–6

    Validation and recommendation

    User validation, evaluation, improvement, and production recommendation.

Timing depends on hardware availability, data quality, system access, and customer response time.

Success Criteria

How success is measured

Before implementation starts, the pilot should have agreed questions and practical validation criteria. The goal is to measure whether the workflow is useful, accurate enough, and realistic for production.

01

Answer quality

  • Correct source retrieval
  • Source-linked answers
  • Agreed questions answered satisfactorily
02

Access control

  • Permission behavior
  • Systems accessed through one interface
03

Operational usefulness

  • Time required to find information
  • Response time
04

User validation

  • User feedback
  • Practical fit for production

The exact criteria are selected during discovery so the pilot can be evaluated against the customer’s real workflow.

Customer Role

What your team provides

A successful pilot requires a small but committed internal team and timely access to the agreed systems or sources.

People

  • Internal project owner
  • IT contact
  • Test users

Access

  • Server-room or infrastructure access
  • Representative sample data
  • Permission information

Validation

  • Agreed test questions
  • Timely feedback

Commercial Model

Commercial model

The Founding Pilot is a paid, narrowly scoped engagement. Exact pricing is defined after the fit call, once scope, hardware needs, and delivery effort are clear.

  1. Fit call

    Review the use case and confirm pilot fit.

  2. Fixed pilot scope

    Define fixed pilot boundaries, scope, and deliverables.

  3. Commercial proposal

    Define exact pricing after scope validation.

  4. Pilot delivery

    Execute the pilot with milestone-based payments.

Exact pricing is not published before scope validation.

Quoted separately when needed

  • Hardware quoted separately
  • Production implementation quoted separately
  • Additional integrations quoted separately
  • Ongoing support begins under a separate agreement

Separate items are reviewed only if needed after the pilot scope is validated.

Confidentiality

Confidentiality and case-study choices

Founding Pilot customers can choose how, or whether, their participation is referenced publicly.

Nothing is published without written approval.

Visibility choices

  1. Named case study
  2. Anonymous case study
  3. Technical case study without identifying details
  4. No public case study
  5. Private reference call only

Application

Apply for the Founding Pilot

If your company has one clear internal-data workflow that could benefit from private AI, apply for a founding pilot and we’ll review whether the scope is suitable.

Apply for the Founding Pilot

Founding Pilot will already be selected in the form.