Engineering time vs a build vs a product.

Most technical work is bought in one of three shapes, and picking the wrong one is expensive. You can buy a consultancy’s engineering time, an agency’s build, or a product. They look similar from a distance — someone technical, helping you with a system — but they are different transactions, with different economics and different things left in your hands at the end. Here is how to tell them apart, and how to know which you actually need.

What you are actually buying

With engineering time, you are buying senior judgement and hours to solve a defined problem. The engineer works on the systems you already run — configuring, integrating, commissioning, designing — and you own what is produced. Price follows the work: a day rate, time-and-materials, a retainer, or a fixed-scope package tied to a written statement of work. This is what 1722 sells.

With a build, you are buying a finished thing delivered to a brief: a website, an app, a system, scoped and shipped and handed over. The deliverable is the build. Agencies are good at this, and the commercial model reflects it — usually a fixed price for a defined build.

With a product, you are buying software or hardware that already exists, at a fixed or subscription price, and configuring it yourself. It is fast to adopt and cheap to start, because the engineering was done once, for everyone. What you cannot do is bend it much beyond what the vendor built.

When you need engineering time

Reach for a consultancy’s time when the problem lives inside systems you already own and no off-the-shelf answer fits it. The picks are slow on a WMS you have already paid for. A circuit needs designing that no catalogue part covers. An infrastructure estate needs an independent resilience design before the board will fund it. In each case the value is the judgement applied to your specific situation — not a product, and not a generic build. You are buying a brain and a pair of hands, and you keep the output.

It is also the right shape when independence matters. A firm that sells only its time, and takes no vendor commission, has nothing to steer you toward. The recommendation follows your problem.

When a build is right

If what you need is a new, self-contained thing — a marketing site, a customer app, an internal tool — built to a brief and handed over, that is a build. It is a different job from engineering the systems you already run, and it is usually better bought from a firm that does builds all day. 1722 does not do ground-up builds; when that is what a conversation turns out to need, we say so.

When a product is right

If your need is common enough that someone has already productised it, buy the product. You will get it faster and cheaper than any bespoke route, and the vendor carries the maintenance. The trade is fit: a product does what it does. When you find yourself paying to bend a product into a shape it resists, that is the signal you have outgrown it — and that bespoke engineering may now be cheaper than the workarounds.

How to tell which you need

Three quick tests:

• Whose systems is the work on? Yours, today → engineering time. A self-contained product built to a brief → a build. Someone else’s platform → a product.
• What do you keep at the end? Judgement, designs and documentation you own → engineering time. A delivered build → an agency. A licence → a product.
• How is it priced? For time and expertise → a consultancy. A fixed price for a defined build → an agency. A fixed monthly fee → a product.

None is better than the others; they solve different problems. The mistake is buying a product for a bespoke problem, or a consultancy’s time for something a product already does. If you are not sure which your problem is, that is a good thing to work out on a short call — sometimes the honest answer is that you need one of the other two, and it is cheaper to hear that early.