Discover public business candidates
Google Maps Lead Extractor takes a query and locality, then returns available business fields from the documented Places workflow.
Reference case study · no client data
Make local market research reviewable before it becomes outreach.
This is a reference implementation, not a customer success claim. It shows how a team can move from an authorized public search to a structured research brief, while keeping every source, limit and human decision visible.
Three bounded contracts
Use evidence in stages, not a black-box lead score.
The workflow combines three product surfaces. Each step has a separate purpose, an inspectable response shape and an explicit boundary.
Enrich an owned or public domain
B2B Domain Enricher organizes observable website and company context. It does not turn missing data into invented facts.
Summarize authorized feedback
Review Sentiment Analyzer groups supplied public or authorized feedback into themes for review, not a hidden purchasing decision.
Reference flow
A concise research pass with visible hand-offs.
Set the research boundary
Define a category, locality and authorized research purpose. Do not supply private records, credentials or restricted sources.
Run focused discovery
Use the maps contract to retrieve candidates. Keep the source context and discard fields that do not support the stated purpose.
Add public operating context
When a verified public or owned domain exists, enrich it with observable signals and preserve an unknown state where evidence is absent.
Review before any action
A person checks fit, source context and applicable outreach rules. The system produces a brief; it does not send messages automatically.
Illustrative output shape
What a human reviewer receives.
The sample below is a field model only. It does not represent a real business, customer, review or conversion result.
Discovery context
Category, locality, source identifier and observed availability.
Business profile
Name, public website when available, observable category and contact route.
Domain context
Public technology and company cues with unknown values preserved as unknown.
Feedback themes
Explicitly supplied feedback themes and supporting text references.
Reviewer decision
Qualified, needs research or do not contact — made by a person, not inferred by the API.
Audit boundary
Input authorization, query timestamp, product limits and any workflow warnings.
Guardrails
Useful only when every hand-off stays accountable.
Authorized inputs only
Use public sources or data you are authorized to process. Do not upload credentials or restricted datasets.
Visible contracts
Every workflow stage maps to a documented API request and response, so implementation teams can inspect the boundary.
Human review stays required
The output supports research. Prospect selection, outreach and compliance decisions remain with the operating team.