Where Tree is going.

The original spark: what if every project was a tech tree? One seed, three trees grow from it.

Public marketing page with parallax forest, problem framing, and waitlist capture.

Email + OAuth sign-in, account management, basic team membership.

Schemas for trees, nodes, edges, statuses, and how they live in the database.

The minimum viable thing: render a tree, click nodes, see prerequisites.

Status transitions and the rule engine that auto-unlocks dependents.

A workspace with several trees side-by-side instead of one big graph.

Animations, sound (optional), and copy that makes unlocks feel earned.

Pre-built tree templates for common project shapes.

Tree splits in two. Plan is where you build the structure. Work is where you get through your day.

The "Tree" name and the metaphor it implies.

How Tree talks. Slightly mossy. Allergic to corporate jargon.

The visual identity bundle that Logo and Visual style live under.

The mark.

Color tokens, typography, the parallax forest, the WH3-tree feel.

The public site you arrived at.

Same one you are reading. The roadmap IS part of the brand.

Email capture for early access.

A place for early users to hang out and tell us we are wrong.

Mastodon, Bluesky, the usual.

A blog. Posts on engineering, design decisions, and the company.

Five posts in the bank before launch.

The semi-final visual pass. Motion, design language, every surface re-elevated.

Logos, screenshots, descriptions, and a one-pager for journalists.

Fast capture, in only. Dump a thought, it gets recognized and routed.

Triage for captured items. Anything that needs a human decision lands here and waits for placement.

Microcopy, button text, error messages: all written in Tree voice.

Newsletter and broadcast emails: what humans write to humans.

Welcome, password reset, billing: all the system-triggered emails.

A short newsletter going out when there is something real to say.

A day-agenda view. Tasks and time-anchored items laid out across the hours you actually have.

Active projects positioned by deadline across the week. Weekdays, weekend, and whatever's looming.

Time tracking by confirmation, not by stopwatch. The tree knows what you planned; you confirm what actually happened.

Core single-user product ships publicly. Free and Paid tiers go online; the team feature track unblocks from here.

Native desktop client. Same data, faster.

Read/write access for integrations and self-hosting.

Multi-user workspaces, comments, assignments, permissions, activity feed, real-time collaboration. The team tier comes online here.

Slack notifications, GitHub sync going beyond v1, webhooks, public API. Tree talking to the rest of the toolchain.

View-only mobile app for browsing your projects on the go. Available to Free users as a Core feature.

Paid visual themes drawing on strategy game design traditions. Our names, our art, our take.

When you add a node, Tree suggests likely prerequisites based on context. Far-future, requires the core product to mature first.

Docker image with the core feature set, free. Paid and Team-only features require a paid license, run on your own infrastructure.

Multi-user workspaces with roles and permissions.

Assign nodes to teammates; ownership and notifications.

Per-node discussion and a chronological feed of changes.

Native mobile app with full editing capability. Far-future, after the companion app validates the mobile use case.

First-run experience copy. The hardest copy to write.

For investors, partners, the occasional curious stranger.

Going on shows to explain why a tech tree is project management.

Writing on external publications (HackerNoon, Indie Hackers, dev blogs, etc.).

The announcement post. Shared everywhere we know.

Reaching out to journalists who cover tools for builders.