Photo: Google Gemini · AI-generated
An IT consultancy sells judgment. Which system to replace, what to integrate, what the architecture should be, what it will cost.
Then someone has to build it.
Often that someone is not the consultancy. They win on advice and domain knowledge, and they bring in a partner to deliver — which works well and is more common than the market admits. It also has a shape that is different from agency work or ISV work, and worth naming.
You arrive after the decisions
An agency usually brings a partner in with a brief. A consultancy brings one in with a commitment.
By the time we are in the room, the client has already been told what is being built, roughly what it costs, and when it lands. The architecture may already be in a slide deck with the consultancy’s logo on it.
That changes the job. You are not choosing an approach; you are delivering one, inside constraints someone else set, against a promise someone else made. The useful questions on day one are not “what should this be” but “what exactly was promised, to whom, and which parts of it are load-bearing”.
Their name is on it
The consultancy’s credibility was earned on advice. If the build goes badly, the damage lands on the advice — the client does not conclude that the builder was weak, they conclude that the recommendation was wrong.
That asymmetry is the whole reason to take invisibility seriously, and invisibility is more literal than people expect. It means their brand in the delivery, their process, their reporting rhythm. It means the client’s questions get answered by them, in their voice, on their relationship. It means not appearing in places nobody thinks about until they do — a commit signature, a document footer, an automated email from a build server.
We built and maintain a tool bridging Lexware and Deutsche Telekom’s D!VE procurement platform for an IT service partner of Telekom — converting order and quotation data into the exact XML Telekom’s interface accepts. The partner owned the Telekom relationship throughout. Our job was to make sure the thing they had promised kept working, not to be visible while doing it.
When you think the architecture is wrong
This is the part that separates a good delivery partner from a compliant one, and most write-ups skip it.
Sometimes the design you inherit is wrong. Not stylistically — actually wrong, in a way that will surface in month five.
Saying nothing is the coward’s option and it fails everyone. Saying it in front of the client is worse: it undermines the consultancy in the one relationship they cannot afford to lose, and it makes you look like you are angling for the advisory seat.
The workable version is narrow. Raise it early, privately, to the consultancy. Bring a costed alternative rather than an objection. Be explicit about what happens if nothing changes, in time and money rather than in adjectives. Then accept their call — they own the client commitment, and they may have context you do not, including commercial context nobody wrote down.
A partner who cannot do this is a liability in a different way from one who cannot code.
The promise has a tail
Consultancy commitments rarely end at go-live, because the systems they connect to keep moving.
That Telekom bridge is a small tool with a long obligation: the D!VE format kept evolving, and the tool had to keep pace or the partner simply could not submit quotations. The build was finite. The commitment was not.
Any delivery partner sitting behind a consultancy inherits that tail. It belongs in the arrangement explicitly — who watches for the change, who pays for keeping up, how fast a break gets fixed — rather than being discovered the first time an external format shifts.
What a consultancy should ask
If you are choosing someone to build behind your name, the technical questions are the easy half. These are the others:
Will you work under our brand, in our process, including in artifacts nobody looks at? What do you do when you disagree with our architecture — and who do you say it to? Who maintains this after launch when the third party changes their format? Can we put you in front of the client if we choose to, and will you stay in role if we do?
That last one matters more than it sounds. White-label delivery is not about hiding; it is about the relationship staying where it belongs.
If you are a consultancy carrying a build you would rather not staff internally, we should talk.