Stored context, made visible.
An action packet is built for a model, not a person. This page shows the other half: what stored context looks like when it's rendered for a human to read — and edit — directly.
The same context, three shapes.
FELLOW doesn't have one generic viewer. It renders each known record type into the form a person actually expects — an org chart, a journey, a profile — never a raw JSON blob.
Reporting lines assembled from graph-linked facts — "Jared works for Richard," "Richard reports to Gavin" — not a synced org-chart import.
Currently: pricing objection raised on last call, procurement now looped in. Stage advanced automatically when that objection was logged.
A buyer's stage isn't a picklist a rep sets by hand — it moves when the underlying evidence changes.
Erlich B.
Economic buyer · Champion
- Prefers monthly retainer over fixed-scope project[1]
- Skeptical of "vapor" — wants proof before commitment[2]
- Reports to a historically cost-sensitive buyer[3]
Every attribute is a cited assertion, not a free-text CRM note — click through to the source conversation.
What's shipping next.
Built in the open, in dependency order — each phase unlocks real usage, not a demo.
Multi-channel access
Query and update FELLOW from where work already happens — starting with Slack, using per-person keys so every request is tied to a real identity, not a shared token.
Auto-capture from conversation
A session with an agent or a colleague turns directly into knowledge — extracted, scored, and immediately usable, with review reserved for the cases that actually need a second look.
Visual interface
This page is the preview: the same read surface shown above, plus the ability to correct, add, or promote a record without leaving the view it was rendered in.
Structured document ingestion
Long, structured source documents — filings, contracts, policy manuals — decomposed into linked, queryable records, with the full source always one reference away.