01
No extraction path
Company search remains a gated target
DewEngine lists companies, search, search.perform, and company.get as target LinkedIn concepts, but none is implemented or approved. This route does not explain how to scrape search pages or bypass provider controls. A product should define the desired company-research outcome and keep an alternative input path while counsel and provider authorization decide whether any connector work may begin.
- Disable LinkedIn query controls until capability is proven
- Accept customer-entered or licensed organization data where appropriate
02
Query scope
Record filters, purpose, and acting account
A company result is meaningful only beside the account and search definition that observed it. Persist normalized filters, query version, customer purpose, run time, and intended destination. Unsupported filters should fail visibly rather than be dropped. Re-running a saved search creates new evidence; it does not rewrite the older candidate set or prove a stable ranking.
- Version saved searches and their eligibility
- Keep provider order separate from customer scoring
03
Organization identity
Match companies with more than a name
Rebrands, subsidiaries, franchises, and common names make string equality unsafe. Retain a provider-scoped identifier and compare customer-known domains, locations, parent relationships, and manual confirmation where lawful. The match should remain a proposal until sufficient evidence exists. An incorrect merge can contaminate territory, ownership, opportunities, and suppression across a CRM.
- Show evidence and conflicting fields in the review
- Support unlink, merge, split, and restore
04
Pagination
Persist partial results without calling them complete
An authorized adapter would need documented cursor, page size, ordering, and limit behavior for the exact product. Store each page transactionally, deduplicate by account-scoped company identity, and expose coverage. On throttling or interruption, resume from durable progress. An empty or missing page can reflect access or query state and must not delete staged or accepted companies automatically.
- Bind cursors to tenant, account, and query version
- Make cancellation preserve reviewed progress
05
CRM commit
Promote selected fields through a review boundary
Stage observations and show proposed new accounts, duplicates, and field conflicts. The CRM remains authoritative for owner, territory, lifecycle, consent, and notes. A user may accept a verified website or industry label without enrolling outreach. Commit idempotently and preserve the decision provenance so a later refresh can propose a change rather than silently replace customer truth.
- Separate company enrichment from campaign eligibility
- Record the source behind every accepted field
06
Qualification
Test matching and lifecycle, not harvested count
Release proof needs legal and provider approval, eligible product fixtures, filter fidelity, pagination, duplicates, subsidiaries, rebrands, partial runs, restriction, reconnect, tenant substitution, correction, retention, export, deletion, and query budgets. Support metrics use safe identifiers and never log copied page content. Until conformance exists, DewEngine cannot extract LinkedIn company-search data.
- Review false merges and rejected candidates
- Verify account disable stops scheduled searches