How Cruma works
You steer on the left, the work lives on the right, and everything meets at the artifact.
Cruma is an AI crew that runs the day-to-day of your business. The workspace is the crew’s office, where its work lands and you meet it: you do not run dashboards, build workflows, or read logs. You talk, you review real work, and you approve what matters.
Two sides, one rule
The screen has two sides. Left is where you steer: one conversation with Cruma, scoped to wherever you are. Right is where the work lives: the actual documents, plans, drafts, tables, and briefs.
The most important rule: you and the crew meet at the artifact. You judge work by looking at the finished thing, an email draft, a proposal, a revised plan, never by reading the machinery that produced it.
The gala can absorb 310 guests. The AV request is what breaks your margin floor.
My recommendation: accept the guest increase, and offer the AV package as a priced upgrade instead of absorbing it. Finance has the estimate staged either way.
Three client follow-ups are drafted, grounded in each thread's history.
$9,800 in deposits posted after last week's reminders.
How your business is organized
A workspace is one business. Inside it, the shape is simple, and Cruma only uses the layers your business actually needs:
- Company root: the shared truth that cuts across everything: your profile, goals, brand and voice, people and roles, policies, and the Playbook.
- Rooms: durable areas of responsibility. Sales, Client Work, Finance, Dispatch. Departments are rooms, not separate silos.
- Projects: work with a goal and a lifecycle. “Corporate Gala 2026”, “Website Relaunch”.
- Folders: organization, nothing more.
- Files: stored or referenced material, including things that live elsewhere, like a Gmail thread or a QuickBooks invoice.
- Artifacts: the meaningful outputs the crew or your team creates and you review: a brief, a proposal, a staged table change, a handoff package.
How work happens
Four words carry the whole model:
Skill: a reusable method for doing a job well (“prepare an event proposal”).
Work order: a specific instruction to do that job now (“prepare the revised gala proposal for 310 guests”).
Run: one execution attempt, with a working plan you can watch.
Artifact: what came out, ready for review.
For bigger jobs, Cruma breaks the goal into steps with an explicit working plan: you see what is checked, what is in motion, and what comes next. If a step fails, it fails honestly, in view, and Cruma repairs just that step instead of pretending or starting over.
The four habits
Everything the crew does follows four habits, and you see each one in plain language:
- Do the work: “Cruma prepared the revised gala plan.”
- Check the work: “Checked against latest venue notes, invoice status and the Catering response.”
- Wake up on its own: “Wakes on: invoice overdue, lead quiet 14 days, new client reply, nightly brief.”
- Learn from outcomes: “Cruma learned: confirm venue access before Catering finalizes menus. Keep, edit, or dismiss.” Nothing becomes standing knowledge without your review.
It speaks up
Cruma does not wait to be asked. It watches for events, schedules, and thresholds, and when something matters it brings you what it noticed, what it means, and what it would do, with the sources attached. When the data is thin, it says so plainly instead of guessing.
Next: Your crew, who actually does the work.