Dedicated CRM

Nimble

Not a CRM - fails on core objects

Every verdict, with its evidence

Core objects

Not at all

Deals and activities are first-class records: a deal carries name, amount, probability, pipeline, stage, owner, expected and actual close dates and Related Contacts, and activities (tasks, events, calls and administrator-defined types) can be raised from a contact, a company or a deal. The organization is not a separate object. Nimble's API states that a contact carries a record_type of either person or company, so a company is a record type inside the contacts object rather than a distinct entity - one store, one endpoint family, one custom-field target, with a type discriminator on the record. Nimble presents it as an organization in the interface, with separate People and Companies views, distinct Add Person and Add Company actions and automatic matching of imported company names to contacts, but interface behavior is not the test. A second constraint compounds it: the deal's association field is documented only as Related Contacts, and no vendor page states that a company record can be attached to a deal.

Source: https://www.nimble.com/developers/docs/, https://support.nimble.com/en/articles/2166089-nimble-contacts-tab-overviews, https://support.nimble.com/en/articles/502860-nimble-csv-import-wizard, https://support.nimble.com/en/articles/6716398-using-deal-s-pipeline-and-lists, https://support.nimble.com/en/articles/2924022-create-custom-activity-types-in-nimble

Verification: Verified

Pipeline stages

In full

A deal sits in a pipeline made of ordered stages that an administrator defines under Settings, each stage carrying a name, guidance for the team, an expected number of days in stage and a default probability. Deals are advanced by dragging from one stage to the next on the board, or from the deal record menu.

Source: https://support.nimble.com/en/articles/6710434-create-multiple-custom-deal-pipelines, https://support.nimble.com/en/articles/6716398-using-deal-s-pipeline-and-lists

Verification: Verified

Status

In full

The outcome is applied to the opportunity itself, not read off its stage. The vendor documents marking a deal Won or Lost from the deal's own three-dot menu, or by dragging it into the Won or Lost drop areas below the board, and stage configuration carries only a name, guidance, expected days in stage and a default probability, with no closed flag or stage type. That the Lost by Stage report can still report the stage a lost deal was in confirms the outcome is held apart from the stage.

Source: https://support.nimble.com/en/articles/6716398-using-deal-s-pipeline-and-lists

Verification: Verified

Resolution

In part

The same per-deal action that closes the opportunity records which way it went: the user chooses Won or Lost on the deal, and won and lost deals then sit in their own lists. A lost reason can also be attached, configured per pipeline. The record overview article does not name a status field explicitly, so the evidence is the documented behavior rather than a named attribute.

Source: https://support.nimble.com/en/articles/6716398-using-deal-s-pipeline-and-lists

Verification: Verified

Actual close date

In full

Nimble ships an Actual close date on the deal, listed by the vendor as a sort option alongside Expected close date, so the two are distinct fields. It is a human entry rather than a stamp: the vendor states that when a deal is dropped into Won or Lost the user is prompted to supply the amount, the close date and notes. Nothing in the documentation says Nimble fills the date itself.

Source: https://support.nimble.com/en/articles/7030974-how-to-sort-and-filter-deals-in-nimble

Verification: Verified

Record preservation

In full

Closed opportunities remain in the account and remain in Nimble's own reporting. Won and lost deals sit in their own lists, which the vendor says carry the same sorting and filtering as any other pipeline list, and the Reports tab ships Deals won over time, Lost by Stage and Deals lost by reasons.

Source: https://support.nimble.com/en/articles/6856776-exploring-the-reports-tab-in-nimble

Verification: Verified

Structured lost reasons

In full

Lost reasons are configured on the pipeline itself, so a lost deal is tagged from a controlled list the administrator maintains rather than free text. The list is reportable: a Deals lost by reasons report groups losses by reason, and the API exposes lost reasons as a managed collection under deal pipelines.

Source: https://support.nimble.com/en/articles/6710434-create-multiple-custom-deal-pipelines, https://support.nimble.com/en/articles/6856776-customize-your-dashboard-with-reports, https://nimble.readthedocs.io/en/latest/

Verification: Verified

Email sync

In full

Connecting a mailbox by OAuth for Gmail and Microsoft 365, or by IMAP for other providers, creates what the vendor calls a bidirectional sync, pulling in the Inbox, Sent, Starred, Archive and Trash folders from the preceding ninety days and continuing forward. Mail can be composed and sent from inside Nimble, and synced messages surface in the Message tab and on the Interactions tab of the matching contact. There is no reliance on a BCC dropbox.

Source: https://support.nimble.com/en/articles/502839-get-started-connecting-your-email-account-to-nimble, https://support.nimble.com/en/articles/6873721-nimble-s-message-tab

Verification: Verified

Calendar sync

In full

Google Calendar and Microsoft 365 calendars connect to Nimble and the vendor describes the result as a two-way sync of events, which are the activity object rather than a date field on another record. Events created in Nimble reach Microsoft 365 on web and desktop immediately, while events created externally flow into Nimble hourly while a user is signed in and every three hours otherwise. Synced events appear on the Activities tab and on the Interactions tab of the related contact.

Source: https://support.nimble.com/en/articles/502832-google-calendar-sync, https://support.nimble.com/en/articles/1473834-microsoft-365-calendar-integration, https://support.nimble.com/en/articles/2043987-get-started-setting-up-calendars-in-nimble

Verification: Verified

Schedulable activity types

In full

Scheduled and completed activities are created inside Nimble and cover tasks with due dates, calendar events and calls. The type set is not fixed: an administrator creates custom activity types under Settings, choosing the form and whether completing that type updates the contact's last-contacted date, with webinars, appointments and campaigns given as examples. New activities of a custom type are raised from a contact, a company, a deal or the Activities tab, and the activity list filters and edits inline on Related Contact and Related Deal.

Source: https://support.nimble.com/en/articles/2924022-create-custom-activity-types-in-nimble, https://support.nimble.com/en/articles/502882-nimble-activities-tab-overview, https://support.nimble.com/en/articles/2511394-nimble-activity-listing-feature

Verification: Verified

Opportunity reporting

In part

Two of the three are documented in the knowledge base. Stage conversion is covered by the Pipeline Funnel widget, which the vendor documents as graphing how well deals convert between stages and as displaying deal count and conversion percentage, so a rate rather than a distribution is a stated output; note that its population is deals won or lost with a close date in the period, so it is built from closed deals rather than from open pipeline. Forecasting is covered by the Revenue Forecast widget, projecting from open and won deals against a first-class expected close date field on the deal, with a per-stage default probability configured on the pipeline - although the vendor does not state that the projection is weighted by it. An overall win rate is not documented: the deals widgets are Revenue Forecast, Pipeline Funnel, Deals Won Over Time, Deals Progress, Lost by Stage, Deals Lost by Reasons, Upcoming Deals and Revenue By Pipeline, with average duration per stage and average deal value in the reports tab, none of which expresses won as a proportion of closed. Reporting is a fixed widget set chosen from a list and filtered, not a builder, so the buyer cannot construct the missing rate.

Source: https://support.nimble.com/en/articles/6929317-nimble-today-page-pipeline-funnel-widget, https://support.nimble.com/en/articles/6929289-nimble-today-page-revenue-forecast-widget, https://support.nimble.com/en/articles/6856776-exploring-the-reports-tab-in-nimble, https://support.nimble.com/en/articles/6930983-nimble-s-deals-widgets-for-today-page, https://support.nimble.com/en/articles/6843724-create-and-manage-your-dashboards

Verification: Verified