Company

One executive. One agent.
One command center.

It started as the internal command center for a 300-person company with no BI team. It changed how that company ran. Nodboard is that playbook, turned into a product.

Mission

One screen a company can trust. And talk to.

The first command center had Finance, People, Customers, Operations, Product and Engineering — more than thirty tabs. Three audiences saw three different versions from one set of data. An agent refreshed it every morning from the CRM, the warehouse, the HR system, the call recordings and Slack.

What we learned building it became the product. Reconcile systems that disagree. Keep each number from the wrong reader. Let people ask for changes without breaking what the CFO relies on. Keep it alive.

Origin

From one request to a product.

Five moments, in order. Click through them.

01 / 05

One executive. One agent.

No BI team. No dashboard backlog. An executive described what the company needed to see, and an agent built it — then kept building.

How we work

Four principles. No exceptions.

Each one is a promise you can check. Flip a card to see it in the product.

  • 01

    Ship the screen, not the tool.

    Our customers don't want a BI platform. They want to know how the company is doing. We measure ourselves by the morning they open it.

    01 · In practice
    Monday · 08:00

    Your command center is ready. Home, Finance and Sales are live.

    The first deliverable is a screen you open on a Monday — not a workspace to configure.

  • 02

    Honest numbers, or no numbers.

    Every figure carries its lineage. When sources disagree, we say so. A card with missing data says what's missing.

    02 · In practice
    ARR$8.4Mlineage
    1. Stripe subscriptions
    2. Reconciled with Salesforce
    3. 2 accounts differ — Stripe used, both shown

    Every number can tell you where it came from. Disagreements are shown, not smoothed over.

  • 03

    Governance is product.

    Approvals, permissions and audit aren't the enterprise checklist. They're why a company can let everyone talk to its dashboard.

    03 · In practice
    1. Ask
    2. Diff
    3. Approve
    4. Live

    09:41 · CR-142 approved by Dana Park · VP Sales
    09:41 · shipped to Sales · audit #8812

    Anyone can ask. An approver decides. The log remembers.

  • 04

    Built to be opened.

    A command center earns its place at 8 a.m., on a phone, in a minute. It leads with what changed overnight, and every number explains itself.

    04 · In practice
    Good morning, Dana.

    3 things changed overnight. 1 needs you.

    • Two renewals over $250k have gone quiet for 30 days
    • Gross margin down 2.1 pp — cloud spend
    • Fleet uptime back above 98%

    It opens on what changed, not on a wall of charts.

Team

Small on purpose. Hiring on purpose.

  • Founder

    Jun Sup Lee

    Founder & CEO

    Corporate strategy and operations leader. Built the first command center that became Nodboard.

    Background
    Corporate strategy & operations
    Built
    The original command center — with one agent
    Ask Jun about
    Becoming a design partner
    Become a design partner
  • Open role

    Founding engineer

    Agents & infrastructure

    This could be you.

    You'd own
    The planner, builder, checker and refresh agents.
  • Open role

    Founding designer

    Product & brand

    This could be you.

    You'd own
    The product and the brand — motion, type, data-viz.

Join the first cohort.
Shape what ships.

Free for up to five people. Connect a few tools and the agents build the first version in an afternoon. Or watch a morning in the command center first, about ninety seconds.

Product walkthrough · Northwind Robotics is fictional; every number is dummy data

A morning at Northwind Robotics

Fictional company · dummy data · 1:18

Northwind Robotics's command center at 8:02 a.m. Fictional company, dummy data, the real product.