TekFocus AI Academy

About · The Multi-Vendor Principle

Match the mission to the tool. Not the tool to the relationship.

TekFocus is multi-vendor by deliberate choice. Microsoft depth, AWS and Google Cloud fluency, Anthropic, OpenAI, and xAI Grok literacy, and a documented refusal to let vendor preference dictate architecture. The principle is not a slogan. It is a working commitment, anchored in a specific career decision the firm's founder made, and translated into a method that governs how every engagement gets staffed, evaluated, and recommended. The sections below explain where the principle came from, how it operates in practice, and what the firm declines because of it.

01 / The Story

Why the principle is anchored in a specific decision.

Miguel Wood spent fourteen years as a Director and Chief Enterprise Solutions Architect inside one of the country's most established Microsoft and federal consulting partners. The work spanned the entire Microsoft platform shift of the 2010s, the maturation of AWS and Google Cloud across the same period, and the early arc of generative AI. Multi-vendor fluency was built deliberately over those years — not as a marketing position, but because customers needed honest comparisons across stacks, and because the right tool for a given mission was rarely the same vendor twice in a row.

Late in that tenure, the expectation in the role began shifting. The pressure moved toward favoring a single vendor as the default recommendation, regardless of fit, and toward shaping the architecture conversation around what the firm could sell more of rather than what the customer should buy. The decision was weighed carefully. The role was senior, the compensation was real, and walking away meant rebuilding the firm Miguel had founded in 2002 from a quieter posture back into a full-time practice.

He left. Not loudly. Not as a grievance. As a professional choice anchored in the operating principle that had been the foundation of his work for two decades — that the recommendation has to follow the mission, not the vendor. The departure is now the founding act of the current TekFocus era. The principle was already real; the departure made it non-negotiable.

The vendor-loyalty departure is what every page on this site stands on top of.

02 / The Principle in Practice

Multi-vendor is a working method. Four practices govern how TekFocus operates inside the principle.

01

Workload first

Every architecture recommendation begins with the workload — what is the work, what are the constraints, what does success require — and only then evaluates which vendor's stack fits best. The landscape evaluated includes Microsoft Azure (including Azure OpenAI), AWS (including Bedrock), Google Cloud (including Vertex AI and Gemini), Anthropic, OpenAI, xAI Grok, Snowflake, Databricks, Microsoft Fabric, and the broader enterprise platform set. When Microsoft is the right answer, TekFocus recommends Microsoft and explains why. When something else is the right answer, TekFocus recommends something else and explains why. Sometimes the honest evaluation arrives at a single-vendor architecture. The discipline is in the order, not in the count.

02

Vendors evaluated by fit

The multi-vendor commitment requires real fluency, not a list of vendor logos. Miguel holds 35+ Microsoft certifications dating to 2000 (some of which are now retired), including both the Microsoft Certified Master (MCM) and the Microsoft Certified Solutions Master (MCSM) — among the most demanding certifications Microsoft ever offered, both retired. Alongside the Microsoft depth: AWS, Google Cloud, Anthropic, CompTIA, and Cisco certifications, with OpenAI credentials in pursuit as they are released. The fluency is operational rather than theoretical — architectures have been built that pulled the right tool from each vendor's stack rather than forcing one tribe to win. Keeping that fluency current over years is itself the practice; it does not happen by accident.

03

Refusals as practice

TekFocus declines certain engagements because of the principle. Vendor-funded engagements with predetermined recommendations. Engagements that ask the firm to position a single vendor as the answer before the workload is understood. Engagements that would require the firm to recommend against a customer outcome because it conflicts with a vendor relationship. The refusals are operational, not theatrical — the firm has turned down work that would have been financially significant because the work would have required positioning otherwise. The principle is a working constraint, not a slogan; it shapes which engagements the firm pursues, and which it walks away from.

04

Documentation discipline

Every recommendation is defended in writing. The reasoning is captured, the alternatives are named, the constraints are recorded, and the tradeoffs are surfaced — not buried. The recommendation can be reviewed by the client's team, challenged on its merits, and revisited as the workload evolves. The discipline serves two purposes: it forces the firm's reasoning into the open, and it gives the client an artifact that survives the engagement. A recommendation that cannot be defended in writing is not a recommendation the firm is willing to make.

03 / What the Principle Means for Buyers

The principle has been described above in operational terms. What it means for the buyer at the table can be said more directly.

For the CIO under board pressure to "do something with AI."

You get an architect who will tell you whether Microsoft Copilot, Anthropic Claude, AWS Bedrock, OpenAI, xAI Grok, an open-source model, or none of the above is the right answer for your situation. The recommendation will come with a written defense and named alternatives. If the honest answer is "not yet," you will get that too.

For the federal or SLG IT leader navigating compliance constraints.

You get an architect with cleared federal delivery experience who has delivered into the Department of War, the Department of Energy, and the Department of the Interior, and who will evaluate vendor stacks against the operational reality of compliance-heavy environments — not against the vendor relationship of the consulting firm.

For the buyer who has been burned by vendor-flavored consulting before.

You get a firm that has turned down engagements that would have required positioning otherwise. Multi-vendor is not a marketing line; it is what TekFocus refuses to compromise on. The asymmetry is the point.

04 / What the Principle Does Not Mean

The principle is precise. A few common misreadings are worth addressing directly.

Misreading 1 — "Multi-vendor means TekFocus has no Microsoft depth."

The Microsoft depth is real and named. Miguel holds 35+ Microsoft certifications (some of which are now retired), including both the Microsoft Certified Master (MCM) and Microsoft Certified Solutions Master (MCSM), and is a Microsoft Press published author. TekFocus was a Microsoft Gold Certified Partner for Learning Solutions in its Infomart era, and Microsoft itself routinely used TekFocus facilities and instructors. The depth is part of why the firm can credibly evaluate Microsoft against alternatives — pretending the depth doesn't exist would itself be dishonest. The principle binds the firm to evaluating Microsoft alongside the alternatives, not to ignoring Microsoft.

Misreading 2 — "Multi-vendor means always recommending more than one vendor."

Sometimes one vendor is the right answer for the entire workload. When that is the honest conclusion, the recommendation reflects it. The discipline is in the evaluation process, not in artificial balance. A Microsoft-only architecture, an AWS-only data platform, or a single-vendor AI stack is fully consistent with the principle — provided the recommendation followed an honest evaluation rather than a predetermined preference. What the firm refuses is to arrive at the single-vendor answer before doing the evaluation.

Misreading 3 — "Multi-vendor is just a marketing position."

The principle has a cost. TekFocus has declined engagements because of it. The cost is operational, not rhetorical — vendor-funded engagements with predetermined recommendations are common in the industry, and refusing them means foregoing revenue the firm could otherwise have taken. The principle is non-negotiable in the literal sense: it has been negotiated, and the answer has been no. Marketing positions do not have costs. Commitments do.