Service guides / AI automation
Scope & boundaries · AI automationCRM data cleanup: scope & boundaries
Define the outcome before requesting a price. Start with a redacted contact export and field rules and plan a proposed deduplication list for review.
Available remotely for local and international enquiries. Platform choice and final scope depend on your requirements.
The project in view
- Start with
- a redacted contact export and field rules.
- Proposed result
- a proposed deduplication list for review.
- A decision to resolve
- different people sharing an email address.
This is a planning example. It does not describe a completed client engagement.
Scope & boundaries for this project
- Map the existing process before selecting automation. Keep a manual route for exceptions.
- Use “a proposed deduplication list for review” as the proposed deliverable; confirm what is included in that description.
- Resolve this boundary early: different people sharing an email address.
Questions to answer together
- Who uses the result, and what decision does it support?
- Which part of the current process is included?
- Which exceptions and adjacent tasks are excluded?
What to have at the end
A bounded scope with an owner, an intended result and explicit exclusions.
Record the decision on different people sharing an email address alongside the source material. If it is still unresolved, identify who can answer it and what work depends on the answer.
Prepare your enquiry
Use this as a starting point. Add your current process, available examples and constraints before sharing.
Send your completed brief to hello@iansamonte.com or visit the main page to discuss your project.