LeadScoutEngine — Documentation

Account, organization and project

Start at app.markengroup.cloud/register. Enter only your email address and confirm the email link before choosing a password. Then add your name and create an organization; logo and company website are optional.

A person has one account and can belong to several organizations. Create or select a project in the intended organization before using a product. Team invitations are email-bound, expire after seven days and are currently shared as links, not sent automatically by email.

Access and credentials

The dashboard uses Firebase Authentication. Server operations require a verified email address, active membership and the relevant project/product permission. Reading a project does not automatically grant editing rights.

Use the dashboard for the setup operations described here. Firebase callable functions are internal dashboard interfaces, not a released public REST API. Never embed AWS credentials, server tokens or private keys in websites, browser bundles or public examples.

Monthly plans and shared prepaid USD balance: local preview

The local billing implementation supports monthly included usage and one prepaid USD balance shared by an organization across TrackMailer, TrackAny.Click and TrackPost. Assigned balance does not unlock unavailable product features: TrackPost remains Coming Soon. Additional usage is sold in whole-cent packages, requires explicit acceptance and sufficient balance, and cannot create a negative balance.

Paid plans, balance top-ups and package prices are configurable drafts until explicitly published. Bold payment activation and production acceptance remain outstanding. The local default of 1,000 tracking events per organization and UTC calendar month is configurable, not a published free plan. Own TrackMailer sender domains require separate approval or an active subscription; USD balance alone does not grant that access.

Projects

A project contains its goal, ICP, market, sources, filters, leads, scoring, enrichments, team, exports, integrations, credit usage and outcomes.

ICP Builder

Describe the target in natural language, then review the generated criteria before discovery. Criteria remain editable and versionable.

Discovery

Discovery runs as a queued job and can report running, partial, completed, failed or cancelled. Searches do not consume credits.

Filters

Filter previews by market, categories, score, freshness and available intelligence without unlocking data.

Lead Scoring

Every score includes matched and failed criteria. The interface shows why a company received its score.

Enrichment

Unlock only the intelligence needed. Data fields retain source, retrievedAt, verifiedAt and confidence where available.

Credits

The ledger is the source of truth. Successful unlocks consume configurable integer credits; duplicate workspace unlocks do not charge twice.

Exports

CSV export requires project permission and contains only data already unlocked for the organization.

API

The app uses authenticated Firebase callables. A public Standard API contract must be explicitly released before external use.

Webhooks

Outbound webhook delivery is part of the prepared integration model, not an active customer endpoint yet.

TrackMailer

TrackMailer remains separately entitled and can be added as a project tool after the first project exists.

TrackAny.Click

TrackAny.Click remains the separately entitled attribution layer; shared project IDs do not grant data access.

TrackPost

TrackPost remains a separate social-publishing product and is less prominent in the LeadScoutEngine workflow.

Integrations

Every cross-product integration requires its own entitlement and permission checks.

Security

Verified identity, active membership, project entitlement and action permission are checked server-side. Provider credentials never enter browser bundles.

Enterprise

Enterprise configuration can override seats, platform fee, credit pricing, sources, scoring, limits, retention, integrations and SLA.