Features
The whole research loop, one field kit
Three chapters — record, tag, report. Each one removes a place where insight used to leak.
Chapter 1 — Record
Capture the conversation, not a summary of it
A notetaker that joins on time
Connect your calendar and Fieldnote joins Zoom, Meet, or Teams calls you invite it to — with participant consent requested up front, in the regions and languages your participants actually live in.
Today, 11:00 — Onboarding review, Bramble
Google Meet · joining in 12 min
Consent confirmed — 3 of 3 participants
Two-party rules applied (California)
Recording notice pinned in call chat
Bring the archive you already have
Upload audio and video, sync a Drive or Dropbox folder, or paste transcripts from other tools. Old research becomes searchable evidence instead of a folder you apologize for.
Importing — Q1 discovery archive
- zoom_recordings/18 files · transcribing
- usability-may.mp452:10 · done
- notes-pilot.docxtext import · done
Step 1
Invite
Add Fieldnote to the calendar event, or drop files in later.
Step 2
Record
Consent is requested, the call is captured, speakers separated.
Step 3
Library
The transcript lands tagged, searchable, and quotable in minutes.
Chapter 2 — Tag
Themes you approve, not themes that happen to you
Suggestions that show their reasoning
Fieldnote proposes themes and shows exactly why each quote matched — the phrase, the sentiment, the pattern across calls. You accept, refine, or reject. Nothing publishes itself.
Suggested theme — “Permissions anxiety”
Matched 17 quotes across 9 interviews
“I didn't want to touch permissions until someone told me I couldn't break anything.”
why: fear + settings context · 0:41
Search that answers questions
Query the whole library in plain language — "what do enterprise admins say about SSO setup?" — and get quotes with timestamps, filterable by segment, date, and study.
what do admins say about SSO setup?
“SSO took us three tickets and a prayer.”
IT admin, enterprise · Mar
“Once SSO worked, rollout was a day.”
Ops lead, mid-market · Apr
Interview — Nora P., Research Ops at Coastline HQ
Transcribed · 24:13 · 2 speakers
04:12Nora: Honestly, we do the interviews and then the insights just… evaporate.
04:31Nora: Notes end up in one doc, recordings in another tool, and the deck is written from memory.
05:02Interviewer: When someone challenges a finding, what happens?
05:09Nora: We dig for the quote. Sometimes for an hour. Usually we give up and soften the claim.
05:40Nora: A report that used to take me a week should really be an afternoon.
Chapter 3 — Report
Findings with the receipts attached
Every claim carries its clip
Reports are built from evidence blocks: a claim, its quotes, and playable moments from the calls. Stakeholders click a sentence and hear the customer say it — belief follows.
Finding 03 — Setup fear stalls admins
New admins avoid the permissions step for a median of 6 days.
Reports that refuse to go stale
Published reports watch for new matching evidence and flag themselves when the picture changes. Synced copies in Notion and Confluence update with one click.
Why admins stall in week one
Synced to Notion · last updated 3 days ago
Q3 onboarding study
Living report · synced to Notion · current
Finding 01
Admins fear the permissions step
“I didn't want to touch permissions until someone told me I couldn't break anything.”
02:41 · admin, mid-market
Finding 02
Setup guides go unread; examples get copied
“Honestly I just cloned the sample workspace and renamed things.”
07:19 · founder, startup