Work breakdown

The six activations, in detail.

Activation 01 is the Prospect Automation Engine - the flagship that finds your buyers, researches them, and writes the outreach. The other five cover the rest of the GTM motion around it. Every activation ships with the same structure: what we need from you, the build sequence, the assets you keep, and the controls that prove it works. Nothing ships on a promise - everything ships on evidence.

Activation Outbound Automation Engine

Identify the right accounts, enrich the buying context, prepare approved messages, and route replies - without turning the system into an unsupervised email cannon.

Inputs & decisions

  • Ideal customer profile and exclusion rules
  • Target geographies, segments, offers, account tiers
  • Approved data sources, sender identities, sequence limits, CRM campaign fields

Delivered assets

  • ICP and segmentation brief
  • Enrichment and qualification workflow
  • Message library and personalization rubric
  • Approval queue, suppression logic, reply routing
  • CRM field map, pilot report, operator SOP

Build sequence

  1. Define the account and contact schema, source priority, and deduplication rules.
  2. Create research and qualification steps with explicit confidence and rejection reasons.
  3. Enroll approved prospects, capture replies and opt-outs, and sync outcomes to the CRM.
  4. Run a controlled pilot, review errors and responses, and revise scoring and copy.

Controls & acceptance evidence

  • No external send before approval - a pilot list passes agreed completeness and duplicate thresholds.
  • Deduplication and suppression - opt-outs, existing customers, competitors, and blocked domains are excluded.
  • Source and confidence stored - reviewers can trace each key claim to its source.
  • Per-run logging - every enrollment, reply, failure, and stop is visible in the run ledger.

Activation Inbound Automation Engine

Turn every approved inbound signal into a complete, owned, time-bound action with the right response and a visible audit trail.

Inputs & decisions

  • All inbound sources: forms, events, referrals, partners, chat, product signals
  • Lifecycle stages, qualification criteria, territories, ownership rules, response SLAs
  • Approved acknowledgement and follow-up language

Delivered assets

  • Inbound source map and field dictionary
  • Qualification and routing rules
  • Enrichment, assignment, alert, and response workflow
  • Exception queue and SLA monitor
  • Pilot report and operating SOP

Build sequence

  1. Inventory all entry points; map each source to the CRM object and source field.
  2. Normalize, deduplicate, and enrich the person and account record.
  3. Apply qualification and routing rules; expose uncertain cases for review.
  4. Assign the owner, start the SLA clock, notify the right channel.
  5. Prepare or send the approved acknowledgement based on risk level.
  6. Track first response, disposition, conversion, failures, and reassignment.

Controls & acceptance evidence

  • Deterministic ownership - test submissions from each source create or update one correct record.
  • Human review for ambiguous qualification - ambiguous records enter a visible queue instead of being silently rejected.
  • Idempotent CRM writes - repeated events never create duplicate contacts or opportunities.
  • SLA breach and failure alerts - owners get an alert with enough information to act.

Activation Pre-Call Intelligence

Give the seller a short, sourced briefing before the meeting so preparation becomes consistent - without replacing seller judgment.

Inputs & decisions

  • Calendar event and attendee identity
  • CRM account, contact, opportunity, activity, and open-task data
  • Approved external research sources and briefing format

Delivered assets

  • Meeting eligibility rules
  • Identity-resolution and retrieval workflow
  • Standard briefing template
  • Source and confidence policy
  • Delivery workflow, QA rubric, and SOP

Build sequence

  1. Trigger the workflow for eligible meetings at an agreed lead time.
  2. Resolve attendee and company identity; flag ambiguous matches.
  3. Research only approved external signals and preserve source links.
  4. Deliver the brief to the chosen channel; log view or delivery status.

Controls & acceptance evidence

  • Source-linked factual claims - sample briefs accurately represent CRM facts and preserve external source links.
  • Restricted-field redaction - restricted fields are omitted from model context and outputs.
  • Identity ambiguity escalation - uncertain attendee matches are clearly flagged for review.
  • No automatic customer-facing action - the workflow prepares context only; the seller runs the meeting.

Activation Post-Call Follow-Up

Convert each conversation into accurate records, clear actions, and ready-to-review follow-up while the context is still fresh.

Inputs & decisions

  • Meeting recording or transcript, where approved
  • CRM objects and required fields
  • Follow-up style, task rules, opportunity methodology, review policy

Delivered assets

  • Transcript-to-summary workflow
  • CRM update map and validation rules
  • Task and follow-up draft templates
  • Human approval queue
  • Exception handling, QA rubric, and SOP

Build sequence

  1. Ingest the transcript and meeting metadata after an eligible call.
  2. Create a structured summary and proposed CRM field updates.
  3. Draft customer follow-up and internal tasks from the approved structure.
  4. Route all material updates and external messages through the human review gate.
  5. Write approved changes, monitor completion, and log exceptions.

Controls & acceptance evidence

  • Transcript permission and retention controls - a test set produces complete summaries with traceable transcript support.
  • Field-level validation - invalid dates, owners, stages, and required fields are rejected before writeback.
  • Human approval for external messages and material CRM changes - nothing external is sent until the reviewer approves.
  • Conflict handling - transcript/CRM disagreements surface as exceptions, never resolved by guesswork.

Activation Workflow Execution Report

Make automation trustworthy by showing what ran, what changed, what failed, what it cost, and who owns the exception.

Inputs & decisions

  • Workflow inventory and criticality tiers
  • Run identifiers, timestamps, inputs, outputs, model usage, cost, error events
  • Severity definitions, alert channels, owners, escalation windows

Delivered assets

  • Execution event schema
  • Run ledger and drill-down view
  • Error taxonomy and alert rules
  • Retry and replay procedures
  • Daily workflow health report and incident SOP

Build sequence

  1. Define the common event schema used by every activation.
  2. Create retry rules, dead-letter handling, and manual replay controls.
  3. Build daily health views by workflow, owner, environment, and severity.
  4. Alert operators on agreed thresholds; record acknowledgement and resolution.
  5. Review incident patterns and feed corrective work into the backlog.

Controls & acceptance evidence

  • Correlation ID from trigger to outcome - operators trace a sample transaction through every step.
  • Least-privilege visibility - sensitive fields redacted; access is role-based.
  • Bounded retries and safe replay - failures retried or routed without duplicate side effects.
  • Owned failures - critical failures generate an owned alert and a recorded resolution.

Activation Daily GTM Executive Report

Turn workflow and CRM data into a short daily decision brief: what changed, what needs attention, and where leadership should intervene.

Inputs & decisions

  • Approved metric glossary and source-of-truth system per measure
  • Audience, delivery channel, timing, thresholds, escalation rules

Delivered assets

  • Metric dictionary and source map
  • Executive dashboard and daily briefing format
  • Anomaly and threshold rules
  • Drill-down and reconciliation views
  • Delivery workflow and operator SOP

Build sequence

  1. Define each metric: calculation, owner, source, refresh cadence, known limitation.
  2. Build governed data queries; reconcile totals against source systems.
  3. Create a concise daily brief: movement, exceptions, required decisions.
  4. Add drill-down paths from every aggregate to the underlying records or runs.
  5. Deliver on schedule; log delivery, data freshness, and exceptions.
  6. Run a monthly metric review - retire noise, add only decision-useful measures.

Controls & acceptance evidence

  • One source of truth per metric - a sample period reconciles to approved source-system totals.
  • Freshness displayed - the report labels stale or incomplete data instead of presenting it as current.
  • No invented causality - anomalies described as observations unless causality is supported.
  • Drill-down to records - leaders move from a headline metric to the records or run evidence.
Book a build session How an engagement works