Vertical package

Property And Estate Workflow

Estate, lettings, and property teams that need inquiry routing, viewing coordination, and compliant follow-up.

Property And Estate Workflow

Lead-heavy workflow with viewing schedules, document requests, and communication across multiple agents.

From GBP 5,400/mo5 linked services

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.

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.

Property Viewing Coordinator

Schedules and confirms viewings while preserving buyer or tenant context.

Qualification Follow-Up

Scores fit, asks the next question, and keeps follow-up moving.

Compliance Review

Injects policy-aware approvals and retention checks into risky workflows.

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.

Compliance Ops Pack

Policy-aware agents that stage reviews and retention-sensitive actions.

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.

Compliance Guardrails

Document retention, suppression, and audit expectations before go-live.

Dashboard and reporting

Where teams track the rollout

Lead Intake

Queues, qualification posture, and handoff readiness.

Bookings

Scheduling posture, reminder coverage, and conversion handoff.

Compliance Desk

Approval posture, retention actions, and compliance watchpoints.

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.

Compliance Audit

Surfaces approval posture, export readiness, and retention-sensitive actions.

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

Viewing calendar ownership set

Document request rules approved

Lead-source attribution standardized

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 Ads

This bundle already maps to the shared workspace connection seam for Google Ads.

Google Analytics 4

This bundle already maps to the shared workspace connection seam for Google Analytics 4.

Compliance watchpoints

Review document retention and identity-verification handling

Keep tenancy and buyer communications aligned with suppression policy

Connector requirements

CRM sync

Lead, customer, and pipeline state mapped into the right record system.

Calendar

Scheduling availability, reminders, and appointment routing.

Messaging transport

SMS or WhatsApp delivery, consent handling, and follow-up coverage.

Document store

Policies, files, and retention-sensitive source documents.

Workflow engine

Durable automation orchestration, approvals, and operational handoffs.

Google Ads

Campaign, attribution, and paid-acquisition signal inputs.

Analytics

Conversion and operational reporting inputs for believable scorecards.

Voice transport

Phone routing, missed-call recovery, and transcript capture.

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.

Catalog-driven

Shared catalog, not page-local copy

Services, bundles, pricing posture, workflow links, and form deep links resolve from the same typed service catalog.

Production path

Lead capture stays durable-first

Contact and audit requests still flow through one shared capture service with hashing, rate limits, and downstream dispatch tracking.

Truthful boundary

Delivery state stays honest

Public pages describe scope and rollout inputs, while real workspace activation and readiness remain in dashboard and admin service ledgers.