Prospector

Prospector started from one observation: the hardest part of selling websites is not building them, it is finding the businesses that need one and keeping track of the conversation. So the product does all three, search, pipeline and build, in one place.

Leads arrive from three scraper providers and are geocoded onto a map. Gold pins mean no website, green means they already have one. That single distinction is the whole product thesis, and every other feature exists to act on it.

The CRM side covers statuses, call logging and a note timeline, feeding a pipeline board. The builder side turns a won lead into a real site from one of three templates, pulling brand colours from whatever the business already has, and publishes it to the customer's own Vercel or Netlify account rather than to mine.

• 01Multi-tenant from the start: users, organisations and roles, rather than a single-user tool retrofitted later.
• 02Bring-your-own-key credential vault, AES-256-GCM encrypted, so customers use their own provider accounts.
• 03Map queries are clustered by viewport, because a national search returns more pins than a browser will draw.
• 04Billing and team invites are deliberately unfinished: the schema supports both, nothing charges yet.