← Back to blog

Field Reports

Why agentic-coding agencies are the next lock-in

Faster delivery with AI — or a new lock-in? How proprietary agentic stacks and retainers echo the traditional agency model.

The first agentic coding engagement feels like progress: faster PRs, more autonomy, less manual typing. But if the same partner keeps stack, tooling, prompts, and runbooks outside your repo and CI, you get the same dependency traditional software agencies sold for decades — with a new label on the box.

Three layers that break when the vendor leaves

  1. Workflow lock-in — Orchestration, review, and sign-off run on vendor conventions. Without your own ADRs, hooks, and quality gates, the knowledge lives in Slack threads and individual heads, not in versioned assets your company owns.

  2. Context lock-in — “Memory” layers, RAG indices, and system prompts sit on someone else’s infrastructure. The path to production works — until you end the contract. Then the ground truth your features stood on is gone.

  3. Economic lock-in — Subscriptions to closed agent runtimes, per-seat licenses, and 24/7 retainers replace day rates, not the business model. Switching costs rise because the system is only stable with the vendor.

What’s different from classic agencies — and what isn’t

The difference is speed and language, not structure. Instead of pure body-lease sprints you get pre-built pipelines, “best prompts,” and tuned IDEs. As long as code, tests, and ops playbooks live in your Git, your cloud account, and your observability stack, you stay the owner. Once the core path is external, your ability to ship drifts the same way monolithic integration contracts did — the kind no finance committee signs blindly anymore.

What teams should verify

  • Exit test: Can you deploy without the vendor in 30 days, including CI, security scans, and on-call?
  • Artifact test: Do ADRs, skills, hooks, and operator runbooks sit in your repo and pass your team’s review?
  • Cost test: What share of run rate is fungible (your own licenses) vs. vendor tax (closed runtime)?

Opinion, not legal or procurement advice — but agentic does not mean decoupled by default. Without a deliberate handover architecture, the hype becomes the next lock-in.

MEMBER · FREE

Read the full article — sign up free

The full article is member content. Magic-link login, no credit card, no risk — and the rest of the article is readable immediately.