account-scoring
Account scoring
State: to-be-approved. Deploy-verified against a live workspace: not yet. Treat Done when
below as the acceptance test and review cargo-ai cdk plan before deploying. Make no outcome claim
for this skill until it is approved.
The outcome
Every account scored against your ICP, tiered, and written back to the CRM with the rationale, so a rep can always see why an account is tier A. The criteria are not point weights in code: they are the ICP markdown in your context repo, versioned in git and shared with every other agent. Edit the ICP and accounts re-score against it as they come due.
Two failure modes worth knowing before you start. If the CRM properties do not exist, the run
looks successful and the scores land nowhere, which wastes the whole batch. And cargo_score plus
cargo_tier must be selected as columns on the accounts model, or the tier segments filter on a
column they cannot see.