Data quality and cleanup
Duplicates, missing owners and inconsistent field meanings can need review before automation. Agree merge rules and a preview rather than treating every matching email as the same inquiry.
Scope and cost guide
A form connection and a CRM overhaul are different scopes.
Make the desired improvement specific before comparing estimates. Record count alone does not describe the work.
Reviewed October 16, 2026 ยท Faith Forge Labs
Routing and exceptions
One owner and one form are simpler than several territories, absences and round-robin rules. Include unmatched records, reassignment and permission differences in the scope.
Connected systems
Forms, calendars, email and other tools each have access requirements and limits. Identify which system owns each field and what should happen when a connection is unavailable.
Reporting definitions
Agree what captured, qualified, answered and won mean. A report needs the relevant events or staff updates; it cannot fill gaps with assumptions.
A useful first phase
One source can create a record, assign it or place it in an exception queue, and show staff the next action. Prove that path before expanding to every source or historical record.
Prepare the CRM name, safe sample fields, approximate volume, current rules, access owner and deadline. A written estimate should state exclusions, testing, release and ongoing responsibilities.