Operator docs

Practical docs for owners and teams.

How Zora works before a pilot: what connects, what needs approval, what workers can do, and how business data stays bounded.

How a pilot runs

We map one business workflow, connect approved sources, build the Company Brain, deploy one scoped worker, then review outputs with your team before expanding.

What data connects

WhatsApp exports or approved channels, Excel sheets, Tally exports, PDFs, folders, CRM records, website forms, email, product files, quote history and supplier notes.

Approval rules

Risky actions such as sending a quote, changing a price, messaging a customer or updating an important status can require human approval. You decide which ones during the data map.

Deployment models

  • Zora Managed, for fast pilots with clear source approvals
  • Local Connector, for approved office folders and systems
  • Private deployment, for stricter data, hosting or integration needs

Security and privacy

  • Data boundaries are mapped before anything connects
  • Worker tools are allowlisted
  • Every important action is logged
  • Owners can stop, correct or escalate any worker
  • Private client names and data are never used in public demos

Example worker spec

A worker has a job description, not unlimited freedom. This spec is illustrative; real specs are written after the pilot data map.

worker: lead_worker
purpose: Capture new enquiries and prepare next steps for sales review.
allowed_topics:
  - product enquiry
  - buyer contact details
  - quantity and timeline
  - previous quotation lookup
blocked_topics:
  - legal commitments
  - final price discounting
  - payment disputes
allowed_tools:
  - approved_whatsapp_inbox
  - lead_register
  - quote_history_search
  - task_draft_queue
human_approval_required:
  - send_customer_message
  - create_final_quotation
  - mark_lead_lost
  - change_discount_or_margin

FAQ

Does Zora replace staff?

No. It gives staff a helper that remembers the rules, drafts faster and keeps handoffs clean.

Can it send messages automatically?

Only if the agreed workflow allows it. Most pilots keep external sends behind approval.

Do we need perfect data?

No. The pilot starts by cleaning and structuring one workflow enough to be useful.

What do the status labels on products mean?

LIVE is sold and running for customers. PILOT is running with a small number of sites. BETA is usable but still changing. IN DEVELOPMENT is being built. LAB is an experiment. ROADMAP is planned. SERVICE is work we do with you.

Credits

This site uses open-source libraries, vendored locally.

  • Paper ShadersDithering, LiquidMetal and PulsingBorder WebGL shadersApache-2.0
  • GSAP + SplitTextHeadline revealGSAP standard licence
  • AtroposDepth on the Company Brain cardMIT
  • NumberFlowAnimated counts and pricesMIT
  • Rough NotationThe hand-drawn underlineMIT
  • Anam JS SDKLive AI Avatar demoMIT
  • Sora, JetBrains MonoTypefacesOFL-1.1

Direction informed by Teknium’s field guide to uncommon web libraries.