Pando
Pando is a Notion-native system for customer data and product development management: one shared core (projects, role slots, launch cadence, contacts) that any team clones into its own operating system. Like the aspen it's named for, every org-OS grown from it is its own tree on one root. An optional Bridge layer connects it to WhatsApp, Slack, Discord, or Telegram.
The vision
Pando is a Notion-native root system. One shared core of projects, role-by-role workstreams, launch cadence, and a contacts rolodex that any team clones into its own operating system. The name comes from the aspen: a single organism in Utah whose ~47,000 trunks share one root system, often called the largest living organism on Earth. Pando works the same way, every org-OS grown from it looks like its own tree above ground, but underneath they share one root. Underneath, it manages the two things every small org juggles, customer data and product development, against one structured database as the system of record. A Bridge layer reads and updates both from wherever the team already talks.
The core insight: the ops manager of a 5–20 person org doesn't need yet another dashboard to check, they need one place that already holds the week. Pando is that place, and because the structure is shared, the same root supports many branches of an organization (or many organizations) at once, each coordinating its own engineers, designers, and stakeholders against a weekly delivery cadence.
How it works
- Notion as the source of truth, projects, people, tasks, and assignments live in a structured database any team member can read directly.
- Role pages as modular slots, every role page is the same skeleton (a workstream board plus a per-release checklist), and every dashboard is just a view of the same underlying task DB.
- Launch cadence, a launch checklist and shared calendar drive the weekly delivery rhythm.
- Optional Bridge layer, Notion ↔ messaging, so you can run your week from WhatsApp, Slack, Discord, or Telegram instead of opening the workspace.
Clones and branches
Pando is built to be cloned. The root stays the same; each clone renames the slots to fit its branch. Backend / Frontend / AI is the default split, but the same shape holds for Producers / Designers / Engineers, or Sales / Ops / Customer Success.
SpoonOS, the Spoonerism clone, was the first tree to grow from Pando, narrowed to WhatsApp because that's where the label coordinates. Healthcare-CRO and clinical-trial coordination clones are next on the roadmap.
