Start with one customer journey
Choose an example that involves more than one team: a new enquiry becoming a proposal, a signed project reaching its first invoice, or a support question returning to an account manager. Write down who acts next, what they need to know and where that information currently lives. The implementation guide helps turn this example into a manageable first release.
Prepare the decisions that affect scope
Migration, integration and permissions deserve attention before a launch date is agreed. A clean contact spreadsheet does not explain every relationship between companies, projects, invoices and historic correspondence. Use the migration checklist to identify those relationships, and the integration guide to agree which system owns each type of information.
Keep the evaluation honest
Ask to see the workflow that matters to you and record any dependencies, optional modules or configuration work. For regulated or sensitive work, discuss the actual service arrangement, data handling and available evidence. Our security questions guide provides a starting point; sector-specific obligations still need review by the people responsible for your organisation.