How to Prevent Deals from Stalling in a Software Agency Pipeline

Product sales tends to have shorter cycles and faster nos. If a SaaS prospect is not interested, they stop responding quickly. The economics of custom software development work differently.

Custom work requires scope alignment. That takes multiple calls. It usually involves people in different roles: a technical evaluator, a budget owner, a delivery manager, sometimes a board member for larger contracts. Each of those people can pause the process without meaning to. A big project kicks off for the prospect. A restructure moves the budget holder to a new team. The technical lead takes three weeks off.

Long sales cycles also mean more opportunity for external circumstances to intervene. A deal that made sense in March might hit a freeze in May when the prospect's Q2 numbers came in wrong. That is not a no. It is a pause. But if no one is actively managing it, it quietly becomes a no.

The signals are rarely sudden. They accumulate over weeks.

Response time stretches. A prospect who used to respond same-day now takes three. Then five. Then a week. This is almost always meaningful. People who want something respond faster.

Meeting requests get deflected. When a next call gets pushed back twice, something has changed. It might be external or internal. Either way, a pattern of deflection is a signal.

Scope questions stop. Early-stage deals involve a lot of questions: how long, what is included, who would work on it. When those questions stop and no decision follows, the evaluation has often moved on without being announced.

A new person appears. A contact who was not mentioned before shows up on a call or is cc'd on an email. This usually means something changed internally. The deal may need to be re-sold to someone new.

The next step gets vague. If the agreed next step from your last call was "I'll loop in our CTO" and two weeks later there is still no CTO on an email, the commitment did not hold.

Different stall points require different responses.

Discovery. The deal has not moved from an initial conversation to a scoping or proposal stage. Usually this means the prospect does not have internal alignment yet, or they are gathering multiple options before committing to a process. The move here is to be direct: ask what it would take to move to the next step. Not "let me know when you are ready" but "what needs to happen internally before we can get to a proposal call?"

After the proposal. The most common stall point. The prospect has what they need but has not made a decision. Either there are objections they have not voiced, the budget approval is uncertain, or a competing option is still being evaluated. The move here is to surface the blocker directly. "I know you have had the proposal for two weeks - what is holding up the decision on your end?" is more useful than a polite check-in that gives them permission to say "still thinking about it."

After a follow-up call. The deal went quiet after what seemed like a productive conversation. This usually means you and the prospect were not aligned on where the deal was. Request a brief call explicitly to understand where things stand: not to sell, but to understand. "We have had good conversations but I want to make sure I understand your timeline before I keep investing time on my end" is honest and usually gets a real answer.

Stuck at legal or procurement. Custom software contracts often require legal review. This stage can legitimately take weeks at large organizations. The risk is losing visibility. Set a specific date to follow up with your main contact about progress, not the legal team directly. "Can you let me know by Thursday where things are in their review?" keeps momentum without creating friction.

A few process changes make a meaningful difference without creating overhead.

Always leave with a named next step. Every call or email should end with a specific action owned by a specific person on a specific date. "I will follow up" is not a next step. "I will send the revised scope by Tuesday and Sarah will confirm budget with her manager by Thursday" is a next step. If you cannot leave a conversation with a mutual commitment, that is worth noting in the deal record.

Set a stale threshold and check it weekly. Decide how many days in any stage before a deal gets flagged for review. For most software agencies, seven to ten days without meaningful activity is worth a rep-level check-in. Fourteen days is a conversation for the team. This does not have to be automated - a weekly pipeline review with those numbers visible is enough to catch drift before it becomes a problem.

Have a dead-deal conversation. If a deal has been quiet for six weeks with no response to two attempts, it is worth a final reach-out that acknowledges the situation. "We have not been able to connect for a while, and I want to close the loop - are you still evaluating this option or would it be better to circle back in Q3?" This message has a higher response rate than another polite check-in, and the answer tells you where to allocate your time.

Oksana ran business development for a nearshore software firm in Kyiv before moving into product work. One pattern she saw repeatedly was that deals would sit in proposal for weeks because each rep assumed the deal was still progressing in the other person's head. Nobody had an explicit conversation about what was actually moving.

The firm eventually started doing a 15-minute pipeline review each Monday where any deal in the same stage for more than two weeks got a mandatory explanation from the rep: what is the next step, who owns it, when does it happen. Not a performance review. Just a forcing function to say it out loud.

"It felt unnecessary at first," she says. "But the first time a rep said out loud that they had been waiting on a prospect for three weeks and had not sent the follow-up they promised, that was when everyone understood why it was worth the 15 minutes."

The Feed surfaces `quiet_deal` signals when deals have gone without activity for longer than is typical for their stage. Instead of scanning a pipeline manually, deals that are slipping surface automatically for review.

Stage velocity tracking compares how long each deal has been in its current stage against the average for that stage across the team. A deal in "Proposal" for twice the usual time shows up as worth checking on.

Next action fields on each deal let you record the specific next step, who owns it, and when it should happen. These can be filtered so a pipeline view reflects not just deal stages but what is actually supposed to happen next, and whether it has.

Lumo can draft a follow-up email based on the deal context: last communication, open questions, the prospect's timeline. Instead of writing the same "just checking in" message from scratch, it produces something specific to the account for you to review and adjust before it goes out.

Software agencies, IT services firms, and consulting practices with deal cycles longer than 30 days. If most of your deals close in a week, the dynamics are different. But if the average from first meeting to signed contract runs two to four months, stall management is one of the highest-leverage things your sales process can do.