Lead Routing + Lifecycle Orchestrator

BlueprintBuild

~1 hour

Architect your lead routing rules, lifecycle stage mappings, and conversion automation. Discovery queries assignment rules, queue memberships, and conversion rates. AI proposes bounded routing flows, lifecycle stage definitions, and required field validations.

The Prompt

Our lead routing is a mess. Assignment rules were set up years ago, nobody documented them, and leads keep falling through the cracks.

Goal: architect a clean lead routing system with lifecycle stages, assignment rules, and conversion automation. Discover what exists first, then propose bounded changes.

Use the Architect blueprint. Deploy to sandbox, verify, then production.

Discovery Before Design

Architect doesn't guess — it queries your org's actual assignment rules, queue memberships, and conversion rates first. The bounded proposal is generated from real discovery data, not assumptions. Safety limits enforce maximums on fields and validation rules.

How Architect Handles This

Discover Current State

Query assignment rules, queue memberships, territory settings, conversion rates, and existing lifecycle fields.

Generate Bounded Specs

AI proposes routing flows, lifecycle stage definitions, and required field validations — within safety limits enforced.

Review Proposal

PROPOSAL.md with routing rules, stage mappings, and validation rules. Proposal hash locks the spec.

Deploy Sandbox

Approval token required. Assignment rules, fields, and automation deployed to sandbox.

Verify

Scouts re-run to confirm routing rules active, stages mapped, and fields present.

Deploy Production

Second approval token. Same pack applied to production with receipt.

After you paste this prompt, Claude Code:

"Lead routing is undocumented and broken. Let me discover the current assignment rules, queues, and lifecycle config before proposing changes."

Running

$ g-gremlin autopilot architect init lead_routing_lifecycle --variant salesforce -p target_sandbox=dev -p prod_org_alias=prod

[Architect] Project arch_m9q2 created from blueprint: lead_routing_lifecycle (salesforce)

Running

$ g-gremlin autopilot architect discover arch_m9q2

[Architect] Querying assignment rules, queues, territories... [Architect] Found: 2 assignment rules (1 inactive), 5 queues, 0 territories [Architect] Lead conversion rate: 12% (last 90 days) ✓ Discovery complete: discovery/discovery.json written

"Found 1 inactive assignment rule and no territory config. 5 queues exist but routing logic is incomplete. Time to propose a clean lifecycle."

Running

$ g-gremlin autopilot architect propose arch_m9q2

[Architect] Generating bounded specs from discovery data... [Architect] Safety limits: max_custom_fields=15, max_validation_rules=8 ✓ Proposal: 3 custom fields, 3 validation rules, 1 permission set ✓ Written: proposal/PROPOSAL.md + proposal/metadata_pack/

Proposal includes bounded lifecycle specs

Custom fields:

- Lead.Lifecycle_Stage__c (Picklist) — New / MQL / SQL / SAL / Converted / Disqualified

- Lead.Routing_Region__c (Text) — Auto-populated from billing country

- Lead.SLA_Response_Due__c (DateTime) — Calculated response deadline

Validation rules:

- Lead.Require_Email_Before_MQL — Email required to progress to MQL

- Lead.Require_Company_Before_SQL — Company required to progress to SQL

- Lead.Block_Stale_Conversion — Block conversion if no activity in 30 days

Running

$ g-gremlin autopilot architect deploy arch_m9q2 --sandbox

[Architect] Approval token required. Posting to Slack... [Architect] Token received (ttl: 600s) [Architect] Deploying to sandbox: dev ✓ Sandbox deploy complete. Receipt: receipts/arch_m9q2/deploy_sandbox.json

Running

$ g-gremlin autopilot architect verify arch_m9q2

[Architect] Running verification scouts... ✓ Verification passed: lifecycle fields active, validation rules enforced

Running

$ g-gremlin autopilot architect deploy arch_m9q2 --prod

[Architect] Second approval token required... [Architect] Token received. Deploying to production: prod ✓ Production deploy complete. Receipt: receipts/arch_m9q2/deploy_prod.json

Lead Routing + Lifecycle deployed. 3 fields, 3 rules, 1 permission set. Sandbox verified. Production receipted.

Output Artifacts

CRM Changes

Lifecycle picklist — New / MQL / SQL / SAL / Converted / Disqualified
Routing region field — Auto-populated from billing country
SLA response deadline — Calculated field for response tracking
3 validation rules — Stage-gate requirements enforced

Local Artifacts

PROPOSAL.md — Routing architecture with stage-gate logic
metadata_pack/ — SFDX-format fields, rules, and permissions
deploy receipts — Before/after evidence for sandbox and production

Cross-CRM: Available for both Salesforce and HubSpot. Use --variant hubspot to architect lifecycle stages in HubSpot.

Results

Custom fields

Validation rules

Permission sets

Pass

Verification

Try This Blueprint

Architect your lead routing system with confidence.

Start Free Trial More Playbooks