Get started with Cromo

The best first Project is small enough to understand and important enough to use. This guide follows a customer-renewal example, but the same path works for onboarding, supplier reviews, internal requests, compliance checks, and other recurring work.

​

Before you begin

You need access to a Workspace and membership in the Project you want to use. A Member can add Sources, review Knowledge, work with Data, and create Workflows. A Viewer can read Project content and use chat, but cannot change operational assets. See Roles and permissions for the complete matrix.

​

1. Choose a Workspace and Project

Use the Workspace switcher to open the correct organization. Create or select a Project with a clear boundary, such as Customer Operations. A useful Project boundary has:

• a recognizable group of people;
• a related set of documents and systems;
• processes that should share context;
• data and automations that should use the same access boundary.

​

2. Add one authoritative Source

Open Knowledge → Sources, then upload the document your team actually follows—for example, a renewal policy or operating procedure. Cromo accepts common documents, spreadsheets, presentations, text formats, and images. A Source upload can be up to 50 MB. See Files and upload limits for the exact list. Wait until processing completes before evaluating the resulting Knowledge.

​

3. Review the proposed Knowledge

Open Knowledge → Review. Cromo may propose a new page or an update to an existing page based on the Source. Before approving it:

• compare the proposal with its source references;
• check dates, thresholds, owners, and exceptions;
• fix wording that is technically correct but operationally ambiguous;
• reject proposals that do not belong in the Project.

After approval, browse the page from Knowledge → Pages or inspect related concepts in Graph.

​

4. Ask a sourced question

Open Chat in Ask mode and try:

Which customer renewals require escalation, and what evidence should the account owner prepare?

Attach the policy page or original Source if the request depends on it. Inspect the citations in the response and open them when a detail matters. You can keep a conversation private or share it with the Project. Pin important conversations so teammates can find them again.

​

5. Teach missing context

If Cromo cannot answer because a rule has never been documented, switch chat to Teach or open Knowledge → Teach. For example:

For enterprise renewals above €100,000, the account owner must start the review 90 days before expiry and include a risk note from Customer Success.

Cromo drafts this as structured Source material. Review and save it, then process any resulting Knowledge proposal as you would an uploaded document.

​

6. Add structure when the list starts changing

Open Data and create a model and table for the records your team needs to update. For a renewal table, useful fields include:

• customer name;
• account owner;
• renewal date;
• contract value;
• status;
• risk level;
• next action.

Use a Knowledge page for the policy and a table for the changing renewal records. They solve different problems.

​

7. Make the work repeatable

Once the team agrees on the process, ask chat:

Create a weekly workflow that finds renewals due in the next 90 days, groups them by owner, prepares a follow-up summary, and records any missing next action.

Review the trigger, inputs, steps, mappings, and expected outputs. Run it manually with safe data before enabling a schedule.

​

You are ready when

• the Project has at least one trusted Source;
• an important Knowledge page has been reviewed;
• chat can answer a useful question with citations;
• changing information has a clear home in Data;
• one recurring process has a tested Skill or Workflow.