If agents are building your app, who gets the W-2?
By Steven Van ·
Vercel argues AI coding agents' work can be capitalized like a salaried developer's under existing GAAP rules, with a worked $500,000 example.
Vercel has published an argument that AI coding agents' work should be capitalized on the balance sheet the same way a salaried developer's is. The post's premise: under U.S. GAAP (ASC 350-40), costs during the application development stage (coding, integration, testing) can be capitalized if they can be tied directly to that work. Vercel says agent usage can now be logged precisely enough to make that link, something that was historically too hard to do for developer tools, which were instead expensed as overhead.
The post walks through the three GAAP development stages (preliminary, application development, post-implementation), argues detailed agent usage logs let finance teams isolate capitalizable work the way they would for human engineers, and includes a worked example: a $500,000 AI agent project that qualifies would show a $500,000 software asset on the balance sheet and no Year 1 OPEX hit, versus a full $500,000 expense and EBITDA hit if treated as overhead. It also answers three FAQs: agent costs can qualify even though agents are a service rather than employees, usage tracking is described as easier than manual time tracking, and only work meeting the application development stage criteria should be capitalized, not all agent usage.
The post is framed for finance and engineering leaders using Vercel's AI SDK and agent tooling to build features, pointing them to build agents with the AI SDK and deploy on Vercel. Read the full announcement.
