Urgent.News

What's breaking now, across thousands of outlets.

AI

Moving from AI adoption to an AI operating model: How Docusign engineering went beyond tool rollout

Docusign rolled out AI coding tools across its engineering teams, expecting them to help developers write code faster and do The post Moving from AI adoption to an AI operating model: How Docusign engineering went beyond tool rollout appeared first on The New Stack .

Moving from AI adoption to an AI operating model: How Docusign engineering went beyond tool rollout

Docusign, a leading electronic signature platform, has successfully transitioned from merely adopting AI coding tools to developing a comprehensive AI operating model across its engineering teams. The company's engineering leaders recognized that while initial enthusiasm for AI was high, early gains in productivity plateaued, leading them to focus on sustained adoption and integration of AI into day-to-day workflows.

To achieve this, Docusign established an Eng AI Champions team, comprised of six engineers, tasked with developing guardrails, sharing best practices, and conducting workshops. This central team then extended its efforts through AI Multipliers embedded in individual development teams. By the end of 2025, 93% of engineers were actively using AI coding tools, and lines of code updated per developer increased by approximately 52% compared to the company's starting point.

Key to Docusign's success was the concept of "teaching AI to speak Docusign." The company built specialized internal tools, such as Kody for coding work, Chronicle for observability, and DocuWiki for internal documentation. These tools, combined with AI-assisted code review (Krew), helped engineers work more efficiently by identifying potential architectural and security issues, generating proposed fixes, and integrating them into pull requests.

The company's approach emphasizes a feedback loop, where AI agents learn from the successes and failures of individual teams. By making these agents reusable across teams and visible to all, Docusign has created a scalable model for AI integration that continues to evolve and improve. Docusign's leadership believes that the combination of central coordination, feedback mechanisms, and reusable AI agents has enabled the company to sustain and expand its AI operating model, setting it apart from other AI initiatives that may have faltered.

Written by urgent.news from The New Stack's reporting — not their text. Machine-written — may contain errors; check the original before relying on it.

Read the original at thenewstack.io →

More in AI

GPT-6 Astra Passed 69.9% of Hidden Checks. It Fully Finished 26.4% of Real Edit Tasks

Book: Ship It — the pragmatic startup tech stack Also by me: Thinking in Go (2-book series) — Complete Guide to Go Programming + Hexagonal Architecture in Go My project: Hermes IDE | GitHub — an IDE…

  • GPT-6 Astra achieved 69.9% success in hidden acceptance checks
  • 26.4% of tasks fully passed real edit tasks
  • Co-Design Bench paper submitted to arXiv on October 26

How to Give an AI Agent a Spending Limit (and the Tools That Do It)

Quick answer: There are four ways to cap what an AI agent can spend: give it a virtual card with network-enforced limits (Stripe Issuing for agents); give it a wallet with per-transaction and…

  • Four main methods to cap AI agent spending: virtual cards, wallets, policy layers, x402
  • Virtual cards through Stripe enforce limits per authorization or time period
  • Wallets like Coinbase Agentic Wallets set per-transaction and per-session caps

AI Agents Work in Demos. So Why Do They Fail in Production?

I've noticed something interesting about AI agent development. Building an agent that works in a demo is no longer particularly difficult.

  • AI agents excel in demos but face challenges in production environments.
  • Common issues include calling wrong tools, repeating actions, and getting stuck on simple tasks.
  • Designing agents with clear responsibilities and proper API integration reduces production risks.

More from Sunday 8 November →