How to set up a Gmail sales pipeline from scratch

A Email sales pipeline works when it answers one question fast: what needs to happen next for each live opportunity? Most founder inboxes fail because conversations are active but stages are unclear. This guide shows how to build a Email pipeline setup from scratch using labels, filters, and a lightweight review ritual. You will get a pipeline that is simple enough to run daily and structured enough to improve close rates.

Step 1: Define stage logic before touching Email

Start with six stages:

• New
• Active
• Waiting
• Committed
• Closed Won
• Closed Lost

Make every stage mutually exclusive. If stage definitions overlap, your pipeline becomes opinion-based and hard to manage.

Before you open Email settings, write the definition of each stage in plain language. A stage definition should answer: "What is true about this deal that makes it belong here, and what needs to happen for it to move forward?"

A working set of definitions might look like this:

New: A lead has arrived and you have not yet sent a first response. This includes both inbound inquiries and outbound contacts that have not yet replied. Time in this stage should be measured in hours, not days.

Active: You are in an ongoing back-and-forth with the prospect. Either you sent the last message and it was acknowledged, or you received their last message and are formulating your reply. Progress is expected within one to two business days.

Waiting: You sent the last substantive message and are waiting for their reply. No action required from you today, but a follow-up trigger is scheduled. Maximum wait before follow-up: five business days.

Committed: The prospect has verbally or in writing indicated they want to move forward. Contract review, onboarding discussion, or payment processing is underway.

Closed Won: Deal is signed or payment received. Thread moves to an archive after a brief transition note.

Closed Lost: No path forward exists or prospect has declined. Closing the loop requires capturing one-line context on the reason.

Having these definitions written before you create labels is the single most important step in building a durable Email pipeline. Teams that skip this step end up with stage labels that each person interprets differently, making weekly reviews useless.

Step 2: Map stages to labels and views

Create labels using a consistent prefix like stage/. Build inbox sections or saved views so active pipeline threads stay visible.

Archive completed or dormant threads to keep your working view clean. A pipeline view should show current commitments, not email history.

In Email, go to Settings → Labels → Create new label. Create each label with the stage/ prefix: stage/new, stage/active, stage/waiting, stage/committed, stage/closed-won, stage/closed-lost. This prefix groups them together in your sidebar.

Assign a distinct color to each label. The most useful color convention: use warm colors (orange, red) for stages requiring immediate action, neutral colors (blue, grey) for passive states, and green for positive outcomes. This lets you scan your sidebar and immediately see where attention is needed.

In Email's inbox configuration (accessible via the gear icon on your main inbox view), create sections that filter by label. Set your primary section to show stage/new and stage/active threads first. This turns your inbox into a prioritized pipeline view without any additional tooling.

Step 3: Route leads automatically into stage/new

Use filters for inbound forms, referrals, and demo requests. Auto-apply stage/new and a source label where possible.

This reduces manual triage and ensures new opportunities land in a predictable entry stage.

Routing automation is what separates an email pipeline from an email inbox. Without filters, every new message lands in the same undifferentiated stream and you have to manually assess and label each one. With filters, high-signal messages arrive pre-labeled and pre-prioritized.

Start with your most important lead source. For most founders, this is the contact or demo request form on their website. Find the email address that delivers form notifications to you, and create a filter:

• From: [your-form-notification-address]
• Apply label: stage/new and source/inbound
• Never send to spam

Repeat for warm introductions (filter by subject line keywords "intro" or "introduction"), outbound reply threads (filter by the email addresses or domains you are actively prospecting), and any partner referral sources with identifiable email patterns.

Add a separate filter to suppress common noise sources: newsletters, billing notifications, and automated software alerts. Set these to skip your inbox entirely and route to a separate label.

Step 4: Add follow-up rules per stage

Define timing norms:

• New: first touch within one hour when intent is high
• Active: same-day movement required
• Waiting: scheduled check-ins with dated reminders

Every thread in stage/active should have a next action and date.

Follow-up timing is where most Email pipelines fail. Leads arrive, get labeled, and then sit in stage/new for days because no timing expectation exists. The stage label becomes decoration rather than a commitment.

Convert your timing norms into specific behaviors. For stage/new, create a habit: every morning and afternoon, open your stage/new label and reply to every thread that arrived since your last check. Batch this into a fifteen-minute session rather than monitoring constantly.

For stage/active, use Email's snooze feature to create a next-action trigger. After sending a message to an active prospect, snooze the thread to the next morning. When it resurfaces, you are prompted to check for a reply and take the next step. This creates a lightweight, reliable follow-up loop with zero additional tooling.

For stage/waiting, set a calendar reminder for the follow-up deadline — typically five business days after your last message. When the reminder fires, send a brief check-in and move the thread back to stage/active.

Step 5: Review and progress weekly

Weekly review checklist:

1. Move stale active threads to waiting or close — any thread with no movement in five business days should be reassigned
2. Confirm each committed deal has a dated next step — "committed" without a next action is a deal at risk
3. Capture one reason for every closed-lost outcome — this data compounds into win/loss insight over months

This gives you lightweight reporting without heavy CRM administration.

The weekly review is your pipeline maintenance session. It should take fifteen to twenty-five minutes when done consistently. If it takes longer, your pipeline has accumulated too many zombie threads that need a close-lost decision.

Run the review at the same time every week. Friday afternoon works well because you can close out the week with a clean pipeline view. Monday morning also works if you prefer to start the week knowing exactly where each deal stands.

During the review, work from the bottom of your pipeline upward: start with stage/waiting, then stage/active, then stage/new. This prioritization ensures you handle the most time-sensitive decisions first.

Building a basic pipeline report from labels

You do not need a CRM to generate a basic pipeline report from your Email labels. Once per week during your review, count the threads in each stage:

• stage/new: [number] threads
• stage/active: [number] threads
• stage/waiting: [number] threads
• stage/committed: [number] threads

Track this count in a simple spreadsheet over time. Even without deal values or probability scores, tracking thread counts per stage week-over-week reveals pipeline trends: is your new-lead volume growing? Are threads converting from new to active within your target timeframe? Are deals stalling at a particular stage?

This lightweight reporting gives you enough signal to improve your process without investing in a full CRM reporting stack. For guidance on how to label and categorize the leads in each stage, read how to label and track leads in Email for a detailed breakdown of the labeling conventions that support this pipeline model.

Common setup errors

• Building too many stages too early — six stages are the maximum most solo or small-team pipelines can maintain
• Treating labels as optional — a label system only works when applied consistently to every active thread
• No scheduled review cadence — without a calendar event, the review gets displaced during busy weeks
• No clear exit criteria for stalled threads — without definitions of when a deal is "lost," zombie deals accumulate indefinitely

Consistency beats complexity every time.

The most common error is building stages for the pipeline you aspire to have rather than the one you actually have today. If your deals typically convert in two weeks with three to four email exchanges, a six-stage pipeline with a "nurture" stage is probably too complex. Match pipeline depth to deal complexity.

Conclusion

An email sales pipeline from scratch is straightforward when stages are clear, routing is automated, and weekly reviews enforce movement. Keep the system tight and practical so you can run it under real startup pressure. For the complete Email CRM framework and connected guides, read The Complete Email CRM Guide for Founders. If you want unified visibility across multiple inboxes, get started with Kaname.