# ITECS AI — Dallas agency that builds, governs and operates custom AI agents for 50-300 employee firms.

> Source: The Agents Index — https://theagentsindex.com/itecs-ai (structured, researched, re-verified)
> Facts last verified: 2026-10-13

ITECS AI is the AI practice of a Dallas managed IT and cybersecurity firm, building custom enterprise and desktop agents wired into client systems. Engagements run from readiness assessment and governance to production builds and ongoing agent operations.

| Fact | Value |
| --- | --- |
| Website | https://itecs.ai |
| Price | from $650/session |
| Free tier | No |

No free or trial use of a product. The only no-cost step is the intake/assessment form that scopes a paid engagement; the cheapest paid item is the $650 Guided Build Session.

## What it does

**Writes code** · Partly — ITECS delivers custom software through an AI-assisted build that a senior architect supervises, so code is authored by the agency rather than by a tool the buyer drives.

> Custom software delivered through the ITECS AI-DevOps model, with a senior architect supervising an AI-assisted build.
> — https://itecs.ai/pricing · Specialize / Custom Build section, AI-Augmented Custom Software Development card

**Writes tests** · Partly — Automated tests and regression checks are set up as part of the release pipeline ITECS builds, but nothing says an agent authors test suites for client code.

> We set up version control, CI/CD, secrets management, staging validation, automated tests, deployment approvals, retrieval health checks, and rollback paths so changes ship predictably.
> — https://itecs.ai/ai-devops · How AI DevOps moves your AI system from demo to production, step 2

**Whole-codebase work** · Partly — Agents can be connected to codebases among other systems, but carrying a migration across a whole repository is never claimed on any page read.

> Secure connections to CRMs, helpdesks, file stores, databases, codebases, and APIs
> — https://itecs.ai/custom-ai-agents · Custom AI Agent Capabilities list, third bullet

**Ships it** · Yes — ITECS builds and operates the deployment path itself: production pipelines, approval gates, controlled rollout and documented rollback for AI apps and agents.

> Production deployment pipelines for AI apps, agents, and automations
> — https://itecs.ai/ai-devops · AI DevOps Capabilities list, first bullet

**Done-for-you service** · Yes — This is a services business: ITECS engineers design, build, deploy, train staff on and then operate the agents for the client.

> ITECS builds custom AI agents that connect securely to your proprietary data, tools, folders, codebases, and business systems - with human-in-the-loop controls, audit trails, and production support.
> — https://itecs.ai/custom-ai-agents · Hero paragraph under 'Custom AI Agents for Your Dallas Business'

## How much it does unattended

**Runs autonomously** · Partly — Agents run multi-step work on their own but consequential actions are deliberately blocked behind an approval queue, so full unattended completion is designed out.

> Sensitive actions wait in an approval queue with the draft, the sources, and the proposed change. Staff approve, edit, or reject. Nothing is sent, changed, or executed until they do.
> — https://itecs.ai/custom-ai-agents · Anatomy of an Agent Run, step 5 'A person approves the action'

**Multi-agent** · Yes — Orchestrated multi-agent systems are a published build phase with their own price band, alongside end-to-end process redesign.

> An orchestrated multi-agent system or end-to-end redesign of a major workflow with integrations, monitoring, and rollout enablement.
> — https://itecs.ai/pricing · Specialize / Custom Build, Multi-Agent System card

**Agent permissions** · Partly — Permission scope is designed per build: agents call only approved tools, and out-of-policy or low-confidence steps are routed to a person instead of acted on.

> Permissions, data boundaries, confidence thresholds, and DLP rules are checked before the agent acts. Out-of-policy or low-confidence steps route to a person instead of guessing.
> — https://itecs.ai/custom-ai-agents · Anatomy of an Agent Run, step 4 'Guardrails check the plan'

## Which models it runs on

**Claude** · Yes — Claude is named as a build target for both enterprise agents and desktop personal agents, with a dedicated Claude Cowork rollout service.

> Claude, ChatGPT, Gemini, Copilot, Codex, CLI, and open-source agent workflows
> — https://itecs.ai/custom-ai-agents · Custom AI Agent Capabilities list, first bullet

**GPT** · Yes — ChatGPT, Codex, the OpenAI API and Azure OpenAI all appear as platforms ITECS builds workflows on when they fit the use case.

> We build custom workflows for AI applications, APIs, CLIs, project folders, and agent frameworks, including Claude, Codex, ChatGPT, Gemini, Microsoft Copilot, Azure OpenAI, and other business AI platforms when they fit the use case.
> — https://itecs.ai/custom-ai-agents · Custom AI Agents FAQ, 'Can you build workflows for Claude, Codex, ChatGPT, Gemini, and other AI tools?'

**Open models** · Partly — Open-source models and open-source agent workflows are listed in scope, but no specific open-weight model or hosting arrangement is named anywhere read.

> Vendor-neutral architecture - we build with the right mix of ChatGPT, Claude, Gemini, Copilot, Codex, APIs, open-source models, and business platforms for your use case
> — https://itecs.ai/custom-ai-agents · Security section, first bullet

**Model choice** · Yes — ITECS states it is not tied to one AI vendor and selects the model and platform per use case, so the buyer is not locked to one engine.

> Yes. ITECS is not tied to one AI vendor.
> — https://itecs.ai/custom-ai-agents · Custom AI Agents FAQ, answer to the Claude/Codex/ChatGPT/Gemini question

## Where you use it

**On the command line** · Yes — CLI workflows and CLI automations are an explicit deliverable, including scoped runtime secret injection through a CLI secrets tool.

> Claude projects, Codex workflows, CLI automations, RAG agents, and external-system integrations are all in scope
> — https://itecs.ai/custom-ai-agents · Pricing section bullet list, 'How Much Does a Custom AI Agent Cost?'

**In your pipeline** · Partly — ITECS builds CI/CD, release gates and rollback for the client's AI stack, but this is pipeline work it operates, not an agent that comments on pull requests.

> ITECS operationalizes AI systems for Dallas businesses with secure CI/CD, model and prompt version control, RAG pipeline monitoring, cost controls, rollback plans, and managed production support.
> — https://itecs.ai/ai-devops · Hero paragraph under 'AI DevOps & MLOps for Production AI Systems'

**In a browser** · Partly — Enterprise builds include a hosted review portal where staff approve actions, but ITECS publishes no general web application a buyer logs into.

> Human-in-the-loop review portal before any action
> — https://itecs.ai/ · Two Kinds of AI Agents, Enterprise Agents card, 'Oversight' row

## Whose machine it runs on

**Self-hosted** · Partly — Personal agents are built and run on the employee's own machine and local agents are delivered inside the client's workspace, while enterprise builds sit in a governed hosted environment.

> Designed and executed inside Claude Cowork, Codex, and Microsoft Copilot on the individual's own machine.
> — https://itecs.ai/ · Two Kinds of AI Agents, Personal Agents card body

## What it costs to run

**How it meters** · Yes — Billing is per engagement and per running agent, not per seat or token: fixed package fees, a required discovery fee credited to the build, then a monthly fee per production agent.

> 1 production agent: $2,500/mo after launch; production operations are separate from the build fee
> — https://itecs.ai/custom-ai-agents · Pricing section bullet list, 'How Much Does a Custom AI Agent Cost?'

**Free tier** · Partly — There is no free product tier; the only no-cost step is a scoping intake that leads to a paid engagement.

> Start the No-Cost Intake
> — https://itecs.ai/ · Hero call-to-action button

**Bring your own key** · Partly — Builds run on the client's own licences and workspaces - Copilot, Claude and ChatGPT seats the employees already hold - rather than on ITECS-resold inference.

> ITECS builds and delivers one local agent inside the client's workspace, ready for the sponsoring employee to use.
> — https://itecs.ai/pricing · Build / Guided & Local Agent Builds, Local Agent Sprint card

## Buying it for a team

**A company can buy it** · Yes — Every package is sold to an organisation, with leadership deliverables, tenant reviews and user-band subscriptions aimed at 50-300 employee companies.

> Executive-ready deliverable suitable for board or leadership review
> — https://itecs.ai/pricing · Start Here / AI Readiness Assessment card, inclusions list

**Seat model** · Partly — The ongoing Managed Intelligence subscription is priced in user bands rather than per seat, and build work is priced per workflow with no seat count at all.

> MIS Core Up to 10 users $1,950/mo 4 optimization hours
> — https://itecs.ai/pricing · Sustain / Managed Intelligence Services, MIS Core tier card

**Pooled budget** · Yes — Prepaid hour blocks are explicitly a shared pool any employee can draw against, with a monthly usage statement to one named contact.

> Any employee may draw against the block
> — https://itecs.ai/pricing · Prepaid Options, AI Retainer card inclusions

**Admin controls** · Yes — Constraining what AI and agents may do is a priced deliverable: acceptable-use policy, governance framework, data rules and human review paths.

> ITECS defines approved use cases, data rules, human review paths, and operating ownership before AI spreads.
> — https://itecs.ai/ · The Stakes section, Governance item

**Audit log** · Yes — Audit logging is part of the standard build pattern, and release changes to prompts, models and retrieval are versioned with approval records.

> Audit-ready releases - prompt, model, retrieval, and code changes are versioned with deploy history and approval records
> — https://itecs.ai/ai-devops · Security section, third bullet

## What happens to your code

**Opt out of training** · Partly — ITECS scopes private or enterprise configurations to the chosen vendors' contractual data terms, so the protection comes from those terms rather than an ITECS guarantee.

> ITECS scopes private or enterprise configurations, permissions, DLP policies, credential isolation, audit logs, and training to the selected vendors' contractual data terms and the client's requirements.
> — https://itecs.ai/custom-ai-agents · Custom AI Agents FAQ, 'How do I secure my business data when using AI agents?'

**Getting out** · Partly — Build artefacts are archived in an ITECS client vault and re-wired for a successor rather than rebuilt, but purchased capacity does expire: sessions at 90 days, retainer hours at 12 months, and MIS hours do not roll over.

> Sessions expire 90 days from purchase.
> — https://itecs.ai/pricing · Guided session terms list, first bullet

## What changed

- 2026-10-13 — Capabilities · Free tier · Price · Terms

## Keeping it current

These facts are re-checked against ITECS AI's own pages and updated when they change. If you represent ITECS AI, sign in and update the listing from your dashboard at https://theagentsindex.com/dashboard. The operations this site accepts from an agent are listed at https://theagentsindex.com/.well-known/agents.json — that catalog needs no key to read, and each entry states its own auth.