ClickUp Shared Work Layer Strategy
Tommy Wang, Chief Business Officer at ClickUp, on the rise of the all-in-one
This advice reflected the old software playbook, where startups won by doing one job better than anyone else. In work software, that meant building tightly for one team, like engineers in Jira, sales in Salesforce, or HR in Workday. ClickUp bet the opposite, that a shared work layer across tasks, docs, chat, goals, and automations would matter more than a tool tailored to one persona, because companies were already drowning in disconnected apps and duplicate data.
-
The practical tradeoff is flexibility versus preset workflow. A vertical tool ships with built in assumptions about fields, approvals, and reports for one function. ClickUp instead built common building blocks, like hierarchy, custom fields, multiple views, and automations, so marketing, product, IT, and agencies can all shape the same underlying system to fit their work.
-
This is why ClickUp compares more naturally to Notion, Airtable, and Monday than to Rippling or HubSpot. Rippling and HubSpot expand outward from a core record, employee data or customer data. ClickUp expands from work data itself, meaning tasks, docs, conversations, goals, and time tied together in one graph that many teams can use at once.
-
The market moved toward ClickUp's view as buyers started cleaning up app sprawl. ClickUp says it often lands through project management, forms, dashboards, or OKRs, then spreads across departments. Its broad package and single seat price also make consolidation easier to justify than stitching together separate vendors for chat, docs, whiteboarding, and task management.
The next step is not simply becoming broader, but becoming the default interface where different kinds of work data meet. As AI makes it easier to pull actions, answers, and workflows out of one shared system, horizontal products with flexible data models are positioned to absorb more of the jobs that used to require separate apps for separate teams.