Baseer GTM — System Report

Autonomous go-to-market engine for baseerocr.com · Arabic-first OCR / IDP · GCC enterprise
Status: Operational · 2026-07-05

Baseer GTM is a 24/7 multi-agent system that finds the right GCC enterprise accounts, researches and qualifies them, drafts personalized outreach across LinkedIn and email, and routes every outbound action through a human approval gate — while a dashboard gives the operator full visibility and control.

18
specialized agent roles
43
ICP-qualified accounts (live)
4
prospecting sources
0
un-approved sends possible

1 · For the decision-maker: what we have built

We have built a complete, automated sales-and-marketing machine for Baseer — not a prototype. It runs continuously on production infrastructure and covers the full GTM cycle:

The outbound sales engine (Phase 1)

  • Sourcing — discovers GCC large enterprises in document-heavy industries (banking, insurance, government, telecom, healthcare).
  • Qualification — a deep ICP rubric scores every account/contact and disqualifies SMEs, off-segment, and non-GCC targets automatically.
  • Journey — per-contact state machine: LinkedIn invite → acceptance → your-approved message → 3-business-day reminders → email hand-off.
  • Booking — Cal.com bookings close the loop and stop all outreach to that contact.

The demand & brand engine (Phase 2)

  • Signals Hub — Twitter/X, LinkedIn, GitHub, community and news signals in one actionable stream.
  • Market intelligence — 7 competitors under watch (ABBYY, Nanonets, Upstage…), research papers, tenders, news.
  • Content calendar — weekly planning + publish-on-approval for Sara & Rawan (LinkedIn) and Norah (X).
  • PR workspace — 20 seeded GCC press contacts, pitch drafting, approval, reply tracking.
The safety guarantee. No email, LinkedIn message, tweet, or PR pitch can ever leave the system without an exact, owner-approved match. LinkedIn connection requests auto-execute after safety checks; everything that carries a message waits for approval. A global kill-switch halts all outbound instantly, and volume caps protect the accounts and email domain.

Where things stand today

AreaStatusDetail
Production infrastructureLiveAPI (Cloudflare Workers), dashboard (Cloudflare Pages), database (Neon Postgres), agent runtime (this machine, 24/7)
Sales pipelineRunningApollo sourcing unblocked; journey state machine, approvals, and execution rails all live
Qualified accounts43 loadedReal GCC targets incl. Saudi ministries (Justice, Health, HR), ZATCA, GOSI — more flowing in
Verified contactsMigrating434 verified contacts + 342 accounts from prior system being ICP-reviewed and imported
Marketing engineDeployedSignals, market analysis, content calendar, PR — all four dashboards live
Quality803 testsFull automated test suite green; every change verified before deploy

2 · How the system works

Everything flows through one disciplined spine — the same pattern for every channel, which is what makes the system safe and auditable:

Scheduler
spawns daily work
Specialist agent
produces typed output
Orchestrator
reviews & routes
Your approval
exact-match gate
Execution
policy checks + send
Dashboard
tracks & logs

Every step writes to Neon; nothing is implied. Malformed or unsafe outputs are quarantined, not shipped.

The two runtimes

  • Hermes agent runtime — runs the LLM reasoning for every agent on the shared Hermes/OAuth configuration (no per-agent API keys). A 1-minute relay carries each agent's request to the model and back.
  • Cloudflare edge — the API worker (business logic, approvals, execution, a 5-minute maintenance cron) and the dashboard, both close to GCC users.

The data source of truth — Neon

  • 35 database migrations define accounts, contacts, journeys, approvals, execution queue, signals, competitors, content plans, PR, and audit tables.
  • Every agent output, review, approval, send, and state change is recorded — the dashboard is a live window onto Neon, never a guess.
  • Typed status constraints and idempotency keys make the pipeline crash-safe.

3 · The agents — who does what

Eighteen specialized roles, each with its own instructions, allowed tools, and hard safety constraints. They never talk to each other directly — they collaborate through data and one referee (the Orchestrator).

Sales pipeline agents

AgentJobTools
Account SourcingDiscover GCC enterprise accounts that fit the ICPApollo · web search · ScrapeGraphAI
Contact DiscoveryFind reachable decision-makers at sourced accountsApollo · LinkedIn (active-only) · Prospeo
EnrichmentComplete + verify account/contact data with evidenceApollo · Prospeo · web research
Account IntelligenceDeep account research: digitization signals, tech stackApollo · ScrapeGraphAI (Arabic-aware)
ICP StrategistRefine targeting from performance dataAnalytics reads
Outreach CopywriterDraft personalized, evidence-grounded outreachContract-producer (no sends)
SDR SequencePlan multi-touch cadencesSequence planning
LinkedIn — SaraPropose LinkedIn actions from Sara's account (read-only)LinkedIn search + activity gate
LinkedIn — RawanPropose LinkedIn actions from Rawan's account (read-only)LinkedIn search + activity gate
Booking & PipelineHandle bookings, prep notes, pipeline healthCal.com reads
Safety & BookingEnforce booking-driven stop rulesContract-producer
Learning & QAWeekly performance review + learning loopAnalytics reads
GTM OrchestratorThe quality gate — reviews every output, decides approve / route / reject / spawn childrenEvidence + policy context

Demand & brand agents (Phase 2)

AgentJobTools
Social ListenerScan Twitter/X, community, GitHub for Baseer-relevant signalsTwitterAPI · news RSS · read tools
Twitter Engagement (Norah)Draft replies to relevant tweets (approval-gated, Arabic-aware)TwitterAPI read → draft only
Market IntelligenceMonitor competitors, research papers, tenders, newsNews RSS · arXiv · ScrapeGraphAI
Content PlannerWeekly content calendar for Sara/Rawan/NorahResearch + persona validators
PR OutreachDraft per-outlet press pitches from the GCC media listContract-producer (approval-gated)

4 · How the agents interact — with each other, Neon, and the dashboard

Agent ↔ Agent (via the Orchestrator)

Agents never call each other. A sourcing agent's approved accounts become child tasks the Orchestrator spawns for contact-discovery; approved contacts spawn enrichment; enriched contacts spawn outreach drafts. Depth is capped (≤3), duplicates are deduped, and only whitelisted task types can be spawned — so no runaway loops.

Sourcing Contact discovery Enrichment Outreach draft

Agent ↔ Neon

The runtime claims a queued task from Neon, gives the agent its data + tools, and records the typed output back to Neon — where it is schema-validated. A valid output moves the task to awaiting orchestrator review; an invalid one is quarantined. Heartbeats and a stale-task reaper keep the 24/7 loop crash-safe.

Agent ↔ Dashboard (you)

When an agent proposes something that sends — a message, reminder, tweet, or pitch — it becomes an approval item you see on the dashboard. You approve, reject, or request an edit. Only your approval, matched exactly to the drafted content, lets the execution layer send it. The dashboard also shows agent health, the task board, quarantine, relay status, and the full contact journey for every prospect.

The four prospecting sources

  • Apollo — primary structured account + people search.
  • Web search — open-web discovery of companies and Vision-2030/digitization signals.
  • LinkedIn MCP — GCC contacts, gated on genuine profile activity (dormant profiles disqualified).
  • ScrapeGraphAI — deep, Arabic-aware extraction of evidence from a candidate's own web presence.

Every finding, from any source, must clear the ICP rubric before it enters the pipeline.

5 · Safety & control

ControlWhat it guarantees
Exact-match approvalA send only fires if an approved record matches the drafted message, target, channel, and timing exactly.
Global kill-switchOne action halts all outbound instantly; resuming is owner-only.
Volume caps + warm-upLinkedIn ≤100 invites/week per account; email ramps gradually and self-throttles if bounces rise.
Suppression & stop rulesBounces, complaints, replies, and bookings automatically stop further outreach to a contact.
Role-based accessSensitive actions (autonomy level, pause-clear) are owner-only; every change is audit-logged.
Read-only agentsAgents propose; they cannot send. Only the policy-gated execution layer talks to providers.

6 · Bottom line

Baseer now has an end-to-end GTM system that a solo operator can run: it discovers and qualifies the right GCC accounts, builds the outreach, and executes only what you approve — across LinkedIn, email, social, content, and PR — with full visibility and hard safety rails. The sales pipeline is live with real qualified accounts; the marketing engine is deployed; and the data foundation is being enriched with hundreds of previously-verified contacts.