Twenty

What is Twenty?

Twenty is an open-source CRM that provides technical teams with modular building blocks for assembling a custom CRM around complex business needs. Rather than a fixed schema, Twenty lets teams extend its core objects — companies, people, opportunities, tasks, notes, dashboards and workflows — with custom objects, fields and actions generated through an AI chat or defined in code, so the system can be reshaped as the business evolves.

Key Features

• Open-source CRM core: Twenty is presented as "the #1 Open Source CRM," positioning the product as an inspectable, self-hostable alternative to closed CRM platforms for teams that want control over their stack.
• Standard sales objects: Workspaces ship with Companies, People, Opportunities, Tasks, Notes, Dashboards and Workflows, giving a sales team the usual record types without custom development.
• Detailed company records: The companies table carries fields for URL, address, account owner, ICP flag, ARR, LinkedIn, industry, main contact, employee count and linked opportunities, so qualification and revenue context live on the record itself rather than in separate spreadsheets.
• Sales dashboards: A Sales Dashboard sits in the workspace navigation alongside the individual object views, providing a reporting surface over the underlying CRM data.
• AI chat scaffolding: An AI Chat panel inside the editor accepts natural-language instructions. The published example asks Twenty to "scaffold a launch-ops CRM in my workspace with rockets, launches, payloads, customers, and launch sites, with relevant actions for each," and the product generates the corresponding objects, fields and actions.
• Schema identifiers for custom apps: Custom objects and their fields are exposed as stable identifiers in a project file such as src/constants/schema-identifiers.ts, where each object (for example rocket, launch, payload, launchSite) maps to a UUID plus the UUIDs of its related fields. That gives developers reliable references when writing applications against the workspace schema.
• Workspace-based app development: The editor shows a local project directory (~/code/my-twenty-app) with a diff view of changes, indicating a code workflow alongside the in-product AI generation.
• Modular, scalable positioning: Twenty describes itself as modular and scalable, with the stated goal of letting technical teams build an "Enterprise CRM at AI Speed."

Use Cases

• Technical teams outgrowing a fixed CRM: Engineering and RevOps teams with non-standard sales processes use Twenty's building blocks to model their own objects instead of bending a rigid vendor schema.
• Sales pipeline and revenue tracking: A sales organisation tracks companies, contacts, opportunities, tasks and notes in one workspace, with ARR, ICP status, account owner and employee count visible on each company record.
• Developer-built internal applications: Teams that already have a workspace schema can write code against it using the exported schema identifiers, keeping custom objects such as rockets, launches and payloads addressable from an application.
• Rapid prototyping of a new process: A team can describe a new operational domain in the AI Chat — the launch-ops example covers rockets, launches, payloads, customers and launch sites — and get objects and actions created before committing engineering time.
• Dashboard-driven reporting: Managers who need a high-level view use the Sales Dashboard for reporting while the underlying object views handle day-to-day record work.

Who It Is For

Twenty targets technical teams — developers, engineering-led RevOps functions and sales operations staff who are comfortable working with a data model rather than only a settings menu — inside companies whose CRM requirements are too specific for off-the-shelf software. The problem it addresses is the mismatch between a fixed CRM schema and a business that keeps changing: Twenty supplies base objects and then exposes custom objects, fields, actions and schema identifiers so the CRM can be extended in-product or from code.

Pricing

The source material does not publish pricing tiers or figures for Twenty. The site offers a "Get started" entry point for self-serve access and a "Talk to us" / "Book a demo" path for teams that want to discuss an enterprise deployment.

Frequently Asked Questions

What is Twenty used for?

Twenty is used as a customer relationship management system for tracking companies, people, opportunities, tasks and notes, with dashboards and workflows layered on top. Its distinguishing use is as a base for a custom CRM: teams extend the standard objects with their own objects, fields and actions rather than working within a fixed schema.

Is Twenty open source?

Yes. Twenty is described on its own site as "the #1 Open Source CRM for modern teams," and its marketing highlights modularity and scalability as the reasons technical teams choose it over closed alternatives.

Who should use Twenty?

Twenty is aimed at technical teams that need a CRM matching complex or evolving business requirements. Teams comfortable with a data model and with code — the product exposes custom object and field identifiers in project files such as schema-identifiers.ts — get the most from it, while sales users work in the standard company, opportunity, task and note views.

Can Twenty's data model be customised?

Yes. Custom objects, fields and actions can be generated through the in-product AI Chat from a natural-language description, as shown in the launch-ops example covering rockets, launches, payloads, customers and launch sites. Those custom objects are then addressable by identifier in code, so applications and the CRM share the same schema.

How much does Twenty cost?

The source material does not state Twenty's pricing or whether a free tier exists. Teams interested in cost details are directed to the site's "Talk to us" and "Book a demo" options, while "Get started" is the self-serve entry point.