12 Red Flags That Mean You Should Walk Away From an IT Vendor (Before You Sign)

Opaque Pricing That Requires Multiple Conversations

If a vendor won't give you a complete price sheet before the first demo — or if every pricing question triggers "let me check with my manager" or "that depends on your specific configuration" — the real cost is higher than they want to reveal before you're emotionally invested in the product.

→ Ask for fully loaded annual pricing in writing before the first demo. If they won't provide it, treat this as a high-severity red flag.

Year-1 Discount Traps

A vendor offers 40% off for the first year, structures the contract as an annual auto-renewing agreement, and buries the renewal price in an appendix or simply states "standard pricing." You sign. Year 2 arrives. Your bill is 60% higher and you have 30 days to cancel — which requires migrating your data on a tight timeline. This is one of the most common and expensive traps in SMB software buying.

→ Always ask: "What is the standard non-promotional price, and what is the price at renewal?" Get both numbers in writing before signing anything.

Vague Implementation Timelines

Implementation timelines that come with heavy qualifiers — "typically 6 to 12 weeks, depending on your data" or "we've seen as fast as 2 weeks but it varies" — are a signal that projects routinely overrun. Every week your team spends on implementation is a week of distraction from your core business. Ask for the median timeline for companies at your size, and ask what percentage of implementations come in on schedule.

→ Ask for median implementation time for companies your size, and the on-time delivery rate. Get milestones and penalties for delays in writing.

SLAs Without Financial Penalties

A Service Level Agreement that promises 99.9% uptime but carries no financial consequence if that commitment is missed is a marketing document, not a contract. Uptime guarantees are only meaningful when breach of the SLA triggers service credits, price reductions, or the right to terminate. An SLA with no teeth is worse than no SLA, because it creates the appearance of accountability without the substance.

→ Read the SLA remedies section carefully. If breach of uptime commitments results only in a right to terminate (not credits or refunds), that's a weak SLA dressed up as a strong one.

Thin Reviews, One-Sided Praise, or Review Gaps

A vendor with 50 reviews on G2, all rated 4.5 or above with near-identical language, is either gaming review platforms or has a self-selected customer base. The useful signal is in the critical reviews: what do unhappy customers say specifically? Look for patterns around support quality, billing disputes, and product gaps. A vendor with 500 reviews and a healthy mix of 3-star critiques is usually more trustworthy than one with 50 uniformly glowing reviews.

Also watch for review velocity gaps. A vendor that had 200 reviews two years ago and only 20 since then has stagnating growth or a worsening reputation keeping new customers from posting.

→ Sort reviews by "most recent" and filter to 2 and 3 stars. The specific complaints in those reviews predict your experience better than the average score.

No Customer References at Your Scale

When you ask for references and the vendor offers introductions to enterprise customers, or to businesses in completely different industries, they're signaling that their SMB customer base isn't happy enough to serve as references — or that SMBs aren't their real market. You'll be treated accordingly after the contract is signed: as a small account to be managed efficiently rather than a customer to be served.

→ Request 3 references from companies with similar employee count, industry, and use case. If the vendor can't or won't provide them, that tells you something.

Feature Bloat That Obscures Core Weakness

A vendor demo that spends 40 minutes on integrations, dashboards, and AI features before showing how the core workflow actually functions is usually trying to distract you from a weak core product. Feature count is not functional fit. If the most important capability — the thing you're actually buying the software to do — requires 20 minutes to demonstrate and comes with caveats, the platform isn't ready for your use case.

→ Before the demo, send your top 3 required capabilities and ask the rep to start there. How easily they demonstrate the core function tells you everything.

High-Pressure Sales Tactics

Artificial urgency — "this pricing expires Friday," "we only have 3 slots left for Q2 onboarding," "my manager approved this discount but only until end of month" — is a classic indicator that the vendor knows the deal won't survive a careful evaluation. Good vendors want informed customers, because informed customers stay longer and generate referrals. Vendors who pressure you to sign before you've finished due diligence have something to hide.

→ The correct response to artificial urgency is to slow down, not speed up. If the pricing genuinely expires, ask for it in writing with the expiration date — vendors that are serious about the business rarely let deals die over a week's extension.

Buried Switching Costs

Switching costs take several forms, and savvy vendors bury all of them. Data portability restrictions — "we can export your data in our proprietary format" — mean migration will require expensive custom development. Deep integrations with proprietary APIs mean every connected tool needs to be rebuilt if you switch. Vendor-managed configurations mean you don't actually own your own setup documentation. Read the contract's data rights and portability provisions before you sign. If you can't get your data out cleanly, you're locked in by design.

→ Ask specifically: "If we cancel, what format will our data export be in, how long will we have access to export it, and is there a fee for bulk data export?" The answers are revealing.

Single Point of Contact With No Escalation Path

A vendor relationship that runs entirely through one account executive or customer success manager is fragile by design. When that person leaves — and in software sales, turnover is high — you lose continuity, institutional knowledge of your account, and sometimes the informal accommodations that made the relationship work. Ask who your escalation contacts are, whether they're named in the contract, and what the vendor's average account team tenure looks like.

→ Ask: "If my account manager leaves, what's the transition process?" and "Who can I escalate to if I can't reach my CSM?" Vendors with healthy support structures answer this easily.

Coordination Fees, Integration Charges, and "Professional Services" Scope Creep

An implementation quote that excludes "professional services" or "custom configuration" is not a real implementation quote. Professional services charges routinely double the first-year cost for complex implementations. Some vendors structure their products to require paid professional services for tasks that should be self-serve — data migrations, custom fields, API connections — because it's a high-margin revenue stream that's hard to cut once you're mid-implementation.

→ Ask for a "fully loaded" first-year cost estimate that includes all implementation, configuration, training, and integration work. If the vendor can't give you that number, request an itemized professional services SOW before signing the software contract.

Multi-Year Lock-In With No Exit Clause or Performance Guarantee

A two or three-year contract with no termination-for-cause provision and no SLA-linked exit right traps you even if the vendor materially fails to deliver. Software changes, companies get acquired, products get sunset, and your needs evolve. A contract that binds you regardless of vendor performance is not a partnership — it's a financial obligation you're taking on with no recourse. The absence of an exit clause in a multi-year contract is almost always a deliberate choice.

→ For any multi-year contract, negotiate a termination-for-cause provision tied to SLA breaches, a material product downgrade, or acquisition. If the vendor refuses any exit provisions, the risk profile of a multi-year commitment is too high for most SMBs.