When forecasting future revenue and expense targets in our 3-Year Picture on the V/TO, how should our leadership team model gross margins as labor costs drop but software subscription and compute fees climb?

Question

Tyler Smith · Accepted Answer

Most leadership teams make the mistake of modeling AI purely as cost savings. They assume headcount costs drop to zero while gross margins jump to ninety percent. In reality, modern operational infrastructure trades variable payroll costs for fixed and variable software licenses, API consumption charges, and workflow maintenance.

When updating the financial targets in your 3-Year Picture on the V/TO, break down your cost structure with precision. Employees are traditionally a massive P&L line item loaded with benefits, management overhead, and payroll taxes. When AI tools automate low-value coordination tasks, you can support substantially more revenue without adding proportional headcount. That increases revenue per employee, which institutional buyers love.

However, you must balance that leverage against rising operational technology expenses. Account for enterprise software seat tiers, token usage, system integration retainers, and security compliance audits. Do not bury these expenses in general administrative overhead. Assign AI infrastructure costs directly to Cost of Goods Sold if they directly power client delivery, or to operating expenses if they support internal operations.

Target a clean operational leverage profile. A healthy 3-Year Picture in an AI-augmented company should show revenue scaling at twenty to thirty percent annually while operational headcount grows at single digits. Your gross margin should expand by three to eight percentage points, even after accounting for increased compute costs. This proves to a future acquirer that your operating model possesses genuine scalability.