Guide
How to prevent deals from stalling in a software agency pipeline
Deals in software agency pipelines rarely end with a clean no. They slow down and go quiet. Here is how to spot the warning signs early and build habits that keep deals moving before they become lost.
Why software agency deals stall more than most
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.
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.
Understanding why deals stall, and building a few habits to catch the signs early, is one of the cheapest ways to improve close rates without generating more leads.
Warning signs a deal is losing momentum
The signals are rarely sudden. They accumulate over weeks. These four are the most reliable early indicators.
Response time stretches
A prospect who used to respond same-day now takes three days. Then five. Then a week. People who want something respond faster. This pattern is almost always meaningful.
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 worth noting in the deal record.
Scope questions stop
Early-stage deals involve a lot of questions about timeline, scope, and team. When those questions stop and no decision follows, the evaluation has often moved on without being announced.
The next step gets vague
If the agreed next step was 'I'll loop in our CTO' and two weeks later there's still no CTO on an email, the commitment didn't hold. A vague next step is where stalls begin.
A new person appearing on a call or email thread is also worth noting. A contact who was not mentioned before usually means something changed internally, and the deal may need to be re-sold to someone new.
Where deals stall and what to do
Different stall points require different responses. Most agencies see the same four stages cause problems repeatedly.
Discovery
The deal has not moved from an initial conversation to a scoping or proposal stage.
The move: Be direct: ask what it would take to move to the next step. Not 'let me know when you're 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.
The move: Surface the blocker directly. 'I know you've had the proposal for two weeks — what's holding up the decision on your end?' is more useful than a polite check-in.
After a follow-up call
The deal went quiet after what seemed like a productive conversation.
The move: Request a brief call to understand where things stand, not to sell. '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 require legal review. This can legitimately take weeks at large organizations.
The move: Set a specific date to follow up with your main contact about progress. 'Can you let me know by Thursday where things are in their review?' keeps momentum without creating friction.
Anti-stall habits that actually work
- Always leave with a named next step, a specific person, and a specific date
- Set a stale threshold (7–10 days) and flag it in your weekly pipeline review
- Have a close-the-loop conversation after six weeks of no response
- Record next actions in the deal record so they are visible to the whole team
The stale threshold matters less than having one written down. Without it, the decision of whether to follow up is made by feel, and feel loses to a full schedule every time.
Why pipeline hygiene is a team habit, not a rep task
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: 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, everyone understood why it was worth the 15 minutes."
How Lumenbase handles deal momentum
- The Feed Surfaces quiet_deal signals when deals have gone without activity for longer than is typical for their stage. Instead of scanning the pipeline manually, deals that are slipping show up automatically for review.
- Stage velocity Compares how long each deal has been in its current stage against the team average for that stage. A deal in 'Proposal' for twice the usual time shows up as worth checking on before the prospect makes a quiet decision.
- Next action fields Record the specific next step, who owns it, and when it should happen directly on the deal. Filter your pipeline view by next action due date so you are looking at what needs to move, not just what stage things are in.
- Lumo Drafts a follow-up email based on the deal context: last communication, open questions, the prospect's stated timeline. Instead of writing the same 'just checking in' message from scratch, you review and adjust something already specific to the account.
Who this is for
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.
Typically $2M to $30M in revenue, with one to four people managing active pipeline at any given time. At that scale, deals going quiet without anyone noticing is a real and frequent problem.