Intended use
What this kit is being designed to do
- Define an initial customer model
- Stage and review imports
- Track contact permission and provenance
Business mini-lecture
Create customer memory before the spreadsheet breaks.
Early customer relationships often live in personal inboxes and spreadsheets until duplicate records, forgotten context, or unclear permission creates real risk. A CRM-starter capability defines a small system of record for people, organizations, opportunities, activities, consent, and provenance. It becomes valuable when several conversations or team members require shared memory and a reliable next action.
The agent can validate imports, flag near-duplicates, stage merges, and preserve where each record and permission came from. Humans still resolve ambiguous identities, decide the sales process, and determine whether data may be kept or used. The founder owns the customer model and any live-system change; efficient organization does not justify unauthorized enrichment or silent merging.
Operating contract
Inputs, outputs, and gates
Inputs
- ICP and segment definitions
- Authorized account and contact records
- Consent and do-not-contact requirements
Outputs
- CRM object and field map
- Staged import and merge queue
- Permission and provenance ledger
Gates
- Founder approves the data model
- Human reviewer resolves imports and merges
- Authorized owner approves any system write
Known limits
What this record does not promise
- This is a roadmap placeholder; no CRM candidate or adapter has been runtime-qualified.
- It must not enrich or use contact data from unauthorized sources.
Lineage
Where the intended practice comes from
Derived from the validated 2026-07-29 sales-and-CRM scout bundle; candidate systems remain evaluation targets, not dependencies.
Lineage explains provenance; it does not substitute for a review record, field evidence, or a versioned implementation.