A pipeline is an ordered set of stages that opportunities move through, from first contact to a closed deal. A sub-account can have several pipelines, for example one for new sales, one for renewals and one for a separate service line. Each stage is a column on the Opportunities board, and every opportunity sits in exactly one stage of one pipeline.
Pipelines are part of a sub-account's build, so they travel with snapshots.
In practice
You create and edit pipelines from the Opportunities area of the sub-account (as of October 2026): name the pipeline, add stages in order, and choose whether stages show in funnel and pie charts. Opportunities then move between stages by drag and drop, by workflow actions, or through the API.
Good pipelines are short and match real decisions, such as New, Contacted, Qualified, Proposal Sent, Won. Too many stages and reps stop moving cards. Workflows tied to stage changes keep things moving: when a card enters "Proposal Sent," send the proposal and create a follow-up task; when it hits "Won," tag the contact and start onboarding.
The board itself is the main working view for many sales teams, which is why small slowdowns there add up. Opening each card's contact record pulls the rep away from the board and back again.
Where it shows up in RGS Tools
Power-Ups' Contact Peek opens a contact in a window over the Opportunities board instead of leaving it. Field Finder's sub-account compare helps check that opportunity fields used by your pipeline workflows exist in every client account.