Build the domain pool
Run resumable search jobs across configured free, imported and optional premium sources, then normalise and deduplicate every result.
SELF-HOSTED PROSPECT DISCOVERY & SMART OUTREACH
NextlerAI Outreach
Free-first discovery, qualification and multi-provider outreach—inside WordPressBuild a qualified prospect pipeline without surrendering control.
Discover the right companies. Fill only the missing data. Reach people through the sender connections you control. NextlerAI Outreach is being built as a self-hosted WordPress control plane for prospect discovery, enrichment, qualification, campaigns and responsible multi-provider delivery.
No NextlerAI SaaS dependency is planned for the core workflow. Your server, provider accounts, sender connections, budgets and approval rules stay under your control.
FREE-FIRSTUse existing and free data before billable providers.CRAWL ONLY IF NEEDEDCheck field sufficiency before visiting a website.SCALE YOUR WAYStart locally and add remote workers later.
- Search jobs with required fields and technology filters
- Freshness, provenance and deterministic deduplication
- Targeted crawling with early stopping
- Campaigns, sender pools, suppression and health controls
THE OUTREACH OPERATING ROAD
WORDPRESS IS THE CONTROL PLANEConfigure the search, data rules, budgets, workers and sender connections in one place.
Self-hosted coreYour provider keysYour sender accountsOptional AIHard budgets
From target market
to qualified conversation.
Outreach is designed as a complete pipeline—not a scraper attached to an email form. Every stage hands structured, auditable work to the next one.
Resolve only what is missing
Check freshness and confidence first. Crawl, enrich or use AI only when a required field still needs work.
Prepare relevant outreach
Turn qualified companies and contacts into lists, sequences and personalised messages with review controls.
Route, observe and protect
Send through compatible healthy accounts, process replies and bounces, and update suppression, prospect and sender state.
GOVERNING RULEExisting data → free data → local computation → optional premium APIs → optional AI
THE DATA SUFFICIENCY GATE
Do not crawl because
a domain exists.
Before any live request, Outreach is designed to ask which fields the Search Job requires, what is already present, whether it is fresh enough and whether confidence meets the configured threshold.
01 / PLAN THE CHEAPEST VALID PATH
Requirements create the work—not the other way around.
If the required company, website, email, location and technology data already meet freshness and confidence rules, the live crawl is skipped. If only an email is missing, the crawler visits only likely pages and stops when the requirement is satisfied.
The required field exists on the canonical company or contact record.
The field remains inside its independently configured freshness window.
Source evidence meets the Search Job threshold.
Skip unnecessary crawl, enrichment and AI calls.
EFFICIENCY YOU CAN MEASURE
Less waste is
a product capability.
The planned reporting layer makes avoided work visible instead of hiding efficiency inside a black box.
Crawler avoidance
Track discovered domains, sites that actually required a live crawl, domains skipped because data was sufficient, pages avoided, bandwidth avoided and estimated processing time saved.
Domains discoveredLive crawl requiredCrawl skippedRequests avoided
Missing-field enrichment
Purchase only fields the Search Job still requires. Known and fresh values are not bought again.
Hard cost controls
Separate provider, Search Job, campaign and AI budgets stop billable work before the limit is crossed.
Source provenance
Keep where a value came from, when it was found, confidence and verification state.
Conflict preservation
Conflicting source values are retained and resolved deliberately—not silently overwritten.
START LOCAL. SCALE WITHOUT A REWRITE.
One control plane.
Three operating modes.
The same queue and worker contracts are planned for a normal WordPress server, a separate worker VPS or a distributed worker fleet.
02 / WORKER INFRASTRUCTURE
Move heavy work away from WordPress when the operation grows.
Capability-aware workers claim tasks atomically, report heartbeats and health, recover abandoned work and keep Search Jobs independent of where processing runs.
Use the WordPress server
Configure workers, global and per-domain concurrency, request rates, memory thresholds and resource profiles.
Separate heavy processing
Connect a secured worker with its own secret, capabilities, concurrency and heartbeat—without WordPress administrator credentials.
Add compatible capacity
Run multiple specialised workers against the same resumable queue contracts with no artificial worker-count limit.
QUALIFIED DATA BECOMES CONTROLLED OUTREACH
Campaigns, senders and health.
Designed as one system.
Campaign quality, individual sender health and provider capability are separate signals. Routing should protect the whole operation—not simply try the next account.
03 / CAMPAIGN ORCHESTRATION
Route the right message through a compatible, healthy connection.
Build audiences from qualified prospects, render tracked message objects once, enforce idempotency and quotas, and run the final suppression check immediately before delivery.
PLANNED PRODUCT CAPABILITIES
A complete outreach operation.
Modular by design.
The product is being built in independent modules so providers, workers and sending transports can evolve without rewriting the core engines.
Search Jobs & discovery planning
Countries, regions, industries, technologies, mandatory contact fields, nested AND/OR/NOT requirements, schedules, targets and source modes.
Free sources onlyFree first + premiumSelected sourcesContinuous search
Domain pool & deduplication
Canonical URLs, one domain entity, multiple sources and resumable search slices.
Smart crawler
SSRF protection, robots handling, sitemaps, adaptive per-domain limits and early stopping.
Technology detection
Registry-based signatures for CMS, ecommerce platforms and known chat technologies.
Prospect database
Companies, contacts, lists, tags, provenance, confidence, freshness and export.
Multi-provider sending
Unlimited-connection architecture for custom SMTP, sender pools and planned Google, Microsoft and email-provider adapters.
RoutingQuotasIdempotencySender healthCampaign health
Events & suppression
Bounces, replies, unsubscribe, company cooldowns and final pre-send suppression checks.
Reports & audit
Cost, throughput, crawler efficiency, source performance, sender state and critical automatic actions.
SELF-HOSTED FIRST
Your infrastructure.
Your operating choices.
The purchased core is planned to remain useful without a NextlerAI-controlled service. Optional managed capacity may be added later without becoming a requirement.
The accounts and infrastructure you choose
- WordPress and its database
- Your discovery and enrichment accounts
- Your SMTP and mailbox connections
- Your optional AI-provider key
- Your budgets, policies and approval rules
The control plane and orchestration
- Search, queue and worker contracts
- Data sufficiency and freshness logic
- Prospect and campaign state
- Routing, health and suppression engines
- Diagnostics, logs and audit history
PLANNED TECHNICAL FOUNDATION
Built for a real prospect operation.
- Platform
- Self-hosted WordPress
- Core mode
- Local Mode without NextlerAI SaaS
- Processing
- Queue-based, resumable background work
- Scale path
- Local, remote and distributed workers
- Discovery priority
- Existing → free → local → premium → AI
- Core free sources
- Common Crawl, Overpass, imports and open-data adapters
- Data model
- Companies, contacts, fields, provenance and freshness
- AI
- Optional and budget-controlled
- Sending
- Transport registry, sender pools and provider-aware routing
- Safety
- Suppression, idempotency, quotas and health separation
- Security
- Encrypted secrets, capabilities, nonces, SSRF and audit controls
- Status
- In production · pricing not yet published
THE BUILD SEQUENCE
Eight controlled phases.
One release architecture.
Foundation comes before scale; discovery before campaigns; delivery before production polish.
- 01Foundation & core infrastructure
- 02Free discovery & domain engine
- 03Smart crawler, extraction & technology
- 04Prospects, enrichment & optional AI
- 05Remote & distributed workers
- 06Campaigns & sending core
- 07Provider adapters
- 08Events, replies & production polish
QUESTIONS, ANSWERED
Before Outreach is released.
Can I buy NextlerAI Outreach now?+
Not yet. The product is in production and pricing has not been published. This page will switch to licence plans when purchasable plans are configured.
Will the plugin require a NextlerAI SaaS subscription?+
The core product is planned to work self-hosted on WordPress with your own infrastructure and provider accounts. Future managed services may remain optional.
Are premium lead databases required?+
No. The discovery architecture is free-first and includes planned Common Crawl, Overpass, public-data and import paths. Premium providers are optional adapters.
Does every discovered website get crawled?+
No. The Data Sufficiency Evaluator is a non-negotiable design rule: live crawling runs only when required data is missing, stale or below confidence.
Is AI required?+
No. Deterministic logic remains the default. AI is planned as an optional, budget-controlled qualification or message-assistance stage and must not invent contact data.
Can the system scale beyond one WordPress server?+
Yes. Local, remote and distributed modes are planned around the same queue and worker contracts so processing capacity can move without redesigning the core.
NEXTLERAI OUTREACH · IN PRODUCTION
Build a smarter path from discovery to conversation.
Pricing and purchase options will appear here when the first commercial release is ready.
