Getcha Solutions, Business, Technology

“Let Me Discuss This With My Partner…” (And 17 Other Classic Client Stall Tactics)

Posted on by admin
17
Jul

“Let Me Discuss This With My Partner…” (And 17 Other Classic Client Stall Tactics)

Real Stories, Pricing Pushbacks, and How to Respond Without Losing the Deal (or Your Sanity) — From a Singapore Software Developer Who’s Heard Every Excuse Since the Dial‑Up Days.

This is an article for fellow developers. If you are a client or a prospect (especially mine), please turn away.

TL;DR (for the busy, the curious, and the serial quotation-requesters): When a potential client says, “Let me discuss this with my partner, and get back,” it may be genuine… but often it’s polite Singaporean for “No thanks,” “Too expensive,” or “I need to Google if you’re legit.” In this romp through real client conversations, I’ll decode the euphemisms, share war stories from nearly three decades of building custom web apps, mobile apps, and management systems, and show you how to respond in ways that save time, preserve goodwill, and even win deals others lose. Expect humour, mild sarcasm, real scripts you can copy, and a few local flavour notes, lah.

What I’m Gonna Talk About

  1. Intro: The Most Common Sentence in Clientland
  2. Why People Say “Let Me Discuss…” — The Psychology of Polite Deferral
  3. Flashback: My First Time Hearing It (Spoiler: I Waited. They Never Came Back.)
  4. Singapore Context: Politeness, Face-Saving, and the Art of Not Saying No
  5. 17+ Variations of “Let Me Discuss…” You’ll Hear in the Wild
  6. What They Really Mean (Decoded by Pattern, Budget, and Timing)
  7. Better Ways They Could Say It (And How to Nudge Them There)
  8. Your Toolkit: Follow‑Up Scripts That Get Real Answers Fast
  9. Pricing Anchors, Budget Discovery & The Magic of Ranges
  10. Story Time: The $500 App That Became a $50K Platform (Because I Asked One Question)
  11. When to Let Go: Spotting Time-Wasters Early
  12. Mini Decision Tree: What to Do After the Stall
  13. Templates You Can Copy & Paste Today
  14. Humour Break: Client Bingo Card & Excuse Translator
  15. Action Plan: Turn Polite Deferrals Into Clear Decisions
  16. Before You Go: Share Your Funniest Client Excuse in the Comments!

1. Intro: The Most Common Sentence in Clientland

If I had a dollar (Singapore, not Monopoly money) for every time a prospect told me, “Let me discuss this with my partner, and get back,” I could retire to Sentosa, buy an overpriced robot coffee machine, and spend my days refactoring code that no one asked me to write.

You know the line. You’ve said the line. I’ve heard the line from founders, SMEs, restaurant owners, tuition centre principals, property agents, multinational teams, and once — from a guy who was the only decision‑maker in his company. (He told me he had to discuss with his partner. He did not have a partner. He had a cat.)

In software development — especially custom builds — money, scope, and trust all collide. People get nervous. Numbers get big. Tech sounds confusing. The polite reflex kicks in. And out comes the great universal delay phrase: “Let me check with…”

This article is my happily overcaffeinated attempt to unpack that moment — why it happens, what it often really means, and how to steer the conversation toward clarity, whether the answer is yes, no, not yet, or we need a cheaper version that doesn’t require a NASA launch team.

I’ll weave in personal stories from my life as a freelance/agency/consulting hybrid developer in Singapore since the late 1990s (yes, we FTP’d live, don’t judge). I’ll give you real reply scripts you can copy. And I’ll show you how to turn what sounds like a brush‑off into a next step that respects both your time and your prospect’s budget.

Ready? Grab kopi. Let’s go.

2. Why People Say “Let Me Discuss…” — The Psychology of Polite Deferral

Let’s not assume bad intent. Most people are not trying to waste your time. They are trying to:

  • Avoid making a bad decision. Tech is confusing. Committing money feels risky.
  • Consult hidden stakeholders. A spouse, silent business partner, cousin‑investor, boss overseas, or that one IT nephew who “knows coding.”
  • Buy time to compare quotes. You’re Vendor B. Vendor A was cheaper. Vendor C promises AI (always AI!).
  • Avoid conflict. Saying “Too expensive” can feel rude, especially in cultures (like Singapore’s multi‑cultural mix) where harmony matters.
  • Get leverage. They want your best price, or upgraded features, so they stall while they gather bargaining chips. (Nowadays, everyone wants to do a Trump.)

A Quick Feelings Map

When a client hesitates, it’s rarely about the code first. It’s about this:

Once you understand the emotional driver, you can respond humanly instead of robotically chasing a yes.

3. Flashback: My First Time Hearing It (Spoiler: I Waited. They Never Came Back.)

It was 1999. I was still carrying a zip disk (if you know, you know) and doing brochureware websites for small businesses around Singapore. A furniture shop owner asked for “simple website, 5 pages, must have wood texture background.” I gave him a quote. He smiled. Said, “Okay okay, let me discuss with my partner and get back to you.”

I waited. Checked email daily (on dial‑up). Called once. Felt shy. Waited more. Nothing.

Three months later, I walked past his shop. There on the door: URL to a new website… built by someone else. With wood texture. (Pain.)

Lesson learned: Silence = No. Unless you create the next step.

4. Singapore Context: Politeness, Face-Saving, and the Art of Not Saying No

If you work in Singapore — or with Singapore clients overseas — you’ll notice a few communication patterns:

  • Indirect decline is common. We soften rejection to maintain “face” and relationship.
  • Hierarchy matters. Even if the contact person likes your proposal, they may need buy‑in from a director, spouse co‑owner, or investor.
  • Budget timing cycles. Many SMEs decide near fiscal year close, after grants, or once GST filings calm down.
  • Grant hunting first, vendor selection second. Especially for tech projects. If your quote helps them justify a grant application, they’ll keep you warm… but may still shop later.

So when someone says, “I’ll check with my partner,” it may actually mean, “My co‑founder approves all expenses above $5K,” or “I need to see whether we can claim this in the next Productivity Solutions Grant cycle,” or “I’m trying to convince my spouse that this system will reduce our double-booking headaches at the tuition centre.”

Understanding the local decision chain saves frustration — and lets you ask smarter follow‑ups.

5. 17+ Variations of “Let Me Discuss…” You’ll Hear in the Wild

Below are real (slightly anonymised) phrases I’ve collected over the years from prospects, SMEs, agencies, and once — a government-linked org that needed three committees and a fruit basket.

I’ve grouped them by flavour: Delay, Budget, Authority, Trust, and Ghost Mode.

A. Straight Delays

  1. “Let me discuss with my partner and get back.”
  2. “We’ll review this internally.”
  3. “I’ll bring this up in our next meeting.”
  4. “Need to talk to the team first.”

B. Budget Uncertainty

  1. “We didn’t expect it to be this much.”
  2. “Let me see what budget we have left.”
  3. “We’re applying for a grant — can wait?”
  4. “Can you break into phases? We do phase 1 now.”

C. Authority Transfer

  1. “My boss has final say.”
  2. “I need to show this to my husband/wife.”
  3. “Our investor has to sign off.”
  4. “Procurement must approve vendors.”

D. Trust / Proof Needed

  1. “Do you have references we can talk to?”
  2. “Can you show sample work similar to ours?”
  3. “We’re comparing a few providers.”

E. Ghost Mode Indicators

  1. No reply after proposal.
  2. “Will revert soon.” (Classic.)
  3. “Circling back after Chinese New Year?” (Say this in August; you know what it means.)

Pro Tip: Track which phrases convert. In my CRM (yes, my own system), I tag the last message received pre‑silence. After 20+ years, “Will revert soon” = 8% chance of closing. “Can you break into phases?” = 43% close rate. Patterns matter.

6. What They Really Mean (Decoded by Pattern, Budget, and Timing)

Not all delays are equal. Use clues:

6.1 By Timing

  • Immediate stall after pricing: Probably sticker shock.
  • Stall after technical explanation: Info overload. Simplify.
  • Stall after success stories: Comparison shopping; you’re in the running.

6.2 By Project Type

  • POS / booking / internal workflow systems: Often co‑owned decisions; expect “need to ask partner.”
  • Marketing website: Single decision maker more likely; stall may mean “I’ll shop cheaper.”
  • Grant‑eligible projects: Long lead time; stall can be real. Ask about grant calendar.

6.3 By Budget Language

If someone says:

  • “Above 5K must get approval.” Good — ask to present to that approver.
  • “We thought it’s like $500.” Education needed; offer small discovery workshop.
  • “We only need basic version first.” Sell phased build.

6.4 Red vs Yellow vs Green Signals

7. Better Ways They Could Say It (And How to Nudge Them There)

Sometimes prospects want help saying no but don’t know how. You can model better conversation by giving them structured choices.

Offer a Multiple‑Choice Close

Try this in email or WhatsApp:

Quick check so I plan my schedule: A) We’d like to proceed as quoted. B) We’re interested but need to adjust scope to fit budget. C) We’re not moving forward now, but keep in touch. D) We’ve gone in a different direction — thanks.

People respond when options are easy. And even a C or D lets you move on respectfully.

Train Clients to Give Useful Feedback

Instead of “Let me discuss,” encourage:

  • “Our budget ceiling is $X — what can we do?”
  • “We need payment in milestones — okay?”
  • “We like you but comparing two other vendors — can you show why you’re different?”

Gentle Script to Invite Honesty

“Totally fine to say this isn’t the right fit or timing. If budget’s tight, we can scale down. If you’re exploring, I can follow up in a month. Let me know what helps you most.”

When you remove pressure, truth comes out.

8. Your Toolkit: Follow‑Up Scripts That Get Real Answers Fast

Here are message templates you can adapt to email, WhatsApp, LinkedIn, or your CRM automation. I’ve tuned these over years of pitching custom management systems, booking tools, dashboards, and mobile apps to Singapore SMEs.

Tone Notes: Friendly, short, pressure‑off, next‑step‑clear.

8.1 Immediate Follow‑Up (Same Day)

Subject: Quick recap + next step?

Hi {{Name}},

Thanks for today’s chat about the {{project type}} for {{company}}. As discussed, I’ve attached the proposal (${{amount}} for Phase 1).

You mentioned you’ll discuss with {{partner/stakeholder}}. 
Would it help if I:

  • Joined that call to walk through cost vs scope?
  • Sent a phased breakdown (MVP vs full)?
  • Shared similar case studies from other Singapore SMEs?

Let me know which is easiest and I’ll prep it.

Cheers, Anees Khan

8.2 3‑Day Light Nudge

Hi {{Name}}, just checking if you had a chance to review the proposal with {{partner}}. Happy to answer budget or timeline questions. If it’s easier, I can do a quick 15‑min call. What works?

8.3 Budget Discovery Rescue

Hi {{Name}}, if the full build feels heavy, we can do a scoped “Discovery & Prototype Sprint” for {{S$X}}. It gives you clickable screens + tech plan you can take anywhere. Worth considering?

8.4 Close‑File Email (Respectful Exit)

Subject: Should I close the file on {{Project Name}}?

Hi {{Name}},

Haven’t heard back — no worries. To keep my schedule tidy, I’ll close the file on {{date}} unless you want to keep it alive. If timing/budget changed, just reply with “Later” and I’ll follow up next month.

Appreciate the chat either way.

— Anees Khan

Why this works: Gives permission to say no. Creates deadline. ~25% of my “dead” leads reply after this.

9. Pricing Anchors, Budget Discovery & The Magic of Ranges

A huge reason prospects stall is because you gave one big number and they froze like a JavaScript thread in an infinite loop.

Use Ranges Early

Instead of: “Full system: $40K.” Try: “Projects like this usually fall between $25K–$60K depending on modules, integrations, and user load. Where do you want to land?”

Now the conversation starts.

Anchor With Tiers

Offer 3 versions:

  • MVP / Lite: Core features, manual data import, basic UI. ($X)
  • Growth: Adds automation, dashboards, role‑based access. ($2–3X)
  • Scale: Integrations, mobile app, reporting, support SLA. ($4–5X)

People pick the middle. (Human nature + pricing psychology.)

Break the Mountain Into Hills

Show multi-phase timeline:

  1. Discovery & UX (2 weeks).
  2. Prototype (2–4 weeks).
  3. Core Build (6–12 weeks).
  4. Enhancements (ongoing).

Now they can commit to Phase 1 while “discussing” Phase 2.

Budget First, Scope Second

Ask early:

“Rough ballpark — are you thinking in the hundreds, low thousands, tens of thousands? Helps me not over‑ or under‑design.”

This single question reduces ghosting by 30% in my tracking. (Yes, I track.)

10. Story Time: The $500 App That Became a $50K Platform (Because I Asked One Question)

Years ago, a small enrichment centre in Singapore emailed: “Hi, how much to build simple booking app? We have 3 tutors, 1 location.” They expected $500.

Instead of quoting, I asked: “What happens after a parent books? Who confirms? How do you track payments? Do you run promotions?”

Turns out: 8 locations planned. Manual Excel madness. Parents double‑booking. No reminder system; lots of no‑shows.

We started with a Discovery Sprint (~$1.2K). That produced clickable wireframes + a clear workflow. They brought that to their partners (who were previously “Let me discuss…” people). Because they could see the value, they bought into a phased rollout.

Over 18 months, the system evolved into a multi‑branch booking + payment + SMS reminder platform pushing past $50K in total project value. Same lead that might’ve ghosted after a $500 quote.

Key Move: Ask process questions that reveal hidden cost of doing nothing.

11. When to Let Go: Spotting Time-Wasters Early

Not every inquiry deserves three follow‑ups. Your time = billable asset.

Walk Away When:

  • They ask for full proposal before sharing budget, timeline, or decision process.
  • Every answer yields a new “partner” who needs to review.
  • They want “trial version free first” for custom build.
  • They disappear repeatedly and resurface only to ask “best price?”

Quick Filter Questions (Use These!)

  1. Who will use this system day to day?
  2. Who signs off on budget?
  3. When do you hope to go live?
  4. Is this project confirmed or exploratory?
  5. What problem is costing you the most now?

If answers = vague, budget = mystery, timeline = “see how”, and decision = “later” — park the lead in a nurture list and move on.

12. Mini Decision Tree: What to Do After the Stall

Client says: "Let me discuss and get back."
          |
     Did they give a timeframe? ---- no ----> Ask: "When's good to follow up?" (schedule date)
          |
         yes
          |
 Wait until agreed date.
          |
 Did they respond? ---- no ----> Send 3-day nudge.
          |
         yes
          |
 Is feedback budget-related? ---- yes ----> Offer phased/tiered options.
          |                              
          no                               > If deal size small + high scope -> Discovery Sprint.
          |                                /
 Is feedback timing-related? ---- yes ----> Park lead; schedule check-in.
          |
         no
          |
 Are they choosing vendor? ---- yes ----> Provide proof, references, demo.
          |
         no
          |
 Close deal.

Stick this in your CRM notes. Turn it into automation triggers.

13. Templates You Can Copy & Paste Today

Below are ready‑to‑go snippets for different channels. Replace {{tokens}} with real data. Keep it human. Add emojis only if they started first. (I once lost a deal because I used a 🛠️ spanner emoji and the CEO thought it looked “too casual”. True story.)

13.1 WhatsApp Quick Reply (After a Call)

You: Great chatting just now! I’ve sent the proposal. Since you’ll be discussing with {{partner}}, would it help if I joined that discussion or prepared a simplified cost vs benefits summary? Let me know. 🙂

13.2 SMS Lite (Old-School Clients)

Hi {{Name}}, Anees here re: booking system quote. Any qns from your side or partner? Happy to adjust scope. Reply 1=Proceed, 2=Change scope, 3=Later.

13.3 Email With Budget Options

Hi {{Name}}, attaching 3 options:

  • Lite: Online form + manual confirm (fastest / lowest cost)
  • Pro: Auto scheduling + reminders
  • Scale: Multi‑branch + payments + dashboard

If you share budget range, I’ll recommend best fit.

13.4 Follow‑Up After Silence (Humour Variant)

Subject: Did your partner run away with my proposal?

Hi {{Name}}, checking in — last I heard you were showing the quote to your business partner. Did they:

  • 🏃 Flee the country,
  • 🧮 Ask for revised budget,
  • ✅ Approve it and you forgot to email me,
  • ❌ Decide against it for now?

Circle one and I’ll react accordingly. 😉

14. Humour Break: Client Bingo Card & Excuse Translator

Because if we don’t laugh, we’ll debug spreadsheets for free.

14.1 Client Excuse Bingo

Make a 5×5 bingo board for your next sales month. Mark them off as you hear them.

First to bingo = you buy yourself bubble tea.

14.2 Excuse Translator (Kid Logic Edition)

15. Action Plan: Turn Polite Deferrals Into Clear Decisions

Here’s a step‑by‑step you can apply to your next five leads. Yes, I’m giving homework. Future‑you will thank me.

Step 0: Before You Quote

  • Ask for budget range.
  • Confirm who signs off.
  • Ask go‑live target date.

Step 1: Present Choices, Not One Big Number

  • Give 3 tiers (Lite / Pro / Scale).
  • Mark recommended tier.

Step 2: Pre‑Handle the Stall

Say during call:

“Often next step is you check with partner. Totally fine. What info do they usually need — budget summary, timeline, ROI?”

Step 3: Calendar the Follow‑Up In the Call

“Shall we tentatively reconnect Friday 3pm after you discuss?”

Step 4: Track Outcomes

Log stall language + outcome in CRM. After ~30 leads you’ll see patterns by industry and budget.

Step 5: Triage Leads

  • Hot (date set) — follow up.
  • Warm (budget interest) — nurture.
  • Cold (ghost) — close file & drip.

Step 6: Re‑Engage Smartly

Send success stories tied to their pain (“How tuition centre cut no‑shows 40% with SMS reminders”). Relevant, not spam.

16. Before You Go: Share Your Funniest Client Excuse in the Comments!

We’ve all heard it: “Let me discuss this with my partner, and get back.” Sometimes they do. Sometimes they vanish like a temporary variable that never got returned.

But now you’ve got tools:

  • Decode the stall.
  • Invite honesty.
  • Offer tiers.
  • Set next steps.
  • Walk away when needed.

Custom software isn’t cheap — but neither is running a business on spreadsheets, WhatsApp chats, and crossed fingers. Your job (our job, fellow devs!) is to help clients see the cost of doing nothing and give them decision paths that feel safe, respectful, and sane.

Your Turn

What’s the funniest, most dramatic, or most polite brush‑off you’ve ever received from a client or vendor? Drop it in the comments. I’ll respond with a recommended comeback script (yes, really!).

Or if you are that client currently “discussing with partner”… tell me what info you need to move forward. I’m here.

Thanks for reading!

If you found this helpful, tap the 👏 on Medium (up to 50, go wild), follow me for more behind‑the‑scenes stories from a Singapore developer’s life, and share this with that friend who keeps saying “will revert soon.”

 

admin