Say what you need, once.
Your AI assistant and digital staff handle the rest
People state their intent in a conversation. The AI assistant coordinates and confirms; AI digital staff produce the work. Tasks, calendars, meetings, files, reports and org insight settle on one chain — and every write, send and edit happens only after you say yes.
Chat · Work · Meetings · Files · Insight · Admin — six modules, one chain
My assistantPersonalToday 09:30
Front-end scheduling estimate
- Owner
- Chen Chen
- Scheduled
- 2026-07-02 15:00 → 17:00
- Details
- Estimate front-end effort and propose a schedule for the Q3 release plan.
Not another chat app
Conversation is the way work starts, not a place messages go to die. Every intent resolves into an action you can approve.
Not a project board
A task has exactly one owner, and the owner maintains its execution data. Nobody spends their week dragging cards to keep a board honest.
Not an AI left unsupervised
The assistant never sends on your behalf unasked, and digital staff never touch business data directly. The boundaries are in the product, not in a disclaimer.
Roles
Four roles, with the boundaries spelled out
How much AI can do for you depends on what it refuses to do. CreateX splits coordination, production, record-keeping and governance into four layers — and each one states what it does and what it will not do.
Your AI assistant
- Coordinates, organises, reminds
- Drafts cards for you to approve
- Triggers system actions on your say-so
- Never authors business files itself
- Never skips your approval
AI digital staff
- Reads source material in the thread
- Calls skills and models
- Produces file-based deliverables
- Never sends files or messages
- Never edits business data
Work · Meetings · Files · Insight
- Holds confirmed task outcomes
- Holds schedules and reports
- Holds meeting and file data
- Never replaces cross-person confirmation
Company admin console
- Company profile and org structure
- People, roles and capabilities
- Spend and usage
- Never manages platform models or executors
- Never sets global parameters
The chain
One sentence in, one clean chain out
From stating an intent to reading org insight, nothing in between needs to be moved by hand — but one step does need a human to nod.
- 01
State the intent
Say what needs to happen, in one plain sentence, in your assistant thread or a group chat.
- 02
Assistant coordinates
It fills in the owner, the planned time and the details, then drafts a card for approval.
- 03
You approve
Confirm and send, edit, or cancel. A shared task also has to be accepted by its owner before it takes effect.
- 04
It becomes data
Tasks, calendar entries, meetings and file references land where they belong — not buried in a thread.
- 05
Reports and insight
Daily, weekly and monthly reports draft themselves. Managers see outcomes they have rights to, not how you got there.
Step 3 is not skippable. Every action that writes, sends, edits or cancels business data has to be confirmed by a person first — and a shared task only becomes real once its owner accepts it.
Modules
Six modules, one set of data
Not six tools that ignore each other, but six views of one chain: once something is approved, the data lands where it should.
Chat and group threads
Your assistant thread is the long-running conversation you keep with your own AI. Group threads bring several people and their assistants into one space, where receipts, reminders and cross-person approvals all close out.
Work: tasks · calendar · reports
A task is the outcome-bearing object and has exactly one owner. The calendar only tracks time. Reports build on task outcomes and lock read-only once submitted.
Meetings
Meetings own their invites, recordings, transcripts and minutes; what shows up on a calendar is a display copy. Action items from the minutes become tasks directly.
Files
Files you uploaded, files you received and files produced in a thread, all in one place — with preview, download, bulk actions and storage-quota checks. Forwarding adds a visible reference; it never copies the underlying file.
Org insight
A leadership view of what the organisation is actually doing right now: an org graph, each person's primary status, and configurable stat cards — showing only confirmed data you have rights to see.
Automation and projects
Turn the coordination you keep repeating into a rule your assistant drafts from — still executed only on your approval. The project view gathers work that spans modules into one place.
Principles
Six rules that decide whether you can trust it
These aren't taglines. They're constraints the product actually enforces, and every module lines up behind the same set.
Approval comes first
Every action that writes, sends, edits or cancels business data must be confirmed by a person before it runs.
A single owner
A shared task takes effect only once its owner accepts it, and every task has exactly one owner.
Tasks and calendar stay separate
Deliverables, owner, planned start and end, blockers, progress and sign-off belong to the task. Time occupied belongs to the calendar.
One source of truth per meeting
The meeting is the record; its calendar entry is a display copy. It doesn't reach an attendee's meeting list or calendar until they confirm.
Forwarding references, never copies
Forwarding a file adds one visible reference instead of duplicating it, so origin and permissions stay traceable.
Permissions have edges
Managers see confirmed outcomes — tasks, schedules, reports, files — within their rights. They do not see your assistant threads or how the work got done.
Admin & billing
Companies govern their org, the platform governs supply
Two consoles, two jobs. A company governs its own org, capabilities and spend. The platform governs tenants, credits and model cost — and never touches the contents of a company's conversations or files.
Company admin console
- Company settings: profile, activation status, storage summary
- Org structure: department tree, people, positions, digital-staff bindings
- Roles: org-insight visibility and admin governance rights
- Skills and digital staff: what capabilities the company can use
- Spend: account overview, top-up orders, usage detail, credit ledger
Platform operations console
- Tenant activation and status
- Confirming payment on top-up orders
- Credit deduction and balance monitoring
- Model cost, call volume and failure-rate monitoring
- Supplying the skill library, digital staff and executors
- Operations accounts and role permissions
How credits flow
- Platform activates the company
- Company raises a top-up order
- Platform confirms payment
- Credit balance increases
- Credits deducted per company rules
- Platform monitors balance and usage
Not in V1 yet
FAQ
Let's settle the boundaries first
The six questions we get asked most about responsibility, permissions and cost.
How is this different from a chat tool like Slack or Teams?
CreateX isn't trying to be a general chat app. Here a conversation is where work starts, not an archive: every intent ends up as a card you can approve, and once approved it becomes a task, a calendar entry, a meeting or a file — instead of sitting in a message stream waiting for someone to move it by hand.
Will the AI send things on my behalf without asking?
No. Every action that writes, sends, edits or cancels business data has to be confirmed by a person first. The assistant's job is to get the content to the point where one click is all that's left — and that click is always yours.
Can my manager read my conversations with my assistant?
No. Managers see confirmed data within their permissions — task outcomes, schedules, reports, files — not the contents of a report's assistant threads or how the work was carried out. The platform operator likewise never reads a company's conversation or file contents.
How do AI digital staff relate to my assistant?
They do different jobs. The assistant coordinates, organises, reminds and handles confirmation with other people, but never authors business files itself. Digital staff read source material in the thread, call skills and models, and produce file-based results — but never send files or messages or edit business data. Anything going outside still runs through your assistant's approval flow.
How does billing work?
Once the platform activates a company, the company raises a top-up order, the platform confirms payment, and the credit balance goes up. Using AI capabilities deducts credits according to that company's billing rules. The spend console shows account overview, top-up orders, usage detail and the credit ledger.
What's missing right now?
V1 doesn't include plans or annual/monthly bundles, online payment, invoicing and automated reconciliation, company self-signup, or per-company model API configuration. Those are deliberately out of scope for now, so nothing gets built against stale assumptions.
Hand off the coordination.
Keep the approval.
CreateX OrgOps is currently onboarding companies for trials. Tell us your team size and the scenarios you care about, and we'll put together a demo that speaks to them.