Six weeks from scope
to an evidence-backed decision.

The Atlas Enterprise Readiness Pilot is a paid, customer-hosted engagement with scope, responsibilities, evidence, and acceptance criteria agreed before kickoff.

DELIVERY MODEL

A bounded path from installation to decision.

Customer delays in access, credentials, connectivity, or approvals should not silently consume the agreed delivery period.

Week 1

Establish

  • Installation
  • Access checks
  • Scope confirmation
  • Collector and connector preparation
  • Baseline collection
Weeks 2–3

Discover and assess

  • Cryptographic discovery
  • Coverage reconciliation
  • Collection-error review
  • Risk assessment
  • Ownership validation
  • Evidence-gap identification
Week 4

Prioritise and plan

  • High-priority findings
  • Dependencies
  • Migration sequencing
  • Target-state recommendations
  • Pilot-candidate selection
  • Migration roadmap
Week 5

Validate the path

  • Migration-readiness workshop
  • Compatibility and recovery planning
  • Optional qualified non-production migration exercise
Week 6

Decide

  • Executive and technical reports
  • Evidence package
  • Acceptance review
  • Operating handover
  • Production-rollout recommendation
PILOT DELIVERABLES

Evidence prepared for handover.

  • Scoped cryptographic inventory
  • Collection provenance and errors
  • Coverage gaps
  • Risk assessment
  • Prioritised findings
  • Agreed owners and ownership gaps
  • Atlas-format CBOM evidence
  • Phased migration roadmap
  • Dependencies and prerequisites
  • Executive report
  • Technical report
  • Pilot evidence package
  • Acceptance decisions
  • Rollout recommendation
  • Migration and recovery results where purchased and completed

Reports distinguish observed facts, customer-provided declarations, AetherQ recommendations, simulated results, and verified results.

PILOT ACCEPTANCE

Success agreed before kickoff.

  • A recorded outcome for every approved collection target
  • Explained coverage gaps
  • Reconciliation against an agreed customer reference sample
  • Evidence and proposed action for agreed high-priority findings
  • Recorded owners or explicit ownership gaps
  • Tested workspace access and collector revocation
  • Verified exports and agreed data-handling controls
  • An accepted migration roadmap
  • Customer ability to operate the agreed workflow
  • Separate migration, validation, and recovery acceptance where execution is included

Acceptance applies to the agreed pilot scope. It does not establish completeness across the customer’s entire estate.

COMMERCIAL MODEL

Fixed-fee, scoped, and explicit.

Atlas pilots are priced by agreed scope. The agreement separately identifies time-limited Atlas access, included engineering allowance, optional migration work, custom integrations, expenses, third-party charges, exclusions, support hours, and acceptance criteria.

After successful acceptance, the customer may proceed to an annual subscription and phased production rollout.

OPTIONAL PLANNING TOOL

Frame the scope before the conversation.

Use the builder to prepare context for an initial discussion. Its output is a planning aid, not an offer or contractual scope.

Pilot objective

What must the pilot prove?

Choose the operational decision the pilot should make possible.