Provisional production plan

From foundation to Early Access

24 months to a living world.

This roadmap outlines the funded development period for Endonaut: converting an early playable environment and established design foundation into a stable, commercially viable Steam Early Access release.

24 months Planned funded development period
5 milestones Each with defined exit criteria
1 objective A cohesive, revenue-capable Early Access release

Build, test, integrate, release.

Each stage ends in an observable product state. Testing, scientific review, and production control intensify throughout the sequence rather than being deferred until launch.

Starting point — completed before funding A playable single-room environment, interactive product walkthrough, biological progression framework, preliminary scope, market analysis, positioning, and launch strategy establish the pre-production foundation for this plan.
  1. Months 1–3

    Production definition

    Convert the existing walkthrough, biological progression framework, prototype, and estimates into an approved production plan.

    Exit: Engine selected; GDD, technical architecture, backlog, schedule, statement of work, and acceptance criteria baselined.
  2. Months 4–8

    Integrated vertical slice

    Bring the defining systems together in one representative environment and establish the target production quality.

    Exit: Exploration, scanning, resources, fabrication, and progression operate as a coherent loop; initial external testing begins.
  3. Months 9–16

    Alpha

    Expand from the slice into the planned multi-biome Early Access experience, with the full progression playable from end to end.

    Exit: Planned systems and environments are integrated; internal QA, scientific review, balancing, and content refinement are underway.
  4. Months 17–21

    Beta & launch preparation

    Stabilize the complete release candidate while improving onboarding, balance, accessibility, performance, and presentation.

    Exit: Feature-complete candidate validated through closed external testing, optimization, QA, and launch-readiness review.
  5. Months 22–24

    Steam Early Access

    Release the first commercial version and begin evidence-driven co-development with players.

    Exit: Stable public build live with analytics, customer support, community operations, and postlaunch development processes in place.

One product, built on many fronts.

The milestone sequence is supported by coordinated work across game systems, content, art, user experience, technology, quality, scientific review, marketing, and educational-research preparation.

Workstream
Definition
M1–3
Vertical slice
M4–8
Alpha
M9–16
Beta
M17–21
Early Access
M22–24
Gameplay systemsCore loop and progression
Architecture & specifications
Integrated core loop
Full EA feature set
Balance & lock
Telemetry-led iteration
Environments & contentBiomes, resources, hazards
Scope & content plan
Representative environment
Multi-biome production
Content complete
Release content support
Art & audioWorld, assets, feedback
Visual targets & pipeline
Production-quality slice
Asset production
Polish & optimization
Launch support
UX & accessibilityInterfaces and onboarding
Requirements & flows
Core interface validation
Complete UI & onboarding
Usability refinement
Player support & iteration
Technical infrastructureEngine, saves, Steam, analytics
Engine & architecture decision
Core technical foundation
Save/load & integration
Performance & Steam readiness
Public build & analytics
QA & player testingAcceptance and stability
Test strategy & criteria
Initial external testing
Internal and focused tests
Closed external testing
Release monitoring
Scientific reviewAccuracy in service of play
Review standards
System-level review
Integrated content review
Final release review
Feedback and corrections
Marketing & communityPositioning and acquisition
Message and asset planning
Credible gameplay capture
Store page, wishlists & previews
Creators, press & launch assets
Launch & community operations
Educational researchPreparation, not commercialization
Study-design planning
Recruitment and access planning
Workshop-material preparation
Research-readiness review
Formal evaluation begins

Progress has to be playable.

The roadmap is structured around integrated product evidence—not isolated feature completion. Every milestone must strengthen the experience players will ultimately receive.

Milestone acceptance

Each stage has defined deliverables and exit criteria. Scope, cost, or schedule changes are reviewed rather than silently absorbed.

Quality throughout

Usability, stability, balance, accessibility, and scientific integrity are evaluated throughout development—not saved for the final months.

Evidence before expansion

The funded objective is a cohesive Early Access product. Version 1.0, institutional tools, and other expansions will be shaped by player, market, and research evidence.

A roadmap with deliberate room to learn.

This roadmap is provisional. Timing, staffing, deliverables, and task-level dependencies will be baselined after funding through the final Game Design Document, development agreement, statement of work, technical architecture, and production backlog. Material changes will follow formal review and change control.