The result includes the person’s role, Software Tester, so users can validate the contact before outreach.
What was measured
Job information
Whether the enrichment output includes the prospect's role, title, or other job-related details.
context, not decisivetransformation
Role and title data improve targeting and personalization, but they are supporting details rather than the main outreach outcome. (2 of 3 judges)
What was given, what came back
Test input: Aditya Nichite prospect lookup · text · group: prospect-search
Input — what we sent
The exact prompt
Aditya Nichite
Direct people/prospect search for Aditya Nichite to test known-prospect retrieval and compare how well tools return validated contact records.
Output — unretouched
Hunter company email results for futuresmart.ai
Also checked on this input — same tool, 4 other criteria
Ability to locate email✓ WorkedA direct name-and-domain lookup can return a usable person email address; the search produced ajay.vekhande@futuresmart.ai for Ajay Vekhande.Ease of Use✗ FailedThe LinkedIn extension does not complete contact discovery in place; it replaces the profile view with a prompt to use Email Finder, adding an extra workflow step instead of returning a contact inline.People Search✗ FailedHunter can fail to validate a known prospect entirely when its data is thin; for this lookup it returned no email address and explicitly said it did not have enough data for tidio.com.People Search✓ WorkedHunter can resolve a known-prospect query into a contact record with validation context: one people search returned a contact record with additional details and confidence signals.
Provenance
- Observation
- 19d2fd29-93ee-4d81-af1b-c2f86265a0c2
- Evidence run
- 9e5960d0-1a72-4f29-9e1e-c7fc96120e61
- Study
- AI Outreach
- Research task
- 86ba3udqq
- Tested at
- Jun 15, 2026
- Source
- first-party
- Evidence state
- verified
- Proof shown
- input + output shown
- Cost / latency
- not captured
- Repeat run
- not captured
- Tester
- not captured
The last three rows are honest blanks, not placeholders — our capture has no field for them yet.
Query this
get_evidence({
tool: "hunter",
scenario: "prospect-search"
})MCP · mcp.aidemos.com/api/mcp
Free with attribution.
Same input, same check — 1 other tool
measured on Job information
This evidence is published in
Real inputs and real outputs, no retouching · every cell queryable via API & MCP · aidemos.com