Public Roadmap

Where Tree is going.

One Idea, three trees: Product, Brand, Distribution — plus the Standalones strip at the bottom. Pan and zoom anywhere on the canvas. Hover any node to trace where it came from. Click for detail.

Trees planted: 1 · Coffees consumed: · Tabs open: 47
hover · trace · click · drag · scroll to zoom
ProductBrandDistributionStandalonesMarketing site liveAccounts & LoginCore data modelFirst interactive treeNode statesMulti-tree projectsVisual feedbackTemplatesWorkspaces & teamsAssigning nodesComments & activity logDesktop appPublic APICompanion mobile appIntegrationsName & conceptTone of voiceBrand identityIn-app copyEmail copyTransactional copyLogoVisual styleOnboarding copyMarketing sitePress kitPublic roadmapPitch deckWaitlistDiscordSocial accountsGuest articlesPodcast appearancesBlog launchNewsletterFirst 5 blog postsPublic launchPress outreachPissed the in-house designer offSurvived first DNS propagationFirst user who isn't a friendFirst feature request received100th tree plantedThe Idea
100%
The full roadmap is best viewed on desktop. Below is a simplified list.

Completed

  • The Idea

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

  • Marketing site live

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

  • Name & concept

    The "Tree" name and the metaphor it implies.

  • Tone of voice

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

  • Brand identity

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

  • Logo

    The mark.

  • Visual style

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

  • Marketing site

    The public site you arrived at.

  • Public roadmap

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

  • Pissed the in-house designer off
  • Survived first DNS propagation

In progress

  • Waitlist
    Marketing siteBrand · Tone of voiceBrand

    Email capture for early access.

Available

  • Accounts & Login
    Brand identityBrand

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

  • Core data model

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

  • In-app copy

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

  • Email copy

    Newsletter and broadcast emails — what humans write to humans.

  • Transactional copy

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

  • Press kit

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

  • First feature request received

Locked

  • First interactive tree

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

  • Node states

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

  • Multi-tree projects

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

  • Visual feedback
    Tone of voiceBrand

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

  • Templates
    Public roadmapBrand

    Pre-built tree templates for common project shapes.

  • Workspaces & teams

    Multi-user workspaces with roles and permissions.

  • Assigning nodes

    Assign nodes to teammates; ownership and notifications.

  • Comments & activity log

    Per-node discussion and a chronological feed of changes.

  • Desktop app

    Native desktop client. Same data, faster.

  • Public API

    Read/write access for integrations and self-hosting.

  • Companion mobile app

    Read-mostly mobile companion for marking work done on the go.

  • Integrations

    Bidirectional sync with GitHub, Linear, and the usual suspects.

  • Onboarding copy

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

  • Pitch deck

    For investors, partners, the occasional curious stranger.

  • Discord
    Brand identityBrand

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

  • Social accounts
    Brand identityBrand

    Mastodon, Bluesky, the usual.

  • Guest articles

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

  • Podcast appearances

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

  • Blog launch
    Tone of voiceBrand

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

  • Newsletter

    Monthly digest with what shipped and what is next.

  • First 5 blog posts

    Five posts in the bank before launch.

  • Public launch
    🔒 First interactive treeProduct

    The announcement post. Shared everywhere we know.

  • Press outreach
    🔒 Press kitBrand

    Reaching out to journalists who cover tools for builders.

  • First user who isn't a friend
    🔒 Public launchDistribution
  • 100th tree planted
    🔒 Social accountsDistribution
Completed In progress Available Locked
II. About the roadmap

Common questions about the roadmap.

Placeholder answer about what Available means — typically a node whose prerequisites are met and could be picked up next, but is not yet in active development.

Placeholder answer about scoping decisions, capacity, and the difference between 'we won't do it' and 'we haven't gotten to it yet'.

Placeholder answer about cadence — when nodes change status, when new nodes appear, and where to watch for changes.

Placeholder answer about how to send feedback or feature requests, and what happens to suggestions after they arrive.