Ten warehouse vendors compared on pricing, deployment and customers, written into your workspace as rows with a source link each. It arrives as a diff you approve.
The competitor analysis that never left the browser tabs. The meeting whose decisions live only in memory. The vendor database that was accurate the week it was made.
A companion creates pages, builds and queries databases, inserts and updates rows and appends content. It does the research across the open web and your logged-in accounts first, so what lands in the workspace is structured the way your team already works. You review every write.
01
How does web research arrive as a Notion database?
You name the destination in the same sentence as the question.
Ask for “a comparison of the top ten warehouse management vendors on pricing, deployment model and notable customers, as a Notion database” and that is what shows up.
This is research and data extraction with the last mile included, the evening somebody used to spend reformatting findings into the team’s format.
The database is created with properties that match the question rather than a generic Name and Tags.
Ten rows, each carrying the source link it came from, so a wrong number is traceable in one click.
The three vendors whose pricing page says “contact us” arrive flagged rather than guessed at.
The whole thing lands as a diff you approve, so a bad run costs you a rejection instead of a cleanup.
02
Meetings and inboxes, filed where the team looks
Strawberry preps and transcribes meetings, and a companion reads your email through the native Gmail and Outlook integrations. Point that at Notion: call notes become pages in the right section, decisions get appended to the project doc, action items land as rows in the tasks database.
Each write is staged for your OK. The workspace stays current because filing stopped depending on somebody’s discipline at 18:30 on a Friday.
03
Can a tracker update itself?
The competitor tracker, the candidate pipeline, the press list: accurate the week they were made. A companion on a schedule re-visits each row’s subject on the web, updates what changed, and flags what needs a human decision.
That is a standing routine instead of a quarterly cleanup, and because updates arrive as diffs you can review, the tracker gets something most wikis never have. You can trust its timestamps.
04
What a plugin inside Notion cannot do
Tools that live inside Notion rearrange what is already there.
The valuable material is upstream: on the open web, in your inbox, in the tabs where information appears first.
A companion works at that source, signed in as you, and delivers into Notion natively. No exporter scripts, no API tokens to manage, no copy-paste shuttle.
Yes. Notion is a native integration, and a companion creates pages, builds databases, inserts and updates rows and appends content. Writes are staged for your review, so the workspace changes only in ways you approved.
Describe the research and name Notion as the destination. A companion works the open web, structures what it finds, and writes it in as a database or page with sources attached.
A scheduled routine re-checks each row’s subject on the live web and stages updates for what changed, so a decaying tracker keeps timestamps you can trust.
A companion stages its writes for approval rather than editing silently. Chats and credentials stay local on your own device, and chats are not saved on Strawberry’s servers.
Yes. Strawberry preps and transcribes meetings, and a companion files the outcome into Notion: notes as a page, decisions appended to the project doc, action items as database rows, each staged for your sign-off.
Notion Strawberry