Dedicated CRM
Not a CRM - fails on status, resolution, scope of work, actual close date, structured lost reasons, schedulable activity types, opportunity reporting
Core objects
In full
Person, Company, Opportunity and Task are separate workspace entities; Opportunity links to Person (pointOfContactId) and Company (companyId), Task links via taskTargets to any of them.
Verification: Verified
Pipeline stages
In full
Opportunity carries a Stage select field and the pipeline is shown as a Kanban board of stage columns; the record itself stores its stage value.
Source: https://docs.twenty.com/user-guide/views-pipelines/how-tos/set-up-a-sales-pipeline, https://docs.twenty.com/user-guide/data-model/capabilities/fields
Verification: Verified
Status
Not at all
Opportunity entity has no status/open-closed field; only name, amount, closeDate, stage, company, pointOfContact, owner exist.
Verification: Verified
Resolution
Not at all
No won/lost field exists on Opportunity, and the default Stage options (New, Screening, Meeting, Proposal, Customer) include no Closed-Won or Closed-Lost stage.
Source: https://github.com/twentyhq/twenty/issues/11598
Verification: Verified
Value
In full
Opportunity has a native `amount` field of Currency type.
Verification: Verified
Scope of work
Not at all
No line-item/product entity and no description field exist on Opportunity; only generic Notes (a separate object usable on any record) can be attached.
Verification: Verified
Expected close date
In full
Native `closeDate` field, described by the vendor as a "projected close date" tracked on the opportunity.
Source: https://docs.twenty.com/user-guide/data-model/capabilities/objects
Verification: Verified
Actual close date
Not at all
Only one closeDate field exists; no separate field or documented behavior captures the date a deal actually closed.
Verification: Verified
Opportunity owner
In full
Opportunity has an `owner` relation to a workspace member, distinct from createdBy/updatedBy.
Verification: Verified
Linked buyer
In full
Opportunity has a `pointOfContact` relation to a Person record, separate from the `company` relation.
Verification: Verified
Record preservation
In full
All workspace entities use soft-delete (deletedAt field on the base entity); records aren't purged when a deal's stage changes.
Verification: Verified
Structured lost reasons
Not at all
No lost-reason field exists on the Opportunity entity, and no lost stage exists to hang a reason off.
Verification: Verified
Email sync
In full
Connects real mailboxes via Google/Microsoft OAuth or IMAP/SMTP; incoming mail syncs in and users can send email directly from Twenty.
Source: https://docs.twenty.com/user-guide/calendar-emails/overview
Verification: Verified
Calendar sync
In part
Documentation states calendar events sync in automatically from the connected Google/Microsoft/CalDAV account onto CRM records; no documented push of Twenty-created events back to the calendar.
Source: https://docs.twenty.com/getting-started/core-concepts/calendar-and-email, https://docs.twenty.com/user-guide/calendar-emails/overview
Verification: Verified
Schedulable activity types
Not at all
Task entity has no type/kind field (just title, dueAt, status, assignee); Calendar Event entity likewise has no type field - no fixed or buyer-defined activity-type set exists.
Verification: Verified
Opportunity reporting
Not at all
Dashboards offer bar, pie, line and aggregate charts on CRM data; no native stage-to-stage conversion rate, win rate, or revenue forecast metric is documented.
Source: https://docs.twenty.com/user-guide/dashboards/overview
Verification: Verified