CRAIM performs best when the workspace is configured as an operating system for the revenue team, not just as a list of contacts.
Company setup
At the company level you should define:
- legal or brand name
- primary working language
- default currency and commercial context
- owner or founder context for escalations
Team setup
Use team setup to define who owns real execution and who reviews AI output.
Recommended roles
- founder or executive reviewer
- sales manager
- operator or SDR
- RevOps or admin
Why this matters
The product already supports authenticated users, invitations, settings, and company-scoped access. If ownership is vague, inbox handling, task routing, and approval queues become noisy.
AI workspace setup
The AI workspace is where CRAIM stores operational memory and source documents for the company.
Start with:
- company profile
- buyer profiles
- offers
- objections
- pipeline rules
- tone of voice
- SLA expectations
Evidence-first rule
Do not ask AI to act confidently where the workspace is still empty.
Good setup means:
- core offers are documented
- objection handling is documented
- qualification signals are documented
- tone of voice is documented
Bad setup means:
- prices only live in random notes
- qualification logic lives only in a founder's head
- AI is expected to infer unsupported claims from message history
Team onboarding checklist
For sales managers
- verify pipeline stages
- verify assignment logic
- verify approval expectations
For operators
- review inbox workflow
- review lead and task states
- understand what AI suggestions mean and what is still manual
For admins
- configure integrations
- validate webhook and OAuth paths
- check access boundaries
Production readiness signal
You are ready for broader AI automation when:
- channels are connected
- lead intake is creating records correctly
- the AI workspace contains real business evidence
- reviewers can approve outbound quickly
- reporting and analytics reflect actual operations