Overview

3-Week Sprint to Live

This is a fast-build. Three weeks from kick-off to live data verification calls running against the Brabys database. Phase 2 — the sales agent — kicks off the moment Phase 1 is done.

3

Weeks to Live

3

AI Agents

5

Blockers to Resolve

2

Phases Total

Week 1

Foundations & Core Infra

DB live · General running · Data imported

Week 2

Voice & Processing

Claire calling · Scrub processing · Dashboard live

Week 3

Merge & Go-Live

Pilot run · Informix merge · Production live

Week 4+

Phase 2: Sales

New agent · New script · Separate persona

Open Blockers — Brabys to Action Now

Maverix can build everything in Week 1 independently. Week 2 is gated on 3CX. The faster Brabys resolves these, the faster we go live.

#	Blocker	Owner	Needed By
B1	3CX — does an existing instance exist? If yes, provide SIP credentials + API access.	Brabys IT	Day 3
B2	Informix connectivity — JDBC driver, VPN/network access, read-only credentials.	Brabys IT	Day 5
B3	Sample CSV extract — 100–200 records (subscriber ID, name, address, phone, email, website).	Brabys	Day 3
B4	Merge approval — manual dashboard trigger or scheduled nightly window?	Mr Isaacs	Day 5
B5	ElevenLabs account — create one at elevenlabs.io (free tier OK for now).	Brabys	Week 3

The Plan

Week by Week

Week 1

Foundations & Core Infrastructure

Goal: PostgreSQL live. General agent running. 100 records imported and queued.

🎯 Milestone: General operational

Maverix — starts Day 1

1.1

Provision staging server + project repo

Linux server for PostgreSQL, Node.js agents, and dashboard. Git repo structured: /agents, /db, /dashboard, /scripts.

Maverix

Day 1

1.2

Deploy PostgreSQL schema

Three tables: records (working copy), call_log (one row per call), field_updates (delta layer). Row-level access per agent role enforced.

Maverix

Day 1–2

1.3

CSV import script + pilot import

Ingest Brabys CSV into records table. Maps columns, validates fields, inserts as NEW status, outputs import report. Run with sample 100-record batch.

Needs B3 (sample CSV from Brabys)

Maverix

Day 2–3

1.4

General supervisor agent

Node.js loop: polls queue, assigns records to CALLING status, spawns Claire instances, retries failed calls (max 3), respects calling hours (08:00–17:00 SAST). Daily summary report to Brabys ops.

Maverix

Day 2–4

1.5

Test General in simulation mode

Run against imported records with mocked Claire responses. Verify status transitions, retry logic, and reporting. No live calls yet. Week 1 sign-off gate.

Maverix

Day 5

Week 2

Voice Agent & Call Processing

Goal: Claire making real calls. Scrub processing transcripts. Dashboard live.

🎯 Milestone: First live call end-to-end

Gated on B1 (3CX) — build in simulation if delayed

2.1

3CX ↔ ElevenLabs bridge

SIP/WebRTC bridge: General triggers call → 3CX dials number → ElevenLabs Claire handles conversation. Capture call IDs from both systems. If 3CX delayed, mock with test number first.

Needs B1 (3CX credentials)

Maverix

Day 6–8

2.2

Dynamic field injection into Claire

Before each call, General injects the record's actual field values into Claire's session — so Claire reads this business's real data, not placeholders.

Maverix

Day 7

2.3

Scrub transcript processor

Reads call transcripts, extracts field corrections, validates each field (email format, phone, URL, address), assigns confidence score 0–100. Auto-approves ≥80% confidence. Routes <80% to human review. DNC → quarantine.

Maverix

Day 7–8

2.4

Operations dashboard

Live view: queue by status, calls in progress, today's stats, QA queue, DNC count. Auto-refreshes 30s. Human review UI: old vs new values, transcript excerpt, one-click approve/reject.

Maverix

Day 8–10

2.5

First real call — end-to-end test

Claire calls a test number. Full cycle: General assigns → Claire calls → transcript captured → Scrub processes → record moves to APPROVED or HUMAN_REVIEW. Both teams review call quality. Week 2 gate.

Both

Day 10

Week 3

Merge, Pilot & Go-Live

Goal: Informix merge engine built. 100-record pilot run complete. Production live.

🚀 Milestone: Data verification live

Gated on B2 (Informix access)

3.1

Informix merge engine

Reads APPROVED records from field_updates. Connects to Informix via JDBC. Field-level updates only — subscriber ID is the immutable anchor. Logs every write. Conflict detection: never overwrites newer Informix data. Rollback script included.

Needs B2 (Informix access) and B4 (merge approval decision)

Maverix

Day 11–13

3.2

End-to-end integration test

20-record full cycle: import → General assigns → Claire calls → Scrub processes → approve → merge to Informix staging (not production). Verify all 20 records updated correctly.

Maverix

Day 13–14

3.3

100-record pilot run

Real calls. Real data. Live merge to Informix staging. Both teams review results: call quality, data accuracy, approval rates, DNC handling. Sign-off required from Mr Isaacs.

Both

Day 14–15

3.4

Production go-live

Switch Informix target to production. ElevenLabs billing transferred to Brabys account. Dashboard access handed to Brabys ops. Ongoing call volume agreed. Phase 2 scoping begins.

Needs B5 (ElevenLabs billing migration)

Both

Day 15

What Comes Next

Phase 2: The Sales Agent

The moment data verification is live, Phase 2 begins. The infrastructure is already built. The only new work is a separate agent persona, a new script, and a warm-lead trigger from Claire's call data.

Critical Architecture Decision

The sales agent must be a completely separate persona from Claire. Claire has built trust — "this is not a sales call." That trust cannot be compromised. The sales agent gets a different name, different voice, and is never described as the same system. Warm leads from Claire's calls are the trigger — but the connection is invisible to the business being called.

Phase 2 Scope

New agent persona — different name, different ElevenLabs voice, separate ElevenLabs agent ID
New script — outbound sales conversation based on warm signals from verification calls (e.g. "no website", "interested in advertising")
Warm lead queue — General flags records during verification where the business showed interest; sales agent picks these up first
Sales outcome tracking — separate sales_log table; outcomes fed back to Brabys CRM or manually
Escalation path — hot leads transferred to a human sales rep (live transfer or callback booking)
Same infrastructure — same General orchestrator, same 3CX, same PostgreSQL DB, same dashboard extended

Timeline estimate: Phase 2 is faster than Phase 1 — the infrastructure already exists. New agent persona + script + warm-lead queue is roughly 1 week of build. First sales calls within 2 weeks of Phase 1 go-live.

Risk Register

Risk	Likelihood	Mitigation
3CX not available / incompatible	Medium	Build call logic in simulation mode. Twilio or Vonage as fallback — 2-week decision window before switching providers.
Informix connectivity complex or delayed	Medium	CSV import/export as interim workaround — pilot can run without direct DB access. Not permanent but unblocks Weeks 1–2 entirely.
Call quality / Claire voice unacceptable	Low	Alternative ElevenLabs voices pre-tested. Script refined on early samples. Human listen-test before any calls to real customers.
Scrub accuracy too low (too much human review)	Medium	Confidence threshold is tunable. Start strict, loosen as accuracy is proven. Human review load decreases as system is calibrated.
POPIA / telecoms compliance (South Africa)	Low	DNC register enforced strictly. Brabys legal to confirm compliance posture before any live calls to real subscribers.

Prepared by

Maverix Studio

darren@maverixstudio.com · maverixstudio.com

Read alongside: Brabys AI Agent Workforce — Project Outline v1.0