Mapspector icon Mapspector BYO-key prospecting bridge
Bring your own provider key

Use your own data provider to find local businesses worth contacting.

Mapspector is the bridge between your own Apify or map-data provider account and a cleaner lead workflow. You bring the API key; Mapspector stores it encrypted, runs the search, normalizes the businesses, and scores outreach opportunities.

Searches Store reusable keyword + location search requests separately from execution jobs.
Jobs Track each run, retry, or provider attempt using dedicated search_jobs rows.
Leads Score businesses for outreach instead of leaving them as raw scraped rows.
Live provider mode

Run a quick prospecting scan

Start with a keyword and city. Mapspector uses your saved provider key, creates a search/job record, fetches live provider results, then stores scored leads.

Need to add a key first? Open Provider Keys and save your Apify token.

Preparing your search...
What Mapspector is for

Built for agencies, local SEO operators, and outbound teams

Most scraping workflows stop at “here are some businesses.” Mapspector acts as your BYO-key bridge: it runs searches through your provider account, stores each run cleanly, normalizes the results, and scores why each business may be worth outreach.

Lead generation teams

Prioritize likely buyers based on visible weaknesses in their local presence and website footprint.

Freelancers and agencies

Use your own provider account to build prospect lists for SEO, web design, reputation management, ads, or local optimization.

Internal operators

Map service categories, benchmark local markets, and build simple territory intelligence from one place.

Opportunity signals

What the scoring can look for

Missing website Low review count Poor ratings Weak reputation Category gaps Thin profile data

The current MVP uses live provider results with simple scoring. The architecture follows a clean progression: users → provider_keys → searches → search_jobs → businesses → leads.

Why the split matters

Separate the saved search from the execution run

Create a search

The search stores the business keyword, location, owner, and high-level status.

Create a job

Every execution of that search becomes a new job row, which is ideal for retries, provider changes, and historical runs.

Upsert businesses and score leads

Businesses remain reusable records, while leads capture why a business matters to a specific search/job.

How the MVP flow works

From input to usable lead list

1. Input

Enter a keyword and location, such as “dentist” in “Houston TX.”

2. Search record

The app stores the user’s requested market search as a reusable search entity.

3. Job execution

A dedicated search job is created to represent the actual provider run.

4. Lead output

The run produces businesses and lead rows that can be viewed, exported, or rescored later.

FAQ

Quick answers

Does Mapspector provide the data itself?

No. Mapspector is the bridge and workflow layer. You bring your own provider key, currently Apify, and Mapspector uses that key to run searches inside your account.

Who should use Mapspector?

It is best suited for anyone selling local services to businesses: SEO, websites, paid ads, lead generation, reputation management, and similar offers.

What makes it better than a raw scraper?

The goal is not just to collect businesses, but to organize the search lifecycle and explain opportunity. That means better follow-up and less manual cleanup.