Saved-research collections

Today’s research lives in a flat list — searches in history, items in watchlist, sessions in chat. Collections lets you group these into named projects that you can share with teammates, comment on, and track over time.

What this will let you do

Create a collection

A collection is a named project — “Q4 2026 launch shortlist”, “Pet-care category exploration”, “Replacement for slowing SKU XYZ”. It contains:

• A list of searches (added from history).
• A list of watchlist items.
• A list of chat sessions related to the project.
• A free-text description.
• Members who have access.
• A discussion thread.

Share with teammates

Invite teammates from your Hilal Software organization to a collection. Permissions:

• Owner — full control; can rename, delete, change permissions.
• Editor — can add / remove items, comment.
• Viewer — read-only, can comment.

When you invite a teammate, they see the collection in their own Product Research view immediately.

Comment in-line

On any item in a collection (a search, a watchlist row, a chat session), drop a threaded comment.

Examples:

• On a search: “This is the shortlist we’re presenting Tuesday.”
• On a watchlist row: “Sample arrived; quality check passed; let’s order 500 units.”
• On a chat session: “Worth re-running this with tighter margin.”

Comments support @mentions to ping a teammate; they get a notification.

Compare collections

Collections you own can be compared side by side — useful for “option A vs option B” analysis where two collections represent two strategy directions.

How it’ll work (preview)

Each collection is its own surface:

Collections
├── Q4 2026 launch shortlist (Owner: you, 3 members)
│   ├── 5 searches
│   ├── 12 watchlist items
│   ├── 2 chat sessions
│   └── 23 comments
├── Pet-care exploration (Owner: Alice, you=Editor)
│   └── ...
└── + Create new collection

Most actions stay where they are today (you still create searches and add to watchlist normally). Adding to a collection is the organizational layer on top — analogous to how Slack channels organize messages without changing how messages are sent.

Why this matters

Real seller decisions are conversations, not solo work. The founder shortlists products; the ops lead vets supplier feasibility; the partner does the financial modeling. Today, that conversation happens outside Hilal — in Slack, in email, in shared Google Docs that get out of sync with the actual research.

Collections moves the conversation onto the data. Comments stay attached to the artifact (the specific search, the specific product) and don’t drift apart from it.

Common patterns

The shortlist

Create a collection per launch cycle. Add candidates from searches and watchlist as you find them. Discuss in comments. When the cycle is done, archive the collection — it stays as a record of how the decision was made.

The category exploration

A long-running collection per category you’re scouting. Searches accumulate; comments evolve over months. When a category becomes a real launch, spin off a new shortlist collection from this one.

The post-mortem

After a launch (or after deciding not to launch), capture the collection’s history as a post-mortem document. “We considered these 30 products, shortlisted 5, launched 1, here’s what we’d do differently.”

Status

• Concept design: in progress.
• Collaboration model: depends on Hilal Software’s organization model (already in place).
• Sharing UI: Run 4 frontend.
• Beta: post-Run-4.

Related articles