What is a technology partner?

Someone who owns whether the technology in your business works, rather than whether a particular deliverable was shipped. The practical difference is where they are twelve months later. A vendor hands over a thing and moves to the next client. A partner is on the call when the thing breaks, when the next decision comes up, and when you need to know whether a vendor is lying to you.

How do I find a technology partner for a small business?

Start with a question you actually have, not a search for a partner. Hire for that one question on a fixed, small scope, and watch how they work: who does it, what they tell you not to do, what happens when something goes wrong. A partner reveals themselves in a small engagement. Nobody reveals themselves in a pitch.

What is the difference between a technology partner and an IT consultant?

An IT consultant answers the question you brought. A partner also tells you which questions you should have brought instead. In practice the test is whether they ever decline work. A consultant who has never told you not to buy something is a vendor, whatever the business card says.

Should a small business hire an agency or an individual?

The honest answer depends on whether the work is continuous. An agency with a bench is the right call when you need many hands at once. An individual with a studio behind them is the right call when you need judgment on decisions that are expensive to reverse, because a bench has to stay billed and a person can afford to say no. Most small businesses need the second thing far more often than the first.

What should the first engagement with a technology partner look like?

Small enough that walking away costs you nothing, and real enough that you see how they actually work. A paid assessment, an architecture review, a scoped roadmap. Not a retainer signed on a call, and not a large build on the strength of a proposal. Anyone worth partnering with will prefer this too, because it protects them from a bad client as much as it protects you from a bad consultant.

Choosing a Technology Partner for a Small Business: The Six Questions That Separate One From a Vendor

Everybody who sells to a small business calls themselves a partner now. The word has stopped meaning anything, which is a shame, because the thing it used to mean is exactly what most small businesses need and almost never get.

So here is a working definition, six questions that test for it, and the structural reason most of the people using the word cannot pass them.

The definition

A vendor is paid for a deliverable. A partner is paid for an outcome and is still there when the outcome is measured.

That second clause is the whole test. Anyone can be accountable in the proposal. The question is who is on the call fourteen months later when the integration stops syncing, the vendor raises prices, or a new decision arrives that nobody scoped for.

The six questions

None of these is a trick question. The answers are just unusually hard to fake.

Who, specifically, does the work? A name is the only acceptable answer. "A team will be assigned" means the person pitching you will not be the person building, and the person building will not be the person on the call in a year.

What happens when it breaks at 9pm? Not whether it will break. It will. The question is whether the answer involves a person you can reach, or a queue.

Who owns the code, the infrastructure and the accounts? You should, in your repository and under your billing, with the ability to leave. "We manage all of that for you" is a lock-in described as a convenience.

How do you get paid? Per deliverable means they are paid when the thing ships, whether or not it works. Per hour, open ended, means they are paid for your indecision. Fixed scope with a named outcome, credited forward, means their interests and yours point the same way.

What would you tell me not to buy? This is the one that separates them. Somebody who has never declined work from you is a vendor. A partner has a list of things you asked for that they talked you out of.

What did you personally ship in the last year? Not the firm. Them. Advice from someone who has not built anything in years drifts away from what is actually buildable, and it drifts in the direction of whatever is easiest to sell.

Why most agencies cannot pass this, however hard they try

It is not a character flaw. It is a structural one.

An agency has a bench, and a bench has to stay billed. That one fact decides everything downstream. A bench cannot tell you not to buy something, because the alternative is idle people. A bench cannot promise you a name, because the name will be reassigned the moment a bigger client calls. A bench cannot be on the call in fourteen months, because the person who built your thing left for a competitor in month eight.

A single accountable person, with a studio behind them for the months that need hands, has the opposite incentive. They can say no. They can be the same name on every call. They are the one whose reputation is on the line when it breaks, which is the only form of accountability that survives contact with a bad week.

How to actually start

Do not go looking for a partner. Go looking for an answer to a question you already have, and hire for that on a scope small enough to walk away from.

A paid assessment. An architecture review. A scoped roadmap. Two to six weeks, a fixed fee, a thing you hold at the end. In that time you will learn everything the six questions were trying to find out, from watching rather than asking.

Anyone worth partnering with will prefer this too. It protects them from a bad client exactly as much as it protects you from a bad consultant, and that symmetry is the first sign you have found one.