Research [vendor category] for [team or use]. My hard requirements are [list]; preferences are [list]; exclusions are [list]. Consider [named candidates or discovery scope]. For each candidate, verify the relevant claims on a specific source page and record the checked date. Drop any candidate that fails a hard requirement and explain why. Return at most [number] finalists with strengths, trade-offs, unresolved questions, and links. Do not contact vendors, create accounts, accept terms, or share our requirements without my approval.
Vendor research shortlist with evidence and gaps
Compare vendors against stated requirements, link each finding to its source, and return a shortlist with unresolved questions.
Copy-ready brief
Example output
Example shortlist for illustration only: Requirement: Data export in a documented format. Candidate A: Meets requirement according to [specific documentation URL], checked [date]. Trade-off: The documentation does not describe automated exports. Candidate B: Unknown. The public page says “portable data” but gives no format. Ask vendor to confirm before advancing. Candidate C: Dropped because the required region is not listed on its availability page. [Source URL] Next decision: Review A and B; no vendor has been contacted.
Trigger and cadence
- The reader supplies a category, requirements, and a decision deadline.
- One research pass followed by updates when requirements or sources change.
Inputs
- Required capabilities, exclusions, geography, and data needs.
- Candidate vendors or a defined discovery scope.
- Evaluation criteria and the date evidence should be checked.
Steps
- Convert the requirements into a comparison checklist.
- Find candidate vendors from the defined scope.
- Verify each claim on a source page and record its checked date.
- Drop candidates that fail a hard requirement, with reasons.
- Return a shortlist, trade-offs, and questions for a human to confirm.
Approval boundary
Contacting a vendor, starting a trial, or accepting terms waits for approval.
Stop conditions
- A hard requirement is ambiguous.
- A vendor claim has no usable source.
- The search would require sharing private requirements externally.
Expected output
A compact shortlist with evidence, exclusions, trade-offs, and next questions.
Receipt fields
- Requirements and sources checked.
- Candidate inclusion and exclusion reasons.
- Open questions and any approved outreach.
Recovery when it fails
- Mark unsupported cells unknown and revisit them when a source becomes available.
- Recheck the shortlist if a hard requirement or decision deadline changes.
On this page
Write requirements that eliminate candidates
A vendor research shortlist separates hard requirements from preferences before ranking anyone. Give OperatorNest testable requirements such as “exports CSV” or “available in our region,” plus the candidates or discovery scope and decision deadline. “Easy to use” needs a named task you can try.
For example, Sam needs an export format their team can read. Candidate A documents CSV but leaves automated exports open; Candidate B says “portable data” without naming a format. Advance A for the format requirement and hold B until its format is confirmed. The example output illustrates that decision.
Keep the condition beside the claim
Link the page that states the capability and record its checked date. A help article may limit a homepage promise to one plan or account type. Attribute third-party reports to their authors instead of presenting them as vendor commitments.
When a page cannot be reached, mark its affected claim unknown and keep the rest of the comparison. Record excluded candidates too: the source showing Candidate C lacks your region belongs in the receipt, so a later researcher can reconsider it if your requirements change.
Return the few candidates you can review
Give each finalist its relevant strength, trade-off and unresolved question. Two candidates and three open questions can be a better result than a forced top five. A missing answer to a hard requirement stays visible before you buy.
The research assistant use case covers broader investigation. This workflow ends at the shortlist; contacting vendors, creating accounts, accepting terms and sharing internal requirements are separate actions that wait for your approval.
If a requirement changes, rerun the filter against the recorded candidate set. Keep the original criteria and inclusion decisions in the receipt, alongside the new shortlist.
Run it on a schedule
Plan the timing and missed-run behavior with the recurring task planner. For documented schedule controls across assistants, read scheduled AI tasks compared.
Related tools
- AI model picker
Choose a model class for a founder task. Compare sourced model examples by context, input types, price tier and open weights.
- AI agent approval policy
Set clear approval rules for an AI agent. Choose systems and risk limits, then copy a policy that says what waits and what can run.
- AI task brief generator
Turn a rough request into a task brief with a goal, needed inputs, steps, approval points, receipt details, and a repeat schedule.
Common questions
How many vendors should appear on the final list?
Choose a number you can review, often three to five. Keep rejected candidates in the receipt with the reason they were removed.
Should an unsupported claim count as a failed requirement?
Mark it unknown. A candidate can remain under consideration, but the missing fact must be confirmed before a decision that depends on it.
Can the operator ask vendors for missing answers?
It can draft questions. Sending them or disclosing your requirements to a vendor waits for your approval.
Keep reading
- An AI research assistant that turns a question into a sourced briefIt researches a question or a standing topic and delivers a sourced brief, once or on a recurring schedule.
- A browser of its own, for real web tasksIts own browser to research, compare and fill in forms across the web, checking with you before it submits or pays.
- Approvals before anything that mattersIt asks before it sends, pays, books, deletes or posts. You approve, edit or hold from any channel.
- A receipt for everything your operator doesEvery task keeps a receipt: what was asked, what ran, which model did it, what it cost, and every approval.
Hand off your first task tonight.
Tell us your email and what you'd hand off first. We'll send your access details and help you set up your operator.