Core outcomes
3
Commercial and operational outcomes already mapped to the bundle.
Workflow templates
4
Workflow blueprints that operationalize the bundle once dependencies are ready.
Connector lanes
8
Provider and connector categories that need to be available for the bundle.
Tracked KPIs
4
Operational or commercial scorecards the bundle is already designed to surface.
Operating model
The service families and workflows inside this bundle
Vertical packages turn the public service families into one more opinionated rollout path, with onboarding, dashboards, and KPI expectations already aligned.
Service family
AI Lead Intake OS
Unify the way inbound demand is captured, qualified, and handed into sales or ops without losing context.
Service family
AI Sales Automation OS
Turn qualified demand into faster meetings, tighter follow-up, and cleaner handoff states.
Service family
AI Reporting OS
See what changed, why it changed, and whether the workflow is helping commercial outcomes.
Service family
AI Workforce / Agent Deployment OS
Move from one-off automations to managed agent packs with cleaner launch and governance posture.
Service family
Lead Qualification & Routing
AI-assisted qualification that shortens response times while keeping CRM records, handoff notes, and buyer context cleaner.
Service-to-vertical map
How this vertical is assembled from shared modules
Recruitment and staffing packages compose the shared intake, screening, workforce-governance, and reporting modules into one two-sided candidate and client workflow.
Service roles
AI Lead Intake OS
Captures role briefs, candidate interest, and inbound responses before recruiters touch the record.
Lead Qualification & Routing
Applies fit rules and pushes the next action to the right recruiter or automation lane.
AI Sales Automation OS
Keeps interview booking, reminders, and candidate or client follow-up moving through the same shared primitives.
AI Workforce / Agent Deployment OS
Stages agent-pack usage, approvals, and operator guardrails for recruiter workflows without a bespoke staffing runtime.
AI Reporting OS
Summarizes screening, interview, and placement movement with the same reporting layer used across the platform.
Assembly sequence
Ingest candidate and client demand cleanly
Lead-intake and qualification flows unify role intake and candidate response capture inside the shared intake operating system.
Services
Lead Intake OS · Lead Qualification
Workflows
Lead Intake Router · Recruiter Screening
Agent packs
Lead Intake Pack
Progress interviews and follow-up
Sales automation reuses booking and follow-up templates so staffing teams do not need a custom sequencing engine.
Services
Sales Automation OS
Workflows
Qualification Follow-Up
Agent packs
Sales Automation Pack
Govern recruiter automation and report throughput
Workforce deployment and reporting modules keep recruiter launch posture and placement scorecards tied to the same shared ledgers.
Services
Workforce Deployment OS · Reporting OS
Workflows
Reporting Digest
Agent packs
Workforce Orchestrator Pack · Reporting Analyst Pack
Blueprint map
What the bundle maps to inside NEXA OS
The same package record now maps to workflow templates, agent packs, onboarding modules, dashboard modules, and reporting without splitting public and operational definitions.
Workflows
Automation templates
Lead Intake Router
Normalizes inbound requests and pushes them into the right queue or owner.
Recruiter Screening
Automates candidate qualification and recruiter handoff packets.
Qualification Follow-Up
Scores fit, asks the next question, and keeps follow-up moving.
Reporting Digest
Builds recurring service scorecards for operators and stakeholders.
Agent packs
AI workforce coverage
Lead Intake Pack
Agents that qualify, route, and summarize inbound demand.
Sales Automation Pack
Agents for nurture, booking, and opportunity follow-up.
Workforce Orchestrator Pack
Launch and governance agents for multi-pack operational rollouts.
Reporting Analyst Pack
Agents that summarize KPIs, trends, and rollout posture for humans.
Onboarding
Launch checklist
Workspace Baseline
Define owners, source systems, and the first service boundaries.
Connector Readiness
Confirm every required connector before workflows are activated.
Handoff Rules
Clarify who owns each stage when automation stops and humans take over.
Reporting Goals
Align on the KPIs and digest cadence that make the rollout believable.
Dashboard and reporting
Where teams track the rollout
Lead Intake
Queues, qualification posture, and handoff readiness.
Bookings
Scheduling posture, reminder coverage, and conversion handoff.
Agent Deployments
Agent-pack launch posture, rollouts, and launch guardrails.
Analytics Scorecards
Service and package KPI scorecards tied to real workflows.
Lead Funnel
Tracks inbound demand quality from capture through qualification.
Pipeline Velocity
Monitors movement from qualified demand into booked or closed states.
Agent Utilization
Shows where agent packs are live and whether they are carrying useful load.
Launch notes
Vertical onboarding notes and KPI mapping
These notes annotate the shared onboarding and reporting modules for this vertical without introducing a separate implementation path.
Onboarding notes
Map the two-sided funnel first
Agree candidate, role, client, and placement stages so the package does not collapse separate workflows into one vague pipeline.
Connect ATS, booking, and comms in one seam
CRM or ATS, calendar, messaging, workflow, voice, analytics, and OpenAI need one shared vocabulary for screening and placement.
Make recruiter ownership explicit
Document which recruiter inherits the next step after screening, interview booking, or rejection routing so automations stop clearly.
Choose throughput metrics before launch
Set the placement, workload, and recruiter-utilization views the reporting pack must publish every cycle.
Reporting and KPI map
Lead Funnel
Measures candidate and client intake quality from first response through qualified screening.
Pipeline Velocity
Tracks whether screening, interviews, and placements are progressing quickly enough across roles.
Agent Utilization
Shows whether recruiter-facing agent packs are useful and where handoff load still clusters around humans.
Readiness and compliance
Dependencies that keep the bundle trustworthy
These bundles deliberately call out operational dependencies and compliance considerations so public storytelling does not pretend the rollout is push-button.
Deployment dependencies
Candidate stages and scorecards agreed
Recruiter ownership rules configured
Interview booking logic approved
Provider mapping
Apideck CRM
This bundle already maps to the shared workspace connection seam for Apideck CRM.
Google Calendar
This bundle already maps to the shared workspace connection seam for Google Calendar.
Twilio
This bundle already maps to the shared workspace connection seam for Twilio.
n8n
This bundle already maps to the shared workspace connection seam for n8n.
Google Analytics 4
This bundle already maps to the shared workspace connection seam for Google Analytics 4.
OpenAI
This bundle already maps to the shared workspace connection seam for OpenAI.
Compliance watchpoints
Review candidate retention and deletion timing
Protect interview notes and recruiter comments from broad export access
Connector requirements
CRM sync
Workspace connectionCRM or ATS-backed connectivity keeps candidate, role, and client state aligned with screening workflows.
Calendar
Workspace connectionCalendar sync remains the shared booking seam for interviews and recruiter handoffs.
Messaging transport
Workspace connectionTwilio-backed messaging supports candidate follow-up and reminder coverage.
Workflow engine
Workspace connectionn8n orchestrates screening, routing, follow-up, and reporting digests.
Voice transport
Workspace connectionVoice transport helps staffing teams recover missed candidate or client calls without a custom telephony path.
Analytics
Workspace connectionAnalytics posture keeps pipeline and recruiter utilization scorecards anchored to actual throughput.
OpenAI runtime
Workspace connectionOpenAI runtime supports recruiter-facing drafting and agent-pack evaluation where that lane is enabled.
Agent orchestration
Onboarding checklistAgent-orchestration remains a governed rollout item until the provider family graduates beyond checklist posture.
Expansion path
The next lanes this bundle usually unlocks
Vertical packages can start with a narrow industry problem, then expand into adjacent service families once the core lane is stable.
Trust posture
Why the bundle page does not over-claim delivery maturity
The public bundle story is intentionally tied back to the same shared records that power dashboards, forms, onboarding, and later activation work.
Shared catalog, not page-local copy
Services, bundles, pricing posture, workflow links, and form deep links resolve from the same typed service catalog.
Lead capture stays durable-first
Contact and audit requests still flow through one shared capture service with hashing, rate limits, and downstream dispatch tracking.
Delivery state stays honest
Public pages describe scope and rollout inputs, while real workspace activation and readiness remain in dashboard and admin service ledgers.