Skip to content
Abstract architectural section: layered mineral-blue and pale steel strata align against an ink-navy field, standing for multiple technical disciplines brought into one operating picture.

Fractional IT consulting

Enterprise IT engineering, delivered using multiple disciplines.

L&A Technical Advisory serves mid-market and enterprise organizations with twenty-five years of enterprise engineering in banking, federal, logistics, retail, healthcare and SaaS — delivered inside those organizations rather than advised on from outside them. The principal who scopes an engagement is the one who performs it.

Who the work is for

Three roles, usually in the same room.

At 800 users or at 30,000, the same small group carries the decision, and rarely with a dedicated function behind any one of them. An engagement has to satisfy all three concurrently.

  • IT and infrastructure leaders

    An estate that has grown incrementally through acquisition, turnover and deferred upgrades, operated by a team with no spare capacity. The requirement is senior engineering capability on the difficult work without adding a permanent position.

  • Security and identity leads

    An access model designed for a perimeter that no longer exists, now receiving requests from AI systems and third parties acting on behalf of users. The requirement is identity re-established as the control plane, sequenced so that operations continue throughout.

  • Executives without a CIO

    Technology decisions arriving at an executive who was not hired to make them, with the next one carrying material cost. The requirement is independent senior judgment on sequencing, cost and risk before a vendor narrows the available options.

What the practice covers

Six competencies, one practitioner.

Each competency stands alone and organizations engage them separately. They are not practiced apart: an identity problem presents at the service desk, an AI rollout stalls on a directory of uncertain accuracy, an audit finding resolves to an infrastructure decision taken years earlier.

CloudVendor modelsSaaS dataCloud appsLocal modelsFile systemsLOB systemsIdentity control planeDirectory · Conditional access · AuditOn-premises

How an engagement runs

Four phases, and a defined end to each one.

No open-ended retainer. Each phase produces a written output the client team owns and can act on independently, and closes at a decision gate where the engagement can stop.

PHASE 1 · 1–2 WEEKSDiscoverStakeholder interviewsCurrent AI and identity inventoryData sensitivity mapDELIVERABLEFindings briefPHASE 2 · 2–3 WEEKSAssessReadiness scorecardGovernance and policy gapsCloud vs. local model fitDELIVERABLEReadiness reportPHASE 3 · 3–4 WEEKSDesignHybrid reference architectureIdentity-centric access modelPilot selection and success metricsDELIVERABLEArchitecture and roadmapPHASE 4 · ONGOINGEnablePilot delivery with the client teamPolicy, training, and metering in placeQuarterly advisory check-insDELIVERABLEWorking pilot and playbookgo / no-gogo / no-gogo / no-goFixed fee for phases 1–3. Deliverables areclient-owned; the engagement can end at any gate.Typical time to a working, governed pilot: 8–10 weeks fromkickoff.
Durations are typical rather than contractual; the sequence is not.

Selected work

Identity was the smallest change on the list, and the one that unblocked everything else.

A publicly traded software company replaced its enterprise AI platform on a compressed timeline. The new platform went live inside the existing identity model rather than beside it: no second access model, no unowned accounts, and no retrofit project after go-live.
Read the case study

Start with an assessment, not a tool selection.

Where AI is the question in front of the organization, the AI Readiness Assessment is the appropriate starting point: a documented account of the environment, the gaps and the sequencing, independent of any vendor. Where the question falls under one of the other five competencies, an equivalent assessment can be scoped.