CRM MVP
The opportunity moves through an ordered sequence of stages, from first conversation to closed. The sequence is defined in advance and the record carries its current position in it.
Stages are what make a pipeline forecastable rather than decorative. An ordered sequence tells you where an opportunity is, how long it has been there, and what has to happen next.
A status flag with no order cannot answer any of those questions. You can tell it apart from a real pipeline by asking whether the platform knows that one value comes before another.
The opportunity must move through defined, ordered stages. Implementation does not matter: a dedicated pipeline construct and a properly ordered select field both qualify, provided the order is stored and the record moves across it.
Fails if opportunities carry only a status flag with no ordered stage sequence.
An opportunity is advanced through the ordered stages of a sales process. Administrators define a process and add its stages, each with its own probability, and the process is then applied to an opportunity. The API model confirms the structure: an opportunity carries a stage, and the stage in turn belongs to a named process.
A pipeline is a defined set of stages, displayed as ordered columns that a deal moves through from left to right. Pipelines are unlimited and each carries its own stage set. Moving a deal to a different stage does not change its status, which stays open until it is explicitly closed.
An opportunity carries a Sales Stage field selected from a configured list, and stages are created and named by the administrator with a description and a chart colour. Stage order is set by dragging stages into sequence within a sales cycle, which the vendor defines as a step by step process made up of a set of pipeline stages. Stages can carry entry criteria that decide whether an opportunity may enter a stage and exit criteria that must be satisfied before it can move on, or no criteria for free movement. A kanban view presents opportunities as cards grouped by sales stage.
The deal record itself carries stage, a required attribute of Attio's Status type - not a generic select on a list. Status is a distinct attribute type reserved for pipeline behaviour: the deal object ships with the only predefined status attribute in the product, defaulting to Lead, In Progress, Won and Lost. Stages form an ordered sequence that can be reordered, hidden or extended in view settings, records are dragged between them on a kanban board, and the ordering is load-bearing for reporting - funnel reports compute conversion using records that reached or surpassed the current stage against the previous stage. Status values also carry active from, target time in status and celebration properties, which a plain select attribute does not.
https://docs.attio.com/docs/standard-objects/standard-objects-deals.md
https://docs.attio.com/rest-api/attribute-types/attribute-types-status.md
https://attio.com/help/reference/managing-your-data/views/create-and-manage-kanban-views
https://attio.com/help/reference/managing-your-data/dashboard-and-reports/set-up-a-funnel-report
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.
A pipeline is a set of ordered statuses that records move through. Stages are added from the pipeline view, renamed, given a colour and reordered by dragging the columns. The public API models a stage as a Status object carrying a name, an explicit numeric order, a colour, a stage type and the identifier of the list the stage belongs to, and a deal's stage can also be changed in bulk from the deal list.
Stages are called Milestones. Each opportunity sits on one milestone, milestones are configured by an administrator, and each carries a probability of winning. The pipeline is presented as a kanban board whose columns are the milestones ordered by that probability, and an opportunity is advanced by dragging it from one milestone column to the next.
A pipeline is a named and ordered group of Opportunity Statuses, and an opportunity moves through those statuses. Each status must have a name that is unique within its pipeline and a status type, and statuses can be dragged to reorder them, so the sequence is defined by the administrator rather than fixed.
An opportunity sits in a pipeline and moves through that pipeline's ordered stages, carrying `pipeline_id` and `pipeline_stage_id`. Stages are defined by the account, can be renamed, reordered and deleted, and each stage carries its own win probability.
Stage is not a native field on the deal object, but the stage construct folk ships is an ordered sequence rather than a bare label set. On creation folk applies a deal template of pre-made custom fields including a Status single-select, and the options of a select field are a stored, user-reorderable list which the vendor states is applied whenever records are sorted by that field, so the order lives on the field rather than only on a view. A pipeline view renders those options as left-to-right columns that deals are dragged across, with the value written back to the deal record, and the value is settable and filterable through the API's custom field values on create and update. There is no stage gating and no documented stage-entry timestamp.
https://help.folk.app/en/articles/9552366-track-deals
https://help.folk.app/en/articles/4991006-contact-fields
https://help.folk.app/en/articles/6044821-create-custom-pipeline-views
https://developer.folk.app/api-reference/deals/create-a-deal
https://developer.folk.app/api-reference/group-custom-fields/create-a-group-custom-field
Deals move through an ordered set of stages that an admin defines, renames and reorders by drag handle, with a probability percentage settable per stage. A pipeline must carry a minimum of three stages, and Won and Lost are present as default stages in every pipeline.
Deals move through an ordered set of deal stages within a pipeline. Stages can be added, renamed and dragged into a new sequence position, and each stage carries a probability used for weighted amounts.
Opportunities are placed on a Pipeline made of ordered stages that an administrator defines, with the record showing completed, current and upcoming stages. Only one pipeline applies to a given record, and stages are worked through in sequence.
A deal is created into a chosen pipeline and moves through that pipeline's stages, and moving a deal to the next stage is a documented action on the deal record and on the pipeline board. Pipelines are created from a template or from scratch, and stage names and the number of stages are set by the buyer.
Opportunities are driven by a business process flow that presents ordered stages as chevrons across the top of the record; the shipped sales process runs Qualify, Develop, Propose and Close. The stage set is administrator-defined, with up to 30 stages in a process and up to 30 steps in a stage, and a process can be sent back to a previous stage.
The Deals board carries a Stage column of Status type that records where the deal sits in the sales cycle, and the stage labels are ordered - the Deal Stages widget lets a board owner drag and drop the labels into the intended sequence and then reports time spent at each stage and lets a closed or abandoned deal be reopened from its last active stage. Stage ordering is treated as a real sequence by the CRM reporting layer, which calculates transitions between stage labels. Stage progression is not enforced - any label can be selected at any time unless a board owner adds conditional status rules.
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.
Leads run through an ordered set of administrator-defined stages within a pipeline. Stages are created from scratch, from templates or from an existing pipeline, can be renamed, given guidance text, a confidence level and an overdue timeframe, and their order is changed by dragging the stage header. The lead board shows one column per stage with lead count and total value.
A deal progresses through the ordered stages of a pipeline until it is marked won or lost, and the deal record carries `pipeline_id` and `stage_id` fields. Stages are configurable per pipeline.
Opportunity Pipelines are described by the vendor as funnels or journeys made up of ordered statuses, where the status at the top of the configured list is the first to appear in the pipeline. An opportunity advances by changing its Status from a drop-down, users can move back to a previous status, and a Kanban board renders opportunities in columns representing the pipeline statuses with drag and drop between them. More than one pipeline can be defined, each with its own status set.
The Opportunity carries a required Stage field driven by a picklist of ordered stage values. Each stage value is assigned a stage type of Open, Closed Won or Closed Lost, plus a probability and a forecast category, and admins add or edit stage values in Setup. A Path component can be configured to guide reps through the stage sequence on the record.
A pipeline is an ordered set of stages and a box moves through those stages until the workflow is complete. Stages are configured from the pipeline's stages and columns settings, where they can be added, renamed, deleted, recoloured and dragged into a new order. Stage is one of the foundational columns present in every pipeline.
A deal carries a Sales Stage that is changed either by selecting a new stage from a drop-down on the record or by dragging the deal between columns in the Kanban view, which opens by default on the Deals list. The vendor documents the stage sequence used by forecast categories as New, Qualifying, Requirements Gathering, Value Proposition, Negotiation, Ready to Close and Closed Won, so the stages form an ordered progression rather than a flat status flag, and deals are described as progressing through stages in a pipeline.
https://help.vtiger.com/faq/149294203-How-can-I-change-a-deal&
https://help.vtiger.com/faq/164350453-How-do-I-change-the-Sales-Stage-in-a-Deal
https://help.vtiger.com/faq/154126989-What-are-the-Forecast-categories
https://help.vtiger.com/faq/163922342-Can-we-delete-certain-deals-in-the-stage-that-are-no-longer-in
A deal moves through an ordered set of sales stages held in the Stage picklist, and an administrator configures those stages through stage-probability mapping, which ties each stage to a probability value, a deal category and a forecast category. Separate pipelines can each carry their own stage set.