Category 1 · Foundation
Schema & Structure
Is the Attio data model serving you, or fighting you? We look at the shape of your objects, attributes, relationships, and pipelines.
Object bloat
Custom objects with fewer than 10 records — usually abandoned experiments.
Attribute count outliers
Objects with wildly more (or fewer) attributes than peers — tech-debt heatmap.
Suspicious relationship cardinality
Multiselect attributes nobody uses that way, single-value links dense enough to suggest N:N.
Select option sprawl
Status/select attributes with too many options to be meaningfully filtered.
Pipeline stage sufficiency
Deal pipelines with too few stages to separate healthy vs stuck work.
Pipeline modeling ambiguity
Status attributes where the stage names don't line up with the workflow Attio can see.
Versioned object names
"Companies v2" patterns that suggest a migration you never finished.
Required but empty paradox
Fields Attio says are required, but records still manage to have unset.
Archived but populated
Archived attributes with live data — hidden but still drifting.