Vendor or partner: how to choose who builds your software

You are looking for someone to build your software. You get quotes, you take calls, and everyone says roughly the same thing: attentive, tailored, outcome-driven. The words are identical from one vendor to the next. Yet behind those words, two opposite postures coexist, and they will produce radically different results on your project.

The first posture is that of the mere executor. They take your spec, price it, build it. The wider the scope, the bigger the invoice, and that suits them. The second is that of the partner. Their interest is not your scope, it is your outcome. They will remove lines, challenge your assumptions, get you to ship faster and cheaper than you imagined. The problem: both show up with the same vocabulary.

This article gives you a buyer's method to tell the two apart before signing. Not impressions, concrete questions whose answers do not lie. Because this choice weighs more on your project than any technical decision you will make afterward.

“Do not ask a vendor if they are outcome-driven. Watch whether their interest grows with your invoice or with your success.”

To understand how someone will behave, do not look at what they say, look at what pays them. A fixed-price vendor billing the scope has a simple short-term interest: for the scope to be as wide as possible. They will not do it out of dishonesty, they will do it because their incentive structure pushes them that way. They will execute your spec as is, including the lines that serve no purpose, because those are billed like the rest.

A partner works the other way. They know a successful project means a customer who comes back and refers others. Their long-term interest is your outcome, not your scope. So they do the opposite of the executor: they remove, they postpone, they focus. They get you to ship a useful first batch as fast as possible, even if it shrinks their immediate invoice.

That figure is your best test. Most of what gets built is almost never used. An executor will build those 64% without blinking, since they are in the spec and they are paid for. A partner will spot them and offer to cut them. Faced with the same document, one bills the waste, the other protects you from it.

This sorting between what produces proof and what produces comfort is exactly the discipline we detail in MVP vs V1: scope the right first version. A good partner applies it naturally to your project.

The pitch can be rehearsed, concrete answers cannot. Here are seven questions to ask in a meeting. Taken alone, they can mislead. Together, they draw a clear posture. Watch the direction more than the words: are they trying to add to you or to protect you?

A vague answer on scope, or enthusiasm to build everything without ever questioning anything, are signals. A partner has concrete examples of features they got dropped. An executor does not, because dropping a feature means shrinking their own invoice, and they have no reason to do it.

A vendor's posture shows in how they react at a few key moments of the project. Here are the same situations, seen from both sides. If you consistently recognize the left column, you are dealing with an executor, whatever their sales pitch.

This partner posture is not only a matter of individual goodwill. It flows from a model. Some structures are built to bill volume of hours or code, others to deliver an outcome to a small number of clients. The model determines the incentive, and the incentive determines the behavior, far more reliably than any sales promise.

This is the whole difference between an agency that optimizes for volume and a studio that optimizes for outcome, which we dug into in product studio vs traditional agency.

“Choose a model whose interest is aligned with yours. You will not have to hope for goodwill, it will be structural.”

Every vendor promises to be outcome-driven. You cannot verify a promise, but you can read an incentive. The one whose interest grows with your invoice does not have the same reflexes as the one whose interest grows with your success, however carefully they both say the same thing.

So do not look for the vendor who talks best. Look for the one who offers to do less, who has examples of dropped features, and whose model is aligned with your outcome. This choice may cost you a smaller initial invoice. It will earn you a product that works.

“The right partner is not the one who accepts everything you ask for. It is the one who refuses what does not serve you.”

To go further: having your first business software built and scoping your first batch with MVP vs V1.