Skip to main content
Live Direct Marketing / B2B outreach

Your agent prepares. You make the call.

Find the right companies, review a relevant message, and manage replies in one workspace — with your agent or by hand.

MCP + APIFull web app
Prefer a guided start? Talk to us
LDM / First sessionIllustrative example

A reason for every company

Brief: introduce a B2B service to growing teams.

Northstar

A new market and a relevant use case

01
Forma

The right team size and business model

02
Atlas

A clear reason to start a conversation

03
One workspace for you and your agent.
A shortlist with reasons
Messages you can review
MCP, API and web UI
Replies and history in CRM
Already working with an AI agent?Connect it through MCP. Start with a brief, a shortlist and a draft you can review.
Connect your agent

From your brief to a reviewed outreach plan.

An example workflow: begin with 5–10 companies and one message, then approve the next step. This is a walkthrough, not a promise of leads.

01

Brief → shortlist

You provide the offer, target market and exclusions. The agent researches companies and shows why each fits, with sources and gaps.

02

Message → your review

The agent drafts a message and adds available materials. You check facts, relevance, tone and the proposed recipient list.

03

Test → campaign → CRM

After activation and sender setup, review placement, cost and readiness. Authorise outreach, then inspect replies and handoff notes in CRM.

You approveRecipients, content, sender, budget and launch.
You receiveA shortlist, sample, test results and a traceable follow-up plan.

What the placement test actually confirms

Where the check runs

On control (seed) mailboxes. LDM observes the folder there for a sending-account × provider × message combination.

What counts as success

The tested copy is observed in Inbox on a control mailbox. Read the provider breakdown and test time; results may be cached.

What it cannot confirm

The test does not reveal the folder at a different, final recipient. It does not guarantee that person’s Inbox, reply or sale.

What causes a charge

Delivery billing is separate: a message marked sent and at least 24 hours without a recorded bounce. A later bounce refunds that delivery charge.

Test method and limitations

What to bring to the first session

Your offer, ideal customer profile, geography, exclusions, supporting facts and any presentation. Agree what counts as a useful result before selecting companies.

Registration starts with PENDING. Reads are available; sending and other permissions require activation. Depending on your email and website, activation may require a questionnaire and review.

See the first-session walkthrough

Receive the sample without connecting a mailbox

Once the workspace and creative permissions are ready, LDM can send the test copy and linked attachment to the workspace owner’s registration email. The agent uses that address automatically, without asking for it again.

This sends materials to you. Campaigns to prospects require a connected sending account or pool and a separate readiness check. A sample sent by LDM does not test your own sending domain.

One platform. Two ways to operate.

Agents and humans work with the same contacts, campaigns, placement decisions, replies and pipeline data.

MCP / API for AI agents

Connect LDM to an agent or your own automation without losing operational control.

  • Find and create contacts
  • Score ICP fit and prepare creative
  • Launch and control campaigns
  • Process replies, CRM records and pipelines

Full web UI for humans

Operate the complete platform directly, supervise agent actions, or step in manually at any point.

  • The same contacts and context
  • The same campaigns and placement results
  • Visibility into agent actions
  • Manual operation whenever needed
Same system · same data · same capabilities

Cloud, dedicated or on-premise.

Run LDM in our cloud, on a dedicated instance, or inside your own infrastructure. The full web UI, MCP and API remain available in every deployment model.

LDM Cloud

A ready-to-use cloud service operated by the LDM team.

Dedicated deployment

An isolated application, database and queues for your organization, operated by LDM.

Licensed on-premise

A private Docker-based deployment inside infrastructure controlled by your organization.

  • Your contacts and CRM data stay in your infrastructure
  • Bring your own AI providers and sending accounts
  • Full MCP, API and web UI
  • Docker-based deployment
  • Customer-managed updates or managed support
  • Connect to LDM Inbox Placement infrastructure when verification is required

On-premise is a licensed deployment package, not a source-code transfer.

Discuss on-premise deployment

Experience behind LDM

Experience from projects delivered by the LDM team, including work across email, phone and social channels.

Team project results; not a benchmark of independent use of the current platform.

From targeting to reply — in one controlled outreach loop.

Company research, message preparation, placement tests and replies share one workspace.

Targeting and context

Find relevant companies and people, score ICP fit, and prepare a concrete message for the recipient and their current context.

Placement testing

On control (seed) mailboxes. LDM observes the folder there for a sending-account × provider × message combination.

Replies, CRM and feedback loop

Capture and classify replies, continue the conversation in CRM, and feed outcomes back into targeting and creative.

For teams that value relevant conversations and a visible process.

LDM is built for deliberate B2B outreach where the quality and economics of each contact matter more than raw send volume.

  • B2B teams, outbound specialists and small agencies
  • Developers of AI SDRs and autonomous sales agents
  • Companies with irregular campaigns that do not justify large fixed plans
  • Teams that need an itemised view of outreach costs

Know what is charged before you launch.

One prepaid balance for web UI, API and MCP. Delivery and preparation are separate operations. The table loads the current public USD rates; your workspace may have individual rates.

Delivery billing: sent + 24 hours without a recorded bounce. This is not proof of the recipient’s Inbox folder.

$50 starting credit at the current public setting.

Public price snapshot: 2026-09-07 08:16:13 UTC. Rates refresh when you open the page.

One prepaid balance for web UI, API and MCP. Delivery and preparation are separate operations. The table loads the current public USD rates; your workspace may have individual rates.
OperationWhen it appliesUSD per unit
Delivery · platform contentPer sent message after 24 hours without a recorded bounce.$0.015
Delivery · your finished content (BYOC)Same delivery event, with content supplied by you. Independent of mailbox ownership.$0.005
Task / creative approvalPer non-system approval of a mailing task, by a human or an authorised agent. Automatic system approval is exempt.$5
Platform message preparationPer message rendered; a paid rate, if configured, applies again to a new render.$0
Successful content auditPer successful audit attempt. This is a content check, not a mailbox placement test.$0
Unsuccessful content auditPer chargeable failed attempt; priced separately, not as a fixed percentage of a successful audit.$0.0005
Send operationSeparate operation when a message is queued for sending; additional to the later delivery charge.$0

Example: 10 drafts, 2 revisions, 9 billable deliveries

Illustration using the loaded public rates, platform content and no individual overrides. Two drafts fail the chargeable audit, both are prepared again and pass. All 10 are sent; one bounces before billing.

  1. Prepare 10 drafts + prepare 2 again$0
  2. 2 failed audits + 10 successful audits$0.001
  3. 10 send operations$0
  4. 9 deliveries after 24 hours; 1 early bounce costs no delivery fee$0.135

Campaign operations total: $0.136

If you also perform one paid task / creative approval: +$5, total $5.136.

A late bounce returns the delivery fee actually charged for that message. Earlier preparation or approval charges remain.

Top-ups are handled manually by the LDM team through support in your workspace. The billing journal records charges and refunds. Zero-priced operations do not debit the balance. BYOC means finished content supplied by you; it does not mean a sending account.

See the placement technology in action.

Inbox Check and developer documentation support the LDM flow; they are not separate competing products.

Technical answers, without the sales fog.

Does LDM know the folder at each final recipient?

Placement is observed on control mailboxes for the tested account, provider and message. It does not prove the folder at another recipient. Delivery billing uses a separate sent-plus-24-hours-without-bounce event.

Is everything free if a message is not sent?

No. Preparation, a chargeable failed content audit or a task approval can have a price even if no delivery follows. Current rates and a complete calculation are shown above. A late bounce refunds the delivery charge, not earlier operations.

What is the difference between BYOC and my own mailbox?

BYOC means you supply finished message content. The discounted delivery operation is chosen by that content source. Connecting a mailbox is a separate sending configuration, not the condition for the BYOC rate.

Can I see my first sample without a sending account?

With an active workspace and the required creative permissions, LDM can send a test copy and linked attachment to the owner’s registration email. No repeated address request is needed. Sending a campaign to prospects requires its own sending account or pool.

What happens after registration?

The account starts PENDING. Reads work; activation is required for sending and other permissions. Corporate email and a matching website can allow automatic activation after email confirmation, subject to capacity. Other cases require a questionnaire and admin review.

How much control do I keep?

You and the agent use the same workspace data. For a first run, agree the shortlist, message, sender, budget and launch before sending. An agent with approval permissions can approve a task, so grant those permissions deliberately.

Do the case studies predict my result?

They describe the LDM team’s project experience, often across several channels. They are not a benchmark of independent use of today’s platform. Each case distinguishes published figures from missing measurement details.

How do I top up?

LDM uses a prepaid balance. During the current demo payment mode, request a top-up from the team through workspace support. There is no automated payment gateway or customer top-up through MCP/API.

Want us to run it for you?

Our team can launch and operate the same LDM platform for your project. You keep visibility into targeting, messages, Inbox Placement, replies and results — and can move to the web UI or an AI agent later.

Start managed. Move to self-service when ready.
Talk to us