Applications

The apps that run on Vavan Core — each a surface over the same shared model of your business.

Vavan applications are not separate products with separate databases. They are surfaces over the same ontology. Every app reads and writes the same typed objects — Accounts, Contacts, Orders, Sites, Routes, Products — so data flows between them with no point-to-point integration to build or maintain. A change made in one app is immediately visible, and actionable, in every other app that touches the same object.

Because of this, you don't have to adopt everything at once. Start with one app — most operators start with the CRM — and grow into the rest as you need them. The CRM is one app on the platform, not the platform itself.

Note. Every app is multi-organization. All reads and writes are scoped to your organization and enforced by row-level security, and each organization uses its own per-organization credentials. See Security & isolation.

The applications

Each app focuses on a part of your operation but operates on the shared object model. The table below lists what each app does and the primary object types it works with.

Application	What it does	Primary objects
CRM	Pipeline, accounts, contacts, and deals, with signals and next-best-actions surfaced against each account.	`Account`, `Contact`, `Order`, `Signal`, `Task`
Dispatch	Delivery routing and ETAs, the driver app, and geofence-based auto-arrival.	`Order`, `Route`, `Stop`, `Driver`, `Vehicle`
Dock	Warehouse fulfillment and pick-pack, on a mobile app for floor staff.	`Fulfillment Order`, `Product`, `Line Item`
Service	Field-service technicians and work orders, on a mobile app.	`Work Order`, `Site`, `Technician`
Maps	Territory and field view of accounts and prospects on a map.	`Account`, `Site`, `Prospect`
Markets	Market and competitor intelligence over a shared public market layer (Vavan World), kept behind the organization data wall.	Public market layer
Stores	Product catalog plus an embeddable storefront and client portal for ordering.	`Product`, `Order`
Sales App	Mobile-first PWA for reps in the field, with an AI coach over the same pipeline data.	`Account`, `Contact`, `Task`
Client Portal	White-label customer portal where your customers see their own orders and account.	`Account`, `Order`
Sequences	Multi-step outreach cadences against contacts and accounts.	`Contact`, `Task`
Analytics	Pipeline, revenue, product, and team rollups computed over the shared objects.	All object types
Ask Vavan	The in-app AI assistant that answers questions and takes actions on your behalf.	All object types

Ask Vavan

Ask Vavan is available inside every app. It can answer questions about your business — read across accounts, orders, signals, and more — and it can also take actions: create a contact, add an order, set a task. It does this by invoking the same governed action types a person would use, so everything the assistant does is validated, permission-checked, and audited exactly like a manual action. The assistant never bypasses Vavan Core.

How apps share data through Vavan Core

Because apps share objects rather than copy them, a single piece of work moves across the platform without any integration code. A concrete example:

The CRM's opportunity engine raises a reorder Signal on an Account — a customer is due to reorder.
A rep (or Ask Vavan) acts on the next-best-action and creates an Order against that same account.
Dispatch picks up the order and turns it into a Stop on a Route, assigned to a Driver and Vehicle.
Dock sees the order's Line Items and presents them as a pick to warehouse staff for pick-pack.

The same Order object is referenced at every step. Nothing is re-keyed and nothing is synced between apps, because there is only one record. That shared model is what makes the apps behave like one operating system rather than a bundle of tools — read more in the ontology overview and the platform architecture.