How LeadForge works

LeadForge is built primarily for agencies, consultants, growth teams, and sales teams that prospect businesses and need more than a disposable lead list.

The product connects territory discovery, lead management, business research, AI-assisted work, sales artifacts, outreach, team collaboration, and pipeline activity around the same business opportunities.

The simplest description is: LeadForge helps an agency move from market discovery to sales execution inside one connected workspace.

LeadForge is organized around an operating workflow rather than a single search box. Discovery creates markets worth working; Territories preserve that work; businesses move into the lead pipeline; intelligence and workspace context help determine the next action; and the resulting sales work stays connected to the business.

The product is designed so research does not end as a score or another list of leads. The goal is to turn what the workspace knows into what happens next.

LeadForge treats a business as a continuing workspace object rather than a disconnected record on each page.

What the team learns through discovery, research, notes, pipeline activity, follow-ups, conversations, meetings, tasks, Copilot, pitch work, and outreach can remain connected to that business context.

This shared context is the idea behind One Business Memory: the workspace should not have to relearn the same business every time work moves to another LeadForge surface.

The strongest fit is an agency, consultant, growth team, or sales team that repeatedly prospects business markets and needs to coordinate discovery, research, outreach, and pipeline work around those opportunities.

Examples include web and design agencies, SEO agencies, paid advertising agencies, local marketing providers, consultants, outbound sales teams, and other service businesses selling to businesses.

LeadForge includes smaller solo plans as well as team plans for larger shared operations.

LeadForge combines several familiar categories around one agency sales workflow, but it is not intended to be only one of them.

If someone asks what LeadForge does: LeadForge is a territory discovery and sales intelligence platform for agencies. It helps teams discover businesses, build persistent sales Territories, research and work opportunities, manage leads and pipeline, collaborate, create outreach and sales assets, and use an AI Copilot that works from the context of the LeadForge workspace.

If someone asks how it differs from a lead database: LeadForge is designed around what happens after a business is found. Discovery becomes a persistent Territory, useful businesses enter the working pipeline, Lead Intelligence researches them, Copilot and Business Partner Tasks help determine and execute next actions, and team conversations, outreach, artifacts, and pipeline activity remain connected to the same business context.

Discovery is the entry point for finding businesses and markets worth working. LeadForge supports four discovery modes with different purposes and usage rules.

Discovery mode finds qualifying new businesses outside the LeadForge index. LeadForge mode searches businesses already known to the LeadForge index and does not consume Discoveries. Targeted mode looks for a named business or chain; rejected or non-returned candidates do not consume Discoveries. Copilot Discovery requires a lead target and a maximum Discovery allowance. It checks eligible fresh directory businesses the user has not previously discovered first, then uses external searches to fill remaining slots within the allowance. Directory results and IDs-only lookups use no Discoveries. Each successful paid Google business-detail lookup uses one Discovery, including businesses that do not match. Failed detail lookups do not consume customer Discoveries. A search can consume Discoveries without returning matches. AI usage may apply separately. Hard requirements remain enforced, and broader searches without a location or industry require confirmation.

Fresh LeadForge directory results use no Discoveries; paid external refresh or discovery work in Copilot Search follows the selected allowance. Discovery work persists so users can return to prior searches and build continuing Territory context instead of treating each search as disposable.

Discovery can use business details such as name, location, website presence, ratings and reviews, public contact information, LeadForge scoring, and opportunity signals to organize results.

Territories are persistent markets built from Discovery activity. They let a user or authorized team return to a geography-and-industry market, see prior progress, and continue working remaining opportunities.

A Territory can connect discovered businesses, remaining opportunities, unlocked or worked businesses, activity, progress, and territory-level intelligence.

Territories support Personal and authorized Workspace visibility. Shared visibility does not mean every teammate automatically receives edit authority over every underlying object.

When a discovered business becomes something the user wants to actively work, it enters the lead workflow. Vault is the working lead area rather than a second search-results page.

Lead records can carry business and contact information, website and social/contact paths, pipeline state, notes, activity, follow-up dates, revenue or deal information, Lead Intelligence, Pitch Decks, and other related workspace artifacts.

Lead unlocking is a workflow transition into the working lead system; it is not a separately paid usage unit. Paid usage is centered on plan capacity such as Discovery and AI-assisted usage, plus plan capabilities and seats.

Lead Intelligence researches an individual business and turns public business information and website signals into a structured sales brief.

The research workflow can crawl the business website, process available sources, build intelligence, and preserve the resulting business context on the lead.

Lead Intelligence is intended to answer a practical sales question: what should I understand about this business before I approach it? Findings can include useful facts, opportunity signals, business weaknesses or gaps, sales angles, and source-backed context.

Lead Intelligence can also be exported as a PDF sales brief.

Daily Actions is the operational prioritization layer. Its purpose is to surface work that deserves attention instead of requiring a user to manually inspect every part of LeadForge.

As the workspace accumulates enough territory, lead, task, and pipeline activity, Daily Actions can organize the next work around those signals.

The core idea is simple: LeadForge should not only store information; it should help turn information into today's work.

LeadForge Copilot is the AI assistant integrated into the product. It is designed to work from LeadForge context rather than behave like a blank general-purpose chatbot.

Depending on the page, permissions, and selected scope, Copilot can work from context such as the current surface, lead, Territory, visible workspace objects, pipeline state, Lead Intelligence, Task Results, conversations, and other LeadForge workspace state.

LeadForge resolves application context, permissions, entities, and workflow state before the final model response where those details are relevant. The value is therefore the connection between the model and the operating system around it, not merely access to a language model.

Business Partner Tasks are bounded pieces of operational work LeadForge can perform against workspace data. They are separate from simply chatting with Copilot.

Tasks can work on supported areas such as lead queues, territory analysis, opportunity shortlists, next-best actions, follow-up planning, outreach drafts, client-ready reports, territory attack plans, territory expansion, and pipeline maintenance.

Completed work becomes a Task Result. Task Results are persistent records that can preserve summaries, explanations, structured artifacts, warnings, target scope, completion state, and recurring-task context.

Personal and authorized Workspace scope control which results can be read. Shared read visibility is separate from mutation authority.

Pitch Decks turn LeadForge business context into client-facing or prospect-facing sales material.

They connect research and business understanding to a presentable output that remains associated with the lead and can be viewed or exported from LeadForge.

Authorized Workspace scope can support shared reading while ownership rules continue to govern modification.

Email Campaigns is LeadForge's outbound email workflow for leads already inside the workspace. A campaign can involve one lead or multiple recipients.

The system connects recipient identity, workspace context, connected mailbox providers, suppression and unsubscribe state, sending capacity, delivery status, failure handling, and retry or recovery behavior.

Real unsubscribe handling is part of the sending path. Synthetic demo workspaces are prevented from dispatching real provider email.

LeadForge can operate as a solo workspace or a team workspace depending on plan and access.

Team functionality includes workspace members and roles, Personal and Workspace scope, Team Chat, direct messages, shared artifacts, assigned work, activity visibility, Meeting Intelligence, and video collaboration.

Current workspace roles are owner, admin, and member. Some authorities, including general billing checkout, are deliberately owner-only.

Personal scope lets a user focus on their own relevant work. Authorized Workspace scope lets eligible users read shared information from the team where that LeadForge surface supports shared visibility.

The model is intentionally not equivalent to 'everyone can edit everything.' Read visibility and mutation authority are separate.

Important shared surfaces include Territories, Lead Intelligence, Pitch Decks, Task Results, Vault and other workspace-aware operating views according to the user's plan and permissions.

Team Chat keeps collaboration inside the same operating environment as the leads, Territories, artifacts, and Copilot context being discussed.

LeadForge also includes video collaboration and Meeting Intelligence so useful discussion and decisions can remain connected to the workspace rather than living entirely outside the business record.

Copilot can use legitimate in-product conversation context when that context is available and authorized.

LeadForge is designed so the same business context can move across Leads, Territories, Lead Intelligence, Task Results, Team Chat, Meeting Intelligence, Pitch Decks, Email Campaigns, Daily Actions, dashboards, and LeadForge Copilot.

That means research, comparison, communication, planning, and execution can share the same underlying business and workspace context instead of forcing the user to rebuild context in each tool.

LeadForge dashboards summarize what is happening across the pipeline, Territories, opportunities, and team activity according to the user's plan and scope.

Workspace activity provides operational visibility into work being performed across the team and contributes to the broader context used by Daily Actions and Copilot.

The goal is useful operating visibility rather than a collection of disconnected vanity metrics.

Businesses do not have to originate in Discovery. Users can import their own lead data so LeadForge can serve as the working system for opportunities sourced elsewhere.

Workspace branding supports client-facing output such as Pitch Decks and reporting so generated assets can reflect the agency behind them.

LeadForge includes a synthetic demo environment that demonstrates real product surfaces without exposing a customer's production workspace.

The landing-page viewer uses prebuilt synthetic scenes. The authenticated live demo uses an isolated demo workspace with synthetic team and collaboration content while allowing limited real user-owned lead and import records that can persist if the user upgrades.

The demo blocks real external effects such as provider email dispatch and keeps synthetic demo-only records separate from production workspace state. LeadForge-only discovery is plan-gated in demo, while Discovery, Targeted, and Copilot discovery flows can be demonstrated under demo rules.

Authenticated demo users can intentionally move into real billing conversion, but billing resolves against the user's real workspace rather than the synthetic demo workspace.

LeadForge offers solo and team plans. Plans differ by operating capacity and collaboration features, including Discovery capacity, AI-assisted usage, workspace seats, import capacity, video capacity on eligible plans, and higher-tier intelligence or workspace capabilities.

Monthly and annual billing are supported. Additional team-seat or capacity products can be available where the plan supports them.

General primary-plan and capacity-pack checkout is restricted to the workspace owner. Team-seat purchasing is also owner-only.

Lead unlocking itself is not sold as a paid unit.

LeadForge uses authenticated workspace membership, server-side authorization, role checks, and workspace-bounded reads and writes to separate customer workspaces and enforce product permissions.

Public demo data is synthetic and separated from normal customer workspace data. External-effect protections are used so demo activity does not silently turn into real provider actions.

No software can promise absolute security. LeadForge's design goal is to enforce identity, workspace, role, scope, and object boundaries at the server and data-access layers rather than relying on hidden buttons or client-side state.