You can get a good price on a well reviewed platform and still end up replacing it. It might not work with the equipment you planned to keep. Or a new office or compliance requirement shows up three years later, and the platform can’t handle it.

Max Clark, CEO of ITBroker.com, covers both problems in a recent Signed Playbook. He argues that what you already run, and where the business is headed, should shape your shortlist before you compare a single feature.

In IT, adding to systems you already have is called a brownfield project. Starting from nothing is greenfield. Most vendor evaluations skip both questions and go straight to a feature and price comparison, because it’s easy to build and it’s the comparison vendor sales teams are trained to win. That comparison assumes every vendor is a real option for you. Usually some of them aren’t.

So answer two questions first. What have you already committed to? And what will the business need next?

How to Check Vendor Compatibility With Your Current Systems

Say you’re replacing your phone system. You have phones on desks and video equipment in your conference rooms, and your team works in Microsoft 365 or Google Workspace all day. Every one of those limits which platforms will fit.

That doesn’t mean everything has to stay. Replacing old desk phones can be the right call. Just make that call on purpose, before the rollout, instead of finding out halfway through it.

Before the first vendor call, write down the hardware you plan to keep, the systems the new platform has to connect to, and any contracts that run past your switch date. Mark each item “must work” or “can replace if the cost makes sense.” Every vendor now has a list to answer to.

How to Plan for What the Business Will Need in Three Years

If you’re starting from scratch, nothing narrows your options, and the business will live with what you pick for five to seven years. If you’re adding to existing systems, the same question applies to whatever you add.

Max’s test goes like this. Three years from now, a new requirement hits someone’s desk. Either you turn on a feature and add a license, or you replace something the business depends on.

You can’t predict everything. You can plan around what’s already in the business plan, like opening new locations or a big customer asking you to meet a compliance standard. Max’s view is that a lot of this follows patterns by industry. A startup getting ready for an IPO needs different things than a healthcare company does, and at different times.

For each change you can see coming, ask what you would actually have to change if it happened. Take expanding into other countries. A vendor that says it “supports global locations” might mean you add licenses. It might also mean setting up new equipment in every region. Find out which one before you sign.

Write those changes down. That’s your second list.

When to Remove a Vendor From Your Shortlist

Check every vendor against both lists.

If a vendor can’t support something on your “must work” list, remove them.

If they can support it only by replacing equipment or changing another system, keep them, but add the full cost and the switching work to their price. A cheaper platform that needs new phones in every conference room can end up costing more once you add it up.

If they say they’ll support a future need, ask whether it’s available today, available for an extra fee, or still on their roadmap. Count it only if it’s available today.

Questions to Ask Vendors Before You Sign

Every vendor says they integrate and scale. Ask for the details.

Ask which features actually work with Microsoft 365 or Google Workspace, what setup that takes, and what doesn’t work. Get the exact phone and conference room models they support, and what it costs to replace the ones they don’t.

For growth, ask what changes when you double your users or open a new location, and whether that means more licenses or new infrastructure. For compliance, ask which requirements they meet today and what you’d have to buy to meet the ones coming next. For anything you plan to add later, ask whether it exists now, what it costs, and whether turning it on means downtime.

Get every answer in writing.

Before the RFP Goes Out

If an RFP is about to go out or a demo is already booked, and you don’t have both lists, build them first. This is the cheapest point to catch a bad fit.

ITBroker.com does this work from the buyer’s side. We start with what you run and where the business is going, before any vendor gets a say, and we’re paid the same no matter which vendor you choose.

If growth is what’s putting this decision in front of you, this is where to start. It covers what’s at stake when the vendor decisions you make now have to hold up for years.

Max walks through both sides in Playbook: Brownfield vs Greenfield.