Membrain

Companies, contacts, sales projects and activities are four separate record types with their own API endpoints - /companies/, /contacts/, /opportunities/ and /activities/ - and each can be linked to the others. A company record holds its own information and lists the contacts, prospects, sales projects, account growth projects and tickets related to it, and a contact is a person with the company they work for held as a link to that company record. The sales project carries CompanyId, and activities of every kind can be related to sales projects, prospects, companies, contacts and account growth projects, appearing in the project's activity stream.

Source: https://www.membrain.com/developers/api-documentation, https://www.membrain.com/help-center/crm/managing-companies, https://www.membrain.com/help-center/crm/managing-contacts, https://www.membrain.com/help-center/getting-started-with-membrain/creating-activities, https://www.membrain.com/help-center/active-pipeline/sales-projects-an-overview

Verification: Verified

A sales project runs on a sales process, and a process is built as an ordered sequence of stages, each holding the steps that have to be completed before the project advances. The opportunity object carries ProcessId, ProcessCurrentStageId and ProcessCurrentStageName, so its position in the sequence is held on the record. Stages are created, renamed and deleted in the process editor, and the pipeline view shows projects moving left to right through each stage of the process from beginning to end.

Source: https://www.membrain.com/developers/api-documentation, https://www.membrain.com/help-center/active-pipeline/creating-a-sales-process, https://www.membrain.com/help-center/active-pipeline/active-pipeline-an-overview

Verification: Verified

The opportunity object enumerated in Membrain's API reference carries a Status property, documented as a string representing the current status of the opportunity, either Open, Won or Archived. It is held separately from ProcessCurrentStageId, so whether a sales project is still running can be read from the record itself without inspecting the stage it sits in.

Source: https://www.membrain.com/developers/api-documentation

Verification: Verified

The outcome is carried by the same Status property that answers whether the sales project is still open: its documented values are Open, Won and Archived, with Archived being the closed-but-not-won state. The opportunity object also carries ProcessEndedDate, documented as the date the opportunity was either won or archived, and LostReasonId, documented as referencing a win or archived reason given when the opportunity is closed. No attribute whose sole job is the outcome, held apart from the open-or-closed fact, appears in the enumeration.

Source: https://www.membrain.com/developers/api-documentation, https://www.membrain.com/help-center/active-pipeline/adding-won-archived-reasons

Verification: Verified

The opportunity object ships Value, documented as a number representing the value of the opportunity in the system base currency, alongside ValueInCurrency, ValueCurrencyId and WeightedValue. Value is one of the fundamental fields on the sales project and can be set directly or built up from the products attached to the project.

Source: https://www.membrain.com/developers/api-documentation, https://www.membrain.com/help-center/active-pipeline/setting-value-on-sales-project, https://www.membrain.com/help-center/active-pipeline/sales-projects-an-overview

Verification: Verified

Products attach to a sales project as line items. Each item is picked from the product list and carries a description, a quantity, a unit price as either a fixed or a recurring charge, a unit discount and a unit cost, and the project shows a summary of value broken into fixed and recurring, which can be set to drive the project value. Quotes and orders build on the same product rows, and the API exposes /opportunityProducts/, /quoteRows/ and /orderRows/.

Source: https://www.membrain.com/help-center/active-pipeline/adding-products-to-a-sales-project, https://www.membrain.com/help-center/active-pipeline/getting-started-with-products-for-sales-projects, https://www.membrain.com/developers/api-documentation

Verification: Verified

The opportunity object ships EstimatedClosingDate, documented as the date the opportunity is expected to close, resolved from either ObjectiveEstimatedClosingDate or SubjectiveEstimatedClosingDate. Closing date is one of the fundamental fields shown on a sales project and can be projected from the expected duration of the process stages or taken from a date field.

Source: https://www.membrain.com/developers/api-documentation, https://www.membrain.com/help-center/active-pipeline/setting-closing-date-on-sales-project

Verification: Verified

The opportunity object ships ProcessEndedDate, documented as the date when the opportunity was either won or archived, with a date starting 1753 standing for an empty value. It is a separate attribute from EstimatedClosingDate and from ProcessStartedDate, so the date a sale actually ended is kept alongside the date it was expected to end.

Source: https://www.membrain.com/developers/api-documentation

Verification: Verified

The opportunity object ships OpportunityOwnerId, documented as a GUID referencing the user that owns the opportunity, with OpportunityOwnerName alongside it. Owner is one of the fundamental fields on the sales project, and it is held separately from the CreatedById and ChangedById audit stamps.

Source: https://www.membrain.com/developers/api-documentation, https://www.membrain.com/help-center/active-pipeline/sales-projects-an-overview

Verification: Verified

Contacts are attached to a sales project as stakeholders and participants, a shipped facility rather than one the buyer builds. A stakeholder is a contact assigned a key role within the sales project, with five default roles supplied and renameable, several contacts allowed per role and one contact allowed in several roles, plus an influence and attitude rating toward that project. The API exposes the association as /processContainerContacts/, which links contacts to process containers including opportunities and carries the role, attitude and influence. There is no single primary-contact attribute on the opportunity object itself: the object enumerates CompanyId, and the person link is held on the association.

Source: https://www.membrain.com/help-center/process-tools/stakeholders, https://www.membrain.com/help-center/active-pipeline/sales-projects-an-overview, https://www.membrain.com/developers/api-documentation

Verification: Verified

Won and archived sales projects stay in the account and stay measurable. Closed projects remain reachable through global search and filtered list views, an archived project can be brought back as a prospect keeping its information, and reactivating within three months returns the project to the state it was in before it was closed. The Win/Loss Analysis reports on won and archived projects together, showing counts, percentages, sales cycle duration, time in each stage and the reasons given for each outcome, all of which need the closed records to persist and stay queryable.

Source: https://www.membrain.com/help-center/active-pipeline/sales-project-status-reactivate-vs-start-over, https://www.membrain.com/help-center/sales-analysis/win/loss-analysis, https://www.membrain.com/help-center/active-pipeline/auto-archiving-sales-projects

Verification: Verified

Administrators define their own lists of won reasons and archived reasons in system setup, and Membrain prompts the user to select one when a sales project is closed. The reason is stored on the record as LostReasonId with LostReasonName, alongside an optional LostComment, and the values feed the Win/Loss Analysis, which reports on the reasons the team gives for winning and losing. Because the reason is a defined option rather than free text, it is countable.

Source: https://www.membrain.com/help-center/active-pipeline/adding-won-archived-reasons, https://www.membrain.com/help-center/sales-analysis/win/loss-analysis, https://www.membrain.com/developers/api-documentation

Verification: Verified

A user connects their own mailbox - Gmail through Google Workspace, Office 365, or another server over IMAP and SMTP - and mail then runs both ways. Messages are composed, sent and replied to inside Membrain and land in the sales inbox and on the activity stream of the related project, company or contact. In the other direction, Membrain reads the connected mailbox and autosaves mail sent or received in the user's own client onto the matching prospect, sales project or account growth project, matching on the sender, recipient or attendee address against the project's stakeholders. A BCC address exists as well, but it is an alternative for users who do not connect an account rather than the mechanism. Mail moved into folders outside the primary inbox at the provider does not sync.

Source: https://www.membrain.com/help-center/crm/email-setup, https://www.membrain.com/help-center/crm/email-in-membrain, https://www.membrain.com/crm/autosave-autorelate-email-and-appointments, https://www.membrain.com/help-center/crm/email-troubleshooting-technical-details

Verification: Verified

Membrain's sales calendar syncs two ways with Google Calendar and with Office 365 or Exchange. Vendor documentation states that appointments created in Membrain's sales calendar appear in the connected calendar and that appointments made in the connected calendar appear in Membrain's sales calendar. The unit synced is the appointment activity, which carries a type, an owner, participants and a link to the project, and autosave relates an incoming appointment to the matching project on the attendee's email address. Appointments created before the integration was switched on do not sync, and a first sync can take up to 48 hours.

Source: https://www.membrain.com/help-center/crm/calendar/calendar-sync-setup, https://www.membrain.com/crm/autosave-autorelate-email-and-appointments

Verification: Verified

Activities in Membrain are emails, calls, notes, appointments and tasks, and each carries an activity type chosen from a list. Administrators create, edit, merge and delete activity types in system setup and choose in a Usable For setting which kinds each type applies to, among task, note, appointment, call, mail and coaching activity, so the taxonomy is defined by the buyer. A task is scheduled with a deadline date and time, an activity type, an assigned colleague, participants, a priority flag and a link to the project it belongs to, and can be reassigned to another user. Custom fields can also be added to activities.

Source: https://www.membrain.com/help-center/getting-started-with-membrain/managing-activity-types, https://www.membrain.com/help-center/crm/working-with-tasks, https://www.membrain.com/help-center/getting-started-with-membrain/creating-activities, https://www.membrain.com/help-center/crm/using-custom-fields-with-activities

Verification: Verified

Two of the three required reports are native. Win rate is reported in the Win/Loss Analysis, which answers what the current win rate is and breaks won and archived projects down by count, percentage and the reasons given, and win rate by count or by value is also one of the effectiveness goals on the Performance View. Forecasting is native on the Performance View, which shows a weighted pipeline forecast built from project value and probability of closing, and the analytics gallery includes a weighted pipeline by stage over time graph. Stage-to-stage conversion is the gap. The Win/Loss Analysis carries a view named Conversion, but vendor documentation describes it as breaking down the win rate for projects as they reach specific stages, which is a win rate conditioned on the stage reached rather than the proportion of projects advancing from one stage to the next. The pipeline views, the time-in-stage and stalling measures and the dashboard value fields of count, value, days since last activity and time in stage are distributions and durations, not transition rates.

Source: https://www.membrain.com/help-center/sales-analysis/win/loss-analysis, https://www.membrain.com/help-center/sales-analysis/performance-view, https://www.membrain.com/help-center/sales-analysis/active-pipeline-analytics, https://www.membrain.com/help-center/sales-analysis/building-graphs-in-the-dashboard, https://www.membrain.com/help-center/active-pipeline/active-pipeline-an-overview

Verification: Verified