Agency Sales Pipeline: From Lead to Proposal, Step by Step

Paul Boards · 2026-10-22

An agency's sales pipeline is the sequence of stages a prospective client moves through from first contact to an accepted proposal. A format that works for most agencies has six stages: New lead, First contact, Discovery, Proposal in progress, Proposal sent, and Won or Lost.

The pipeline only helps when each stage has a clear entry criterion and a defined next action. If nobody can say what needs to happen for a lead to move from "First contact" to "Discovery," the stages become nice-sounding names on a board nobody updates. Below is a step-by-step look at each stage, with what to record and where agencies lose the most deals.

Why agencies need a pipeline, even when they sell through referrals

Many small agencies sell almost entirely through referrals and think a pipeline is for companies with a sales team. The problem shows up when four contacts arrive in the same week: one asked for a proposal on a partner's WhatsApp, another filled out the website form, a third was introduced at an event. Two weeks later, nobody remembers who was supposed to call whom.

The pipeline fixes that forgetfulness. It shows, in one place, how many opportunities are open, where each one stands, and what the next step is. It also helps you spot patterns, like proposals that always stall at the same point.

The six pipeline stages, step by step

1. New lead

Entry criterion: any contact with stated interest. Website form, message, referral, conversation at an event.

What to record: name, company, lead source, how they found you, and the request in one sentence. Lead source is the most ignored field and the most useful. After six months, it tells you whether that channel is worth continued investment.

Next action: reply the same business day. A lead who waits three days for a reply has usually talked to another agency.

2. First contact

Entry criterion: there was a real conversation, by phone, video, or messages with an actual exchange of information.

What to record: what the company does, what problem it wants to solve, and whether there's a budget and timeline. It doesn't have to be a questionnaire. A note like "bakery chain with 4 locations, opening a fifth and nobody in the new neighborhood knows the brand, opening deadline in March" already guides everything else.

Next action: schedule discovery or disqualify the lead with a reason.

3. Discovery

Entry criterion: a meeting has been scheduled or held to understand the business in depth.

This is the stage that determines the quality of the proposal. Ask what has already been tried, what worked, who makes the decision, who approves assets day to day, and how the client will measure whether the agency succeeded. That last question prevents half of all contract problems, because it aligns expectations before there's a price.

Next action: set the proposal delivery date and let the client know.

Pipeline, forms, and lead conversations in one place. The Scrumboards CRM has a stage-based pipeline and forms that create leads automatically, connected to your team's tasks. Build your agency's pipeline for free.

4. Proposal in progress

Entry criterion: discovery is done and there's enough information to price the work.

Turn the proposal into a task with an owner and a deadline, like any other deliverable. That way it enters the team's queue instead of waiting for "when there's time." If the proposal depends on other people, like the art director estimating the volume of assets, each part becomes a subtask.

Next action: send it by the promised date.

5. Proposal sent

Entry criterion: the client has received the proposal.

This is where many agencies lose deals to silence. Agree during the presentation itself on when you'll hear back, and record that date on the lead. If the date passes, the team gets a reminder to follow up. Presenting the proposal in a meeting, not just by email, also helps clear up questions before they turn into objections.

Next action: follow up on the agreed date with a direct question, like "Did you get a chance to review the proposal with finance?"

6. Won or Lost

Won: record the close date and the amount, and move on to onboarding. Ideally, a won client automatically generates the project and the team's first tasks, so nothing promised in the sale gets lost.

Lost: record the reason. Price, timing, chose another agency, dropped the project. After a few months, this list shows whether the problem is pricing, the proposal, or lead qualification.

How to measure the pipeline without overcomplicating it

Three numbers are enough to start:

• Leads by source per month. Shows where opportunities come from.
• Stage-to-stage conversion rate. For example, out of every 10 discovery calls, how many become proposals. If the biggest drop is at one specific stage, that's where to make changes.
• Average time to proposal. Measured from first contact to sending.

To calculate the conversion rate, always use the same period and count each lead by the date it entered the stage. A common pitfall: when the report filters won deals by the lead's creation date, a deal closed in October that came in back in July shows up in the wrong month. Filter won deals by close date instead.

Example: the pipeline at an agency with three partners

Picture an agency with three partners who share sales. Before the pipeline, each one kept contacts on their own phone. With the pipeline in the CRM, the website form creates the lead in "New lead" with the source filled in, the partner who takes it moves it to "First contact" and writes a summary, and the proposal becomes a task on the team board. At the Monday meeting, the three review the pipeline together for 15 minutes and decide who handles each follow-up that week. The win is that everyone sees the same board, with no sophisticated process required.

Where technology helps and where it doesn't

A CRM connected to the rest of your operation saves repetitive work: the lead comes from the form, the email conversation is logged, the proposal becomes a task, and when the client signs, their project opens right there, next to the sales history. In Scrumboards, LEX, BrainPilot's sales intelligence agent, can help organize information about the lead, and STELLAR supports client service. Each team member sees the leads and clients they're assigned to, according to their role's permissions.

Technology doesn't replace a well-run discovery or a follow-up on the agreed date. A full pipeline with generic proposals still loses deals. If you want to see how CRM, tasks, and finance work together on one platform, check out Scrumboards' CRM and project management and the plan options.

Frequently asked questions

How many stages should an agency sales pipeline have?

Between five and seven. What matters is that each stage has a defined entry criterion and next action.

What's the difference between a lead and an opportunity?

A lead is any contact with interest. An opportunity is a lead that has gone through first contact and has a real chance of becoming a proposal.

How long should I wait before following up on a proposal?

Whatever timeframe you agreed on with the client during the presentation. If nothing was agreed, three to five business days is a common benchmark.

Is it worth recording lost leads?

Yes, with the reason. It's the only way to find out whether the agency loses on price, timing, or qualification.

Do I need a CRM separate from my project management tool?

Not necessarily. Having the pipeline and projects on the same platform saves you from re-entering data when the client signs.

Start organizing your proposals

A simple pipeline, updated every week, already shows where the agency loses deals and which channels bring in the best clients. Create your free account and add this week's leads, or see how the CRM works with pipeline and forms.