CRM Evaluation Matrix

Act! keeps contacts, organizations, opportunities and activities as separate records that link together, though the opportunity's links to organization and activity weren't directly documented.||An Act! opportunity moves through the ordered stages of a sales process, and an administrator defines each process and its stages, each stage with its own probability.||Act! gives every opportunity its own Status box holding Open, Closed - Won, Closed - Lost or Inactive, so you can see whether it's still live without checking its stage.||Act! records won or lost as two of the values in the same Status box that says whether the opportunity is open, so the outcome is read off the status rather than held in a field of its own.||Act! carries pricing and totals through from the products on the opportunity, giving both a weighted total and a grand total.||Act! gives the opportunity a Products and Services tab where you list each item with its name, item number, quantity, price and discount.||Act! has an Est. Close Date field for when you expect an opportunity to close, kept separate from the Close Date recorded when it actually closes.||Act! sets the Close Date itself when the status changes - closing asks only for a status and an optional reason - and clears it again if the opportunity is reopened.||Every Act! opportunity has a Record Manager field, which names the user responsible for it.||An Act! opportunity must have a contact attached, with a separate Associate With setting for the organization or group.||Closed Act! opportunities stay in the database, can be filtered by status and reopened, and feed won and lost reports, though the pipeline chart shows open ones only.||Act!'s documentation didn't establish either way whether a reason can be recorded against a lost opportunity, as a structured field or as free text.||Act! sends mail to contacts from its Write menu and automatically files sent and received Gmail and Outlook messages as history on the contact, rather than showing a mailbox.||Act! syncs its activities both ways with Google and Outlook calendars, with settings for sync preferences, conflicts and running the sync automatically.||Act! ships Call, Meeting and To-Do activities, schedules them against contacts with several attendees invited, and lets you create your own activity types as well.||Act! documents a forecast with a probability-weighted report, but its current documentation couldn't be read, so the other two required reports weren't established either way.

CRM; structured lost reasons, opportunity reporting unresolved

ActiveCampaign keeps opportunities, contacts, organizations and tasks as separate records, with the organization optional on an opportunity and tasks attaching to contacts and opportunities.||ActiveCampaign pipelines are ordered columns of stages that an opportunity is moved through, and you can have as many pipelines as you like, each with its own stages.||Every ActiveCampaign opportunity carries its own open, won or lost status, separate from its stage, so moving it along the pipeline leaves it open until you close it.||ActiveCampaign reads won or lost from the same status that says whether the opportunity is still open, rather than from a separate field of its own.||An ActiveCampaign opportunity must be given a value, and it has its own currency field alongside it.||An ActiveCampaign opportunity has only a general Deal Description box - there are no products or line items on it.||ActiveCampaign ships a Forecasted Close Date field on every opportunity, and it can't be deleted.||ActiveCampaign keeps the date an opportunity was marked won or lost itself, but surfaces it through reporting rather than as a plainly named field on the record.||Every ActiveCampaign opportunity has a Deal Owner field, which names the user who manages it.||Every ActiveCampaign opportunity must have a primary contact, and further contacts can be added alongside it.||Won and lost ActiveCampaign opportunities stay in the database, can be listed by status, and feed the Deal Overview and Deal Forecast reports; nothing describes closing as deleting them.||ActiveCampaign ships no lost reason field, so you set one up yourself as a dropdown, which is then filterable and reportable, and nothing makes it compulsory at close.||A user connects their own Gmail, IMAP or Exchange mailbox to ActiveCampaign, and mail sent and received then appears on contact and opportunity records, visible only to that user.||ActiveCampaign's Calendar Feed publishes unfinished tasks to Google, Apple or Outlook calendars one way only - changes made in the calendar never come back.||ActiveCampaign tasks are created from an opportunity or contact with a due date and an assignee, and administrators define their own task types such as call, email or meeting.||ActiveCampaign reports win rate by count and by value and forecasts the pipeline by period, but no shipped or custom report measures conversion from one stage to the next.

CRM

Airtable does not ship any built-in opportunity, contact, company or activity records - a buyer builds every table and field from scratch or from an editable template.||There's no built-in sales stage sequence - a buyer has to define and order the stages themselves.||Whether a deal is open or closed isn't a built-in value - a buyer has to add and maintain that field themselves.||Won versus lost isn't a built-in value - it's a field a buyer has to create and keep updated.||There's no built-in deal-value field - a buyer has to add a currency field to their own table.||Nothing built-in records what's being sold - a buyer has to design that structure themselves.||There's no built-in expected close date - a buyer adds a plain date field and names it themselves.||There's no built-in actual close date - a buyer adds a plain date field and names it themselves.||There's no built-in deal owner field - a buyer adds a collaborator field to their own table.||There's no built-in link from a deal to a contact - a buyer sets up that link themselves between tables they create.||There's no built-in closed-deal state, so there's nothing vendor-documented about how closed records are kept for reporting.||A buyer can add a dropdown lost-reason field that Airtable's grouping and summary tools can count.||Airtable doesn't connect to a real mailbox - its email-related tools only import spreadsheet attachments or run through a third-party automation tool.||Google Calendar events flow into Airtable automatically, but changes made in Airtable don't flow back out to the calendar.||There's no built-in set of schedulable activity types - a buyer has to build that structure themselves.||There's no built-in win rate, conversion rate, or forecast reporting for deals - nothing ships to calculate them from.

Not a CRM - fails on core objects, pipeline stages, status, resolution, value, scope of work, expected close date, actual close date, opportunity owner, linked buyer, record preservation, email sync, schedulable activity types, opportunity reporting

Apptivo keeps opportunities, contacts, customers and leads as separate apps with activities attached, though an opportunity can be linked to only one customer, chosen as it's created.||Apptivo opportunities carry a Sales Stage from a list the administrator names and drags into order, and stages can require criteria to be met before entry or exit.||An Apptivo opportunity has no open or closed indicator of its own - whether it's still live is carried only by the wording of the stage, such as one named Closed Won.||Apptivo records won and lost only as stage names, with no won, lost or outcome value on the opportunity and nothing marking a stage as the winning or losing one.||Apptivo records what an opportunity is worth in an Amount field, with its own currency code alongside it.||An Apptivo opportunity has only a general Description field - there are no products or line items on it.||The Close Date field on an Apptivo opportunity is documented as the date on which it's estimated to close.||Apptivo's Close Date holds the estimated date, and the vendor's own answer is to build an automation that resets it to today when the stage becomes Closed Won or Closed Lost.||Every Apptivo opportunity has an Assigned To field, which picks the employee the opportunity is assigned to.||An Apptivo opportunity has a Contact attribute linking it to a person, separate from the Customer link to the organization.||Closing an Apptivo opportunity is an ordinary stage change, so it stays in the lists and keeps feeding pipeline, stage performance and loss analysis reports; deleting is separate.||Apptivo has a configured list of Loss Reasons to pick from, each with its own chart color and the option to note the competitor and extra comments.||Apptivo files incoming mail against the matching record and sends mail out from the connected mailbox, but nothing documents mail sent from the user's own client coming back in.||Apptivo syncs its events both ways with Office 365 and Google calendars once sync is switched on, so an event created in either place turns up in the other.||Apptivo schedules events, tasks, follow ups and call logs against any record, covering meetings, calls and internal work, but the set is fixed and no new type can be defined.||Apptivo reports counts of won, lost and stage moves but gives no win rate, no stage-to-stage conversion and no forecast, and its report builder offers no percentages.

Not a CRM - fails on status, resolution, actual close date, opportunity reporting

Attio ships organizations, people and opportunities as separate records, with tasks and logged meetings that link to any of them, and the organization link on an opportunity is optional.||An Attio opportunity must carry a stage, drawn from an ordered set you can reorder or extend, dragged between columns on a board and used to work out conversion in reports.||An Attio opportunity carries only six built-in fields, none of which says whether it's still live - that's signalled only by the wording of the stage title, which can be renamed.||Won and Lost are only stage names in Attio, with no recorded outcome on the opportunity and nothing marking a stage as the winning or the losing one.||Attio ships a value field on the opportunity as standard, holding what it's worth as a currency amount.||Attio's opportunity ships with no description, no products and no line items among its built-in fields.||Attio ships no close date field on the opportunity, so as standard there's nowhere to record the date it's expected to close.||Attio ships no date field of any kind on the opportunity, and its own reporting guidance assumes the buyer creates and fills in a close date field themselves.||Attio ships a Deal owner field on the opportunity as standard, and it points at a person in the workspace.||Attio ships an associated people field on the opportunity as standard, kept separate from the associated company field.||Closing an Attio opportunity is only a change of stage with no archiving, so the record stays put and still feeds the Stage changed and Funnel reports.||Attio ships no lost reason field, so you create one yourself as a dropdown, which Attio's own template expects, after which it's structured, filterable and reportable.||Attio connects a Gmail or Microsoft 365 mailbox and pulls in past and future mail including sent items, and mail written inside Attio goes out through that same account.||Attio pulls events in from Google or Outlook calendars onto person and organization records, but nothing it documents writes an event back out to the calendar.||Attio tasks are scheduled against records with a due date and assignees, but they carry no type or category, and their text can't be filtered or reported on.||Attio reports stage-to-stage conversion and win rate through its Funnel report, but has no forecast report and ships no expected close date to drive one from.

Not a CRM - fails on status, resolution, expected close date, actual close date, schedulable activity types

Bigin has all four record types - the pipeline record is the opportunity, and it can be linked to an organization, to contacts, and to tasks, events and calls.||Bigin pipelines are built from named stages you drag records between, up to 25 of them, and rules can block a move until named fields have been filled in.||A Bigin opportunity only records which stage it's on - whether that stage counts as open, won or lost is held in the stage's own settings, not on the record.||Won and lost are also read from the stage in Bigin - you drag the record onto a Won or Lost target to set its stage, as no outcome field exists on the record.||Bigin ships an Amount field on the opportunity, holding the money expected once it closes.||Bigin lets products be attached to an opportunity, so what is being sold is recorded on the record itself.||Bigin ships a Closing date field on the opportunity, which the vendor defines as the expected closing date.||Bigin has no field for the date an opportunity was actually settled - the only date is the expected closing date, and the Timeline tab is a history trail, not a field.||Bigin ships a Pipeline Record Owner field on the opportunity, naming the user it's assigned to.||Bigin ships a Related contacts field on the opportunity, separate from the organization name, linking it to a person.||Closing a Bigin record moves it to a closed stage rather than removing it, so won and lost opportunities stay in the pipeline and can be filtered out of the working view.||Bigin ships no lost reason field, but you can build one as a custom drop-down, require it before a record moves stage, and group a dashboard chart by it.||Bigin connects your mailbox so incoming mail and mail sent from Bigin show on the record, but the vendor never states that mail sent from your own mail app is pulled back in.||Bigin syncs events both ways with Google, Microsoft 365 or Outlook calendars, so adding one in either place updates the other, although recurring events aren't synced.||Bigin schedules tasks, events and calls against records, but those three types are fixed and no new type of your own can be created.||Bigin has no ready-made sales reports - you build charts on a dashboard, and with no percentage or ratio measure there's no conversion rate, win rate or forecast.

Not a CRM - fails on status, actual close date, opportunity reporting

Bitrix24 keeps deals, contacts, companies and activities as separate records that link to each other.||Stages carry their own order, and every deal records which stage it is in.||Whether a deal is open or closed is its own field, separate from which stage it is in.||Win or loss isn't its own field - it's read from which stage group the deal's stage belongs to.||Deals carry a shipped money field for the deal's value.||Deals can carry a structured list of products, not just a description box.||Deals ship a native close-date field used as the target completion date.||There's no native field that records when a deal actually closed.||Deals have a responsible-user field that's separate from who created the record.||Deals link to a contact person separately from the linked company.||Closed deals stay in the system and feed the reporting tools.||There's no shipped lost-reason field, but a custom one can be built and used in some reports.||A connected mailbox syncs mail into the CRM both ways and lets you send from inside it.||Calendar events sync both ways with Google Calendar.||You can define your own activity types, not just the built-in call/meeting/task set.||Native reports cover stage conversion rate and a weighted forecast, but not a clear win-rate report.

Not a CRM - fails on actual close date

Breakcold has opportunities, people and tasks as their own records, but an organization is a lead record flagged as a company rather than a record in its own right.||Breakcold pipelines are built from ordered stages you add, rename, color and drag into the order you want, and records move through them.||A Breakcold opportunity doesn't itself say whether it's live or settled - that's set on the stage, which is marked Deal Won, Deal Lost or Default.||Won and lost are likewise a property of the stage in Breakcold, chosen while editing the stage rather than on the individual opportunity.||Each Breakcold opportunity is tracked with its own value, and the currency a pipeline uses can be set.||Breakcold offers only notes on each opportunity - there's no field for what is being sold and no line items.||Breakcold has no expected close date on the opportunity - only a manually set percentage chance of closing.||Breakcold's documentation doesn't establish either way whether the date an opportunity was settled is held in a field.||Breakcold opportunities carry an owner, which can be assigned one at a time or to many records at once.||A Breakcold opportunity can be linked to a contact as well as to an organization, so a named person can be attached to it.||Won and lost opportunities stay in Breakcold in their stage, and its pipeline analytics count opportunities created, won and lost and the average value of those won.||Breakcold has no lost reason field, and the reason written into a deal note doesn't appear in any of its pipeline analytics, so whether a loss reason can be counted at all couldn't be established either way.||Breakcold connects a Google, Microsoft 365, Outlook or IMAP mailbox and syncs mail sent and received outside it onto the matching contact, and you can send from inside it too.||Breakcold pulls meetings in from a connected Google or Outlook calendar and files them against the matching lead, but it can't create or update invites, so nothing goes back out.||Breakcold tasks can be scheduled, assigned and made recurring, but nothing records what kind of work a task is, so a call, a meeting and paperwork are the same record.||Breakcold forecasts revenue from a manually set chance of closing on each stage, but its analytics give only counts and values - no win rate and no stage-to-stage conversion.

Not a CRM - fails on core objects, status, expected close date, schedulable activity types, opportunity reporting; actual close date, structured lost reasons unresolved

Capsule keeps people and organizations in one record type called a Party rather than as two separate objects, though opportunities and tasks can link to both.||Capsule calls its stages Milestones - an administrator configures them, each carries a chance of winning, and opportunities are dragged from one column to the next.||A Capsule opportunity has no open or settled marking of its own - that comes from the Milestone it sits on, which is flagged as complete or not.||Won and lost are Milestones in Capsule, told apart by that milestone's chance of winning being 100 or 0 rather than by anything held on the opportunity itself.||Capsule ships a value field on the opportunity, which holds both an amount and the currency that amount is in.||Capsule offers only a general description on the opportunity - the vendor suggests tags or custom fields for recording what is sold.||Capsule ships an Expected Close Date on the opportunity, distinct from the date it actually closed.||Capsule fills in a separate Actual Close Date once an opportunity is won or lost, so it can be compared with the Expected Close Date the user entered.||Capsule ships an owner on the opportunity naming a user, with an optional team alongside it.||Capsule requires a main contact on every opportunity and lets further people be linked to it as well.||Won and lost opportunities are kept in Capsule and can be reopened, and standard reports cover won and lost counts and values, losses by reason and a conversion rate.||Capsule offers an optional Lost Reason chosen from a list the administrator sets up, and three built-in reports break lost opportunities down by it.||Capsule sends mail from a record, but incoming mail only reaches it by forwarding, copying in a special address, or the Gmail and Outlook add-ins, which attach to contacts only.||Capsule's calendar link runs one way in each direction - it publishes a read-only feed of your tasks, and shows a connected calendar's events without letting you edit them.||Capsule tasks are scheduled with a due date, owner and links to a contact or opportunity, and are sorted into categories - Call, Email and Follow up ship, and you can add your own.||Capsule ships a win rate and a weighted pipeline forecast built from expected close dates, but no report shows the proportion of opportunities moving from one milestone to the next.

Not a CRM - fails on core objects, status

ClickUp has one record type, the task; opportunities, contacts and companies are all the same object relabeled, not separate linked records.||Each ClickUp list holds an ordered set of statuses, and every task carries the status it's currently in.||ClickUp reads open versus closed from which status a task sits in, not from a separate field.||ClickUp statuses are only tagged open or closed; there's no shipped won-versus-lost value.||ClickUp ships no money field on a task; a currency field must be added by the buyer.||Every task has a native description box, but there's no shipped product or line-item list.||Every task has a native due date field that can serve as an expected close date.||ClickUp automatically stamps a native 'date closed' field the moment a task's status turns closed.||A task's assignee is a separate, shipped field from whoever created the task.||ClickUp has no shipped person record, so there's no native link from a deal task to a buyer.||Closing a task doesn't archive or delete it; closed tasks stay in place and remain reportable.||A buyer-built dropdown field can capture a lost reason, and dashboards can count it.||Users connect a real mailbox to send and receive email from inside a task, two-way.||Google and Outlook calendar events sync both ways, but a task's own due date only pushes out, not back.||Buyers can define their own named, schedulable task types beyond the generic task.||Dashboards only offer generic sums, counts and distributions - no native win rate, conversion rate or forecast.

Not a CRM - fails on core objects, status, resolution, value, linked buyer, opportunity reporting

Close has all four record types, but every opportunity must sit under an organization, and activities attach to that organization rather than to the opportunity.||Close lets an administrator name each pipeline's stages and drag them into the order they want, and an opportunity moves through them.||The Close opportunity itself records whether it's active, won or lost, so you can tell if it's still live without checking which stage it sits on.||Close reads won or lost from the same active-won-lost marking that says whether the opportunity is still open, rather than from a field of its own.||Close ships a money value on the opportunity, which can be a one-off amount or a recurring one.||Close offers only a general note on the opportunity - there's no field for what is being sold and no line items.||Close ships an Estimated Close date on the opportunity, separate from the date it was recorded as won.||Close records the date an opportunity was won or lost separately from the Estimated Close date, filling the won date in automatically when it's marked won.||Every Close opportunity carries a field called User, which names the person responsible for that opportunity.||Close ships a Contact field on the opportunity, which links it to a person on the parent Lead record.||Won and lost opportunities stay in Close and remain visible, and its Opportunity Funnels report counts them, derives a win rate and reports average days to close.||Close has no built-in lost reason field, but you can add your own drop-down list to the opportunity and report on it if you keep it to ten choices or fewer.||Close connects a Gmail, Office 365 or IMAP mailbox both ways - mail you send from your own mail app is logged automatically, with no need to copy in a special address.||Close pulls meetings in from a connected Google or Office 365 calendar when an attendee matches a contact, but nothing goes back out to the calendar.||Close schedules tasks and calls against a record with a date, time and assignee, but the list of task types is fixed and you can't add one of your own.||Close reports stage-to-stage conversion and a win rate in its Opportunity Funnels report, and projects revenue in the pipeline view from value multiplied by confidence.

Not a CRM - fails on core objects

Coevera keeps organizations, people, opportunities and activities as separate records, and an activity or an opportunity can be linked to the others.||An opportunity in Coevera sits on a pipeline and moves through steps that administrators name, reorder and weight with a closing probability.||Every Coevera opportunity carries its own status of Open, Won or Lost, so whether it is still live is readable from the record rather than from its step.||Coevera reads Won or Lost from the same status field that says whether the opportunity is still open, rather than from a separate outcome field.||Every Coevera opportunity has a built-in money field for its value, held with a currency rather than as a plain number.||Coevera attaches priced product line items to an opportunity, so what is being sold is recorded as structured lines and not just as a description.||Coevera ships a closing date on the opportunity, documented as the date the deal is expected to close, and asks for it when the opportunity is created.||Coevera keeps a Won Date and a Lost Date on the opportunity, separate from the expected closing date, so the date a deal actually ended is recorded.||Coevera requires an owner on every opportunity, naming the user it belongs to, and that ownership can be reassigned.||A Coevera opportunity links to the contacts it is being sold to, with one marked as primary, separately from the organization it links to.||Closed opportunities stay in Coevera: won deals stay in the pipeline, lost ones move to the Archive where they can still be viewed, reactivated and reported on.||Coevera makes you pick a lost reason from an administrator-controlled list before an opportunity can be archived as lost, and those reasons are meant to be reported on.||Coevera connects a Gmail or Microsoft 365 mailbox so mail sent and received in your normal mail client lands on the record, and you can send from inside the CRM too.||Coevera syncs appointments both ways with Outlook and Google Calendar, so a meeting booked in either place shows up in the other.||Coevera schedules tasks and appointments with a type, an owner and a due date, and higher-tier customers can define their own types and report on them.||Coevera reports step-to-step conversion, win rate and a revenue forecast out of the box, though those analytics sit on the Business tier and above.

CRM

Copper keeps people, organizations, opportunities and activities as separate records that can be linked to one another.||An opportunity in Copper sits in a pipeline and moves through ordered stages that you can rename, reorder or delete, each with its own win probability.||Every Copper opportunity carries its own status of Open, Won, Lost or Abandoned, so you can tell whether it's still live without checking its stage.||Copper reads Won or Lost from the same status that says whether the opportunity is still open, rather than from a separate outcome field.||Every Copper opportunity has a built-in money field for its value, which the product shows as projected revenue.||Copper gives you only a free-text description for what is being sold, with no facility for products or priced line items.||Copper ships a close date field on the opportunity, documented as the date that opportunity is expected to close.||Copper has only one close date field and its guidance tells the user to overwrite it by hand on closing; no documentation says Copper fills it in.||Copper ships an assignee field on the opportunity, naming the user who owns it, so ownership is recorded on the opportunity itself.||Copper requires a primary contact person on each opportunity, held separately from the linked organization.||Closed opportunities stay in the Copper account and stay measurable, with report metrics counting won, lost and open opportunities and working out win rates.||Marking an opportunity Lost in Copper prompts for a loss reason from a list administrators control, and those reasons feed a Loss Reasons report.||Copper syncs Gmail both ways onto matching records and lets you send and reply from inside Copper, but only Google mailboxes connect - other clients get a BCC address.||Copper syncs meetings with Google Calendar in both directions and pushes Copper Tasks out one way, but documents no Outlook or Microsoft 365 calendar sync.||Copper activities carry a due date, owner, priority and a type; Phone Call, Meeting and To-do ship, and administrators can add their own, thirty enabled at once.||Copper reports win rates and a weighted forecast natively, but has no built-in report for the conversion rate between one pipeline stage and the next.

CRM

Creatio keeps people, organizations, opportunities and activities as four separate records, and an activity can be attached straight to an opportunity.||An opportunity in Creatio sits on a stage, and the stages are a list you control with a number column that fixes their order.||Creatio's help pages show no open-or-closed field on the opportunity itself and closure living on the stage's Final checkbox, but the vendor publishes no full field list, so we've asked Creatio rather than recorded the field as absent.||Creatio tells a win from a loss by which final stage the opportunity ended on, using a Successful checkbox held on the stage rather than an outcome field on the record.||Creatio ships a money field for what the opportunity is worth, held in a currency and converted at the rate you set.||Creatio attaches priced products to the opportunity as line items, so what is being sold is recorded properly rather than only described.||Creatio ships an expected close date on the opportunity, meaning the date you expect the sale to be settled.||Creatio has a separate Closed on date for when the sale actually ended, and reporting counts what closed in a period from it.||Every Creatio opportunity names an owner, and access rights and forecasts are both driven off that owner.||Creatio links the opportunity to the person you are selling to, in a field of its own separate from the organization.||Closed opportunities stay in Creatio and keep appearing in its own reports and forecasts.||When an opportunity is lost, Creatio shows a Reason for closing field whose options come from a list you control, and reports can count them.||Creatio connects your own mailbox both ways: incoming mail lands on the matching records and you can send and reply from inside Creatio.||Creatio syncs its activities with external calendars - out to Google and in from Exchange and Microsoft 365 - though neither provider is documented as running both ways on its own.||Any piece of work can be scheduled in Creatio with a category, and you add your own categories rather than living with the ones supplied.||Creatio reports stage-to-stage conversion and forecasts revenue by period natively, but has no built-in win rate and its dashboards cannot divide one set of records by another.

CRM; status unresolved

Efficy keeps organizations, people, opportunities and activities as four separate record types, joined by link tables so any of them can be related to any other.||An Efficy opportunity moves along statuses grouped into pre-sales, proposal and outcome columns, but nothing published says the order of those statuses is stored on the data rather than drawn by the board.||Efficy's documentation never lists what an opportunity record actually holds, so whether the record itself says open or closed could not be established either way.||Because Efficy never publishes the opportunity's field list, whether won and lost are a marker of their own or just values of the status could not be settled.||Every Efficy opportunity has a built-in amount, and the product totals and weights it as money on the Kanban board and in forecast reports.||What is being sold goes on the Efficy opportunity as linked products rather than as a note, and quotes are built from there.||Efficy ships a date on the opportunity for when it is expected to conclude, shown as the target date on the Kanban card.||Efficy records a conclusion date up front, but nothing in the documentation says whether the date a sale actually ended is kept.||An Efficy opportunity names the account manager who owns it, and the link between opportunities and users is part of the shipped model.||Efficy links the opportunity to the person being sold to, separately from the organization, and records that person's role in the decision.||A closed Efficy opportunity stays in the database on its closing status and keeps feeding the standard sales reports.||Efficy ships a list of loss reasons as a coded field, so losses can be counted by reason through its queries and KPI widgets.||Efficy sends mail from inside the CRM and a service collects mail from your mailbox folders, but there is no live two-way mailbox sync.||Efficy appointments and tasks sync both ways with Microsoft Exchange and with Google Calendar, so a meeting booked in either place shows up in the other.||Any piece of work can be scheduled in Efficy as an action, and the kinds of action come from a list the administrator maintains.||Efficy forecasts revenue natively, but the documentation does not establish whether a win rate or a stage-to-stage conversion rate can be reported.

Not a CRM - fails on pipeline stages; status, resolution, actual close date, opportunity reporting unresolved

EspoCRM keeps opportunities, people, organizations and activities as separate, linkable record types.||Each opportunity moves through an ordered set of sales stages the system keeps track of.||Whether an opportunity is open or closed is read from its stage, not a separate field.||Won or lost is read from which closing stage the opportunity landed in, not a dedicated field.||Every opportunity carries a shipped money value field.||Line-itemized products or services can be attached to an opportunity through a linked quote.||Opportunities carry a native expected close date field.||There's no separate field recording when an opportunity actually closed.||Every opportunity has a shipped owner field separate from who created it.||Opportunities link to an individual buyer contact, separate from the linked organization.||Closed opportunities stay in the system and continue to feed reports.||There's no built-in lost-reason field, but a custom one you add can be counted in reports.||Mailboxes sync both ways and you can send email straight from the CRM.||Calendar events can sync in both directions with Google Calendar.||Beyond the default call, meeting and task types, admins can add their own schedulable activity types.||There's no built-in conversion-rate, win-rate, or forecast report - only counts and charts, or ones you build yourself.

Not a CRM - fails on status, actual close date, opportunity reporting

folk keeps people, organizations and opportunities as separate records, but an opportunity can only be linked to people and organizations in its own group.||folk has no built-in stage field, but a ready-made Status list arrives with every opportunity and shows as columns you drag opportunities across.||The folk opportunity record has no open-or-settled field of its own, so open versus closed is only whatever option a user puts on an ordinary Status list.||folk records nothing that separates a win from a loss, and the only won or closed values the vendor shows are options a user added to their own Status field.||folk's ready-made opportunity template supplies a Deal value field, so a money figure is there from the start.||The ready-made opportunity template in folk supplies no field for a description, a scope of work or products.||folk supplies a Closed at field recording when an opportunity actually closed, but nothing for the date it's expected to close.||folk's ready-made template includes a Closed at date field, but it's an ordinary field a person fills in and no documentation says folk writes it.||folk's ready-made opportunity template supplies a Deal owner field naming the team member responsible.||In folk, people are a built-in attribute of the opportunity record, kept separate from the organizations linked to it.||A settled opportunity stays in folk and stays in its charts, which cover revenue and average value by closing date and by the person assigned.||folk holds a lost reason as a pick-from-a-list field you have to create yourself, though its charts can then break records down by that reason.||folk can send mail and import what arrives in a connected Google or Outlook mailbox, but replies land in your own mailbox and nothing done in folk is sent back out.||folk imports events from a connected Google or Microsoft calendar as interactions, but nothing goes back the other way and you can't create an external event from folk.||folk lets you schedule tasks and log interactions with a date, but the interaction types are a fixed vendor list and tasks have no type field at all.||folk's dashboards can show an overall conversion rate from a field you build yourself, but offer no stage-to-stage conversion and no forecast, and cover all time only.

Not a CRM - fails on status, resolution, expected close date, opportunity reporting

Freshsales keeps opportunities, contacts and organizations as separate records, with tasks and meetings as activities, and linking an organization is optional.||Freshsales opportunities move through ordered stages an administrator names and reorders, each with a probability, and every pipeline holds at least three.||Freshsales documentation didn't establish either way whether an opportunity carries its own open-or-settled marker separate from the stage it sits in.||Freshsales documentation didn't establish whether won and lost sit on the opportunity itself; everything reachable points to the stage name carrying the outcome.||Freshsales ships a Deal Value field on the opportunity, holding the amount that opportunity is potentially worth.||Freshsales ships a Product field on the opportunity, and products can be attached to it as line items.||Freshsales ships an Expected Close Date field on the opportunity, kept separate from its Closed Date field.||Freshsales ships a separate Closed date alongside the expected one, though no documentation says the platform writes it, so a person fills it in.||Every Freshsales opportunity carries an Owner field, naming the user the opportunity is assigned to.||Freshsales links contacts to the opportunity through a Related Contacts field, kept separate from the organization it names.||Settled opportunities stay in Freshsales and stay reportable, with ready-made Won and Lost views and analytics that filter on the closed date.||Freshsales holds the lost reason as a pick-from-a-list field an administrator can customize, and reports on it through a Lost Reasons view.||Freshsales syncs a connected mailbox both ways by default, so mail sent from your own client or from the CRM shows in both; Gmail, Microsoft 365 and IMAP work.||Freshsales syncs meetings both ways with Google Calendar and with Office 365, so a meeting booked on either side appears on the other and on the contact record.||Freshsales ships tasks and meetings, and an administrator can add up to 50 activity types of their own, each with its own icon and set of outcome choices.||Freshsales reports win and loss rates and a forecast natively, but its documentation describes no conversion rate between one stage and the next.

CRM; status, resolution unresolved

GoHighLevel keeps contacts, companies, opportunities and tasks as separate records, and opportunities can be linked to both a contact and a company.||Opportunities move through an ordered list of stages that the user sets up and can reorder.||Whether an opportunity is open or closed is its own field, not something read off which stage it sits in.||Won versus lost is recorded directly as a value, not inferred from anything else.||Opportunities carry a shipped money field.||What's being sold is captured as a name or free-text field, not as an itemized product list.||There's a shipped field for when the deal is expected to close.||There's no field for when a deal actually closed, only for when it's expected to.||Each opportunity carries a shipped owner field pointing to a user.||Every opportunity links to a person record, separate from its company link.||Closed deals stay in the system and show up in reports.||Lost reasons come from a set list and can be counted and reported on.||A real mailbox connects both ways, and you can send email from inside the CRM.||Calendar events sync in both directions with Google Calendar.||Tasks and appointments have no activity-type field at all, so there's nothing to schedule against.||Reporting shows counts and totals, not conversion rates, win rates or a revenue forecast.

Not a CRM - fails on actual close date, schedulable activity types, opportunity reporting

HubSpot keeps opportunities, contacts, organizations and activities as separate record types that can be linked, and linking is optional when creating an opportunity.||HubSpot opportunities move through ordered stages in a pipeline that you can add to, rename and drag into a new order, each stage carrying a probability.||Every HubSpot opportunity carries Is closed won and Is closed lost markers that HubSpot sets itself, so open or settled reads straight off the record.||Those same two markers separate a win from a loss on the record, filled in by HubSpot when the opportunity reaches a stage whose probability is set to Won.||HubSpot ships an Amount field for the opportunity's monetary value, plus a weighted figure derived from it.||HubSpot ships line items on the opportunity record, taking either products from your library or one-off items.||HubSpot ships a Close date field on the opportunity, documented as when that opportunity is expected to close.||HubSpot uses one Close date for both the expected and the settled date, stamping it with today when you move an opportunity to a closed stage unless that's switched off.||HubSpot ships a Deal owner field on every opportunity, naming the user who is responsible for it.||HubSpot links contacts to an opportunity as a standard association, kept separate from the link to the organization.||Closed opportunities stay in HubSpot and stay in its reporting, feeding won and lost counts by user or team, a loss reasons report and a report on the share won.||HubSpot has a Closed lost reason field feeding a native loss reasons report, though it arrives as free text and only converts to a dropdown while it still holds no data.||HubSpot sends mail from records and logs replies onto them, and its Gmail and Outlook add-ins log mail you compose there, but a message that isn't a reply needs logging by hand.||HubSpot syncs meetings both ways with a connected Google or Outlook calendar, though only your primary calendar syncs and private events are left out.||HubSpot lets you schedule calls, meetings, tasks, notes and emails from a record and define your own call and meeting types, but task types stay a fixed three.||HubSpot ships all three natively - a stage funnel with conversion rates, an overall win rate and a forecast tool - with no add-on or outside reporting tool needed.

CRM

Insightly keeps opportunities, contacts and organizations as separate records that link to one another, and activities come as tasks and events that link to them too.||Opportunities in Insightly sit on a pipeline of ordered stages that an administrator sets up, and the record shows which stages are done, current and still to come.||Insightly's opportunity carries a Current State field of Open, Suspended, Abandoned, Lost or Won, so whether it's still live is read off the record, not the stage.||Insightly reads Won, Lost or Abandoned from the same Current State field that says whether the opportunity is still open, though a reason can be attached as the state changes.||Every Insightly opportunity comes with a Value field as standard, which holds a money amount.||Insightly ships Opportunity Products as line items with their own layout, and these drive the calculated value of the opportunity.||Insightly ships a Forecast Close Date on the opportunity as standard, recording when it's estimated to close.||Insightly ships a separate Actual Close Date, updated by the system when the state changes, although choosing Suspended leaves it unchanged.||Insightly ships a Who's Responsible field on the opportunity as standard, naming the user accountable for it.||Opportunities in Insightly ship linked to the individual contacts involved as well as to the organization.||Settled opportunities stay in Insightly and feed its shipped dashboard cards for win rate, value by state and lost opportunities by reason.||Administrators set up Insightly's Opportunity State Reasons as a fixed list, picked as the state is changed, and a dashboard card reports lost opportunities by reason.||Insightly's Email Inbox Sync connects a Gmail, Office 365 or Outlook mailbox and captures mail both ways automatically, with no forwarding or BCC address needed.||Insightly syncs events with Google or Microsoft calendars both ways, but external calendar items can't be edited in Insightly and invitations can't be sent from it.||Tasks are created inside Insightly with due dates, reminders and links to records, meetings are events, and administrators define the task categories themselves.||Insightly ships win rate and forecasting on its standard opportunity dashboard, but nothing documented gives the conversion rate from one stage to the next.

CRM

Keap holds contacts, companies, deals, tasks and appointments, but no vendor page shows a deal attached to a company, or a task or appointment attached to a deal, so whether those links exist couldn't be established either way.||A Keap deal is created into a chosen pipeline and moved through its stages, and the buyer sets the stage names and how many stages there are.||The Keap deal carries a Status field, and choosing Won or Lost on it closes the deal with that outcome, as does dragging the card into the matching column.||Keap reads Won or Lost from the same Status dropdown that says whether the deal is still open, rather than from a separate outcome field.||Keap captures the money amount as a Deal Value field, filled in at the point the deal is added.||Keap's documentation didn't establish either way whether anything beyond a general Notes box records what is being sold - the articles describing the deal's fields didn't survive the vendor's help-center migration.||Keap records an estimated close date on the opportunity, which is added from the full deal view.||Keap's documentation didn't establish either way whether a second field records the date the opportunity was actually settled.||Keap's documentation didn't establish either way whether a deal carries an owner. Team members can be attached to it, but the articles describing the deal's fields didn't survive the vendor's help-center migration.||A contact must be chosen when a Keap deal is created, and the deal carries a primary contact.||Keap's documentation didn't establish what becomes of a deal once it's closed, or whether closed deals still appear in Keap's own reporting.||Keap has no lost reason field, and although a dropdown can be built on the deal, no vendor page says whether that field can then be reported on, so whether a loss reason can be counted couldn't be established either way.||Keap sends mail from the contact record and writes mail from a connected Gmail or Microsoft mailbox back to it, but mail sent from Keap isn't synced to that mailbox.||Keap displays connected Google and Outlook events but can't edit them, and only the Outlook documentation says Keap appointments are written back to the calendar.||Appointments are booked inside Keap against a contact using appointment types the buyer defines, and tasks with a due date and a reminder are a separate record.||Keap's documentation didn't establish its pipeline reporting either way - the claims sit in announcements, and the help article itself couldn't be retrieved.

CRM; core objects, scope of work, actual close date, opportunity owner, record preservation, structured lost reasons, opportunity reporting unresolved

Kommo keeps leads, people, companies and tasks as four separate record types, and a task can be attached to any of the other three.||A Kommo lead sits in a pipeline and moves along stages you can add, rename and reorder, with the order stored on the stage itself.||Nothing on a Kommo lead says whether it is open or settled; you read that from whether it sits in the reserved Closed-won or Closed-lost stage.||Whether a Kommo lead was won or lost is read from which of the two closing stages it ended in, not from an outcome field on the lead.||Every Kommo lead has a built-in sale value that the product treats as money and sums into revenue reporting.||Kommo lets you attach catalog products to a lead with quantities, and the sale value adds itself up from those line items.||Kommo ships no expected close date on a lead, so a buyer wanting one adds a date field of their own.||Kommo stamps a closing date on the lead when it is first closed, and leads can be filtered by that date.||Each Kommo lead names a responsible user, held separately from whoever created the record.||A Kommo lead links directly to the person it is with, separately from any company link.||Closed leads leave the pipeline board but stay in the account and keep counting in Kommo's own reports.||Kommo ships a proper list of loss reasons on the lead, but no vendor documentation says whether a report or filter can count them.||Kommo connects a real mailbox over IMAP and SMTP, pulls in both received and sent mail against the record, and lets you write from the lead.||Kommo syncs tasks, events and bookings with Google Calendar in both directions, and documents no other calendar.||Kommo tasks carry a type, an owner and a deadline; Follow-up and Meeting ship and administrators can add their own.||Kommo forecasts upcoming sales natively, but no report states the conversion rate between stages or a win rate as a proportion.

Not a CRM - fails on status, expected close date, opportunity reporting; structured lost reasons unresolved

Maximizer holds companies and people in one Address Book record that is tagged Company, Individual or Contact, so the organization is not a record type of its own.||An opportunity in Maximizer sits in a sales process and moves through the stages an administrator defines for it, with the current stage held on the record.||Every Maximizer opportunity carries its own status of In Progress, Won, Lost or Abandoned, held separately from the sales stage.||Maximizer reads Won or Lost from the same status field that says whether the opportunity is still running, rather than from a separate outcome field.||Maximizer ships revenue fields on the opportunity - a forecast amount and a realized amount - and shows the revenue on the opportunity card.||Maximizer attaches products and services from an administered catalogue to the opportunity, though the documentation describes no quantities or per-line prices.||Maximizer ships a close date on the opportunity, shown and filtered on opportunities that are still running, so it carries the date the sale is expected to land.||Maximizer has one close date field and no second one, and no Maximizer documentation says what that field holds once the opportunity is settled.||Maximizer ships a Leader field on the opportunity naming the user who owns it, plus a separate sales team assignment.||A Maximizer opportunity links to a named contact person as well as to the company it is against.||Won, lost and abandoned opportunities stay in Maximizer, can be listed back by status, and feed the win rate and stage conversion dashboards.||Maximizer stores the reason an opportunity was lost as a pick-list value, but ships no loss-reason report, so somebody has to build one.||Maximizer pulls mail from a connected Microsoft 365 mailbox onto the record, but nothing documents mail sent from Maximizer going back into that mailbox.||Maximizer's Outlook desktop integration syncs appointments and tasks both ways with conflict resolution, while its newer cloud Outlook and Google connections bring calendar events in one way only.||Maximizer schedules appointments and tasks with a type on each, and administrators define the type list rather than being stuck with the vendor's.||Maximizer ships dashboards for stage-by-stage conversion rate, win rate and sales forecasting as part of its own reporting.

Not a CRM - fails on core objects; actual close date unresolved

Membrain keeps companies, contacts, sales projects and activities as four separate record types that can all be linked to one another.||Each Membrain sales project sits on a named sales process and moves through that process's ordered stages, with its current stage held on the record.||Every Membrain sales project carries its own status of Open, Won or Archived, so you can tell whether it is still live without looking at its stage.||Membrain reads won or archived from the same status field that says whether the project is still open, rather than from a separate outcome field.||Membrain ships a money value on every sales project, in the currency you choose, and can build it up from the products attached.||Membrain lets you attach priced products to a sales project as line items, with quantity, discount and cost, so what is being sold is recorded on the record.||Membrain ships an estimated closing date on every sales project, either projected from the process or entered by the salesperson.||Membrain stamps the date a sales project was won or archived in its own field, separate from the estimated closing date.||Every Membrain sales project names the user who owns it, held separately from who created or last changed the record.||Membrain links people to a sales project as stakeholders and participants with named roles, rather than through a single primary contact field.||Closed sales projects stay in Membrain, stay searchable and keep feeding the win and loss analysis.||Closing a Membrain sales project prompts for a reason from a list your administrator controls, and those reasons feed the win and loss analysis.||Membrain connects your Gmail, Office 365 or IMAP mailbox, lets you send and reply from inside the CRM, and pulls mail you send from your own client onto the matching project.||Meetings sync both ways between Membrain's sales calendar and Google or Office 365, and incoming meetings attach to the matching project.||Membrain activities carry a type, an owner and a due date, and administrators can define their own types for tasks, calls, meetings and more.||Membrain reports win rate and a weighted forecast natively, but nothing documented measures the proportion of projects moving from one stage to the next.

CRM

Method keeps customers, contacts, opportunities and activities as separate records, and an activity or an opportunity can be tied to the person and the company it belongs to.||Method ships ten renameable sales stages with a probability and a sequence number held on the stage, but the vendor's own pages disagree about whether that sequence number actually orders anything, so this is unresolved until Method answers.||In Method you tell whether an opportunity is still live by looking at the category set on its stage, not from anything on the opportunity itself.||Whether a Method opportunity was won or lost is read from the category on the stage it ended in rather than from a separate outcome field.||Every Method opportunity has a built-in amount field for what the sale is worth, and Method weights it by the stage probability to give a pipeline figure.||Method gives you a description box on the opportunity for what is being sold, with priced line items living on the estimate or invoice you create from it.||Method ships a close date on every opportunity, documented as the date it is expected to be won or lost.||When you close a Method opportunity the close date is stamped with today's date automatically, which records when it settled but overwrites the date you had forecast.||Method ships an assigned to field on the opportunity naming the user who owns it, held separately from who created the record.||Each Method opportunity is linked to a named contact person as well as to the customer they work for.||Closed opportunities stay in Method, move into closed views and keep feeding the won and lost charts and the opportunity reports.||Method does not ship a lost reason, so you add your own dropdown to the opportunity and count it with a report you build.||Method sends email from inside the CRM and logs it as an activity, but nothing pulls received mail back onto the record.||Method syncs activities both ways with Google Calendar every twenty minutes, but documents no Outlook or Microsoft calendar sync.||Method activities carry a type, an owner, a status and a scheduled time, nine types ship and you can define your own.||Method charts the share of closed opportunities won and totals weighted pipeline value, but has no report for the conversion rate from one stage to the next.

Not a CRM - fails on status; pipeline stages unresolved

Dynamics 365 Sales keeps opportunities, organizations, contacts and activities as separate records, and each opportunity must name a customer, person or organization.||Opportunities in Dynamics 365 Sales follow an administrator-defined set of ordered stages shown across the top of the record, and can be sent back to an earlier stage.||The Dynamics 365 Sales opportunity carries its own Status of Open, Won or Lost, held on the record and separate from the stage it's sitting in.||Dynamics reads Won or Lost from the same Status field that says whether the opportunity is still open, with a Status Reason adding more detail on the same footing.||Dynamics 365 Sales ships a money field on the opportunity for the potential revenue it represents.||Dynamics 365 Sales ships an opportunity product record, so line items can be attached to the opportunity as standard.||Dynamics 365 Sales ships an estimated close date on the opportunity, described as the expected closing date used for forecasting.||Dynamics 365 Sales ships a separate actual close date, filled in automatically when the opportunity is closed and open to adjustment in the closing dialog.||Every Dynamics 365 Sales opportunity must have an owner, which can be an individual user or a team.||The Dynamics 365 Sales opportunity names a customer that can be an organization or a person, and also carries a link to a contact.||Closing an opportunity in Dynamics 365 Sales switches it off rather than deleting it, so it stays in the Closed Opportunities view and can be reopened later.||Dynamics 365 Sales records the reason on a closing record, using a status reason list administrators can extend, plus a competitor and a free-text explanation.||Dynamics 365 Sales syncs mail both ways with Exchange without any Outlook add-in, so mail sent from a record or from Outlook lands on the record's timeline.||Dynamics 365 Sales syncs appointments both ways with Exchange, but the vendor records calendar sync as unsupported for Gmail and Yahoo mailboxes.||Activities are created from inside a Dynamics 365 Sales record, the shipped types cover appointments, calls, tasks, emails and letters, and new types can be added.||Dynamics 365 Sales ships forecasting and won against lost counts the buyer has to turn into a win rate, and conversion between stages isn't available at all.

CRM

monday CRM ships Leads, Contacts, Accounts, Deals and Activities boards, linked by columns a board owner sets up and keeps in place rather than by a fixed structure.||monday CRM records the stage in a column on the Deals board whose labels a board owner puts into order, though any label can be picked at any time unless rules are added.||monday CRM has no separate open or closed field on the deal - whether it's settled depends on whether the stage label has been marked as done in the column's setup.||Nothing in monday CRM marks a stage label as won rather than lost; the done setting only separates settled from unsettled, so won and lost are words the buyer types.||monday CRM ships a Deal Value column on the Deals board as standard, holding the amount as a number.||monday CRM ships no description, deliverables or products column - the Products widget has to be added, is in beta and needs a connected catalog board.||The Deals board in monday CRM ships an Expected Close Date as one of its default date columns.||Expected Close Date is the only date monday CRM ships on the Deals board, so a buyer wanting the date a deal actually settled has to add a column of their own.||The Deals board in monday CRM ships an Owner column by default, and that column holds a person.||Every monday CRM deal ships with a Contacts column linking it to records on the Contacts board.||Settled deals stay on the monday CRM Deals board in a Closed Won group, still count in its forecasting and funnel reporting, and can be reopened.||monday CRM ships no lost reason field, but a board owner can add a dropdown and require it before the lost label is set, though automations and the API bypass that rule.||monday CRM connects a Gmail or Outlook mailbox and logs mail both ways onto the record, though messages sent before it was set up aren't captured.||monday CRM pulls external Google and Outlook events onto the contact's timeline, but activities added in monday aren't automatically put back on the calendar.||Activities are created inside monday CRM with an adjustable date and time, and beyond the supplied meeting, call summary and note types users can name their own.||monday CRM ships overall conversion and forecasting as native dashboard views, but no documented report gives the conversion rate from one stage to the next.

Not a CRM - fails on status, resolution, actual close date

Nimble treats an organization as a type of contact rather than a record in its own right, and no vendor page says an organization can be attached to an opportunity.||A Nimble opportunity sits in a pipeline of ordered stages the administrator defines, and is moved along by dragging it across the board or from the record's own menu.||A Nimble opportunity is marked won or lost on the record itself rather than by moving it to a final stage, so the outcome is held apart from where it sits.||Nimble records won or lost through the same action that closes the opportunity, so the outcome is a consequence of closing it rather than a field of its own.||Nimble ships an amount as a standard field on the opportunity record, so the value of the work is there by default.||Nimble gives the opportunity only a general description box, with no documented way to itemise products or lines of work.||Nimble ships an expected close date as a standard opportunity field, offered when the opportunity is created and shown on the record.||Nimble holds an actual close date separate from the expected one, but the person closing the opportunity types it in rather than the system filling it.||A Deal Owner field ships as standard on the Nimble opportunity and is set at the point the opportunity is created.||Nimble links people to the opportunity through a field called Related Contacts, and more than one person can be attached to the same opportunity.||Closed opportunities stay in the Nimble account: won and lost work sits in its own lists with the usual sorting and filtering, and feeds the built-in reports.||Lost reasons are set up on the pipeline in Nimble, so a lost opportunity is tagged from a list the administrator controls, and a report groups losses by reason.||Nimble connects to Gmail, Microsoft 365 or any IMAP mailbox and syncs mail both ways, pulling in the last ninety days and letting you write and send from inside Nimble.||Nimble syncs events both ways with Google and Microsoft 365 calendars, though events created outside Nimble flow in hourly while a user is signed in and every three hours otherwise.||Nimble covers tasks, calendar events and calls, and an administrator can create activity types of their own, such as webinars or appointments.||Nimble offers a stage conversion widget and a revenue forecast, but no win rate, and its reports are a fixed set of widgets rather than something you can build.

Not a CRM - fails on core objects

Notion ships no built-in opportunity, contact, company or activity records - only generic databases a buyer builds and links themselves.||There's no shipped sales pipeline; any stage sequence has to be built by hand from a generic property.||Open-versus-closed isn't a field Notion ships - it would have to be added by the buyer.||Won-versus-lost isn't a field Notion ships natively.||There's no built-in deal-value field; a buyer adds a currency-formatted number field themselves.||Nothing ships to describe what's being sold - a buyer builds that from scratch.||There's no native expected-close-date field - a buyer creates a generic date field for it.||There's no native actual-close-date field - a buyer creates a generic date field for it.||There's no native owner field - a buyer adds a generic person field to a database they design.||Linking a deal to a specific person requires the buyer to build both databases and the relation.||Records stay in the workspace and keep showing up in views and totals unless someone deletes them.||A lost-reason field isn't built in, but a buyer-added tag field can be counted in views.||Notion has no shipped way to log or send email against a record, and its inbox product is being shut down.||Calendar items tied to a database sync back to that database, but they don't push out to Google or Outlook.||Scheduling any kind of activity and defining its type both have to be built by the buyer.||None of conversion rate, win rate, or forecast reporting ship - a buyer would have to build all three.

Not a CRM - fails on core objects, pipeline stages, status, resolution, value, scope of work, expected close date, actual close date, opportunity owner, linked buyer, email sync, schedulable activity types, opportunity reporting

Nutshell keeps organizations, people, Leads and activities as separate records, and a Lead can be attached both to organizations and to people.||A Nutshell lead runs through an ordered set of administrator-defined stages, which can be renamed, reordered by dragging and given guidance and a confidence level.||Status is its own field on the Nutshell lead - Open, Won, Lost, Cancelled or Pending - and closing is a change of status, not a move to a final stage.||Nutshell reads won, lost or canceled from the same status that says whether the lead is still open, and separately captures an Outcome when it's lost or canceled.||Nutshell ships a Lead Value figure on the opportunity, worked out automatically from the products sitting on the lead.||Products attach to a Nutshell lead through the Revenue widget, each with a quantity, price and discount you can edit.||Nutshell leads store an expected close date, and the vendor's forecast report ranges over that date.||Nutshell keeps an actual close date apart from the expected one, and it comes from the platform when the lead is closed rather than being typed in by the user.||Every Nutshell lead carries an Assignee, which starts as whoever created it and can be reassigned to someone else.||Nutshell leads attach to individual people as well as to organizations, and the lead card displays the primary person.||Closed leads stay in Nutshell and stay in its reporting: won leads are added to the Sales report, and lost or canceled ones feed the losses reporting.||Administrators pre-define the list of outcomes and Nutshell offers it as a drop-down when a lead is lost or canceled, with the Losses report comparing them.||Nutshell connects a Gmail or Office 365 mailbox so mail sends and receives in both places and appears on the person, organization and lead timelines.||Nutshell syncs both ways with Google Calendar and Office 365, sending activities out and bringing outside events back in, though past events aren't imported.||Activities are booked in Nutshell from a lead, person or organization with a type chosen from a drop-down, and administrators can add types of their own.||Nutshell ships all three natively: a Funnel report on stage progression, win rate as a calculated metric, and a Forecast report driven by the expected close date.

CRM

Odoo uses one contact record for both people and companies, just flagged as one or the other, instead of two separate record types.||Stages have their own order and every opportunity records which stage it is in.||Whether an opportunity counts as closed-won is decided by which stage it sits in, not by a separate status field.||Won and lost are worked out by combining a stage flag and a separate archive flag, not stored as one clean field.||Every opportunity has a built-in money field for its expected revenue.||The opportunity itself has only a notes box; itemized products live on a separate linked quotation, not the opportunity record.||A native expected-closing date field ships on every opportunity.||A native closed-date field is automatically stamped when an opportunity is won or lost.||Every opportunity has a native Salesperson field separate from who created the record.||The opportunity has just one customer link that can be a person or a company - not a separate person link alongside an org link.||Closed opportunities stay in the system and can still be filtered and reported on.||Lost reasons are a structured, selectable field that reporting can count and group by.||Email connects one way, from the mailbox into CRM records, plus sending from inside the CRM - not a full two-way mailbox sync.||Two-way calendar sync exists at the platform level, but no CRM-specific vendor page confirms it applies to CRM meetings.||Beyond the default call/meeting/to-do types, users can define their own schedulable activity types.||Reporting gives counts and revenue totals, but no built-in conversion-rate or win-rate figure - only revenue-style measures.

Not a CRM - fails on core objects, status, linked buyer, opportunity reporting; calendar sync unresolved

OnePageCRM has all four record types, but an organization only comes into being from a contact's company name, and an activity attaches to the contact rather than to the opportunity.||A OnePageCRM deal belongs to a pipeline and moves through that pipeline's own ordered stages, which you can add, rename, reorder and remove.||Every OnePageCRM deal carries its own status of pending, won or lost, so whether it is still live is readable from the deal itself.||OnePageCRM reads won or lost from the same status field that says whether the deal is still open, rather than from an outcome field of its own.||A OnePageCRM deal has a built-in amount field that the product treats as money in the account's currency.||OnePageCRM lets you attach priced products or services from a catalog to a deal as line items, and the deal amount adds itself up from them.||OnePageCRM ships an expected close date on every deal, separate from the date it actually closed.||OnePageCRM keeps a separate close date on won and lost deals recording when the sale actually ended.||Each OnePageCRM deal names an owner, held separately from whoever created it, and ownership can be reassigned.||Every OnePageCRM deal must name the contact it belongs to, and further people can be linked to the same deal.||Won and lost deals stay in the OnePageCRM account, filterable in the deal list and counted on the dashboard and activity reports.||Marking a deal lost in OnePageCRM prompts for a reason from a list administrators control, and those reasons are charted on the dashboard and can go into a custom report.||OnePageCRM connects your Gmail, Outlook 365 or IMAP mailbox, logs incoming and outgoing mail against contacts automatically, and lets you send from inside the CRM.||OnePageCRM pushes your next actions out to Google, Outlook or Apple calendars, but nothing documented comes back the other way.||OnePageCRM actions have no type field, so the kind of work has to live in the action's wording - which you can at least standardize with templates and search on.||OnePageCRM forecasts revenue from your pipeline, but nothing in it works out a win rate or the conversion rate from one stage to the next.

Not a CRM - fails on core objects, opportunity reporting

Oracle Sales keeps opportunities, organizations, people and activities as four separate record types, each addressable on its own and linkable to the others.||An Oracle Sales opportunity moves through the ordered stages of a sales method, with the order number stored on each stage rather than on a view.||Every Oracle Sales opportunity carries its own status of Open, Won, Lost or No Sale on the record, so you can tell whether it's still live without looking at its stage.||Oracle Sales reads Won or Lost from the same status field that says whether the opportunity is still open, rather than from a separate outcome field.||Oracle Sales ships a revenue amount on the opportunity in a chosen currency, which it converts to a common currency for forecasting.||What's being sold goes on the Oracle Sales opportunity as revenue lines of products or services, not just as a description.||Oracle Sales ships an effective date on the opportunity, documented as the date the opportunity is expected to close.||Oracle Sales stamps a separate actual close date when an opportunity is closed, and buyers can't import into it.||Oracle Sales names an owning employee on every opportunity, and that owner is who the record belongs to rather than who created it.||An Oracle Sales opportunity links to a named primary contact, with more people attachable and given roles, held separately from the account.||Closing an Oracle Sales opportunity only changes its status, and won and lost records stay in the platform's own reporting.||Oracle Sales records why an opportunity was won or lost in a shipped field whose values administrators control, and it can be made compulsory at close.||Oracle Sales sends mail from the opportunity, account, contact and lead pages through the user's own Exchange mailbox and files the replies back on the record automatically.||Oracle Sales appointments and tasks sync both ways with Microsoft 365, and the activity record itself carries the Outlook sync fields; there's no Google equivalent.||Any activity in Oracle Sales can be scheduled and typed, and administrators add their own activity types on top of the appointment, task and call report functions Oracle ships.||Oracle Sales ships forecasting outright, and win rate and stage-to-stage conversion are reports you build yourself in its own analytics, which holds the stage history and can divide one measure by another.

CRM

NetSuite keeps opportunities, people, organizations and activities as separate records, and activities attach straight to the opportunity.||A NetSuite opportunity moves through a list of statuses the account defines, each carrying its own probability and its place in the sales cycle.||NetSuite tells you an opportunity is finished only by which status it sits in, so there is no separate field saying whether it is open or closed.||You can tell a won NetSuite opportunity from a lost one by the status it ended in, rather than from a field whose job is the outcome.||Every NetSuite opportunity carries a Projected Total in money, plus a weighted total that applies the probability of closing.||What is being sold goes on the NetSuite opportunity as priced line items, not just as a description.||NetSuite ships an Expected Close date on the opportunity, and it is the date the forecast and pipeline reports work from.||NetSuite records the date an opportunity actually closed in its own field, separate from the date it was expected to close.||Each NetSuite opportunity names the sales rep who owns it, and a sales team can be credited alongside.||NetSuite attaches contacts to the opportunity on a Relationships subtab, including one flagged as the decision maker, separately from the company.||Won and lost opportunities stay in NetSuite and keep appearing in its own reports for whatever period you choose.||NetSuite ships a Win/Loss Reason list on the opportunity, filled with the account's own reasons, and reports can count them.||You can send mail from a NetSuite record and replies come back onto it automatically, but nothing connects your mailbox, so mail you write in Outlook only reaches NetSuite through an add-in.||A meeting in Outlook can be pulled onto a NetSuite record, but nothing documented pushes a NetSuite event back out to the calendar.||NetSuite schedules tasks, phone calls and events, but the kind of work is fixed to those three rather than a list you define.||NetSuite forecasts natively and a win rate can be built in its own search builder, but nothing measures how many opportunities get from one status to the next.

Not a CRM - fails on status

Pipedrive holds opportunities, people, organizations and activities as separate records, and every opportunity must be linked to a person, an organization or a project.||An opportunity in Pipedrive moves through the ordered stages of a pipeline until it's marked won or lost, and the stages are configurable for each pipeline.||The Pipedrive opportunity carries its own status of open, won, lost or deleted, so you can tell whether it's still live without looking at its stage.||Pipedrive reads won or lost from the same status that says whether the deal is still open, with a won time and a lost time recorded to match.||A value field ships as standard on the Pipedrive opportunity, with a companion currency field so the amount is recorded in the right money.||Products attach to a Pipedrive opportunity as line items with their own quantity, price and currency, and they can drive the opportunity's value.||Pipedrive ships an expected close date on the opportunity, kept separate from the dates recording when it was actually closed, won or lost.||Pipedrive records the date and time an opportunity was actually closed, which can only hold a value once it's won or lost, and it keeps the won time separately.||Every Pipedrive opportunity ships with an owner field that identifies the user who owns it.||A Pipedrive opportunity links to an individual person through its own field, which is separate from the link to the organization.||Closed opportunities stay in your Pipedrive account, with ready-made filters for won and lost work and a report showing how many were started, won and lost.||Pipedrive holds a lost reason on the opportunity, which an administrator can switch from free text to a fixed drop-down list, and either form can be tracked in reports.||Pipedrive connects to a Gmail, Exchange, Outlook.com, Yahoo or iCloud mailbox so mail flows both ways and can be read, sent and replied to from inside the CRM.||Pipedrive syncs both ways with Google, Exchange, Outlook or Office calendars, so activities booked in either place appear in the other and edits follow across.||Activities are booked inside Pipedrive against an opportunity, organization or person, and a global administrator can add activity types of their own.||Pipedrive ships its own named reports for conversion between stages, overall win and loss rates, and a revenue forecast built on the expected close date.

CRM

Prospect CRM stacks its records in a hierarchy - Company, then Contact, then Opportunity - with tasks a separate record that can be set against any of them.||A Prospect CRM opportunity moves through an ordered list of pipeline statuses, changed from a drop-down or by dragging its card across a Kanban board.||A Prospect CRM opportunity holds only its current status, so to know whether it's settled you have to check whether that status was set up as a closed one.||Won or lost isn't held on the Prospect CRM opportunity itself: each status is configured as a positive, neutral or negative outcome, and reporting filters on that.||Prospect CRM ships a Size field holding the revenue value of the opportunity, alongside a Margin field.||The Prospect CRM opportunity carries only a Summary overview, and itemized products sit on a separate Quote record beneath it.||Prospect CRM ships an estimated close date, editable straight from the Kanban card and used by the pipeline reports.||Prospect CRM has no field for the date an opportunity actually closed - every vendor page that lists opportunity dates names only the estimated close date.||Prospect CRM ships a Sales Person field naming whoever takes overall responsibility for the opportunity.||In Prospect CRM an opportunity is created underneath a Contact, so the link to an individual person is built into the record.||Closed opportunities stay in Prospect CRM and in its reporting, through an All Opportunities report and dashboard tiles for lost opportunities and closed deals.||Every Prospect CRM status can carry Status Details picked from a drop-down, so a lost opportunity records why, such as lost on price, in a field reports can use.||Prospect CRM doesn't connect to your mailbox: you can send from inside the CRM, but incoming mail only arrives if someone saves it with an add-in or forwards it in.||Prospect CRM shows a live reflection of an Outlook calendar and writes its own events out to it, but only Outlook is supported and events must be amended in Outlook.||Tasks are created inside Prospect CRM against any record with a name, assignee, date and type, and administrators maintain their own activity and task type lists.||Prospect CRM can project revenue from the estimated close date, but has no stage-to-stage conversion report and no win rate, and its builder can't work out percentages.

Not a CRM - fails on status, actual close date, email sync, opportunity reporting

Sage CRM keeps companies, people, opportunities and activities as separate records, and an appointment or task can be attached to the opportunity it belongs to.||An opportunity in Sage CRM sits at a named stage and is moved to the next one by the shipped opportunity workflow, with a pipeline graphic counting what is at each stage.||Every Sage CRM opportunity carries its own Status of In Progress, Won, Lost or Closed, held separately from the stage it sits in.||Sage CRM reads Won or Lost from the same Status field that says whether the opportunity is still open, rather than from a separate outcome field.||Sage CRM ships a Forecast amount on the opportunity and handles it as money, with a base currency and exchange rates behind it.||Sage CRM attaches quotes and orders with priced product line items to the opportunity, so what is being sold is recorded item by item.||Sage CRM ships a Close By date on the opportunity for when the sale is expected to land, and the forecast is built from it.||Sage CRM keeps the date an opportunity actually closed in its own field, separate from the date it was expected to close.||Every Sage CRM opportunity names the user it is assigned to, so the sale belongs to somebody.||Sage CRM links each opportunity to a named contact person as well as to the company.||A Sage CRM opportunity stays in the system after it closes, keeps its closing date and can still be reported on.||Sage CRM ships a Reason For Loss field on the opportunity, but documents it as a notes box rather than a fixed list, so counting the reasons means grouping a report on it.||Sage CRM watches a mailbox and files arriving mail against the matching record by itself, but mail you send from your own email program only reaches the record if you BCC or forward it.||Sage CRM keeps appointments in step with the user's Exchange calendar in both directions, so a meeting booked in either place shows up in the other.||Any appointment or task in Sage CRM carries an Action saying what kind of work it is, and administrators can add their own actions to that list.||Sage CRM forecasts revenue natively, but its documentation never says whether its report builder can work out a win rate or a stage-to-stage conversion rate, so we could not settle it.

CRM; opportunity reporting unresolved

Salesflare keeps organizations, people and opportunities as separate records, but emails, meetings, calls and tasks are filed against the organization, so they reach an opportunity only through the organization they share.||An opportunity in Salesflare sits in a pipeline and moves through ordered stages you create, rename and reorder yourself, each with its own win probability.||Every Salesflare opportunity carries its own closed flag, so you can tell whether it is still live without checking which stage it is in.||Salesflare records that an opportunity is closed, but whether it was won or lost looks to be carried by the name of the stage, and the vendor documentation we could reach does not say whether anything else holds the outcome.||Every Salesflare opportunity has a built-in value field that the product treats as money and reports in the team's currency.||Salesflare ships no products or line items on an opportunity and no description box, so what is being sold goes in the opportunity name or in a field you add yourself.||Salesflare ships a close date on the opportunity and documents it as the date you expect to win it.||Salesflare uses one close date field: before closing it is the date you expect, and once the opportunity is closed as won or lost it is the date it actually ended.||Salesflare ships an owner field on the opportunity naming the user it belongs to, held separately from whoever created the record.||Salesflare ships a main contact field on the opportunity that links it to a named person, separate from the organization.||Closed opportunities stay in Salesflare and keep feeding the insights dashboard even after they are archived out of the pipeline view.||Salesflare ships a lost reason list an administrator controls, and the insights dashboard counts the most common reasons you lose.||Salesflare connects your mailbox both ways: you can write and reply from inside Salesflare, and mail you send from your usual mail program is picked up automatically.||Salesflare pulls meetings in from your calendar, but nothing you schedule inside Salesflare is pushed back out to it.||You can schedule tasks in Salesflare with a date and an owner, but the kinds of work it recognizes are Salesflare's own and there is no documented way to add your own types.||Salesflare reports stage-to-stage conversion in its funnel analysis, closing percentages per rep and across the team, and a probability-weighted expected revenue against target, all from its own reporting.

Not a CRM - fails on core objects; resolution unresolved

Salesforce ships opportunities, contacts, organizations and activities as separate records, and every opportunity must be linked to an organization.||Every Salesforce opportunity must sit at a stage taken from an ordered list, and administrators can add or edit those stages themselves.||The Salesforce opportunity itself carries a tick box showing whether it's closed, so you don't have to look up its stage to tell.||Salesforce puts a won tick box on the opportunity next to the closed one, and stage values are separately typed as closed won or closed lost.||Salesforce ships an Amount field on the opportunity, holding the estimated total value of the sale.||Salesforce ships a Products list on the opportunity that takes line items with a quantity, a sales price and a discount.||Salesforce ships a Close Date field, documented as the date you plan to close the opportunity.||Salesforce has only one close date field, but on marking an opportunity won it stamps that field with the current date if the stored date was still in the future.||Salesforce ships an Opportunity Owner field as standard, naming the user the opportunity is assigned to.||Salesforce ships Opportunity Contact Roles as standard, linking named people to the opportunity with no build work required.||A settled Salesforce opportunity stays an ordinary record, can still be reported on as open, closed or closed won, and keeps its stage history, which isn't deleted.||Salesforce ships no lost reason field on the opportunity, only free text, so the buyer has to create a lost reason list of their own to report on.||Salesforce can connect a user's Microsoft or Google mailbox so mail sent and received there is captured against matching records, and mail can be sent from a record.||Salesforce syncs activities with Microsoft or Google calendars in one or both directions, though custom fields don't sync and there's a 50,000 event ceiling per user.||Salesforce schedules activities from the record itself, and administrators can add their own activity types, so internal work such as preparing a quote gets its own type.||Salesforce ships forecasting as a built-in feature, and win rate and stage conversion can be built in the report builder, but no ready-made dashboard is supplied.

CRM

SAP Sales Cloud keeps organizations, contacts, opportunities and activities as separate records, and activities can be required on an opportunity before it is won.||An opportunity moves through the ordered phases of a sales cycle that administrators define, and the system keeps the history of those moves.||An SAP Sales Cloud opportunity carries its own status field, set up separately from the sales phases it moves through.||SAP reads won or lost from the same status field that says whether the opportunity is still running, rather than from a separate outcome field.||Every SAP opportunity carries a money amount - an expected value you enter, plus a negotiated total added up from its line items.||What is being sold sits on the SAP opportunity as product line items, each carrying its own negotiated value.||SAP ships a close date on the opportunity, and it marks the end point on the opportunity's progress bar.||SAP documentation reachable for Version 2 does not say whether the date an opportunity actually settled is recorded when it closes.||Each SAP opportunity has an owner, and routing rules can assign that owner automatically.||An SAP opportunity links to the actual people involved through contact roles, not just to the company.||Closed opportunities stay in SAP Sales Cloud and keep appearing in its analytics, quarters after they settled.||SAP records a coded reason when an opportunity's status changes, but nothing reachable says whether those reasons can be counted in a report.||SAP connects a Microsoft mailbox to Version 2 through a server-side groupware integration, but the reachable documentation does not say which way mail flows.||SAP documents a server-side mail integration for Version 2, but nothing reachable says whether appointments sync with an external calendar.||SAP activities carry a type, and administrators can add their own appointment and task categories beyond the ones SAP ships.||SAP reports win rates and a forecast natively, and shows opportunities moving between stages as counts and values rather than as a conversion rate.

CRM; actual close date, structured lost reasons, calendar sync unresolved

Smartsheet has no built-in contact, company, deal or activity record types - everything is a generic row on a sheet you design yourself.||There's no shipped pipeline-stage object; a stage list is just a dropdown column you build and order yourself.||Open-versus-closed isn't a field Smartsheet ships - you'd build one yourself from a generic column.||Won-versus-lost is not a field Smartsheet ships; it would be a column you create.||There is no shipped money field on a deal - you'd format a generic number column yourself.||Nothing native captures what's being sold - that's a column you'd add yourself.||There's no native expected-close-date field - any date column is one you name and use yourself.||There's no native actual-close-date field either - it would be a buyer-built date column.||No native 'owner' field exists on a deal - a Contact List column would be built and assigned by the buyer.||There's no shipped link from a deal to a person record - any linking is set up by the buyer.||It's not documented whether closed records are retained and still feed reports.||A lost-reason field is one you'd build, but Smartsheet's reports can count it once you do.||An email add-on can pull message content into a record one way; it can't send mail from Smartsheet or sync both ways.||Calendar sync only runs one direction at a time - out to Google or in as a read-only overlay, not both ways on the same event.||There's no built-in activity type to schedule - calls, meetings and tasks are all rows you define.||None of conversion rate, win rate or forecast comes built in - reports only total or count whatever columns you set up.

Not a CRM - fails on core objects, pipeline stages, status, resolution, value, scope of work, expected close date, actual close date, opportunity owner, linked buyer, schedulable activity types, opportunity reporting; record preservation unresolved

In Solve an opportunity is an activity you place on a person, company or project record rather than a record in its own right, and tasks cannot be attached to it, so the work and the sale meet only through the record they share.||A Solve deal records how far along it is as a percentage rather than moving through a named list of stages you define.||Every Solve deal carries its own status of Discussion, Pending, Won, Lost or On-hold, so you can tell whether it is still live without looking anywhere else.||Solve reads won or lost from the same status field that says whether the deal is still open, rather than from a separate outcome field.||Solve ships a money field on the deal, with a currency and the option to express the amount as a rate over a period.||Solve gives you a description box for what is being sold, and an administrator can add a field such as Product, but there are no priced line items.||Solve ships a closing date on the deal, and its opportunities report filters on it for the next seven or thirty days.||Solve holds one closing date on a deal, and vendor documentation does not say what that date means once the deal has been won or lost.||Every Solve deal names the user responsible for it, and the opportunities report groups deals by that person.||A Solve deal is created on a record, and that record can be the person you are selling to.||Closed Solve deals stay on the record and stay in the opportunities report, which can be filtered to won or to lost.||Solve ships no lost reason field, and although an administrator can add one, no vendor documentation says a report can count it.||Solve links Google Workspace mail onto the matching records automatically and sends mail back out through the same account, but only Google mailboxes connect.||Solve pushes the events it holds into a Google calendar and pulls the Google calendars you choose back onto your records, but only Google calendars connect.||Solve's activity types are fixed by the vendor, but the set covers tasks, follow-ups, calls and calendar events, each with an owner and a date.||Solve's opportunities report lists and groups deals but works out no win rate and no stage-to-stage conversion rate, and the vendor sends you to Google Sheets for pipeline and funnel reporting.

Not a CRM - fails on core objects, pipeline stages, opportunity reporting; actual close date, structured lost reasons unresolved

Companies, people, opportunities and activities are all separate records, but a person must sit under a company, and opportunities, tasks and activities hang off the company rather than linking directly to each other.||An opportunity carries a status field whose values are your own sales stages, kept in the order you drag them into, and every stage change is written to the opportunity's history.||Spotler CRM has no field saying whether an opportunity is open or settled - the vendor's own convention is that won means the probability was set to 100 percent and lost means zero, which is a habit, not a status.||You can tell a won opportunity from a lost one, but only from the probability being 100 or zero and from the stage name, not from a field whose job is the outcome.||Every opportunity has a value in money, worked out by the system from the quantity and unit price on its lines.||What is being sold is recorded as priced line items on the opportunity, each with a product, a quantity and a unit price.||The opportunity ships with a close date meaning when you expect the sale to land, and the forecast is built from it.||Spotler CRM ships one close date and calls it the expected one; nothing in the documentation says what that field holds after the sale is settled.||The person responsible is recorded on the company account, not on the opportunity, so a salesperson per opportunity is a field you add yourself.||An opportunity belongs to the company, not to a person - to record who you are selling to you have to add a contact field yourself.||Won and lost opportunities stay in the system and keep showing up in reports; records only disappear if somebody deletes them, and then they sit in a recycle bin.||Marking an opportunity lost records a reason from a list you control, and that field can be filtered and reported on.||Spotler CRM can connect to your mailbox and pull your sent and received mail onto the records, but you cannot write and send an email from inside the CRM.||CRM tasks can be pushed out to Google Calendar one at a time, but nothing comes back from the calendar and no Outlook or Microsoft 365 calendar sync is documented.||Any piece of work can be scheduled as a task with a date, a time and an owner, and the list of task types is yours to define.||Spotler CRM forecasts well, but its report builder can only add and count, so there is no native win rate and no stage-to-stage conversion rate.

Not a CRM - fails on core objects, status, opportunity owner, linked buyer, opportunity reporting; actual close date unresolved

Streak holds the opportunity as a box, with contacts and organizations as separate records linked to it through a column, though neither link is compulsory.||A Streak pipeline is an ordered set of stages a box moves through, and stages can be added, renamed, reordered or deleted; every pipeline carries a Stage column.||Streak's documentation doesn't list what a box holds, so whether it carries an open or closed marker couldn't be established either way.||Streak's documentation never lists what a box or a stage holds, so whether any won or lost marker is supplied couldn't be established either way.||Streak ships no value column on a box, so what a sale is worth has to be added by the buyer as an extra column.||Streak ships only a general Notes column on every box, which is free text rather than any way to set out what is being sold.||Streak ships no date column on a box, so an expected close date is something the buyer has to create for themselves.||Streak ships no date column in a pipeline, so anything holding the date a sale actually ended has to be created by the buyer.||Streak ships an Assigned To column in every pipeline, so every opportunity has a named owner without any setup.||Streak ships a Contacts and Organizations column by default, linking a box to both the people and the companies involved.||A settled Streak box stays in its pipeline and keeps counting in Streak's own reporting, including close rate and funnel reports.||Streak documents no lost reason at all, but the buyer can add a dropdown column of set choices and report on it through the Boxes by Column report.||Streak runs inside Gmail, so mail can be attached to a box from the inbox, and correspondence with a chosen contact or organization can be filed automatically.||A Streak task with a due date is automatically created in the user's Google Calendar, but the documentation describes nothing coming back the other way.||Streak lets you schedule tasks with a title, due date and assignee, but a task has no type, so one kind of work can't be separated from another.||Streak reports close rate as a percentage, but no stage-to-stage conversion rate is documented, and its projected close value relies on a date column the buyer creates.

Not a CRM - fails on value, expected close date, actual close date, schedulable activity types, opportunity reporting; status, resolution unresolved

Sugar keeps accounts, contacts, opportunities and activities as separate modules, and calls, meetings and tasks can all be pointed at the opportunity they belong to.||A Sugar opportunity moves along an ordered list of sales stages, each with its own win probability, and administrators can add stages of their own.||Sugar's field list shows a Status field on the opportunity but never says what it holds, while the vendor elsewhere treats open-or-closed as a property of the sales stage, so we cannot yet say either way.||Whether a Sugar opportunity was won or lost is read from the stage it ended in, which the system classifies as open, closed won or closed lost.||Every Sugar opportunity carries built-in money fields for its likely, best and worst amounts, in a chosen currency.||Sugar attaches priced line items to an opportunity, each naming a product from the catalog with a quantity and a unit price.||Sugar ships an Expected Close Date on the opportunity, documented as the date the sale is likely to be completed.||Sugar ships one close date, documented for the opportunity as the date the sale is expected to complete and for the line item as the date it expects to close or already has, so what it holds after close is unsettled.||Sugar ships an Assigned To field naming the user who owns the opportunity, and permissions can be scoped to the records a user owns.||A Sugar opportunity links to one or more contacts in their own subpanel, each with a role, separately from the account it belongs to.||Closed opportunities stay in Sugar and keep appearing in reports and dashlets that count won and lost business.||Sugar ships no loss-reason field, but an administrator can add a dropdown of reasons in Studio and count it in a report.||You can send mail from inside Sugar through your own Google or Outlook account, but the vendor says mail cannot be received into Sugar from your mailbox - it has to be forwarded or pushed in from an add-in.||Sugar's own calendar only publishes a read-only feed, but the vendor's Sugar Connect add-in keeps meetings and calls in step both ways with Google and Outlook calendars.||Sugar schedules calls, meetings and tasks with owners, dates and a linked record, but you cannot define activity types of your own.||Sugar reports win rate and stage-to-stage conversion through its prebuilt forecasting analytics, and forecasts revenue in its own Forecasts module - though the report builder itself can only count and total.

CRM; status, actual close date unresolved

SuiteCRM keeps organizations, people, opportunities and activities (calls/meetings/tasks) as separate linked records.||Opportunities move through a fixed, ordered list of sales stages that each record carries.||There's no separate open/closed field - you can only tell by which sales stage the deal sits in.||Won and lost are two of the sales-stage options, not a field of their own.||Every opportunity has a built-in money field.||Deals can carry itemized product/service line items through the built-in Quotes module.||There's a native, dedicated expected close date field.||There's no native field for when a deal actually closed, only the expected date.||Every opportunity has a native owner field, separate from who created the record.||A deal can be linked to a specific person, separately from its linked company.||Closed deals stay in the system and can still be reported on.||There's no built-in lost-reason field, but you can add one yourself and count it in reports.||The CRM sends mail and auto-imports shared inboxes, but a rep's own mailbox needs manual import.||Calendar events sync both ways with Google Calendar or a CalDAV calendar.||You can schedule calls, meetings and tasks, but can't define new activity types.||Reporting gives a revenue forecast natively, but no built-in win rate or stage-conversion rate.

Not a CRM - fails on status, actual close date, opportunity reporting

Teamgate keeps organizations, people, opportunities and activities as separate records that can be linked to one another.||A Teamgate opportunity sits in a pipeline and moves through ordered stages an administrator defines, each with its own win probability and time limit.||A Teamgate opportunity carries its own status of active, won or lost, so you can tell whether it is still live without checking its stage.||Teamgate reads won or lost from the same status that says whether the opportunity is still active, rather than from a separate outcome field.||Every Teamgate opportunity has a built-in price field in a chosen currency, which the forecast and the reports treat as money.||Teamgate lets you attach priced products from a catalog to an opportunity, so what is being sold is recorded as line items rather than only as prose.||Teamgate ships a close date on the opportunity, described by the vendor as the estimated closing date, and warns when it goes past.||Teamgate ships an estimated closing date, but nothing in its documentation establishes either way whether the date an opportunity actually settled is kept.||Every Teamgate opportunity is assigned to an owner, and the deals list can be filtered and reported by that owner.||A Teamgate opportunity is created against a company or a person, so it can be linked to the individual you are selling to.||Closed opportunities stay in Teamgate, are found again by filtering the list on status, and keep feeding the win, loss and revenue reports.||Marking a Teamgate opportunity lost requires a reason from a list administrators control, and those reasons are counted on the dashboard and in Insights.||Teamgate connects your mailbox both ways - mail sent from your normal mail program lands on the record, and you can read, reply and send from inside Teamgate.||Teamgate syncs meetings both ways with Office 365 and Outlook.com calendars; the Google route is documented only for meetings leaving Teamgate.||Teamgate activities carry a type, a time and an owner, and administrators can add their own types beyond the built-in Call and Task.||Teamgate reports stage-to-stage conversion, a win rate and a forecast from its own views, with the analytics module included on the paid plans.

CRM; actual close date unresolved

Trello only ships one real record type, the card - it has no separate person, company or activity records.||Trello's lists are ordered and every card records which list it sits in.||Trello has no won-lost status field apart from which column a card is in.||Nothing in Trello records a card as won or lost.||Trello ships no deal-value field, and its optional custom fields have no money type.||A card has a free-text description box but no structured product or line-item list.||Every card has a native due date field that can serve as an expected close date.||Trello marks a due date complete with a checkbox, not a completion date.||Cards have a native member-assignment field separate from who created the card.||Trello has no customer contact record, so a card cannot link to one.||Closed cards are kept and can be recovered, but it's unclear if they feed native reports.||There's no shipped lost-reason field, and native reports can't count custom fields either.||Trello turns incoming email into cards one-way; it does not connect to a mailbox.||Due dates export one-way to outside calendars; nothing syncs back into Trello.||There's no call, meeting or task type to schedule - just a due date on a card.||Native reporting shows card counts, not conversion rate, win rate or forecast.

Not a CRM - fails on core objects, status, resolution, value, actual close date, linked buyer, record preservation, structured lost reasons, email sync, schedulable activity types, opportunity reporting

Twenty keeps people, companies, opportunities and tasks as separate, linkable record types.||Each deal sits in one stage of an ordered pipeline, and that stage is stored on the deal.||There's no separate open-or-closed field on a deal - only the stage.||Nothing on a deal records whether it was won or lost.||Every deal has a built-in money field.||There's no shipped field or line-item list for what's being sold.||Deals carry a built-in projected close date.||There's no separate field for the date a deal actually closed.||Each deal has a shipped owner field separate from who created it.||A deal can link directly to a person, not just the company.||Closed deals stay in the system and remain available for reporting.||There's no field to record why a deal was lost.||Twenty connects to a real mailbox both to receive and to send email.||Calendar events flow into Twenty from your calendar, one direction only as documented.||Tasks aren't categorized into types like call, meeting or email.||Dashboards can chart deal data but don't ship named win-rate or forecast metrics.

Not a CRM - fails on status, resolution, scope of work, actual close date, structured lost reasons, schedulable activity types, opportunity reporting

Vtiger holds opportunities, contacts, organizations and activities as separate records, and an organization shows both its people and its opportunities.||A Vtiger opportunity carries a Sales Stage changed from a drop-down or by dragging the record across a board, and the stages run in a documented order.||Vtiger's documentation never lists the fields an opportunity carries, so whether it holds an open or closed marker couldn't be established either way.||Vtiger's documentation doesn't list what an opportunity or a stage holds, so whether any won or lost marker is supplied couldn't be established either way.||Vtiger ships an Amount field on the opportunity, added up automatically from the prices of the line items.||Vtiger ships revenue line items on the opportunity, holding the products and services being sold.||Vtiger ships an Expected Close Date field on the opportunity, which the vendor uses by name in its own worked examples.||Vtiger ships an expected close date, but the documentation didn't establish either way whether anything records the date a sale actually ended.||Vtiger ships an Assigned To field on the opportunity and filling it in is compulsory, so every opportunity has a named owner.||Vtiger ships a built-in link between an opportunity and contacts, and it allows several people to be attached to the same opportunity.||A settled Vtiger opportunity stays a live record and keeps feeding its reporting, covering won value against target and the work a team closed and lost.||No ready-made lost reason field appears in Vtiger's documentation, but the buyer can add their own list of set choices to the opportunity and report on it.||Vtiger syncs mail both ways with a connected Gmail, Outlook or other mailbox, and mail is related to records so the correspondence sits with the customer.||Vtiger syncs activities both ways with Microsoft Exchange and syncs calendar entries with Google, though the Exchange route needs software installed on the mail server.||Vtiger schedules activities from the calendar or from inside an opportunity, and administrators can add their own activity types on top of the six supplied.||Vtiger ships forecasting against targets and a report builder, but the documentation didn't establish either way whether win rate or conversion reports are supplied.

CRM; status, resolution, actual close date, opportunity reporting unresolved

Workbooks keeps organizations, people, activities and opportunities as separate records that link to one another.||An opportunity in Workbooks sits on a stage from an ordered list that administrators define, with each stage carrying its own order, probability and forecast setting.||Workbooks holds whether an opportunity is open or closed on the stage it sits in rather than on the opportunity record, and reports tell open from closed by matching stage names.||Workbooks can clearly tell won from lost in its reports, but published documentation does not show where that outcome is stored on the record.||Every Workbooks opportunity carries a money amount in a chosen currency, worked out from the line items on it.||Workbooks records what is being sold as priced line items on the opportunity, drawn from a product book or typed in.||Workbooks makes you set a close date on every opportunity, meaning the date you expect the sale to land.||Workbooks documents one close date, the one you expect; whether it also keeps the date a sale actually ended could not be confirmed.||Each Workbooks opportunity is assigned to a named user, and reports break pipeline and results down by that person.||A Workbooks opportunity lists the people involved in the deal, each with their role, and you can email them from the opportunity.||Closed opportunities stay in Workbooks and keep showing up in reports, which is what win rates and historic sales figures are built on.||Workbooks has a Lost Reason field on the opportunity, and you can count the reasons by building a grouped report yourself.||You send email from inside Workbooks and it is filed against the record, while mail from Outlook or Gmail comes back in through Mail Sync, a paid add-on, once you tag or save it.||Workbooks meetings and Outlook calendar entries keep each other up to date, including sending the invites; with Google only the incoming direction is documented.||Any piece of work can be scheduled as an activity in Workbooks with an owner and a due date, and you can add your own activity types.||Workbooks reports a rep's win rate and a weighted pipeline forecast out of the box, but the conversion rate from one stage to the next needs the separately licensed Audit extension.

Not a CRM - fails on status; resolution, actual close date unresolved

Zendesk Sell keeps people and companies in one Contact record type separated by a true-or-false flag rather than as two objects, though deals and tasks link to both.||A Zendesk Sell deal sits on a stage, and stages carry their own position in the pipeline, so the sequence is real data you can add to and rename.||A Zendesk Sell deal has no open or closed marking of its own - that is read from the stage it sits in, which the vendor flags as an active or a closed stage.||Won and lost in Zendesk Sell are stages, so the outcome is read from the category on the stage rather than from anything held on the deal.||Every Zendesk Sell deal has a built-in value field with its own currency code, so the platform treats the figure as money.||Zendesk Sell has a product catalog, and products attach to a deal as priced line items with quantity and discount rather than as a free-text note.||Zendesk Sell ships an estimated close date on the deal, held separately from the date the deal actually closed.||Zendesk Sell stamps a close date on the deal when it moves into a closed stage, kept apart from the estimated close date.||Zendesk Sell ships an owner field on the deal naming the user it is assigned to, separate from whoever created it.||A Zendesk Sell deal carries a primary contact, so the sale is linked to a named person and not only to a company.||Closed deals stay in Zendesk Sell and keep feeding its reports, including sales totals, loss reasons and historical win rates.||Zendesk Sell records a loss reason on the deal from a list the account defines, and ships a Deal Loss Reasons report that counts them.||Zendesk Sell connects to your Gmail, Microsoft 365 or Exchange mailbox, mirrors mail onto the matching records, and lets you send from inside Sell.||Appointments in Zendesk Sell and Google Calendar sync both ways, including deletions, so a meeting booked in either place shows in the other.||Zendesk Sell schedules tasks and appointments but the kinds of activity are fixed by the vendor - you cannot add your own type.||Zendesk Sell reports stage-to-stage conversion, win rates and a sales forecast from its own reporting, with the conversion and win rate reports on its top plan.

Not a CRM - fails on core objects, status

Zoho CRM ships separate opportunity, contact and organization records plus tasks, meetings and calls, and every opportunity must name an organization.||A Zoho CRM opportunity moves through an ordered set of stages that an administrator configures, and each pipeline can carry its own set of stages.||Nothing on the Zoho CRM opportunity itself says whether it's still live, so you have to look up its stage, which is marked open, closed won or closed lost.||Zoho CRM carries the win or loss on the stage rather than on the opportunity, so nothing on the record itself tells you which of the two it was.||Zoho CRM ships an Amount field on the opportunity, holding the expected closing value as a sum of money.||Zoho CRM ships a Products list on the opportunity record, alongside Quotes and Sales Orders.||Zoho CRM ships a Closing Date field on the opportunity, documented as the expected close date, and filling it in is compulsory.||Zoho CRM has only the one expected close date, and closing an opportunity raises a Verify Details window where the user completes or leaves that date as it stands.||Zoho CRM ships a Deal Owner field as standard, which assigns each opportunity to a named user.||Zoho CRM ships a Contact Name field linking the opportunity to a person, with Contact Roles available as a related list.||A settled Zoho CRM opportunity stays a normal record and keeps appearing in reporting, including a Lost Deals report and the achieved figure in Forecasts.||Zoho CRM shows a Reason for Loss field when an opportunity is closed as lost, and it's a pick-from-a-list field that can be filtered and reported on.||Zoho CRM can attach a user's mailbox so sent and received mail is associated with the matching person, and mail can be composed and sent from inside the CRM.||Zoho CRM syncs with Google Calendar one way or both ways, and with an iOS calendar both ways, but repeating appointments are left out of both.||Zoho CRM schedules tasks, meetings and calls with reminders and recurrence, but there's no documented way to add an activity type of your own beyond those three.||Zoho CRM ships a Stage dashboard component giving stage conversion rates and an overall win rate, plus a forecasting module run against monthly or quarterly targets.

Not a CRM - fails on status