Governance
Teams adopt tools faster than leadership can set policies.
ITECS defines approved use cases, data rules, human review paths, and operating ownership before AI spreads.
Custom AI Agents
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.
Custom AI does not mean one chatbot on one model. ITECS designs secure agents, project folders, CLI workflows, and retrieval systems around the way your team actually works. We can configure Claude projects, Codex workflows, ChatGPT workspaces, agentic RAG, human approval queues, and API-connected automations that retrieve the right context, take approved actions, and keep sensitive data controlled.
The Stakes
Most organizations do not need another disconnected AI experiment. They need a managed operating model that tells people what is approved, where data can go, which workflows deserve investment, and who owns reliability after launch.
ITECS Position
Managed Intelligence applies ITECS's 24-year managed IT and cybersecurity operating model to AI systems, prompts, agents, connectors, and employee adoption.
Teams adopt tools faster than leadership can set policies.
ITECS defines approved use cases, data rules, human review paths, and operating ownership before AI spreads.
Sensitive data moves into public prompts, unmanaged plugins, and disconnected workspaces.
ITECS brings managed-IT discipline to access, identity, data handling, and vendor selection.
AI experiments consume subscriptions and meetings without a measurable operating case.
ITECS starts with workflows, cost of delay, and measurable outcomes before recommending build work.
Useful pilots stall when they have to connect with Microsoft 365, CRM, service, or finance systems.
ITECS designs automation around the systems, permissions, approvals, and support model already in place.
Illustrative Planning Signal
Your employees are already asking ChatGPT, Claude, Gemini, Copilot, and coding assistants to draft answers, summarize documents, write scripts, and speed up daily work. The gap appears when those useful experiments need approved data, repeatable prompts, project folders, tool access, audit trails, and a human approval path before anything touches a customer or production system.
ITECS builds that missing operating layer. We create custom AI agents and guided workflows that can retrieve the right context, call approved tools, connect to external systems, request human approval, and log what happened. Sometimes that means a Claude project folder or Codex workflow. Sometimes it means a full agentic RAG system with integrations, guardrails, and AI DevOps.
Illustrative Planning Scenario
This modeled example shows how an engagement could be scoped; it is not presented as a reported client result.
A 55-person property management company in Dallas: could have front-desk staff repeatedly searching separate systems for lease, maintenance, and payment information while useful prompt experiments remain disconnected from approved records and review rules.
Modeled outcome: A governed agent could retrieve approved material through scoped connections, draft an answer, and escalate policy or account-specific decisions with source context for staff review. Resolution targets would be validated during discovery.
Anatomy of an Agent Run
Scroll through a single request as a custom agent handles it. Each move is a control ITECS designs, tests, and documents before an agent touches a live system.
Illustrative run: the moves are the design pattern. Your workflow, systems, and approval rules are defined during discovery.
A staff member asks the agent to prepare a customer follow-up. The agent confirms who is asking and which folders, workspaces, and systems that person may use.
Agentic RAG pulls only approved documents, tickets, and records. Answers carry source citations, so staff can check the evidence before anything moves.
The agent plans the next step and calls scoped tools: a CRM lookup, a helpdesk search, a file store, an API, or an approved CLI workflow.
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.
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.
Only approved actions run. Each step lands in an audit log, and monitoring tracks quality, cost, and drift after launch.
Capabilities
We identify which tasks should be assisted, automated, or left human-owned. Then we map the folders, apps, APIs, databases, prompts, approvals, and security controls the agent needs.
We use the right mix of AI applications, APIs, RAG pipelines, CLI tooling, prompt systems, tool calls, and workflow automation. That can include Claude projects, Codex workflows, ChatGPT, Gemini, Microsoft Copilot, or custom-built agent services.
We validate accuracy, permissions, guardrails, logs, costs, and escalation paths before launch. Then we train your staff and monitor the agent so it keeps improving safely.
Custom AI Agent Pipeline
Map Workflows
Tasks, folders, tools, data
We identify which tasks to assist, automate, or leave human-owned, and the approvals the agent needs.
Build Agent
Prompts, tools, RAG, CLI logic
The agent is built with the right mix of AI applications, APIs, RAG pipelines, CLI tooling, and tool calls.
Test & Tune
Approvals, guardrails, evals
Accuracy, permissions, guardrails, logs, costs, and escalation paths are validated before launch.
Deploy
Claude, Codex, Slack, web
It ships where your team already works, and staff are trained on how to use and escalate it.
Monitor
Logs, costs, actions, quality
Monitoring keeps it improving safely after launch.
Agent Designs
The first four are defined ITECS service and solution designs, not reported client case-study outcomes. The last two are agents ITECS built and runs for its own operations.
Manufacturing finance
Watches purchase price variance and commodity cost exposure for finance and procurement, with human approval before any financial action.
Explore the PPV Agent designAsset-based lending
Turns borrower agings, inventory, GL, and bank data into a first-draft working-capital exam that the examiner reviews and signs.
Explore the Field Exam Analyzer designKnowledge and IT operations
Turns approved company knowledge and vendor guidance into cited answers and maintained SOPs, with human review for consequential changes.
Explore ITECS OpsMemoryIT change readiness
A read-only review agent that stress-tests infrastructure change plans and produces an auditable readiness verdict. It never makes the change.
Explore ITECS Change AssuranceBuilt for ITECS
A Microsoft Copilot agent in Teams that checks on-call coverage, creates events, and automates shift-swap approvals, tied into the ITECS PSA.
Read how ITECS built the on-call agentBuilt for ITECS
ITECS distributes Codex and Claude Cowork agent files through self-hosted Seafile while governing model, tool, and client-data flows separately.
Read how ITECS shares agents across the teamSecurity
Custom AI agents can touch customer data, internal policies, source code, credentials, and proprietary business systems. ITECS AI is backed by ITECS — a Dallas cybersecurity MSP since 2002 — and credential, access, and compliance posture is reviewed alongside our cybersecurity advisory team when an agent handles regulated or high-value data.
Agent Control Stack
Each layer answers one question an agent must clear before it acts. The linked ITECS guides go deeper on every control.
An AI bill of materials inventories what each agent depends on before it moves to production.
Governed registries, pinned versions, scoped access, and drift detection keep poisoned tools, plugins, skills, and MCP servers out.
Authorization judges the chain of tool calls an agent makes, not each action alone.
When work moves between agents and people, bounded task contracts, least-privilege access, and evidence-bearing handoffs keep an accountable owner in place.
Scoped runtime injection, for example through the 1Password CLI, reduces how often credentials sit in plain text around agent workflows.
Trace-based evaluation scores outcomes, tool use, safety, reliability, latency, cost, and human review before an agent handles live work.
An emergency stop, an incident playbook for containment and evidence, and backups an agent cannot delete define what happens when something goes wrong.
AI kill switch plan AI agent incident playbook AI agent recovery plan
Pricing
Useful one-off prompts need a governed system before they access business data, call tools, or change records. Here is the design comparison ITECS validates when an experiment moves toward production.
Planning comparison only. Scope, timing, and outcomes vary by data, workflow, approvals, adoption, and implementation conditions.
Outcome hypothesis to validate
The right custom agent should remove handoffs, reduce errors, and give staff leverage without removing human judgment from sensitive business decisions.
This is not a reported client result or guarantee. Baseline the current workflow and measure accepted work before relying on it.
Agent Operations
Ongoing operations for production agents after launch, separate from Managed Intelligence Services adoption tiers. ITECS runs the checks that keep a production agent accurate as data, tools, and usage change.
Agent runs, tool calls, costs, and answer quality are monitored and re-scored against the evaluation set.
Changes in data, prompts, or model behavior are caught before they erode results.
Retrieval sources stay current, and exceptions route to the right person with context.
Prompts, tools, and thresholds are tuned from real usage, with changes versioned and tested.
Agent Operations pricing
Production operations are billed separately from the build fee.
AI DevOps for production agents Managed Intelligence services Published AI pricing
Engagement Targets
Illustrative targets to baseline and validate during discovery — not reported client results or performance guarantees.
Related work · An anonymized client account
How ITECS and a client employee used four guided sessions to build a planning agent, turning business knowledge into reusable reports and review controls.
See what we built alongside the employeeFAQ
Every production build starts with Agent Discovery & Technical Specification at $4,500–$7,500, credited toward the build. Published phases then range from $8,000–$18,000 for a bounded prototype to $55,000–$120,000 for a multi-agent system or major process redesign. Final scope is confirmed before work begins, and production operations are separate.
Yes. ITECS is not tied to one AI vendor. 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.
An agentic RAG agent retrieves approved context from your documents, databases, tickets, or systems before it answers or acts. Unlike a basic chatbot, it can use tools, follow multi-step instructions, request human approval, cite sources, and update external systems when permitted.
The biggest risk is connecting AI to sensitive data without access controls, logging, or approved workflows. 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.
Yes. Agents can draft messages, summarize records, create tickets, update CRM fields, prepare reports, run approved CLI workflows, trigger automations, or route work to the right person. Sensitive actions can require human approval before anything is sent, changed, or executed.
Yes. We build integrations with HubSpot, Salesforce, HaloPSA, ConnectWise, Hudu, ServiceNow, Microsoft 365, Google Workspace, GitHub, databases, file stores, and custom APIs. The agent pulls only the data it is allowed to use.