CSV Data Format Guide
Our AI Concierge can handle many different formats, but following these guidelines ensures the most accurate analysis.
Essential Columns
Revenue
RequiredThe inflow of money from the customer. Can be MRR, ARR, or total billing for the period.
RevenueSalesMRRAmountInvoicedCost
RequiredThe direct costs associated with serving this customer (COGS). Do not include fixed overhead.
CostCOGSExpensesDirect CostVariable CostIdentifier
A unique ID or Name for each customer. If missing, we'll use the row number.
Customer IDCompany NameAccount NumberEmailOptional Metadata (Highly Recommended)
Adding metadata allows our AI to find patterns in your segments (e.g., “Enterprise customers in Fintech are 20% more profitable”).
Plan / Tier
The subscription level of the customer.
PlanTierLevelSubscriptionIndustry
What industry the customer belongs to.
IndustryVerticalSectorRegion
Geographic location of the customer.
RegionCountryStateTerritoryOptional Cost Drivers
Use these optional fields when you have support, infrastructure, onboarding, or success usage data. They do not replace the cost column today, but they preserve the drivers that explain why a customer is expensive to serve.
support_tickets
Support tickets or cases opened by this customer during the period.
support_tickets0, 3, 18support_hours
Support or service desk hours spent on this customer.
support_hours0.5, 4, 22onboarding_hours
Implementation, setup, training, or onboarding hours for this customer.
onboarding_hours0, 8, 40csm_hours
Customer success or account management hours spent during the period.
csm_hours1, 6, 15api_calls
API requests, AI calls, or metered compute events attributed to the customer.
api_calls1000, 250000storage_gb
Storage used by the customer in gigabytes.
storage_gb5, 120.5seats
Paid or active seats/users associated with the customer.
seats3, 25, 200workspaces
Workspaces, environments, tenants, or instances maintained for the customer.
workspaces1, 4, 12integrations
Customer-specific integrations or connected systems to support.
integrations0, 2, 7sla_tier
Service level commitment, such as standard, premium, or enterprise.
sla_tierstandard, premium, enterpriseimplementation_complexity
Relative setup complexity or custom implementation burden.
implementation_complexitylow, medium, highData Quality Best Practices
- 1
Use consistent headers
Keep your headers in the first row. The AI is smart, but clear names like “Revenue” are always preferred.
- 2
Clean your numbers
Remove extra symbols like $ or commas if possible, though our parser handles most currency formats automatically.
- 3
Ensure data is periodic
All rows should represent the same time period (e.g., Monthly or Annual) to ensure the profit curve is mathematically sound.
Ready to start?
Download our pre-formatted template to ensure your data is perfect.