observant
Get started

Let your product learn from its users — automatically.

Observant talks to each of your users one-on-one and keeps learning automatically — following up in the moment, relaying your team's questions live, so insight flows in while you ship.

Turn on learning mode
observant/Northwind Learning mode · On
On autopilot — Observant runs each 1:1 in turn, right where the user already is
  1. MMayain your product
  2. DDevinbrowser companion · soon
  3. SSofiaover email
In-app · Maya is at checkout
MObservant → Mayaprivate 1:1 · in your product
I noticed you started an order yesterday but didn't finish — what got in the way?
app.northwind.com◎
DObservant → Devinbrowser companion · soon
You've opened team settings 3× today — would a shared workspace change how you use this?
ReplyLater
‹Your workflow — a quick look?
O
Last week the CSV export felt clunky — did the new layout help?Tue
Better — but I still rebuild the header row by hand every time.Tue
O
The team would love to watch your workflow live — here's a link for a quick voice session.now
Northwind team · live 1:1 · 15 min
Join voice session →
24/7
always-on signal collection — no need to launch ad-hoc studies
∞
users on their own private 1:1 line, all at once
1st
to know — fully integrated with your product data, the why arrives before you ask

Loop One

Dispatch your questions

Dispatch a line of inquiry from your dashboard. The agent takes it from there — deciding how deep to go, reaching the right people through your feedback program or inside your product, and returning with the answer, ready to act on.

Loop Two

The in-product agent

One code snippet gives the agent a reserved space inside your product, within guardrails you control. There it holds feedback sessions with the right users at the right moments — and quietly grows your standing feedback program as it goes.

MCP

Ready for your agentic workflow.

Observant installs as an MCP server over HTTP — right inside Claude Code, Cursor, or Claude Desktop, for teams who ship in the editor. User learning runs on autopilot and shows up where you build: surfaced in the flow, agent-ready.

Add Observant to your stack
claude code — ~/northwind observant · mcp
›why are power users dropping the new export flow? ⏺ observant  pulling from your panel… ↳ triggered by PostHog · 22% drop-off on export_v2 · cohort: Power users ↳ 18 recent 1:1s matched · synthesizing
Insight · agent-ready
61% rebuild the export by hand to get a shareable view. The CSV-first flow is the friction — not the export itself.
→ recommend: ship a live, shareable dashboard; keep CSV as secondary
3 supporting quotes · draft spec attached
›draft the implementation plan

No dashboard, no context-switch — the insight arrives where you're already building.

FAQ

Those wait for you to ask — and for users to answer a form. Observant actively listens: it knows what your team cares about, figures out what it needs to learn, and goes and finds out through real 1:1 conversations. No studies to launch, no surveys to write.
No. Observant comes with ready-to-go autopilot programs — product sentiment, user journey health, always-on product discovery — that run on their own and deliver on a rhythm. When you do have a specific question, drop it in your own words; Observant figures out who to ask and how, and comes back with the answer.
On each user's own private line — inside your product, over email or Telegram.
Genuinely 1:1. Each user has a private line and a relationship that builds over time — Observant remembers every conversation, so nobody's ever asked to start from the beginning. It runs hundreds of these in parallel.