Friday Q&A: How far should you go to land that BIG customer?

It’s Friday. Your pipeline is lukewarm. Then a whale appears. A big-name customer. A logo you’d proudly slap on your homepage. The kind of deal that makes your team walk taller, your investors smile wider, and your coffee taste… slightly less like panic.

So you ask the classic Friday question: How far should you go to land that BIG customer?

Answer: Farbut not off a cliff.

This Q&A-style guide breaks down where “going the extra mile” is smart (and scalable), where it turns into expensive people-pleasing, and how to set guardrails so you can win the deal and keep your margins, morals, and Monday morning sanity.

The real question isn’t “How far?” It’s “How far in which direction?”

Big customers don’t just buy your product. They also buy:

• Your operational maturity (can you deliver, support, and secure this thing?)
• Your commercial maturity (can you price, negotiate, and contract without melting?)
• Your integrity (can you win without questionable shortcuts?)

So “how far” really splits into three practical questions:

• How far should you flex your roadmap?
• How far should you flex your pricing?
• How far should you flex your boundaries?

Let’s answer them like a proper Friday Q&Aclear, direct, and with minimal corporate haikus.

Q1: How far should you go before you even know it’s the right deal?

A: Far enough to qualify it like your rent depends on it. Because it probably does.

Big customers are masters of motion. Meetings happen. Decks get requested. “Can you just…” becomes a daily phrase. And three months later you realize you’ve been running an unpaid graduate program in “How We Think About Our Internal Problems.”

A fast “BIG customer” qualification checklist

• Business pain: Is there a real, urgent problemor just “we’re exploring options” energy?
• Impact: Can they name measurable outcomes (cost, revenue, risk, time)?
• Authority: Do you have access to an actual decision-maker, not just a professional meeting-attender?
• Process: Do they have a defined buying process (procurement, legal, security), and can they explain it?
• Timeline: Is there a deadline with consequencesor a vague seasonal mood?
• Fit: Do you solve the problem without becoming a custom dev shop in disguise?

If you can’t get clarity on those basics, going “far” is just jogging enthusiastically in the wrong direction.

Q2: How far should you go with customization?

A: Go far on outcomes. Go cautiously on one-off features.

Big customers often ask for “one small tweak,” which is adorablelike a toddler calling a grand piano “a little toy.” The trick is distinguishing between:

• Configuration: Settings, workflows, integrations, permissionsthings that use your existing product muscles.
• Productizable enhancements: Improvements that will help multiple customers and strengthen your platform.
• One-off customization: Features that only make sense in their universe, maintained forever by you (and your future regret).

The “Museum Gift Shop” rule

If you build a one-off feature, you own it like a souvenir you didn’t want but feel guilty throwing away. It sits there. It collects dust. It becomes your responsibility in every release cycle.

Instead, try this boundary-friendly approach:

• Translate requests into outcomes: “What would this enable you to do that you can’t do today?”
• Offer three options: (1) configuration now, (2) workaround + timeline, (3) paid custom project with clear scope.
• Use “product language”: “We can commit to capability X by date Y, if we agree on success criteria and a commercial exchange.”

The goal is not to be rigid. The goal is to be intentional.

Q3: How far should you go with pricing and discounts?

A: Far enough to be competitivenever far enough to train them to undervalue you.

Here’s the uncomfortable truth: a “big logo” doesn’t pay your bills. Cash flow does. And deeply discounted deals often come with premium-level demands: more support, more compliance, more meetings, more “quick calls,” more everything.

Discounting without self-sabotage

Use discounts as a trade, not a gift:

• If you want a lower price, we need something back: longer term, upfront payment, reduced scope, standard contract terms, a reference story, or a faster decision date.
• Make discounting conditional: “This pricing assumes X users by Y date” or “This rate is tied to a 24-month term.”
• Protect your floor: Build a minimum viable margin that accounts for onboarding, security reviews, and support load.

A big customer should be a growth engine, not a slow-motion charity fundraiser.

Q4: How far should you go with procurement, security reviews, and legal redlines?

A: Very farbecause this is the stuff that actually closes enterprise deals.

Enterprise buying isn’t just persuasion. It’s proof. Big customers need confidence that you’re safe, stable, and not one unexpected incident away from starring in a “Lessons Learned” meeting.

Make it easy for them to say “yes” internally

Think of the buying committee as a group project where nobody volunteered. Your job is to hand them the materials to defend the decision:

• Security package: clear controls, incident response, data handling, encryption basics, access controls.
• Assurance reports: where relevant, have a plan for third-party assurance (for many buyers, a SOC 2 report is a familiar signal).
• Implementation plan: timeline, responsibilities, milestones, “what you need from them.”
• ROI summary: a simple business case with measurable outcomes.

And yes, the paperwork can be intense. But if you treat it like a closing activitynot a bureaucratic punishmentyou’ll move faster than competitors who treat it like background noise.

Q5: How far should you go with pilots and proofs-of-concept?

A: Far enough to prove value. Not so far you build a second product for free.

Pilots are useful when they’re structured. Dangerous when they’re fuzzy.

A “healthy pilot” has these ingredients

• Written success criteria: “If we achieve A, B, and C, you move to purchase.”
• Time box: 30–90 days is typical; longer pilots should have milestones.
• Mutual commitment: named stakeholders on both sides, regular check-ins, and clear access to data or environments.
• Commercial clarity: paid is best; if free, scope must be tight and conversion terms explicit.

If a pilot becomes “let’s just keep trying things,” congratulationsyou are now running a consulting practice with none of the pricing power.

Q6: How far should you go with relationship-buildingdinners, travel, and “perks”?

A: Far on professionalism. Extremely cautious on anything that smells like influence-buying.

Let’s say the quiet part out loud: sometimes people confuse “enterprise sales” with “I should probably expense something shiny.”

Here’s the safer rule: keep relationship-building clearly business-related, modest, and policy-friendly. Many large organizations have strict gift and entertainment policies. And if government entities or international business are involved, anti-bribery rules can be especially serious.

What “good” looks like

• Modest hospitality: reasonable meals tied to legitimate business discussion.
• Transparent agendas: “Here’s what we’ll cover” beats vague “let’s hang out.”
• Documentation: keep records of business purpose and attendees when needed.

What “bad” looks like (and can explode later)

• Lavish gifts, luxury travel, or entertainment that looks like a reward for influence.
• Anything hidden (“don’t put this in writing”)that sentence is basically a siren.
• Using third parties to do what you “can’t do directly.” That’s not clever; that’s a compliance horror story.

If you ever find yourself thinking, “Would I feel comfortable if this showed up in a public report?”listen to that instinct. It’s the adult in the room.

Q7: How far should you go in negotiations without giving away the store?

A: Go far on preparation and claritythen negotiate in trades, not concessions.

Big-company negotiations can be tricky because the other side may have internal misalignment: procurement wants the lowest price, legal wants zero risk, security wants every document ever created, and the business owner just wants the problem solved yesterday.

Negotiation guardrails that keep you from spiraling

• Know your “must-haves” vs. “nice-to-haves” before the first redline arrives.
• Bundle concessions: “We can accept X if we also agree on Y and Z.”
• Limit custom terms: special clauses should have an internal costbecause they create future work.
• Protect scope: define what’s included in onboarding, support response expectations, and change control.

Think of negotiation like Jenga: remove too many blocks (margin, scope, boundaries), and eventually the whole relationship collapsesusually right after you hire three people to support it.

Q8: How far should you go before you walk away?

A: Walk away when the deal asks you to become someone you don’t want to be.

Legit “walk away” signals

• No access to real decision-makers after repeated attempts.
• Endless unpaid work with no defined next step.
• They want extreme customization but refuse to pay for it.
• Contract terms create existential risk (unlimited liability, impossible SLAs, vague security obligations with strict penalties).
• They pressure you into questionable behavior (“everyone does it,” “just invoice it differently,” “keep this off the books”).

Walking away doesn’t mean you’re “not enterprise-ready.” Sometimes it means you’re strategy-ready.

Friday lightning round: quick answers to common “BIG customer” dilemmas

“Should we do a custom feature to win?”

Only if it supports a broader product direction, has clear scope, and has a commercial exchange. Otherwise, you’re adopting a permanent pet.

“Should we fly out tomorrow?”

If there’s clear purpose, decision-maker access, and a defined next step. If it’s a vibe-based visit, save the airfare.

“Should we match the competitor’s price?”

Match the buyer’s desired outcomes, not a random number. If you do discount, trade for term, scope, or speed.

“Should we accept their contract as-is?”

Rarely. Enterprise contracts often start aggressive. Respond with calm, specific edits tied to realistic delivery and risk.

“Should we give them a free pilot?”

Only if it’s tightly time-boxed with written success criteria and conversion terms. Free + vague = doom.

“How do we avoid being buried by security reviews?”

Prepare a repeatable security package and standard answers. The goal is to answer fast without improvising your way into contradictions.

Bonus: 10 experience-based lessons from chasing (and landing) big customers

To make this feel less theoretical, here are real-world patterns teams run into when they go after big customers. These are “seen it a dozen times” lessonsno confidential details, just the recurring themes that show up like clockwork.

1) The deal doesn’t start bigit starts unclear

Early conversations often sound like: “We’re exploring,” “We’re evaluating vendors,” “We’re just gathering info.” The winning teams don’t panic. They gently force clarity. They ask what problem triggered the search, what happens if it’s not solved, and who will own the decision. If the answers are foggy, they don’t sprintthey slow down and qualify.

2) The fastest way to lose credibility is to overpromise

In big deals, credibility is currency. Saying “yes” to everything feels helpful, but it creates future moments where you have to explain why you can’t deliver what you implied. The stronger move is: “Here’s what we can do now, here’s what we can do next, and here’s what would require a separate scope.” Buyers usually respect precision more than enthusiasm.

3) Procurement isn’t your enemyconfusion is

Teams that treat procurement like a villain end up emotionally exhausted and strategically sloppy. Procurement’s job is to reduce risk and create consistency. When you provide clear terms, clean documentation, and fast answers, procurement often becomes a pathnot a wall.

4) Big customers love pilotsuntil nobody defines “success”

A pilot without success criteria turns into a never-ending “maybe.” The teams that win write down what success means (metrics, adoption, performance) and what happens next (purchase, expansion plan, timeline). It can feel awkward to ask for that clarity. Do it anyway. Awkward beats endless.

5) Discounts that aren’t traded come back to haunt you

When teams give a big discount “because it’s a big name,” they often get a customer who expects special treatment forever. The healthier pattern: every discount buys somethinglonger term, upfront payment, limited scope, faster timeline, or a reference story. The discount becomes part of a professional exchange, not a hopeful sacrifice.

6) The internal champion is everything (and needs tools)

Inside every big company, someone has to sell your solution internally. If you don’t arm them, they’ll get outvoted by risk, inertia, or “we already have something for that.” Winning teams provide business-case summaries, simple ROI math, and a clear narrative the champion can repeat without needing a translator.

7) Custom requests are often a proxy for fear

Sometimes the customer isn’t truly demanding a unique featurethey’re anxious about adoption, integration, or accountability. When you ask, “What risk does this request reduce for you?” you often find a simpler solution: configuration, training, or a documented control instead of building something new.

8) Security readiness speeds up sales more than most marketing campaigns

Teams that prepare security documentation early move faster when a deal heats up. Teams that wait often hit a brutal stall: “We love it, but security needs…” followed by weeks of scrambling. The big lesson: security readiness isn’t just complianceit’s sales velocity.

9) “No” said early can preserve the relationship

It’s counterintuitive, but a respectful “we can’t do that” can build trustespecially when you offer a workable alternative. Big customers don’t only want agreeable vendors; they want reliable partners. Reliability includes honest constraints.

10) The biggest win isn’t signingit’s successfully onboarding

Many teams celebrate the signature and then stumble during onboarding, which damages expansion potential. The best enterprise wins include a clear implementation plan, named owners, and early “quick wins” that make the buyer look smart. A big customer isn’t truly “landed” until they’re live, seeing value, and willing to expand.

Conclusion: Go farbut set your “far” in advance

Landing a BIG customer is absolutely worth extra effortwhen that effort is strategic. Go far on preparation, clarity, proof, and customer success. Go cautiously on one-off customization, open-ended free work, and anything that compromises ethics or long-term margin.

In other words: Earn the logo. Don’t sacrifice your company to it.

SEO Tags