Built systems
OpenXCEL AI: Give your business an AI coworker with company context.
OpenXCEL AI brings company memory, editable skills, tools and approval boundaries into a business-owned AI workspace. Built around a self-hosted Slack coworker, it gives teams a practical way to organize context and define how delegated work should be reviewed.
About this view
Existing workspace presentation with masked identities.
About this view
Existing setup image. their status is retained.
What it does
- Company-context workspace with retained memory and editable skills.
- Self-hosted Slack coworker setup for business task intake and tool use.
- Connection setup and approval boundaries tied to the intended task and reviewer.
Why it matters
Provides a company-specific foundation for delegating bounded work while keeping context and review responsibilities together.
- where Ahmad reports building and deploying OpenXCEL AI
- 3 agenciesOwner-reported deployment history, not an independent audit.
- reported monthly cost per agency, including hosting in the lower figure
- $3K–$4K → under $600Ahmad’s October 18 account. Not a workload-matched benchmark or a universal savings guarantee.
Technology stack
- Slack
- Self-hosted deployment
Build note
Three agencies. Their own AI coworker in Slack.Source & context
Ahmad's first-person deployment account, confirmed 18 October 2026, and separate product media. Deployment receipts were not independently inspected.
Existing public product images reviewed October 27, 2026. These are not current provider-health or transaction checks. Public release and client-material clearance remain separate.
A business-owned workspace, not another chat tab
OpenXCEL brings skills, company memory, connection setup and review boundaries into a business-owned workspace. The gallery shows the existing published workspace views, with recorded connection status retained.
A coworker needs context and boundaries
The system is described as a self-hosted Slack coworker with company context, scoped memory, tools and approvals. A product presentation of an approval is not itself evidence that a production action ran.
Keep the cost comparison on its actual basis
Across the three agency deployments, Ahmad reports monthly per-agency spend of roughly $3,000–$4,000 reduced to under $600 including hosting. These are reported operating costs, not a workload-matched independent benchmark or a universal saving.
Use genuine views without changing their meaning
The workspace screenshots are existing product evidence with adapted branding and masked identities. The Slack film is a staged product presentation, not a recording of authenticated live Slack work.
Inside the system
- Agency deployment experience Ahmad reported building and deploying the self-hosted Slack coworker for three agencies on 18 October 2026.
- Product working method The presentation describes request intake, editable skills and retained context.
- Separate local walkthroughA recovered -record memory-and-permissions pattern, not an agency workspace or backend permission test.
- Task acceptance Defines the output, reviewer and completion check for the intended workflow.
The handoff
- Bounded task-selection brief
- Skill and context requirements
- Connection authorization scope
- Output and approval acceptance checks
Technology stack
Product delivery channel
- Slack
- Self-hosted deployment
Owner-reported deployment model and existing product presentation.
Not established
- Application framework, database and hosting provider are not established by the available product evidence.
Source & context
| View | Provenance and limitation | Evidence class |
|---|---|---|
| Fig. 1 | OpenXCEL business memory Existing workspace presentation with masked identities. | Workspace view |
| Fig. 2 | OpenXCEL connection setup Existing setup image. their status is retained. | Workspace view |
Ahmad's first-person deployment account, confirmed 18 October 2026, and separate product media. Deployment receipts were not independently inspected.
Existing public product images reviewed October 27, 2026. These are not current provider-health or transaction checks. Public release and client-material clearance remain separate.
Reviewed: 2026-10-27
Map one workflow handoff
Bring one workflow and the output the next person needs. Define its inputs, review decision and completion check before agreeing implementation scope.