Steadybase
Core Concepts

Drew Coordinator

The 9-step multi-agent orchestration workflow that coordinates research, content, and cross-namespace calls.

Drew Coordinator

The Drew Coordinator is Steadybase's centerpiece workflow — a 9-step multi-agent orchestration that takes a natural language request and coordinates specialized agents to deliver comprehensive GTM intelligence.

Overview

Drew acts as an AI project manager. Given a request like "Prepare outreach for our top 5 enterprise prospects," Drew:

  1. Plans the work and breaks it into subtasks
  2. Delegates research to Lisa (research agent)
  3. Delegates content creation to Brian (content agent)
  4. Manages human approval for high-stakes outputs
  5. Coordinates with Marketing via Nexus for ABM alignment

The 9 Steps

Drew Plans the Request Model: Claude (claude-sonnet-4-5)

Drew analyzes the natural language input and breaks it into structured subtasks. Each subtask is assigned to a specialist agent.

Lisa Queries Gong Calls Agent: Lisa (Research)

Pulls 30-day call transcripts from Gong, runs LLM analysis to extract key themes, objections, and buying signals.

Lisa Cross-References Salesforce Agent: Lisa (Research)

Matches Gong insights against Salesforce account data — deal stage, ARR, champion contacts, last activity dates.

Lisa Finds Temporal Cloud Signups Agent: Lisa (Research)

Checks whether target accounts have active Temporal Cloud signups, indicating infrastructure alignment.

Lisa Enriches Contacts via LinkedIn Agent: Lisa (Research)

Enriches contact data with LinkedIn profiles — role, tenure, recent posts, mutual connections.

Brian Drafts Outreach Model: GPT-4o

Using all research context, Brian generates personalized outreach for Tier 1 accounts — emails, LinkedIn messages, and call scripts.

Human Approval Signal-based gate — 7-day wait

Execution pauses and waits for an AE to review and approve the outreach drafts. The workflow can wait up to 7 days.

Marketing ABM Check (Nexus) Cross-namespace call

Nexus Operation to the Marketing namespace validates whether target accounts are in active ABM programs.

Brian Builds AE Dashboard Agent: Brian (Content)

Compiles all research, approved outreach, and ABM status into a comprehensive AE dashboard.

Multi-LLM Routing

The Drew Coordinator uses different models for different steps:

StepModelReason
Planning (Step 1)Claude claude-sonnet-4-5Best analytical reasoning for task decomposition
Research (Steps 2-5)ClaudeDeep analysis of call transcripts and data
Content (Step 6)GPT-4oStrong creative writing for outreach
Dashboard (Step 9)GPT-4oStructured content compilation

Input and Output

Input

{
  message: string;   // Natural language request
  userId: string;    // Requesting user's ID
}

Output

{
  activityFeed: ActivityEntry[];  // Step-by-step execution log
  summary: string;                // Executive summary
  dashboard: DashboardData;       // Compiled AE dashboard
  outreachDrafts: Draft[];        // Approved outreach content
  abmStatus: ABMResult;           // Marketing ABM validation
}

Human-in-the-Loop

Step 7 is a signal-based approval gate. The workflow:

  1. Emits an activity feed entry: "Awaiting AE approval"
  2. Sends a notification (WebSocket + optional Slack)
  3. Pauses execution for up to 7 days
  4. Resumes when the approveStep signal is received
  5. If no approval after 7 days, the workflow times out
// Approve the outreach
await handle.signal('approveStep', {
  stepId: 'human-approval',
  approved: true,
  notes: 'Looks good, send to top 3 accounts'
});

See the full workflow reference for implementation details.

On this page