Objections are not obstacles — they're opportunities. When a prospect raises an objection, they're engaging with your idea and giving you the chance to address their concerns. The partners who master objection handling convert more referrals and build stronger client relationships.
This guide covers the most common objections you'll encounter when referring software projects, along with proven response frameworks for each.
The Mindset Shift: Objections Are Good
Before diving into specific objections, it's important to reframe how you think about them. An objection means the prospect is interested enough to engage — they're not dismissing the idea, they're evaluating it. Silence and disinterest are far more dangerous than vocal objections.
The goal of objection handling isn't to "win" an argument. It's to understand the prospect's concern, address it honestly, and determine whether the fit is right. Sometimes the correct response is to acknowledge that the timing isn't right — and that's valuable information too.
Objection 1: "It's Too Expensive"
The Objection
"We don't have the budget for custom software development."
Response framework: Reframe the conversation from cost to value. "I understand budget is a consideration. Let me ask — what's the current cost of the problem this would solve? If your team spends 20 hours per week on manual work that could be automated, that's over $50,000 per year in labor costs. The software investment pays for itself within the first year. Would it be helpful to have the team put together an ROI analysis so you can see the numbers clearly?"
The key is shifting from "this costs $X" to "this saves/earners $Y." When you frame the investment in terms of business outcomes, the price objection often dissolves.
Objection 2: "We Can Use an Off-the-Shelf Solution"
The Objection
"We can just use [existing SaaS product] instead of building something custom."
Response framework: Validate the option while exploring limitations. "That's a valid option for many businesses. Out of curiosity, does [SaaS product] handle your specific [workflow/integration/requirement]? Many of our clients started with off-the-shelf solutions but found they needed custom capabilities as they grew. Would you be open to a brief comparison to see if custom development might offer advantages in your specific situation?"
Don't dismiss SaaS alternatives — they may genuinely be the right choice. But help the prospect evaluate both options thoroughly.
Objection 3: "We've Been Burned Before"
The Objection
"We had a bad experience with a previous development project."
Response framework: Acknowledge their experience and differentiate. "I'm sorry to hear that — a bad development experience is frustrating. What happened, if you don't mind sharing? [Listen carefully.] Those are exactly the kinds of issues we work to prevent. FussionShade has a 95% client retention rate because we handle projects differently. Would it be helpful to speak with some of our existing clients about their experience?"
Past bad experiences create skepticism but also create an opportunity to differentiate through transparency, references, and proven processes.
Objection 4: "We Don't Have Time"
The Objection
"We're too busy to go through a software development process right now."
Response framework: Flip the time argument. "That's actually a common concern — and often the reason businesses seek custom solutions. If the software saves your team even 10 hours per week, you're gaining back 520 hours per year. The initial time investment in discovery and planning is minimal compared to the time you'll save. Plus, FussionShade handles most of the work — your involvement is mainly in key decisions and approvals."
Objection 5: "We Need to Think About It"
The Objection
"This is interesting, but we need some time to think it over."
Response framework: Respect the timeline while maintaining momentum. "Absolutely, this is an important decision. To help with your thinking, what specific questions or concerns would be most helpful to address? I can arrange a brief call with our technical team to answer any detailed questions. When would be a good time to follow up?"
Pushing too hard creates resistance. Give space while ensuring there's a clear next step.
Objection 6: "We Need to Talk to Our Partner/Board/Team"
The Objection
"I need to discuss this with my business partner / board / team before making a decision."
Response framework: Support their internal process. "Of course — involving your team is the right approach. Would it be helpful if I prepared a brief summary document that addresses the key points? I can also arrange a short presentation for your partner/board if that would be useful. What questions do you think they'll have?"
The LAER Framework for All Objections
For any objection, use the LAER framework:
- Listen: Give the prospect your full attention. Don't interrupt or formulate your response while they're speaking.
- Acknowledge: Validate their concern. "I understand" or "That's a valid point" shows you're hearing them.
- Explore: Ask clarifying questions to understand the root of the objection. Often the stated objection isn't the real concern.
- Respond: Address the specific concern with relevant information, and confirm it's been addressed.
Need Help Handling Objections?
FussionShade provides partners with objection handling guides, sales scripts, and dedicated support to help you navigate difficult conversations.
Get Sales Support