Bigin by Zoho CRM - is it a CRM?

Every verdict, with its evidence

Core objects

In full

Bigin's data is organized into modules: Pipelines, Contacts, Companies, Products, Activities and Dashboards. The pipeline record is the opportunity, and its default fields include Company Name and Related Contacts alongside Amount, Closing Date, Sub-Pipeline and Stage. A pipeline record carries one primary Contact Name plus a Secondary Contacts field for additional people. Activities are tasks, events and calls, and a task is created with a Related To selection covering contacts, companies and pipeline records. Company association on a pipeline record is a field rather than a requirement, and the vendor does not document it as mandatory.

Source: https://help.zoho.com/portal/en/kb/bigin/get-started-with-bigin/articles/basic-terminologies, https://help.zoho.com/portal/en/kb/bigin/customization/articles/default-fields-bigin, https://help.zoho.com/portal/en/kb/bigin/faqs/record-management/articles/can-i-associate-multiple-contacts-to-a-pipeline-record, https://help.zoho.com/portal/en/kb/bigin/modules/activities/articles/creating-tasks

Verification: Verified

Pipeline stages

In full

A pipeline is defined by the vendor as a set of stages a prospect passes through, and every pipeline record sits on a named stage within a sub-pipeline. The pipeline view presents records grouped by stage as a board, and a record is advanced by dragging it between stage columns or by clicking a stage in the record's timeline. A pipeline may hold up to 25 stages including defaults, must retain at least two open stages, and may carry up to five closed stages. Stage transition rules can further constrain which stage a record may move to next and can require named fields to be completed before the move is allowed.

Source: https://help.zoho.com/portal/en/kb/bigin/team-pipelines/articles/team-pipelines, https://help.zoho.com/portal/en/kb/bigin/modules/pipelines/articles/pipeline-records, https://help.zoho.com/portal/en/kb/bigin/automation/articles/stage-transition-rules

Verification: Verified

Status

Not at all

The pipeline record carries Stage as a plain picklist value and nothing else about its state: the documented default fields for the Pipelines module are name, owner, company, related contacts, sub-pipeline and stage, amount, closing date and description, with no state attribute, and the API response for the module returns Stage as a string such as Closed Won. Whether that stage is live or settled is held in the stage's own metadata, where each picklist value carries a deal_category of Open, Closed Won or Closed Lost plus a probability and a forecast category. A pipeline is configured as a set of open stages and closed stages. Ruled 30 Aug 2026: status and stage must be completely separate values, so an outcome that is a property of the stage is not a status attribute at all.

Source: https://help.zoho.com/portal/en/kb/bigin/customization/articles/default-fields-bigin, https://www.bigin.com/developer/docs/apis/v2/field-meta.html, https://help.zoho.com/portal/en/kb/bigin/team-pipelines/articles/pipeline

Verification: Verified

Resolution

In part

Won and lost are also read from the stage rather than the record. The stage picklist metadata splits the settled categories into Closed Won and Closed Lost, with matching forecast_type and a probability of 100 or 0. In the interface the outcome is applied by dragging the record onto a Pipeline Record Won or Pipeline Record Lost target, which sets its stage; no won or lost attribute exists among the module's default fields.

Source: https://www.bigin.com/developer/docs/apis/v2/field-meta.html, https://help.zoho.com/portal/en/kb/bigin/modules/pipelines/articles/pipeline-records, https://help.zoho.com/portal/en/kb/bigin/customization/articles/default-fields-bigin

Verification: Verified

Value

In full

Amount is a shipped currency field, the amount expected after closing.

Source: https://help.zoho.com/portal/en/kb/bigin/customization/articles/default-fields-bigin, https://www.bigin.com/developer/docs/apis/deals-response.html, https://help.zoho.com/portal/en/kb/bigin/modules/products/articles/manage-products

Verification: Verified

Scope of work

In full

The API response ships Associated_Products, and products associate to pipeline records.

Verification: Verified

Expected close date

In full

Closing date is a shipped field defined as the expected closing date.

Verification: Verified

Actual close date

Not at all

The only date of that kind in the module is Closing date, which the vendor defines as the expected closing date of the pipeline record, and which sits alongside Amount as the amount expected after closing. The published list of default fields for the Pipelines module contains no second date for when the record was actually settled, and the module's API response returns only Closing_Date, Created_Time, Modified_Time and Last_Activity_Time. The record's Timeline tab holds a history of what was done to the record, but that is an audit trail rather than a field.

Source: https://help.zoho.com/portal/en/kb/bigin/customization/articles/default-fields-bigin, https://www.bigin.com/developer/docs/apis/deals-response.html

Verification: Verified

Opportunity owner

In full

Pipeline Record Owner is a shipped lookup naming the assigned user.

Verification: Verified

Linked buyer

In full

Related contacts is a shipped lookup, separate from Company name.

Verification: Verified

Record preservation

In full

Closing a record means moving it to a closed stage, not removing it: the module's API response documents a record returned with Stage set to Closed Won, and the vendor's own tips advise filtering old closed lost records out of the working view precisely because they stay in the pipeline. Deletion is a separate action that sends the record to the recycle bin. Dashboard charts, KPIs and target meters are built by selecting a module, and the vendor states that default Deals or Pipeline dashboards ship with the product. Note that the documentation does not spell out in so many words that closed records are included in those dashboards; the finding rests on closed records remaining ordinary records of the module the dashboards read.

Source: https://www.bigin.com/developer/docs/apis/deals-response.html, https://help.zoho.com/portal/en/kb/bigin/modules/dashboards/articles/dashboards, https://help.zoho.com/portal/en/kb/bigin/faqs/trouble-shooting-faqs/articles/dashboards-17-11-2025

Verification: Verified

Structured lost reasons

In part

No reason for loss field appears in the vendor's list of default pipeline record fields, and no vendor article describes a reason being requested when a record is marked lost. The default field that could hold one is Description, which is free text. A structured reportable field is reachable by configuration rather than out of the box: custom picklist fields can be created on the Pipelines module, a stage transition rule can mandate that a named field is completed before a record moves to a given stage, and dashboard charts can be grouped by a module field. That combination gives a structured, mandated and reportable lost reason, but the buyer builds it.

Source: https://help.zoho.com/portal/en/kb/bigin/customization/articles/default-fields-bigin, https://help.zoho.com/portal/en/kb/bigin/customization/articles/modules-and-fields, https://help.zoho.com/portal/en/kb/bigin/automation/articles/stage-transition-rules, https://help.zoho.com/portal/en/kb/bigin/modules/dashboards/articles/dashboards

Verification: Verified

Email sync

In part

A user connects a personal mailbox to Bigin over IMAP, with Gmail, Microsoft 365, Outlook Mail, Zoho Mail and other IMAP services named and direct sign-in offered for the major providers. Email is composed and sent from records in the Contacts and Pipelines modules, but not from Companies. Once a mailbox is configured, the Emails tab on a record shows sent and incoming email interactions, and messages can be replied to and forwarded from there. What the vendor does not state anywhere is that mail sent from the user's own email client outside Bigin is pulled back onto the record, so the return path is documented for incoming mail only. A separate mechanism forwards incoming mail to a Bigin email alias, which is a capture address rather than a mailbox sync. An admin setting governs whether a user's email is private, public or the user's choice.

Source: https://help.zoho.com/portal/en/kb/bigin/channels/email/articles/em, https://help.zoho.com/portal/en/kb/bigin/channels/email/articles/sending-email-from-bigin, https://help.zoho.com/portal/en/kb/bigin/faqs/emails/articles/how-can-i-view-incoming-emails-in-bigin, https://help.zoho.com/portal/en/kb/bigin/faqs/emails/articles/how-to-configure-imap-in-bigin, https://help.zoho.com/portal/en/kb/bigin/channels/email/articles/forwarding-your-incoming-emails-to-bigin, https://help.zoho.com/portal/en/kb/bigin/channels/email/articles/email-sharing

Verification: Verified

Calendar sync

In full

Events are one of the three activity types in Bigin's Activities module, and both calendar integrations sync that object rather than a generic date field. The vendor states that integrating Microsoft 365 or Outlook with Bigin synchronizes contacts and events from Bigin to Microsoft 365 and the other way round, and that when a contact or event is added in one account it is updated in the other automatically. The Google integration is described in the same terms, with events and contacts activated separately. Synced Bigin events appear in Microsoft 365 under a dedicated Bigin Calendar category. The stated limitation is that recurring events are not synchronized, and contact sync with Google runs on a 24 hour cycle.

Source: https://help.zoho.com/portal/en/kb/bigin/integration/articles/integrate-microsoft-365-bigin, https://help.zoho.com/portal/en/kb/bigin/integration/articles/integrate-google-bigin, https://help.zoho.com/portal/en/kb/bigin/get-started-with-bigin/articles/basic-terminologies

Verification: Verified

Schedulable activity types

In part

Activities are scheduled inside Bigin and the set covers the three required shapes: tasks carry a name, owner, due date, priority, status, repeat and reminder; events carry a title, location, from and to times, participants and reminder; calls carry a start time, call type, purpose, duration and outcome. All three can be related to contacts, companies and pipeline records, and the Activities module offers a calendar view. The constraint is that the type set itself is fixed at task, event and call, presented as three sub-tabs, and no vendor article describes creating a new activity type. A task's name is free text so internal work such as preparing a quote can be scheduled, and custom fields including picklists can be added to the Tasks, Events and Calls modules, but a user-defined type is a field the buyer adds rather than a native construct.

Source: https://help.zoho.com/portal/en/kb/bigin/modules/activities/articles/creating-tasks, https://help.zoho.com/portal/en/kb/bigin/customization/articles/default-fields-bigin, https://help.zoho.com/portal/en/kb/bigin/modules/activities/articles/calendar-view-for-activities-module-in-bigin, https://help.zoho.com/portal/en/kb/bigin/customization/articles/modules-and-fields

Verification: Verified

Opportunity reporting

Not at all

Reporting is a dashboard the buyer builds from three component types - charts, KPIs and target meters. Charts are built on a module and an optional related module, with a measure on the Y axis, a grouping and criteria filters, across nine chart types including a funnel. Because Stage, Amount and Closing Date are default pipeline record fields, a funnel grouped by stage and a chart of amount grouped by closing date are both constructible, and a Stage History related module lets charts analyze how long records sat in each stage. What is missing is computation. The vendor documents no percentage, ratio or conversion measure, so stage conversion and overall win rate can only be read off record counts rather than produced as rates, and neither is therefore available. No forecasting feature, weighted projection or win probability appears anywhere in Bigin's documentation, including its AI material, so at most a chart of amount by closing date stands in for a forecast. Nothing purpose-built for any of the three ships; the buyer assembles charts in a general dashboard builder.

Source: https://help.zoho.com/portal/en/kb/bigin/modules/dashboards/articles/dashboards, https://help.zoho.com/portal/en/kb/bigin/customization/articles/default-fields-bigin, https://help.zoho.com/portal/en/community/topic/gain-deeper-insights-with-stage-history-and-associated-products-in-bigin-dashboards

Verification: Verified