Turn professional search into reviewable product value

A product guide for designing search around user decisions, explainable filters, saved work, and safe handoffs while the LinkedIn connector decision remains closed.

Educational research only. LinkedIn account access remains decision-gated. No DewEngine LinkedIn connector is approved or implemented.

Talk to us ↗Read technical guides →

Value definition

Measure decisions completed, not queries issued

Search creates value when a user can find a plausible company, candidate, or professional context and make a better documented decision. Query volume and result count can reward noise. Define the downstream task, such as assigning a research candidate, resolving a duplicate, or adding context to a requisition. LinkedIn search itself remains a decision-gated DewEngine target with no approved connector.

Track reviewed and resolved candidates
Avoid metrics that encourage indiscriminate collection

Search experience

Make filters understandable and recoverable

Users should see the active filters, their source, and which are supported for the connected product. Save a versioned search definition rather than an opaque URL or session fragment. If an entitlement cannot express a filter, explain the limitation instead of approximating silently. A shared saved search also needs tenant ownership and role checks before another user can run it.

Name filters in customer language and retain exact values
Validate saved searches again after reconnect or product change

Result workspace

Support triage without forced import

A result list should allow dismiss, annotate, assign, compare, and confirm before creating a CRM or ATS entity. Preserve the observation time and query that produced each candidate. An analyst may reject a company because it is a subsidiary already covered elsewhere; that decision is useful product state even though no provider data is written and no outreach begins.

Keep rejected candidates from reappearing without explanation
Let users compare source evidence with existing customer records

Collaboration

Coordinate ownership inside the customer system

Two users may review the same professional result under different connected accounts and purposes. The customer workspace should control assignment, notes, duplicate resolution, and visibility. Provider-scoped identity helps associate observations, but it must not leak one account's search context to another. Use optimistic concurrency or review locks where simultaneous decisions could create duplicate contacts.

Keep account visibility and workspace authorization distinct
Record who accepted or dismissed each candidate

Action separation

Do not turn a search click into outreach permission

Saving a result may create a research item; it should not send an invitation, draft a deceptive message, or enroll a sequence. Provider-visible actions require a separate capability, current account health, recipient context, suppression, customer purpose, and explicit approval. This separation lets search improve a workflow even when messaging is prohibited or intentionally excluded.

Use distinct permissions for research and action
Re-evaluate recipient eligibility at the moment of any approved command

Release review

Validate user value within the authorization envelope

A responsible pilot would test approved account eligibility, query fidelity, partial and reordered results, collaboration conflicts, duplicate matching, accessibility, retention, deletion, account loss, budgets, and support diagnostics. Qualified counsel and provider authorization remain mandatory. If those gates do not clear, keep the review workspace and connect it to customer-entered or licensed data rather than weakening the boundary.

Run usability tests with deliberately ambiguous candidates
Prove the workflow degrades cleanly when search access disappears

Questions

Before you build.

What is a better KPI than LinkedIn searches per user?+

Measure completed research decisions, correctly resolved duplicates, time saved in review, and reversal rates. These indicators reflect product value and data quality without encouraging users to collect more records than their purpose needs.

Can a saved search be shared across every connected account?+

Only after validating workspace permission and that the exact filters are authorized and supported for each account's product entitlement. Results and visibility may be account-scoped, so reuse cannot be assumed.

Build with us

Does this match the workflow your users need?

DewEngine is in development. Real use cases decide what ships first.

Share your use case ↗