setup-interview

Configuring an Atomic CRM project without manual errors requires a guided interview that captures requirements across 8 domains and generates a validated configuration file. This structured approach eliminates inconsistent settings and broken workflows.

Requirements gathering for CRM setup is a structured interview process covering business context, custom entities, fields, pipeline stages, user roles, integrations, UI preferences, and deployment settings. It ensures all project needs are captured before finalizing the configuration.

You can resume an interrupted CRM setup interview because the guided workflow applies to new project setups, interrupted interview resumption, and existing configuration updates. It continues capturing requirements across the 8 core domains.

Validating Atomic CRM configuration errors involves running consistency checks to catch issues like duplicate fields or missing pipeline entities. This validation occurs before finalizing the setup and committing the project context file to the repository.

Atomic CRM setup supports removing unused default features through automated cleanup derivation. The interview identifies which default features are unnecessary for your specific project, keeping the instance clean and tailored to your needs.

The CRM guided interview outputs a validated project-context.json file. This configuration file contains all captured project requirements and is automatically committed to your project repository after passing consistency checks.