Insights

AI Agents and Custom Software

When to wrap an agent around an existing system, and when to build the system.

82% ticket deflectionUnder 12 weeks100% IP ownershipUS + AU

By AsymiLink Meta · Published

The decision, not the buzzword

Custom software used to mean a team writing every workflow. Agents now take the mechanical layer — CRUD, extraction, first-pass tests, routine orchestration. The work that remains is architecture, integration, compliance, and the parts of the system that carry business risk. The companies that get this right do not buy “an AI agent” or “a custom build.” They decide which of those two the problem actually is.

Agent on existing systems

Use this when the system of record is fine and the work is repetitive. Helpdesk, CRM, scheduling, internal knowledge. The agent is a project with a runbook, not a seat licence. Production window is typically 5–12 weeks. Ticket deflection in this work has landed at 82% on production deployments.

Custom software with agents inside

Use this when the workflow is the product. A new operations platform, a CRM that does not exist yet, a compliance surface that cannot be rented. Agents write the first pass on standard layers. Engineers keep architecture, integrations, and regulated logic. You own the repository.

Offline and sovereign

When data cannot leave the building, the same two choices still apply. The model and the application run on your hardware. That is a deployment constraint, not a seventh service.

Frequently asked questions

When is an agent enough, and when do you need custom software?

An agent is enough when the system of record already exists and the work is repetitive — tickets, qualification, extraction, scheduling. Custom software is required when the workflow itself is the product: a new platform, CRM, operations system, or compliance surface.

Do we own the code and the models?

Yes. You own the code, models, and data. No licence seat and no vendor lock-in. Every engagement includes IP transfer at handover.

How long to production?

Typical production window is 5–12 weeks. Single-channel agents often ship in 5–6 weeks. Custom platforms land closer to 12 weeks.

Can this run on-premise or air-gapped?

Yes. Offline and sovereign deployments run on client hardware with no external API calls when data cannot leave the building.

Map the highest-ROI use case

A discovery call with a senior engineer. No generic strategy deck.