Endonaut
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

Development sequence

Build, test, integrate, release.

Each stage ends in an observable product state. Quality control, player testing, and scientific review continue throughout development 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.

Parallel workstreams

One product, built on many fronts.

The milestone sequence is supported by coordinated work across game systems, content, art, user experience, technology, quality assurance, 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
Balancing & feature-complete review
Player-data-led iteration
Environments & content Biomes, resources, hazards
Scope & content plan
Representative environment
Multi-biome production
Continued environment and content development
Art & audio World, assets, feedback
Concept art & technical planning
Vertical-slice art
Art production & integration
Continued art and audio development
UX & accessibilityInterfaces and onboarding
UI/UX mockups
Initial player feedback
Core interfaces & onboarding
Onboarding & usability refinement
Customer support & player feedback
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
Acceptance criteria
Initial external testing
Internal testing
Closed external testing & QA
Player data & feedback
Marketing & communityPositioning and acquisition
Messaging & asset planning
Gameplay footage & screenshots
Store page, wishlists & previews
Creators, press & launch assets
Launch & community operations
Educational researchPreparation, not commercialization
Pre-release preparation may begin
Study design & access planning
Recruitment & workshop materials
Preparation continues
Formal evaluation begins
How to read this matrix Each column represents a planned development phase, while each row follows a funded workstream across those phases. Bright green identifies an activity closely associated with the phase's central milestone; it does not distinguish Early Access features from other work. Dark green indicates development or refinement planned during that phase. Tan identifies validation, completion, or release milestones. Neutral cells indicate that no phase-specific activity is currently assigned. This matrix represents the overall funded program, not solely the contracted development-and-art scope described in Appendix C of the business plan. Marketing and educational validation are separately funded workstreams. Marketing activities are shown as part of the integrated plan, but their exact timing may change according to product readiness. Final task timing will be established through the Game Design Document, statement of work, production backlog, and educational research plan.

Delivery principles

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.

Planning status

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.

Explore the game walkthrough See the long-term product vision