Portfolio VII Nexus

An AI seller that finds, qualifies, and books the meeting — while your team sleeps.

Nexus

Sales automation · AI SDR · MCP · Operator · Engine lead · Active · 2026-01-30+

Status

Beta · In production

Sector

Sales automation · Outbound AI

Operator

Harold Mideros · Engine lead

Site

nexus.brainzlab.ai

The Receipts

One agent. The whole top of the funnel.

95%

Of the funnel, run by the agent — find, enrich, qualify, book. The human walks in for the close.

2

Channels, one conversation — email and WhatsApp threaded together, in real time.

6

Languages the seller works in — calibrated to the buyer, not the tech team.

24/7

Outreach that never clocks out — replies read and meetings booked around the clock.

Most tools draft a message and stop. Nexus runs the whole play.

Nexus is an AI seller. It reads a segment of scored accounts, opens the conversation, reads the reply, and books a live meeting — then hands a showed-up call to a human closer. Not a copilot that suggests; an operator that acts.

It works the channels a real seller works — email and WhatsApp, threaded as one conversation — and writes to the decision-maker in their own language, across six of them.

The boundary is deliberate. The AI does the first 95%. The human walks in for the close. Autonomy settings, reply guards, and handoff controls mark exactly where the machine stops.

“

The AI does the first 95 percent. The human walks in for the close.

Operating principle · Brainz · 2026

Find. Reach. Read. Book.

  1. I.

    Find and enrich.

    Nexus reads a segment of scored accounts and pulls firm-level context for each one — so every message is grounded in who the account actually is, not a mail-merge field.

  2. II.

    Reach out.

    It writes a discovery message calibrated to the decision-maker, in their language, and sends across email and WhatsApp — with deliverability instrumented, not assumed.

  3. III.

    Read the reply.

    When a reply lands, Nexus evaluates intent, drafts the response, and qualifies the account against the fit criteria — escalating from a knowledge base when the conversation needs depth.

  4. IV.

    Book the meeting.

    It proposes a time, confirms the booking, and routes the showed-up call to a human closer — the one step still reserved for a person.

The engine Nexus pipeline / booking dashboard · drop a screenshot here
— image placeholder · drop a screenshot or photo here —

Ninety-five percent automated. One channel-agnostic conversation. Compliant by design.

  • 95%

    The agent runs find → enrich → qualify → book. Your team is reserved for the close, where a human still wins.

  • 2

    Email and WhatsApp handled as one threaded conversation — the buyer never feels the seam.

  • 6

    Six languages, calibrated to the buyer rather than the tech team — the mid-market decision-maker, in their own words.

  • 1581

    Ley 1581 (Habeas Data) opt-out and suppression built in — one-click unsubscribe, privacy footers, a global suppression list. Cold send, legally defensible.

What it runs on. Who runs it now.

  • Rails 8
  • MCP server
  • WhatsApp Cloud API
  • RAG knowledge base
  • AWS SES / SMTP
  • CRM connectors
  • One-click opt-out
  • Delegated AI routing

— end of chapter VII —

Harold Mideros

Operator · Nexus

Same loop. Your pipeline next.

If this pattern fits your funnel, let's have a conversation.

A single discovery call. Then a written, scoped engagement — or a clean no, with notes on what we saw.