Users
Store ownership and account-level context.
A bring-your-own-key bridge for local business intelligence
Mapspector is a lightweight prospecting platform that connects your own provider keys to a structured lead workflow.
What the product does
Mapspector starts with a simple idea: you bring the provider account, Mapspector provides the app layer. It takes your keyword and location, runs the search through your saved provider key, normalizes the business records, and highlights which businesses are the best outreach targets.
The MVP now supports bring-your-own Apify keys. This makes Mapspector a bridge, not the data provider: key storage, search execution, result normalization, job history, and lead scoring live in one organized workflow.
Who it helps
- SEO and website agencies prospecting local businesses
- Outbound teams looking for warm-ish signals from public presence
- Operators building niche lead databases by city and category
- Anyone who wants repeatable, organized market searches without building the app layer around their provider account
Why the current architecture matters
The important MVP decision is separating provider access, search intent, and execution history. A provider key belongs to the user. A search is the saved keyword/location intent. A search job is the actual run through that provider.
Searches
Store the reusable query itself: what to search and where.
Search jobs
Store each run, its status, provider, and execution details.
Businesses
Store normalized business records that can be reused across searches.
Leads
Store search-specific opportunity outcomes and scores.
Exports later
Once this base is stable, exporting and scheduling become easier additions.