Job-focused spreadsheets win adoption
Taimur Abdaal, CEO and co-founder of Causal, on the future of the "better spreadsheet"
The main signal is that spreadsheet infrastructure alone rarely wins, the category breaks open when a tool owns one painful job end to end. Causal got early traction by giving FP&A teams a better way to connect actuals, update models, and share plans. Clay did the same for outbound, and Attio for CRM. By contrast, browser spreadsheets with connectors and dashboards pull in many personas at once, which makes messaging, onboarding, and repeatable sales much harder.
-
Causal itself is the case study for this pattern. It spent about 18 months finding FP&A, then sold into 100 to 500 person companies where finance teams were wasting one to two days each month pulling numbers from systems like NetSuite, QuickBooks, Salesforce, and data warehouses into spreadsheets. That narrow pain made ROI obvious and helped the product spread inside accounts.
-
Equals shows the opposite pressure. It started as a general spreadsheet with live data, then found that broad spreadsheet positioning attracted finance, ops, support, agencies, and other unrelated users. The company later narrowed its funnel to revenue reporting, CRM reporting, and lightweight BI, and pushed dashboards because buyer level executives cared more about a visible company wide output than analyst time savings alone.
-
Clay and Attio are narrower in a more literal workflow sense. Clay is built around building prospect lists, enriching records from 100 plus data providers, and pushing those lists into outbound tools, with usage priced on credits tied to enrichment and AI actions. Attio is built as a programmable CRM system, which gives it a concrete home base inside sales teams rather than a generic spreadsheet wedge.
The better spreadsheet market is likely to keep splitting by job rather than consolidating around one general purpose winner. The companies that compound fastest will be the ones that start with a single repeated workflow, become the default system for that team, and only then expand into adjacent use cases from a position of trust.