How it works — Nodboard

northwindrobotics.nodboard.app Refreshed 05:54 · 23 sources

Good morning, Maya

4 things changed overnight. 3 change requests need you.

ARR trend

30D · All regions

$48.4M$46.4M$44.4M

Sep 6Sep 8Sep 11Sep 14Sep 16Sep 19Sep 22Sep 25Sep 27Sep 30Oct 3Oct 6

Needs attention

agent · 05:54

Pipeline by stage

$M

Discovery$18.4M

Evaluation$12.9M

Proposal$8.10M

Negotiation$4.60M

Closed won$3.60M

Headcount

Rippling

412 +9 this month

Engineering 38%Go-to-market 24%Field 18%G&A 20%

What customers said

Gong · 7d

“Integration with the WMS” came up on 11 calls — 4 of them in late-stage deals.

Pricing came up on 6. Uptime on 2.

01 · Connect

Plug in the whole company. Minutes, not a data project.

Sign in with Google or Microsoft. You're the owner.
Connect every tool with an MCP server — or paste any MCP URL.
Read-only scopes wherever the vendor allows. Any tool that can write is blocked in code.
A discovery pass shows exactly what we can see: objects, channels, tables, freshness.

Try itPick tools, approve the scopes, watch the discovery pass.

Connections · Northwind Robotics

1Pick
2Consent
3Discover

Read-only scopes. Write tools refused in code.

02 · Understand

The agent reads your business. Homework first.

What you sell and how you charge — from your site, CRM products, billing plans and board decks.
How you're organized — from HR and Slack.
Why numbers move — from Slack channels, call notes and docs, each line cited back to its source.
Your vocabulary: the acronyms and metric names you actually use.
Where systems disagree, it keeps both numbers, picks one, says why, and flags it.

Try itClick any node. Then settle the ARR disagreement.

company-model.json · v7

412 people · FY Feb–Jan · close BD6

{
  "company": "Northwind Robotics", "version": 7,
  "business": { "model": "hardware + subscription (RaaS)", "fiscal_year": "Feb-Jan", "close": "BD6", "people": 412 },
  "sources": [
    { "id": "salesforce", "kind": "crm", "objects": 4, "fresh": "2m", "access": "read" },
    { "id": "stripe", "kind": "billing", "objects": 3, "fresh": "1m", "access": "read" },
    { "id": "snowflake", "kind": "warehouse", "tables": 38, "fresh": "12m", "access": "select" },
    { "id": "drive", "kind": "docs", "docs": 11238, "access": "read" },
    { "id": "slack", "kind": "chat", "channels": 214, "access": "read" }
  ],
  "products": [
    { "id": "raas_fleet", "pricing": "per_robot_month", "term_months": 36, "revenue_share": 0.81 },
    { "id": "pilot", "days": 90, "converts_to": "raas_fleet", "conversion": 0.62 },
    { "id": "parts_rma", "recurring": false, "in_arr": false }
  ],
  "departments": [
    { "id": "sales", "head": "dana.park", "headcount": 46, "approves": ["tab:sales"] },
    { "id": "customer_success", "head": "priya.nair", "headcount": 29, "approves": ["tab:customers"] },
    { "id": "field_ops", "head": "luis.ortega", "headcount": 118, "approves": ["tab:fleet_ops"] },
    { "id": "engineering", "head": "ken.ito", "headcount": 104, "approves": ["tab:engineering"] },
    { "id": "finance", "head": "sam.okafor", "headcount": 14, "approves": ["tab:finance", "fixed:*"] }
  ],
  "metrics": [
    { "id": "arr", "definition": "subscription_mrr * 12", "source": "stripe", "alt": ["salesforce"], "owner": "cfo", "flag": "disagreement" },
    { "id": "nrr", "definition": "ttm_rev(cohort) / rev(cohort, t-12)", "source": "stripe", "owner": "vp_cs" },
    { "id": "uptime", "definition": "avail_hours / contracted_hours", "excludes": "scheduled_maintenance", "source": "snowflake", "owner": "vp_field_ops", "north_star": true },
    { "id": "rma_rate", "definition": "rma_units_90d / deployed * 100", "source": "snowflake", "owner": "vp_eng" },
    { "id": "pipeline_coverage", "definition": "open_qualified / remaining_target", "pilot_weight": 0.4, "source": "salesforce", "owner": "vp_sales" }
  ],
  "glossary": { "RaaS": "robots-as-a-service", "RMA": "return for repair", "fleet": "all deployed robots", "pilot→rollout": "90-day pilot converting to fleet" },
  "disagreements": [
    { "metric": "arr", "salesforce": 48.6, "stripe": 48.2, "chosen": "stripe", "status": "open" }
  ]
}

Click any node. Every entity says what it is and where the agent learned it.

2 sources disagree

ARR

Δ $0.4M · 0.8%

Salesforce$48.6MClosed-won contracts, annualised. Leads billing by ~2 weeks.StripeAgent's pick$48.2MActive subscriptions × 12. What customers are actually invoiced.

Inspect evidence3 items explain $400K of $400K

+$310KHelix Logistics signed Sep 28; first invoice Oct 15. In Salesforce only.
+$62KCobalt Foods downgraded Sep 1; opportunity never updated.
+$28K2 EUR contracts booked at plan FX rate, billed at actual.

Both numbers are kept. The gap shows as a card on Home, never hidden.

03 · Build

Your command center, assembled. In a day, with your sign-off.

Finance is built from a fixed template your CFO will recognize.
Customers, Sales and People are shaped to how you run them.
Operations, Product and Engineering are invented for your business.
Every number has lineage: source, query, as-of time, owner. Click it.

Try itWatch four builders work in parallel. Click a tab for the planner's reasoning.

build · dashboard-spec v1

Planneridle

Builder 1idle

Builder 2idle

Builder 3idle

Builder 4idle

Checkeridle

Elapsed 0h 00mCards 0/49Waiting

04 · Talk

Change it by saying so. Questions answer instantly. Changes ask permission.

Ask anything from any tab — answered only from data you can already see.
Ask for a change and get a change request: diff, live preview, impact summary.
Routed to the right approver by domain. Widening access goes to the owner.
Every ship is a snapshot. Roll back in one click.

Try itPick a request. Diff, preview as any audience, approve, roll back.

Change requests · NorthwindSigned in as you · Editor

CR-152 · SalesTalk-time by rep → Sales · Leadership onlyPending approval

+3 −1 ~1 · dashboard-spec.json

1 {

2~ "version": 41 → 42,

3 "tabs": {

4 "sales": { "cards": [

5 { "id": "pipeline_by_stage" },

6 { "id": "win_rate_90d" },

7+ { "id": "talk_time_by_rep",

8+ "metric": "gong.talk_ratio", "group_by": "rep",

9+ "window": "30d", "audience": "leadership" }

10 ] },

11 "home": { "cards": [

12- { "id": "talk_time_by_rep", "audience": "company" },

13 { "id": "arr" },

14 …

05 · Live

It never goes stale. Refreshed, reconciled and checked before you're awake.

Agents refresh every source on schedule — daily by default, hourly where it matters.
Nothing reaches readers until checks pass: completeness, reconciliation, leak probes.
A morning brief in Slack or email: what changed, what needs you.
A watchlist that flags problems before your board does.

Try itHit Run now. Then try it with a leak.

Refresh · daily 05:40 · Northwind

Simulate a leak

1Pull23 sources
2Reconciledisagreements
3Check4 audience tiers
4Publishmove pointer

Salesforce

HubSpot

Gong

Stripe

NetSuite

Snowflake

BigQuery

Postgres

MySQL

Databricks

Redshift

Slack

Gmail

Drive

Notion

Confluence

Jira

Linear

GitHub

Zendesk

Intercom

Rippling

Fleet API

Checks

Completeness49 cards
Reconciliation3 rules
Leak probe · OwnerRestricted
Leak probe · LeadershipConfidential
Leak probe · ManagersInternal
Leak probe · CompanyCompany

Snapshots immutable

#318Today 05:5423 sources · 49 cardscurrent
#317Yesterday 05:5223 sources · 49 cards
#316Mon 05:5522 sources · 48 cards
#315Sun 05:5122 sources · 48 cards

05:54:02Snapshot #318 published · current → #318

07:30:00Morning brief sent to #leadership: 3 changes, 1 needs you

Under the hood

Agents do the work. The server keeps them honest.

Pick a flow and watch it move. Every box is a guarantee: hover or click it to see which one.

request data

Agents finish their work in a sandbox. The server verifies it, builds every audience tier and only then moves the pointer readers see.

Agents write a dashboard spec: tabs, cards, metrics, sources, audiences. Our renderer draws it. Consistent, beautiful, diffable.

Agents read text written by thousands of people. Their code runs without secrets or open network, connectors are read-only, and nothing ships without checks.

Every refresh is a new version. Publishing is moving a pointer. Rollback is moving it back.

Turn and cost limits stop a runaway agent before it becomes your problem.

Frontier models plan and build; fast models answer and classify. You get quality where it matters and sane costs everywhere else.

Five steps.
Zero SQL.

Good morning, Maya

ARR trend

Needs attention

Pipeline by stage

Headcount

What customers said

Plug in the whole company. Minutes, not a data project.

Allowed · read

Blocked · write verbs

The agent reads your business. Homework first.

ARR

Your command center, assembled. In a day, with your sign-off.

Change it by saying so. Questions answer instantly. Changes ask permission.

It never goes stale. Refreshed, reconciled and checked before you're awake.

Checks

Snapshots immutable

Agents do the work. The server keeps them honest.

Your command center.
By tomorrow morning.

Dashboards aren't dead.
Building them is.

Five steps.Zero SQL.

Plug in the whole company. Minutes, not a data project.

The agent reads your business. Homework first.

ARR

Your command center, assembled. In a day, with your sign-off.

Change it by saying so. Questions answer instantly. Changes ask permission.

It never goes stale. Refreshed, reconciled and checked before you're awake.

Checks

Snapshots immutable

Agents do the work. The server keeps them honest.

The server publishes. Not the agent.

Declarative, not generated spaghetti.

Prompt injection assumed.

Immutable data versions.

Budgets on every run.

The best models, routed.

Your command center.By tomorrow morning.

Five steps.
Zero SQL.

Your command center.
By tomorrow morning.