Skip to main content
Cromo is a chat-first workspace for turning the way your team works into an operational system. You can begin with a question or outcome in plain language, then preserve what matters as shared knowledge, structured data, a dashboard, a reusable skill, or a workflow. You do not need to model the whole business before you start. Add the context for one real process, use it with your team, and make the system more formal when the work becomes repeatable.

​
The Cromo model

Cromo keeps three kinds of information connected: Chat works across these layers. Dashboards make the current state visible. Process Skills preserve reusable instructions. Workflows execute repeatable processes and keep a run history.
Sources, Knowledge, and Data are complementary. A policy PDF can remain as evidence, become a concise Knowledge page, and define fields used in a structured compliance table.

​
How work moves through Cromo

1

Bring in context

Upload documents, connect an application, or teach Cromo directly in chat.
2

Review what Cromo learned

Inspect generated Knowledge pages, check their source references, and approve or improve proposed changes.
3

Use the context in chat

Ask sourced questions, draft deliverables, or describe the operational outcome you need.
4

Make repeated work durable

Add a data model and table, publish a dashboard, create a Process Skill, or compile the process into a workflow.
5

Monitor and improve

Review dashboard state, workflow runs, failures, and changes to the underlying knowledge.

​
Where work lives

Everyday work lives in a Project. A Project keeps its conversations, Sources, Knowledge, Data, Dashboards, Skills, Workflows, integrations, and members together. Projects belong to a Workspace, the organization-level home where roles and access are managed.

Get started

Build a useful Project from one real business outcome.

Sources and Knowledge

Understand how evidence becomes reviewed, usable context.

Data and Dashboards

Track changing records and turn them into an operational view.

Workflows

Run repeatable work manually, on a schedule, by webhook, or from an event.

​
A concrete example

A customer operations team can upload its renewal policy, review the generated Knowledge page, create a table of customer renewals, ask Cromo to publish a dashboard of upcoming expirations, and create a weekly workflow that prepares follow-up actions for each account owner. The same context supports the answer, the view, and the automation—without losing the source material behind it.
Cromo helps your team organize and execute work, but important answers and automated actions still need appropriate human review. Check citations, permissions, inputs, and outputs before relying on them for a business-critical decision.