Seven technology and service partners brought into the practice across two years, each for a capability the team either did not have or could not scale to.
The decision underneath every one of them is the same and is worth stating plainly: whether to say no, hire for it, or partner for it. A services practice under pressure has a fourth option, which is to take the work and improvise, and that is the one that ends up in a design review as a problem nobody can fix. Partnering is the honest version of admitting a gap while still answering the client.
Alongside it, a formal manufacturer specialization track and enablement across four vendor stacks — Cisco, Fortinet, Palo Alto Networks and Juniper. Certifications in a services business are not decoration: they set what the company is permitted to sell and support, they price the work, and for the engineers they are the visible part of a development path. Running them as a track with named targets rather than as something people get around to is the difference between a practice that deepens and one that merely stays busy.
Both halves serve the same end as the design review gate: the client should not be able to tell which architect drew their design, or which company employed the person who installed it.
Outcome
Capability added without pretending to have it, and certification depth built deliberately rather than accumulated.