Vendor evaluation · billed hourly

You don't know what you don't know. Especially across the table from a software vendor.

Vendors know their product better than you ever will, and the demo is built to show its best side. Before you sign, renew, or expand, I go through the proposal and the demo with you, find the questions nobody has asked yet, and put them in plain language. Then I check that you're solving your actual problem the simplest way available. Sometimes that's the vendor. Sometimes it's a setting in a tool you already pay for.

Hourly, with the hours estimated on the call before you commit

Four questions behind every good software decision.

Features are the easy part to compare. These are the parts that decide whether you're happy a year later.

?
Does it solve the problem you actually have?

I map the problem first, then the product. Most mismatches are visible before the demo ends, if you know where to look.

⚙
What happens when something changes?

A file format shifts, a rule changes, a person leaves. Does the product stop and tell you, or quietly produce a wrong answer? Who fixes it, and how fast?

$
Are the numbers honest?

The savings in a proposal are usually the vendor's own estimate. I check them against how your team actually works today, so you know what you're paying for.

⇄
What are you locked into?

Who owns your data and the logic built on it, how you get both out, what leaving costs, and whose AI model sits inside the product.

The questions that usually go unasked.

Every review ends with questions written for your vendor and your decision. These are the ones I start from, because they apply to almost any software and a sales process rarely raises them on its own.

  • The demo "Which parts of what we just saw are the live product, and which were set up for this demo?"
  • Change "When your product updates, how do we find out what changed before it affects our work?"
  • Support "Who owns our account after we sign, and how long does a fix take when something breaks?"
  • Leaving "If we cancel, what do we get back, in what format, and how fast?"
  • Pricing "What makes the price go up at renewal?"
  • AI "Which AI model is inside, from which provider, and what does it decide on its own?"
Not gotchas. Most of these have good answers. If the vendor gives them, your confidence should go up. If they can't, you've learned that before signing instead of after.

A free call, a review, then questions you can use.

01

Free 30-minute call

What you're evaluating, what's at stake, and when you need to decide. I'll tell you whether I can help and estimate the hours before you commit to anything.

02

I review

The proposal, the demo or recordings, the contract terms, and how you work today. If it helps, I'll sit in on a vendor call and listen.

03

You get the questions and my read

Written questions ranked by importance, what a good and a bad answer sound like, and my recommendation: buy, negotiate, wait, or solve it another way.

What people ask before booking

What kinds of software?

Anything that runs part of your operations: CRMs, scheduling and booking systems, automation and AI tools, finance and back-office platforms, and industry-specific software. The questions change by category. The habit of asking them doesn't.

Are you going to try to sell me a build instead?

No. If the vendor is the right answer, I'll say so. If building something yourself would be cheaper, I'll show you the math, and you're free to hire anyone to do it, or nobody.

We already signed. Is it too late?

Not at all. Renewals and expansions are often the better moment to ask, because you have real usage to point to and the vendor wants to keep you.

Evaluating a vendor right now?

Book a free 30-minute call. No pitch.

Tell me what you're looking at and when you need to decide. I'll tell you whether I can help and roughly how many hours it would take.

Book a free 30-minute call