Deal Stages for Software Development Agencies: A Practical Template

Before defining stages, it is worth understanding how the selling motion is different.

Custom software projects have a scope problem. The client often knows they need something but not exactly what, which means the first few conversations are about discovery more than selling. The agency is learning the problem at the same time as they are being evaluated as a potential partner. That phase takes longer than a SaaS demo and matters more.

This is also why "qualified" means something different in agency sales. In SaaS, qualified usually means the prospect fits the customer profile and has budget. In agency sales, qualified often means the agency understands the scope well enough to make a credible proposal, and the prospect trusts the agency enough to take that proposal seriously. Getting to that point takes genuine investment from both sides.

Then there is the buying committee dimension. Larger engagements typically involve a technical evaluator, a budget owner, a project sponsor, and sometimes a legal or procurement function. Each of these people can slow the process without the deal being dead. A deal in evaluation for six weeks might be moving at procurement, stalled at technical review, or waiting on a board decision. The stage label does not tell you which.

These stages reflect how agency deals actually move. They can be adapted for your specific context, but this structure gives you something concrete to react to rather than a generic placeholder.

Stage 1: Outreach

The prospect is aware of you and contact has been made, but no conversation about a specific engagement has happened yet. This stage is about getting a real meeting, not pitching a product.

Exit criteria: A discovery call scheduled.

Stage 2: Discovery

You are learning the client's problem. They are evaluating whether you actually understand it. No formal proposal has been discussed. This stage is often underestimated. Rushing it is one of the main reasons proposals miss the mark, because you are proposing a solution to a problem you do not fully understand yet.

Exit criteria: Enough scope clarity to write a credible proposal; a clear sense of timeline, budget range, and who is involved in the decision.

Stage 3: Proposal in progress

You are preparing the proposal or statement of work. The prospect is waiting. This stage should be short. A proposal that takes three weeks to produce from a good discovery call is often already over-engineered for the relationship stage you are at.

Exit criteria: Proposal sent.

Stage 4: Evaluation

The prospect has the proposal and is reviewing it, potentially with multiple stakeholders. You may have a clarification call or a negotiation conversation. This is where deals most often stall and where time-in-stage management matters most.

Exit criteria: A verbal decision, a negotiation request, or a clear next step with a confirmed date.

Stage 5: Contract and close

The deal is agreed in principle. You are working through contract review, procurement, or legal sign-off. This stage often takes longer than expected, especially in larger engagements. It is worth tracking separately from evaluation because the obstacle shifts from the buying decision to the administrative process.

Exit criteria: Signed agreement.

Stage 6: Handoff

The transition from sales to delivery. Introductions made, kickoff call scheduled, project structure confirmed. This stage is often left out of pipeline management, which is a mistake. How handoffs are handled directly determines the first impression the delivery team gets to make, and that affects everything downstream including referrals and renewals.

Exit criteria: Project formally started with delivery team.

Stage labels alone are not enough. A deal sitting in Evaluation for 14 days with a confirmed next call is very different from a deal in Evaluation for 14 days with no recent contact. The label is the same. The situation is not.

Next action and date. What is the specific next thing that needs to happen, and when? This is more useful than stage alone because it captures forward motion rather than just current position. A deal with no next action and no expected close date should trigger a review.

Decision-maker clarity. Who is actually making this decision? Who else is involved? Understanding the buying committee structure early reduces the chance of a late-stage surprise where someone you have not met has veto power.

Last meaningful interaction. When did you last have a real conversation with someone at this prospect? Not an email, a conversation. This separates deals that are actively moving from ones that just look like they are.

Estimated close date. Not always accurate, but useful for spotting when a deal has missed its own timeline. A deal with a close date two months in the past that has not moved stages is a problem worth naming.

These vary by project size and industry, but they give you a reference for spotting when something is moving too slowly.

When a deal has been in Evaluation for six weeks with no documented next step and no recent contact, that is worth a direct phone call. Not a check-in email.

• Outreach to Discovery: 1 to 3 weeks
• Discovery: 2 to 4 weeks for a mid-size engagement
• Proposal in progress: 1 to 2 weeks
• Evaluation: 2 to 6 weeks for a mid-size engagement; longer for enterprise
• Contract and close: 1 to 4 weeks

Mariana spent years working with B2B service agencies across Portugal and Brazil on sales operations before moving into product. One thing she observes consistently across Iberian and Latin American markets: the stage of a negotiation is not just an administrative label. It carries relational weight.

"In Portuguese business culture, sending a proposal is not just a step in a process," she says. "It is an implicit signal that you take this relationship seriously enough to invest real time in it. Agencies that rush the proposal because they want to move the stage forward often miss what the client is actually looking for at that moment, which is evidence that the agency is genuinely invested."

She also notes the inverse: a proposal that arrives late, with typos, or that clearly does not reflect what was discussed in discovery, signals something about how the agency will run the engagement. "Clients read the proposal the same way they read the quality of a first meeting. The content matters, but so does the care."

The mechanics of deal stages matter. But the stage of a relationship is not the same thing as the deal stage in your CRM. Both are worth paying attention to.

Too many stages. Eight stages with granular sub-statuses sounds thorough. In practice it means reps do not know where to put a deal and start skipping updates. Five to seven stages is usually the right range for a team without a dedicated sales ops function.

No exit criteria. A stage without a clear definition of what moves a deal forward becomes a holding area. If a deal can stay in Evaluation indefinitely without triggering a review, it will.

Conflating stage with probability. Win probability is a separate input from stage. A deal in Evaluation with a strong relationship and a verbal yes has a completely different probability from a deal in Evaluation with one conversation and a downloaded proposal. Track them separately.

Skipping the handoff stage. Closed won is not the end of the deal. It is the beginning of a different kind of work. Treating it as the pipeline endpoint leaves out the transition that determines whether the client will come back and refer you.

Lumenbase lets you configure deal stages with labels and exit criteria that fit how your agency actually sells rather than forcing a generic template.

Stage velocity tracking shows how long deals have been at each stage. When something looks stuck, it surfaces before it becomes a problem.

The Feed flags deals with no recent activity regardless of their stage label, which catches the specific failure mode where a deal is parked at the right stage but nothing is actually happening.

Next action fields track the concrete next step for each deal. Pipeline reviews stay actionable instead of turning into a conversation about stage label definitions.

Lumo drafts follow-up messages and pre-call briefing notes from the deal's context, including what was discussed in discovery, what the proposal covered, and how long the deal has been at the current stage.

Software development agencies and custom software consultancies who have either outgrown a spreadsheet or found that their current CRM's default pipeline does not match how they actually sell. This framework applies to agencies of 5 to 200 people with deal cycles of one to twelve months. It does not require a dedicated sales ops function to implement, though it helps to have someone who owns the pipeline review cadence.