TekFocus AI Academy

Experience-led. Founder-led. Not founder-limited.

TekFocus is built around senior delivery. Miguel Wood is the principal architect and engagement leader on every engagement; the firm brings technical, management, and supporting resources into the work as the scope requires. Engagements scale beyond a single architect without losing experience-led delivery. The sections below cover the engagement models the firm offers, how the firm scales when the work requires it, the geographic reach the firm maintains, the cycle that runs between first contact and engagement start, and the work the firm declines.

01 / Engagement Models

Five engagement models cover the work TekFocus is built to deliver. Each is operationally distinct; the right one depends on the situation, the cycle, and the kind of senior judgment the work requires.

  • 01

    Project-based consulting and architecture

    The model most engagements use. A defined project with a clear scope and outcome — an AI Readiness assessment, a cloud architecture review, a data platform modernization, an enterprise AI strategy engagement, or a security and governance review. Typical duration ranges from four weeks (a Data Readiness Sprint) to several months (a multi-phase architecture and migration program). Experience-led throughout; technical, management, and supporting resources brought into the engagement as the scope requires. The deliverables are architecture, defensible recommendations, and the operational path forward — not headcount augmentation.

  • 02

    Long-term advisory retainer

    For organizations that need senior architecture authority on a continuing basis without hiring a full-time enterprise architect. Miguel and the firm operate as the on-demand senior architect, on-demand AI advisor, or on-demand data architect — engaged on a defined monthly cadence, available for vendor evaluations, architecture review boards, technical due diligence, and ongoing technology strategy. Best suited to mid-market organizations scaling toward enterprise complexity, and to enterprise organizations that want senior architecture authority without a full-time hire.

  • 03

    Managed services

    For organizations that need ongoing operational support inside the architectural patterns TekFocus has helped them establish. Managed services engagements include cloud governance support, AI deployment oversight, security and identity administration, and continuing modernization work. Engagements are scoped to the operational footprint and the level of senior architecture authority required. Experience-led, not staff-augmentation.

  • 04

    Executive briefings and workshops

    Focused, short-form engagements for boards, leadership teams, and IT executives. Briefings are 30 minutes for first contact, longer (half-day or full-day) for workshop-format engagements. Topics include the AI Readiness Framework, the AI-as-Intern Model, Commander's Intent for AI workflows, multi-vendor architecture evaluation, and post-mortems on prior AI deployments. The format is direct conversation with the architect — not a slide deck delivered to a passive audience.

  • 05

    TekFocus AI Academy programs

    For individuals, small business owners, and learners who need AI fluency at the right scale. Academy programs deliver the same disciplined, vendor-neutral guidance that Fortune-class clients pay TekFocus for, scaled and translated through webinars, online content, and mentorship. Academy programs are operated under TekFocus AI Academy at tekfocusai.com. Same firm. Different audience. Same frameworks.

02 / How the Firm Scales

Founder-led, not founder-limited.

Miguel is the principal architect and the engagement leader on every TekFocus engagement. The firm is founder-led by design — the architect's name is on the work, and the architecture conversation runs through senior judgment. This is not a model where the firm sells Miguel's name and delivers a junior team; senior involvement is structural, not promotional.

Beyond Miguel, the firm brings technical, management, and supporting resources into engagements as the scope requires. Technical resources execute delivery work alongside the architect — implementation, configuration, integration, hands-on platform work. Management resources coordinate larger engagements — multi-phase programs, multi-team workstreams, cross-organizational governance. Specialist resources bring domain depth where the engagement requires it — security and identity specialists, data platform engineers, specific vendor or platform expertise. The resourcing model is built around the principle that the right people show up for the right work, and that senior architecture authority is not diluted by scaling.

The net effect is that TekFocus engagements scale from focused executive briefings to multi-team enterprise programs without losing experience-led delivery. The firm declines engagements that would require dilution of that model — large headcount-driven engagements where senior architecture is not the work, body-shop staff augmentation that doesn't require architectural judgment, and engagements where the structure would make Miguel's involvement merely nominal. The selectivity is part of the operating model, not an afterthought.

03 / Geographic Reach

Based in North Texas. Delivering across the country and beyond.

TekFocus is based in the Dallas–Fort Worth area, used as an operational hub rather than a service-area constraint. The firm's reach is shaped by the work, not the location.

DFW · TX · USA

DFW as operational hub

The firm's North Texas geography carries three operational advantages: connectivity (DFW is one of the most connected airports in the United States, making onsite travel across the country routine), proximity to the Dallas-area technology corridor (which carries a deep set of enterprise and federal customer relationships from the Infomart era and beyond), and time-zone centrality (central time supports both coasts on the same business day). The firm operates from the DFW area; engagements happen wherever the work is.

National

U.S. delivery

Onsite delivery across the United States is routine. The firm has delivered into federal agencies, Fortune-class enterprises, state IT organizations, healthcare systems, and Ivy League universities — none of which are concentrated in North Texas. The model is the same regardless of geography: senior architecture authority brought to the engagement, technical and management resources brought as the work requires, and the engagement remains experience-led.

Selective

International engagements

International engagements remain possible on a selective basis. The constraint is not capability — Miguel's training-era work and Planet-era engagements included international scope, and the firm's multi-vendor cloud authority crosses jurisdictions cleanly — but selectivity. Federal sector commitments are the primary constraint on international travel. Engagements that involve significant international travel are evaluated case-by-case against current commitments.

04 / The Engagement Cycle

Most engagements follow the same cycle between first contact and start. The path is short, the cycle is direct, and the structure is designed to confirm fit before it consumes either side's time.

Stage 1 — Executive briefing (30 minutes)

The first conversation. Miguel responds personally. The briefing focuses on the situation, the constraints, the timeline, and the kind of senior judgment the work would require. The briefing is the briefing — not a pitch, not a sales call, not a qualification interview. By the end, both sides know whether a fit exists worth pursuing further.

Stage 2 — Fit confirmation

If the briefing surfaces a likely fit, the next step is a deeper conversation — usually one to two hours, often with additional stakeholders on the buyer side. The fit confirmation conversation tests the engagement's scope, the operating constraints, the multi-vendor evaluation expectations, and the practical realities of how the engagement would run. If TekFocus is not the right firm for the engagement, the fit confirmation is where that becomes clear; the firm declines engagements at this stage when the answer is no.

Stage 3 — Discovery and scope definition

For engagements that pass fit confirmation, discovery and scope definition follow. The scope is written down — engagement model, duration, phases, deliverables in operational terms, resourcing, and the boundary conditions that protect the multi-vendor principle. Terminology varies across the industry — some organizations call this stage discovery, others scoping, others both — but the work is the same: defining the engagement with enough specificity to commit to it. Scope is defined before the engagement document is finalized; the firm does not commit to engagements that have not been scoped.

Stage 4 — Statement of work and engagement document

The engagement model, scope, resourcing, and schedule are finalized in a written engagement document — referred to in some organizations as a statement of work (SOW), in others as a master services agreement (MSA) with an attached SOW, and in others simply as an engagement letter. The document, whatever it is called, is the contract. Engagements are quoted to scope.

Stage 5 — Engagement start

The engagement runs against the scope and structure defined above. Miguel is the architect and engagement leader. Technical, management, and supporting resources join the engagement as the scope requires. The AAR habit applies — each phase ends with a brutally honest post-mortem before the next phase begins.

05 / What the Firm Declines

TekFocus is selective by design. Some engagements are not a fit for the firm, and the firm names them rather than discovering the mismatch in delivery.

  • Vendor-funded engagements with predetermined recommendations. Engagements where the architecture conversation is shaped around what the funder can sell more of, rather than what the customer should buy. The multi-vendor principle is non-negotiable in the literal sense.
  • Headcount-driven engagements where senior architecture is not the work. Body-shop staff augmentation, large-scale junior implementation contracts, and engagements where Miguel's involvement would be nominal rather than structural. The firm declines work that would dilute experience-led delivery.
  • Engagements that demand certainty the firm cannot honestly provide. Engagements where the contract requires guaranteed business outcomes from AI, fixed commitments before the Data Estate is real, or assurances about a deployment whose foundations have not been assessed. The honest answer is sometimes "we don't recommend going live yet" — and the firm will give that answer.
  • Engagements that conflict with active commitments. Federal sector engagements that conflict with active commitments, international engagements that displace federal scheduling without good reason, and engagements where the firm cannot give the work the senior attention it requires.
  • Engagements requiring violation of the multi-vendor principle. Engagements that ask the firm to position a single vendor as the default before the workload is understood, or to recommend against a customer outcome because it conflicts with a vendor relationship.

Declining the wrong engagement protects the right ones.