> ## Documentation Index
> Fetch the complete documentation index at: https://seal-d2ca5bea.mintlify.site/llms.txt
> Use this file to discover all available pages before exploring further.

# Implementation

> How we get you up and running on Seal.

## At a glance

<CardGroup cols={3}>
  <Card title="Live in 1–6 weeks" icon="calendar">
    Most implementations. Complex multi-system migrations take 8+ weeks.
  </Card>

  <Card title="Minimal effort from you" icon="wrench">
    We do the configuration, migration, and documentation. You review and sign off.
  </Card>

  <Card title="Life sciences expertise" icon="flask">
    Deep experience with LIMS, ELN, QMS, and GxP compliance requirements.
  </Card>
</CardGroup>

<Note>
  **Every engagement starts with a consultation.** We assess your workflows, compliance requirements, and goals—then give you an accurate timeline.
</Note>

## Your team

Your **solutions consultant** stays involved throughout. Day-to-day, the work is led by an **implementation consultant** specialized in your area—whether that's QMS, laboratory workflows, manufacturing, or clinical operations.

From the start, we agree on a **go-live date** and a **visible specification** that defines what we're building. Both stay visible throughout—you always know where we are, what's left, and when we'll be done.

## Why implementation is fast

Seal has **AI built into the platform—Neil**. Building a form that would take a day in traditional systems takes minutes. Configuring a workflow, generating validation documentation, restructuring a template—all happen in real time. Because iteration is so fast, we can try things, get your feedback, and refine until it's right.

Everything we do is through the platform UI. There's no custom code or hidden configuration. **Anything we can do, you can do.** We train your team as part of implementation, so you're self-sufficient afterward—though we're always available if you need us.

We're here because we know life sciences workflows and what works. We get you to a strong initial state faster than starting from scratch, with proven patterns built in.

## New processes or migrations

<CardGroup cols={2}>
  <Card title="New processes" icon="sparkles">
    Digitizing paper-based workflows, replacing spreadsheets, building new systems from scratch.
  </Card>

  <Card title="Migrations" icon="arrow-right-arrow-left">
    Moving from existing platforms—LIMS, ELN, QMS, document management. See [Data Migration](/validation/data-migration) for details.
  </Card>
</CardGroup>

## What we need from you

* **System access or exported data** — read-only access to understand your current processes
* **How you work today** — SOPs, workflow diagrams, or a walkthrough with your team
* **API documentation** — if integrating with existing systems

Before receiving any data, we sign NDAs and data processing agreements. All credentials are handled securely.

## Timeline expectations

| Scenario                                                         | Typical timeline      |
| ---------------------------------------------------------------- | --------------------- |
| Single workflow                                                  | As little as 24 hours |
| Initial value / first use case                                   | Within 1 week         |
| Full implementation (multiple workflows, integrations, training) | 2–6 weeks             |
| Complex multi-system migrations                                  | 8+ weeks              |

## The process

For new processes, we work through four phases. For migrations, configuration runs in parallel with data extraction and transformation — see [Data migration](/validation/data-migration) for details.

<Steps>
  <Step title="Requirements gathering (1–2 weeks)">
    We run workshop sessions with your team to understand your workflows, document process flows and approval chains, and identify any integrations needed (ERP, LIMS, etc.).

    **Deliverable:** Functional requirements document
  </Step>

  <Step title="Platform configuration (1–3 weeks)">
    We build your system:

    * Configure entity types, templates, and fields
    * Set up review requirements and approval workflows
    * Configure user roles and permissions
    * Build any required integrations or automations

    Throughout this phase, you review configurations iteratively and provide feedback.
  </Step>

  <Step title="Validation (1–2 weeks)">
    Following your qualification approach:

    * Seal executes test scripts against your configured workflows
    * Your team executes User Acceptance Testing (a few hours over 1–2 weeks)
    * All test evidence is captured in Seal's validation module

    **Deliverable:** Complete validation documentation package
  </Step>

  <Step title="Training and go-live">
    * End-user training sessions (recorded for future reference)
    * Admin training for your Seal administrators
    * Go-live support during the initial rollout
  </Step>
</Steps>

## Verification

| Type                            | What we verify                                                                            |
| ------------------------------- | ----------------------------------------------------------------------------------------- |
| **Functional testing**          | Test scripts executed against your configured workflows                                   |
| **User acceptance**             | Your team validates the system meets business requirements                                |
| **Data integrity** (migrations) | Record counts, checksums, audit trails — see [Data Migration](/validation/data-migration) |

All validation evidence is documented and available for regulatory inspection.

## After go-live

You're not on your own after cutover:

* **Dedicated support contact** with clear escalation path
* **Training materials** remain accessible for your team
* **Customer success manager** for ongoing support as you grow

<Tip>
  **Ready to get started?** Contact your Seal representative or email [support@seal.run](mailto:support@seal.run).
</Tip>