Deployment Architecture
How Orbiis is deployed.
This document describes the three deployment configurations Orbiis builds, the operational contexts each is architected for, and the structure of an Orbiis engagement. Specific deployment scope is confirmed in the Revenue Audit.
Operational Contexts
Each deployment is architected for a specific operational context.
Foundation Deployment
Single-location operation with no existing operational system, or a fragmented manual process.
Typically under 25 inbound leads per month.
Lead response, booking coordination, and missed-call recovery are still handled manually.
Best for founder-led teams that need the first operating layer installed quickly.
Full Operational Deployment
Active marketing is generating consistent inbound demand.
Typically 25–100 leads per month across multiple channels.
The team is growing, and manual coordination is beginning to limit conversion.
Best for businesses that need full response, reputation, campaign, and lifecycle coverage.
Multi-Location Operations
Two or more business locations, or sustained volume above 100 leads per month.
Existing tools, teams, or locations are no longer operating from one clear source of truth.
Location-level access, reporting, pipeline visibility, and management need to be unified.
Best for operations that require dedicated architecture and continuous oversight.
Operational context is confirmed in the Revenue Audit. The deployment scope is then specific to the business.
Engagement Structure
An engagement has two components.
Deployment Build
The build of the operational system for the business — configuration, integration, testing, and handover. Scope is confirmed during the Revenue Audit; the figure follows from scope.
Operational Management
Active management of the deployed system: monitoring, optimisation, reporting, operational support. Billed monthly as managed operations, not software access.
Operational usage is measured monthly across communication and execution layers. Each engagement includes a defined operating allowance.
01
FOUNDATION
Foundation Deployment
- Deployment
- From $1,500
- Management
- $397/month
- Timeline
- 10 days
Included monthly
300 AI conversation credits, 500 SMS segments, 3,000 emails, and 30 voice AI minutes per month.
The tools that replace this cost $700–$2,000/month — before paying anyone to build or run them.
Built for single-location businesses that need the first operational layer installed and running.
Response Layer — handles inbound enquiries across web and SMS, around the clock.
Booking Infrastructure — coordinates the appointment lifecycle, from scheduling through attendance.
Missed Call Recovery — immediate outreach on every missed call.
Operating View — pipeline state, lead status, and reporting on a single operational layer.
Scope is confirmed in the Revenue Audit. When the business is ready to expand, every deployed component carries forward — nothing is rebuilt.
02
FULL OPERATIONS
— Primary scaling deployment
Full Operational Deployment
- Deployment
- From $4,500
- Management
- $997/month
- Timeline
- 21 days
Included monthly
1,500 AI conversation credits, 3,000 SMS segments, 15,000 emails, and 150 voice AI minutes per month.
The assembled equivalent — software, AI, campaigns, and an operator — costs $4,000–$10,000/month. Without a deployment methodology.
Built for businesses operating active marketing with consistent inbound volume across multiple channels.
Full Response Layer — all active channels: voice, web, SMS, social messaging.
Reputation System — manages the review surface across platforms: acquisition, monitoring, and resolution.
Campaign Infrastructure — campaign execution across the operational calendar, managed by Orbiis.
Lifecycle Operations — operational coverage from first contact through reactivation.
Scope is confirmed in the Revenue Audit. When the business is ready to expand, every deployed component carries forward — nothing is rebuilt.
03
MULTI-LOCATION
Multi-Location Operations Architecture
- Deployment
- From $8,500
- Management
- $1,997/month
- Timeline
- 30 days
Included monthly
5,000 AI conversation credits, 10,000 SMS segments, 50,000 emails, and expanded voice AI capacity per month.
A part-time RevOps manager costs $13,000+/year in labour alone. This includes the operator, full infrastructure, and quarterly reviews.
Built for businesses operating across multiple locations, or at sustained volume above 100 leads per month.
Unified Operations Architecture — all channels and all locations on a single operational layer.
Revenue Capture — invoicing, recurring billing, and the quote-to-close path.
Location-Level Operating Structure — per-location pipelines, role-based access, and consolidated reporting.
Dedicated operational management — a named Orbiis operator and quarterly strategic review.
Scope is confirmed in the Revenue Audit. Every deployed component carries forward as the architecture expands across locations.
After Deployment
How the business operates with each deployment running.
FOUNDATION
Foundation Deployment
Inbound enquiries enter a structured response layer and are answered within minutes.
Missed calls trigger recovery instead of disappearing into silence.
Bookings remain coordinated from request through confirmation and attendance.
Every new enquiry becomes visible in the pipeline with source and status attached.
FULL OPERATIONS
Full Operational Deployment
Web, SMS, social messaging, and call activity are routed into one operating path.
Review acquisition runs after the service moment, with issue routing handled before public reputation is affected.
Campaign execution runs on a managed calendar instead of ad hoc staff memory.
Every active lead, follow-up, review request, and reactivation path has a visible operating state.
MULTI-LOCATION
Multi-Location Operations Architecture
All locations operate from one architecture while keeping access, pipelines, and reporting separated where needed.
A dedicated Orbiis operator monitors performance and manages operational changes continuously.
Revenue, pipeline, team, and location-level visibility are consolidated into one operating view.
The business no longer depends on individual staff memory to understand what is happening.
Operational Questions
01
What does the deployment build cover?
The deployment build covers the complete construction of the operational system: infrastructure configuration, workflow setup, system testing, and operational handover. This is the work of building the system specific to the business — not an onboarding sequence or account activation.
02
What happens when the operational scope changes over time?
All deployed assets carry forward. Operational architecture, configuration, workflows, and operational state extend with the business — nothing is rebuilt. The conversation about expanding scope happens when operational signals indicate readiness.
03
Is there a minimum term?
No minimum term on monthly engagements. 30-day written notice to cancel. The build itself is non-refundable — it reflects work completed. Annual agreements are available; they include a pricing lock and improved SLA.
04
What is the Revenue Audit?
The Revenue Audit is the first structured conversation in any Orbiis engagement. It maps the current operational state of the business, identifies operational gaps, and produces a deployment proposal specific to the business assessed. Not a generic demonstration.
05
How is the AI trained on the business?
The AI is configured from two sources: a crawl of the business's existing web presence, and a structured set of custom Q&A pairs built during the deployment phase. This covers services, pricing approach, booking logic, hours, location, and common enquiry types. The knowledge base is reviewed and updated as part of ongoing operational management.
06
Does Orbiis replace an existing CRM?
In most cases, yes — the Orbiis operational system becomes the operating CRM. Contacts, pipeline state, communication history, and reporting are managed within the deployed system. If the business has an existing CRM with data that needs to carry forward, migration scope is assessed during the Revenue Audit.
07
Which channels does the system handle — does it include WhatsApp and inbound calls?
Foundation Deployment covers web chat and SMS. Full Operational Deployment adds Facebook Messenger, Instagram DM, and inbound voice AI call handling. Multi-Location Operations Architecture adds outbound voice AI where applicable. WhatsApp is available for UAE and GCC-based deployments where business WhatsApp is active.
08
Is there Arabic language support?
Arabic-language configuration is available for UAE and GCC deployments. This covers the AI response layer, outbound messages, and system communications. Arabic scope is confirmed and scoped during the Revenue Audit.
09
What happens when moving from Foundation to Full Operational?
The upgrade path is structured so that no previously deployed work is lost. The existing capture infrastructure, CRM configuration, pipeline, tags, and workflows carry forward. The upgrade adds the remaining workflows, AI channels, Reputation Engine, and Growth Campaigns on top of the existing base. No rebuild. The conversation about upgrading happens when the operational signals indicate readiness.
10
Who is the operator and how does the business contact them?
Every Orbiis engagement has a named operator responsible for the account. At Foundation and Full Operational, the operator manages the system and is reachable during business hours via the designated support channel. At Multi-Location, a dedicated named operator is assigned exclusively to the account, with a backup operator named for continuity. Operator contact details are delivered at handover.
The Next Step
Deployment begins with a Revenue Audit.
The conversation produces a deployment proposal specific to the business assessed. Not a generic demonstration.