How to Evaluate an Implementation Partner

Implementation help is genuinely hard to buy. No two proposals are shaped alike, references are curated by definition, and every deck in the category says partner, proven, and end-to-end. The certifications tell you a firm passed a vendor’s exam, not whether its work survives contact with your quarter. What actually sorts the field isn’t better instincts — it’s a handful of questions that force the delivery model out into the open, where you can look at it.

Six of them follow. They aren’t trick questions, and they don’t test the people — capable firms exist under every model, and a good one will answer all six without flinching. What the questions test is the structure the people work inside: who gets paid when, who finds out when something breaks, and what has to be true for the engagement to end. Bring them to every scoping call you take. Including ours.

1 · “Show me a system you built that’s still running.”

Not a case study — a system. Slides describe the week the project shipped; a live walkthrough shows what survived the two years since. A firm that can share one, with its customer’s permission, or walk you through the stack it runs its own business on, is showing you the only evidence that can’t be written after the fact: work that outlived the invoice.

A strong answer names something specific and shows it working. And when a firm is young and honest enough to say “our own stack is the production system — here’s the wiring,” that candour is worth more than a borrowed logo wall. What you’re listening for isn’t age. It’s whether anything the firm builds is still alive somewhere it can be seen.

2 · “When a step fails at two in the morning, how do I find out?”

Every integration and automation fails eventually — the question was never whether, but who finds out, and when. The expensive version of failure is silent: a connector pauses, a sync half-completes, and the discovery happens weeks later in a report that doesn’t reconcile. Whether you get the cheap version or the expensive one is decided at build time, by whether anyone designed the failure path at all.

A strong answer has three parts, and they’re concrete: failures retry automatically; what still can’t complete is logged somewhere with an owner; and that owner is a name, not a dashboard nobody opens. If the answer to this question is a monitoring product rather than a person, ask the question again.

3 · “Which specific tools have you integrated — and how?”

“We integrate with everything” is a sales answer. An engineering answer names pairs and methods: which prospecting tool into which CRM, native connector or middleware or direct webhook, and why that method for that pair — including, from a candid firm, where a native connector was honestly good enough and they used it.

The answer tells you where the firm’s depth actually lives, which matters because integration expertise doesn’t generalize as smoothly as the decks imply: fluency with one ecosystem’s APIs, quirks, and rate limits is real, earned, and specific. You are not hiring the category’s average competence. You’re hiring their particular scar tissue, so find out where it is.

4 · “How do you scope and price — and when do I see the plan?”

Fixed price, time-and-materials, retainer — each has honest uses, and this question isn’t a purity test. What the pricing model does tell you is the incentive structure you’re about to live inside: what the firm earns more of when scope grows, and what it earns when the project ends. You should know that before signature, from the firm’s own mouth, stated as plainly as the price itself.

The second half of the question is the sharper edge: when do you see the week-by-week plan — before the contract, or billed into existence after it? A plan you can read before signing, with named deliverables per week, is the only proof of prior repetition a buyer can inspect for free. Whatever the pricing model, a firm that has done this many times can show you the shape of the work in advance. Ask to see it.

5 · “What does handoff look like?”

An engagement designed to end looks different from one designed to renew, and the difference is visible in the last week’s deliverables. Ask what, exactly, you hold when it’s over: documentation a new admin could operate from, credentials in your accounts rather than the vendor’s, acceptance criteria that were written down before the work started — and a date after which you aren’t paying anyone.

Ongoing support isn’t a red flag; plenty of teams genuinely want a partner on call, and firms that provide it well provide real value. The tell is whether ending is an option. If every path through the proposal terminates in a retainer, the handoff was never designed — dependence was.

6 · “Who actually does the work — and is any of it subcontracted?”

You are hiring hands, not a logo, so it’s fair to ask whose hands: who touches your CRM and its data, who builds the integrations, and whether any of it is delivered by people outside the firm. Subcontracting itself is not the problem — plenty of excellent delivery runs on disclosed partnerships, and a firm that names its partners and what they own is showing you how it actually works. Undisclosed subcontracting is the problem, because everything else you evaluated — the answers to the five questions above — may describe people who won’t be on your project.

A strong answer is a straight one: here’s who does what, here’s who sees your data, and here’s how we stand behind work we didn’t personally type. Disclosed before signature, not discovered after.

Run them on us

These questions work on any firm in the category, and they’re meant to — a capable partner under any model will answer them plainly, and the conversation will be better for it. Run them on us too: question four is answered on every build page on this site, and the other five belong in the scoping call. A firm that answers all six without flinching is probably a good place to put your quarter. Whoever it is.