Loading tutorials…
Loading tutorials…
Lists and Pipelines are how Attio teams turn the data model into an actual sales motion. Lists hold the cohorts (ABM target, sequence enrollees, onboarding cohort); Pipelines move records through stages. Build them well and forecasting is real. Build them poorly and you live in spreadsheet exports forever.
Who this is forSales leaders, RevOps owners, and founders running their own sales who need pipeline reports they can trust. If your last forecast missed by 30%+ and you blame 'rep hygiene,' the issue is probably stage design.
What you'll need
Step 1
Lists are cohorts (ABM target, sequence enrollees, onboarding batch). Pipelines are stage-driven progressions (sales pipeline, onboarding pipeline). They work together.
List: a persistent cohort of records, dynamic (rule-based) or static (manually curated). Examples: "Q2 ABM target list," "Sales sequence — VP Marketing cold," "Onboarding cohort — May 2026."
Pipeline: a Status-driven view of records moving through stages. Built on Deals natively, can also be built on Companies, People, or any custom object via a Status attribute.
Lists can have their own attributes — e.g. an "ABM target list" can have a "Touchpoints" number attribute that only exists when a record is on that list.
Use Lists for "who is in this cohort" questions. Use Pipelines for "where in the process" questions. Often a record is on multiple lists AND moving through one pipeline.
Step 2
Each stage should represent a clear, observable buyer signal — not an internal rep activity. "Demo completed" is a buyer signal. "Working" is not.
Workspace settings → Objects → Deals → Attributes → Status attribute → Edit options.
Default Attio stages are minimal — most teams customize. Common B2B SaaS pattern: Discovery booked → Discovery completed → Demo completed → Proposal sent → Contract sent → Closed Won / Closed Lost. 5-7 stages plus the two terminal stages.
Each stage needs a clear "what just happened" definition. Write it down in a stage-definition doc that lives outside Attio (Notion, wiki).
Avoid stages that describe internal activity ("Working," "In progress") — they hide stuck deals. Use buyer-signal stages so a stuck deal is visible.
For complex motions (multi-product, multi-region), prefer multiple pipelines (multiple Status attributes) over one mega-pipeline with 12 stages.
Step 3
Attio does not have a built-in probability field; add a custom "Stage probability" Number attribute or hardcode in your Reports.
Add a custom Number attribute on Deal called "Stage probability" (or use a Workflow to auto-set based on Status).
Pull your historical data: of deals that hit Demo completed, what % closed won? Of deals that hit Proposal sent, what %? Use 6-12 months of data for stability.
Typical B2B SaaS rates: Discovery booked 5-10%, Demo completed 15-25%, Proposal sent 35-50%, Contract sent 70-85%. Calibrate to your reality.
In Reports, build a "Weighted pipeline" calculation: sum of (Deal value × Stage probability). Pin to the leadership dashboard.
Recalibrate quarterly based on actual close rates. Stage probabilities are not "set once" — they reflect reality, and reality drifts.
Step 4
New business, expansion, renewal, channel — each often deserves its own pipeline (its own Status attribute or its own Deal object).
For 2-3 distinct motions: add multiple Status attributes on Deal (e.g. "New business stage," "Expansion stage," "Renewal stage"). One Deal has one active Status attribute populated.
For 4+ distinct motions or complex multi-product motions: consider separate Deal sub-types via a custom "Deal type" Select attribute, with stage progressions documented per type.
A renewal deal does not need a Discovery stage; an expansion deal does not need an SDR-handoff stage. Forcing them through the same stages corrupts both forecasts.
Restrict pipeline access by team: Workspace settings → Permissions. CS team owns Renewal pipeline; AE team owns New business; etc.
Resist building too many pipelines. 3-4 distinct motions is healthy; past 5, maintenance cost (reports, workflows, training) outweighs clarity benefit.
Step 5
Sales sequences in Attio live as Lists with list-specific attributes (sequence started, step number, last sent). Workflows drive the cadence.
Sidebar → Lists → New list → pick People → name it ("Sales sequence — VP Marketing cold — Q2").
Add list-specific attributes: "Sequence step" (Number), "Last sent" (Date), "Replied?" (Checkbox), "Removed reason" (Select).
Build a Workflow: "When Person added to list → Send Email step 1, set Sequence step = 1, set Last sent = today."
Build follow-up workflows: "Scheduled daily → For each Person on list where Sequence step = 1 AND Last sent > 3 days ago → Send Email step 2, increment step."
Build exit workflows: "Person attribute updated → If Replied = true → Remove from list, set Removed reason = Replied."
See the deeper sequences-style playbook in the sister hubspot-crm tutorials — the pattern translates.
Step 6
Reports → Sales pipeline. Pin to the leadership dashboard. Review every Monday.
Sidebar → Reports → Add report → 'Pipeline by stage.' Group by Status, sum Deal value.
Include: total pipeline value, weighted pipeline (Deal value × Stage probability), deals by stage, stage-to-stage conversion rates, average deal age per stage.
Pin the report to a shared dashboard. Each AE reviews their pipeline weekly; sales leadership reviews team-wide pipeline weekly.
Walk every deal over a threshold ($X amount) in the weekly review: is this in the right stage? Has it moved in the last 30 days? Is the close date realistic?
Stage-to-stage conversion rates are the most valuable metric most teams ignore. If Demo → Proposal is 30% but Proposal → Closed Won is 85%, the leakage is at qualification, not closing.
Step 7
Any deal that has not moved stages in 60 days is suspect. Pull this view monthly, force a disposition (move it or close it lost).
Build a view on Deals: filter "Last activity < 60 days ago AND Status ≠ Closed Won AND Status ≠ Closed Lost AND Expected close date > today."
Sort by Last activity ascending. The oldest stuck deals are at the top.
For each, ask the owner: is this real? If yes, what is the next step and when does it happen? If no, mark Closed Lost with reason 'Stalled — no buyer urgency.'
Most stuck deals are wishful thinking. Closing them properly improves forecast accuracy by 20-40% within a quarter.
Make this a recurring calendar event. Pipeline audit cadence is what separates teams with accurate forecasts from teams with theater forecasts.
Common mistakes
Using internal activity stages ("Working," "Negotiating") instead of buyer signals
What goes wrong: Reps mark deals 'Negotiating' indefinitely. Stuck deals hide in the pipeline. Forecast keeps saying $400K is coming and the head of sales keeps missing the number. Eventually trust in the pipeline collapses.
How to avoid: Rewrite every stage as a buyer signal: "Discovery booked," "Demo completed," "Proposal sent" — each requires an observable buyer action. Internal activity = a Task or attribute, not a stage.
No stage probability — weighted forecast is unweighted
What goes wrong: You report total open pipeline as 'the forecast.' Of $1.2M in open pipeline, only $180K actually closes. Board reviews keep predicting more revenue than arrives. Credibility erodes quarter by quarter.
How to avoid: Add a Stage probability attribute. Build weighted pipeline in Reports. Calibrate probabilities to historical close rates quarterly.
One mega-pipeline mixing new business + expansion + renewal
What goes wrong: Renewal deals (95% close rate) and new-business deals (10% close rate) sit in the same pipeline. Average close rate becomes meaningless. AE compensation calculations break. Reports cannot answer 'how is our new-business motion doing?'
How to avoid: Separate pipelines per motion: New business, Expansion, Renewal, Channel. Each gets its own Status attribute, probabilities, and ownership. See the multiple-pipelines step above.
Lists with no exit workflow — records get stuck on the list forever
What goes wrong: Sales sequence list has 2,400 People on it, half of whom replied or closed-lost 3 months ago. Workflows keep firing emails to People who already said no. Sender reputation degrades. Open rates drop 30-50%, and on a 1,000-contact/month sequence that translates to $10-30K in pipeline missed.
How to avoid: Always build exit workflows for every List used for outreach. Triggers: Replied = true, status changed to Closed Lost, opt-out clicked, owner manually removed.
Never running the stuck-deal audit
What goes wrong: Deals stuck in Proposal sent for 9 months sit in the pipeline forecast. Sales leaders 'expect' $200K from them. Nobody acknowledges they are dead. Pipeline coverage looks healthy; actual conversion is brutal.
How to avoid: Monthly: filter for deals with no activity in 60+ days. Force disposition — move forward with a concrete next step, or mark Closed Lost with reason. Make it a calendar recurrence.
Recap
Done — what's next
How to set up the Attio data model without making a mess
Read the next tutorial
Hand it off
Pipeline design is the highest-leverage CRM work most owners do — and the easiest to do wrong because it requires judgment about your real sales motion. A specialist who has built 30+ Attio pipelines knows which stages tend to be theater, which probabilities to trust, and how to set up the weekly review cadence. EverestX Attio specialists run $400-1,200/month at $14-16/hr.
See specialist rates
5-7 stages plus Closed Won and Closed Lost (so 7-9 total). Past 9 stages, reps stop reliably distinguishing them and forecast accuracy suffers. If you feel you need more, the answer is usually a second pipeline (Expansion, Renewal) — not more stages in the same pipeline.
Yes — that is a Dynamic list. When creating a list, choose 'Dynamic' and set the rules ('All Companies with ARR > $50K AND Industry = Fintech'). Attio auto-adds and auto-removes records as they match or stop matching. Use Dynamic lists for evergreen segments; Static lists for time-bound campaigns where you want manual control.
Functionally similar — both let you define stages, move records, automate transitions. Attio is more flexible (any object can have a Status-driven pipeline, not just Deals) and faster UI. HubSpot has built-in stage probability + Forecasting Tools out of the box. For most B2B SaaS teams under 50 reps, Attio's flexibility outweighs the missing built-in forecast UI.
Yes — always. Create a 'Closed Lost reason' Select attribute on Deals with values like 'No budget,' 'Lost to competitor,' 'No timeline,' 'No champion,' 'Wrong fit.' Require it via workflow when marking Closed Lost. Quarterly review of lost reasons is where you find the biggest motion-improvement leverage.
Attio Lists are richer — they can have their own attributes, their own workflows, their own permissions. HubSpot Tags (Static Lists) are simpler key/value labels. If you are migrating from HubSpot, expect to convert most Active Lists into Attio Dynamic Lists, and most Tags into either Lists or Multi-select attributes on the underlying record.
Attio
Attio's data model is its superpower and its trap. Anything is customizable; that means anything is also rewritable into a mess. Get the objects, attributes, and relationships right up front and the rest of the workspace (workflows, views, reports) glides. Get them wrong and you rebuild every 90 days.
Attio
Attio Workflows are the operational core of the platform — assign owners, send Slack pings, update stages, sync to other tools. Build them carelessly and they fire 800 times the first weekend and you spend Monday unwinding. Build them with discipline and reps stop doing repetitive busywork. Here is the discipline.
Attio
Attio Reports are powerful but easy to over-build. Twenty dashboards no one opens. Or under-build — a single pipeline view that is somehow the only chart. The right Reports library has 6-10 dashboards covering every recurring decision your team makes. Here is the discipline.
Attio
DIY Attio is a great idea — until it isn't. This is the honest framework for when the cost of self-managing exceeds the cost of hiring help, and how to tell which side you are on.