Pricing page copy is in review — comments by end of day.
The connected day
Descending into the company
Inside the building
At the desk
On the desktop
QA pass on the new empty states is done. Two small fixes left, both tracked in #qa.
Staging is up for the design review. The link is pinned in this channel.
Thanks, all. Let’s jump on a quick gather and walk through it.
Design review notes are in — can someone own the empty-state copy?
Own the empty-state copy
Back into the office
Out through the window
On the street
On the phone
Tuesday · 18:42 · Hands-free
Evening, Lina.
2 things need you before tomorrow’s stand-up. CO-114 is waiting on your approval. Content migration slips unless the design review moves.
Tomorrow · 09:30 · Gather
Design stand-up
Needs you · 3
- CO-114 · Budget +2% Aquatics scope +QAR 2.5M Approve
- @you · #launch-q3 Sara: “Nav ships Friday?” Reply
- Risk ▲ · Content migration Yusuf is blocked on copy View
Capture
Photo · today 16:30- Ship new nav
- Empty-state copy
- Move design review to Thu
- Unblock content migration
- Voice
- Photo
- Scan
- Cast
- Task
- Ask
Approval
CO-114Lusail Complex · Change order
Aquatics scope
+QAR 2.5M · +30 days
Why: client-requested Olympic pool. Budget headroom 4.1%. Rejecting delays handover by ~6 wks.
ComingAsk at my desk
Assistant · Hands-freeComing
“Push the design review to Thursday and tell the channel why.”
✦ Plan — 2 actions
- 1 Move Design review → Thu 14:00 (all free)
- 2 Post note to #launch-q3 — draft attached
The problem
Companies don’t buy tools.
They accumulate them.
-
9–12
SaaS tools in a typical team’s daily stack — each with its own inbox, search and login.
-
~4 h/wk
lost per person to switching, re-finding context and re-explaining it — “work about work.”
-
0
tools in that stack that can answer “why did we decide this?” — the context lives in the seams.
Illustrative Figures are illustrative of consistent industry findings; the pattern, not the decimals, is the point.
The consolidation map
Every seat Arca can take
-
Team chat
Arca Chat
Channels, DMs, threads, reactions, mentions, files & pins — live today.
Live today -
Video calls
Arca MeetingsLive today
Built-in calls (Gathers) with a persistent mini-window, so work continues mid-call — live today.
-
Project tracker
Arca Projects
Register, boards, timelines, milestones, dependencies, goals.
Coming -
Wiki
Arca Docs
Collaborative editor, wiki, templates, verification & backlinks.
Coming -
File storage
Arca Drive
Versioned files, previews, per-project folders, permissions, retention.
Coming -
Scheduler
Arca Calendar
Team calendar, availability, booking links, meeting-cost awareness.
Coming
Escape hatch, not a cage. One-click importers from your current chat, project and docs tools — and full exports out. Consolidation must be earned. Coming
Product principles
Five rules that keep “all-in-one” from becoming “none-of-it-well.”
Design commitments — the rules every module is built against. Some describe work that is still on the roadmap.
-
One graph,
not ten silos.Every message, task, doc, file, meeting and event is a node with links — a task knows the thread it came from, the doc that specs it, the meeting that decided it. Backlinks and activity are automatic. This graph is what no point-tool can replicate, and what makes the AI layer smart instead of generic.
-
AI woven in,
not bolted on.No “AI tab.” Every surface gets four verbs: assist (draft, rewrite, translate), understand (summarize, search, cite), anticipate (risk, anomalies, briefs) and act (generate, automate, execute with confirmation). One assistant, present everywhere, that reads only what the caller is permitted to read.
-
Humans stay
in the loop.AI produces drafts and previews; people approve. A generated project, an automation, a bulk edit — nothing commits without an explicit confirm, and everything lands in the audit trail. Trust is a feature, and it is designed, not assumed.
-
Fast beats
featureful.The all-in-one promise dies the day the app feels heavy. Instant module switching (the portal shell already does this), one search over everything, keyboard-first, offline-tolerant, and a mobile app that respects thumbs. We ship fewer features that feel instant over more that feel damp.
-
Sovereign-ready
by design.Deployable into a customer’s own cloud; bilingual (Arabic/English, full RTL); data-residency aware; and the AI layer runs on a switch — external provider, zero-retention, self-hosted model, or off entirely. Enterprise and government readiness is an architecture, not a sales slide.
Trust, governance & sovereignty
The AI data boundary —
a dial, not a debate.
Coming The AI layer is not live yet. This is how its boundary is designed.
Control where workspace AI requests may run
Select a mode, or use the arrow keys.
01 / 04
External
Frontier models via API for maximum capability — with zero-training on your data.
02 / 04
Zero-retain
The design goal: nothing persisted by the provider once a call leaves the boundary.
03 / 04
Self-hosted
Open-weight models inside the customer’s tenancy for sovereign deployments.
04 / 04
Off
A real kill-switch: zero external calls, product fully functional without AI.
By design, one gateway carries every AI call — provider-pluggable, quota-metered per workspace, fully logged. Retrieval is permission-filtered before the model ever sees a token.
✦ The act contract
ComingEvery AI action is permission-checked as the caller, previewed before commit, confirmed by a human for anything consequential, and audited. No exceptions.
- Permission-checked
- Previewed
- Confirmed
- Audited
“Close these 4 tasks, move the milestone, notify the channel” — every step permission-checked against your role, previewed, confirmed, audited.
What the customer can verify, not just believe
Design commitments for the AI layer.
- Provable scope
- Ask the copilot as a guest and as an admin — watch the answers change with permissions.
- Provable audit
- Every AI action in the same audit stream as human actions, exportable.
- Provable exit
- Run the full export any day; the data leaves clean, structured and complete.
The road
Three horizons,
each one shippable.
✦ marks where the AI layer plugs in. Every ✦ item is still to come.
Horizon 1
The proven core
- Channels, DMs, threads, reactions & mentionsLive today
- Files, links & pins inside chatLive today
- Built-in calls (Gathers) with mini-windowLive today
- Unified inbox & notificationsLive today
- Org directory, teams & departmentsLive today
- Global searchLive today
- Workspaces, roles & MFALive today
- To-dos inside chatComing
- Collaborative docs with folders & templatesComing
- Single sign-on (SSO)Coming
- Mobile foundationsComing
Horizon 2 Coming
Work & memory
- Projects: register, boards, timeline, milestones
- Tasks as first-class citizens · My Tasks
- Home dashboard & company pulse
- Drive: versions, previews, per-project folders
- Calendar + booking links
- ✦Copilot v1 (ask + summarize + catch-me-up)
- ✦Morning brief & channel digests
- ✦Meeting transcription → minutes → tasks
- ✦Brief → project generation (HITL)
- ✦Delay-risk v1 (explainable)
- Importers from your current chat, project and docs tools
Horizon 3 Coming
The intelligent whole
- Casts studio: async video with ✦ intelligence
- Whiteboards & intake forms
- Automations builder + recipe library
- ✦Plain-language automations & agents
- ✦Semantic search & org memory (RAG)
- ✦Document understanding & auto-filing
- ✦Anomaly, workload & freshness signals
- ✦Copilot write-actions across modules
- Goals/OKRs & portfolio intelligence
- Public API, webhooks & app surface
- Self-hosted AI option for sovereign deals
Why this wins
One space. One graph. One assistant.Coming
Stop renting your workflow from six vendors. The suite always wins when the seams cost more than the features.