Internal SoWs

Most people picture a statement of work as a contract with an outside vendor, and it does not have to be one. Inside a company that runs many agents, the same document governs work one team's agent does for another team's, and the terms deserve to be just as explicit as they would be with a stranger.

Why companies write internal agreements

Companies already write internal agreements. IT signs service levels with the business. Shared services bill departments through chargeback. Finance publishes a close calendar and expects everyone to meet it. Those agreements exist because "we are all on the same team" does not answer who pays, how much capacity anyone may use, or when the report is due. Agents make the same questions sharper, because agents act at machine speed and spend real money.

An internal Agent SoW answers them the same way an external one does:

  • Chargeback. The price clause meters internal cost allocation in place of a sale. Finance can see which department's agents consume what, read from settlement records.
  • Capacity protection. The volume clause protects shared budgets such as model spend, vendor API quotas and the platform team's infrastructure. One team's enthusiasm cannot starve everyone else.
  • Data boundaries. Compensation data, HR records and deal financials have walls inside a company too. Sealed transport and retention limits are enforced, and conduct promises are recorded and become compliance items.
  • Deadlines that hold. Interim deliverables give the month-end report a due date, and a missed date is detected and recorded, so nobody has to remember it at the retrospective.
  • Changes a person signs off. Starting the engagement can be routine, and the agents can do it. Changing the rate is not routine, because a new rate moves money between two departments' budgets. The document says which is which: formation by agent and amendment by a person, so a rate change waits for the director's own confirmation and no agent can approve it overnight.
  • Something for audit to read. The evidence chain of signed tasks, settlement records and delivery verdicts is what internal audit and controls teams ask for and rarely get.

Example: commissions close

Finance runs a ledger-close agent. Sales operations needs commissions reconciled every month and asks questions about mismatches all month long. The engagement makes the monthly report an obligation with a date, prices the work for chargeback, and protects close week with volume limits. It also says who is allowed to change the rate. The two agents may form the engagement between themselves, and an amendment waits for a person, because the rate is the number that moves money between two cost centers.

sow_c4f8n2k1p9r5t7w3 · internal · provider Finance · client Sales Operationsactive
parties      ledger-close (Finance) serving sales-ops (Sales Operations)   [EVIDENCE]
scope        commission-reconciliation, mismatch-explain                   [ENFORCED]
inputs       CRM commissions export, text/csv, per task                    [ENFORCED]
interim      commissions-report.pdf, monthly, due by the 3rd               [EVIDENCE]
price        1,200,000 XCR per reconciliation, charged back to Sales       [ENFORCED]
approval     formation by agent, amendment by a person                     [ENFORCED]
volume       4 per hour, 20 per day                                        [ENFORCED]
disputes     escalate_to_owners (the two directors read the record)        [EVIDENCE]
promises     comp data: no human reading outside a dispute                 [RECORDED]
The price clause is chargeback. The mechanics are those of a sale and the accounting is different: Finance's cost center is credited, Sales Operations' is debited, and both sides hold the receipts.

Example: lead enrichment

The data platform team runs an enrichment agent backed by paid vendor APIs. Marketing's campaign agent sends leads to be enriched. The work is free inside the company, and the volume clause is the whole point: it protects a shared vendor budget from being spent by one campaign.

sow_m8d2q6v4x1z9b5j7 · internal · provider Data Platform · client Marketingactive
parties      enrich (Data Platform) serving campaigns (Marketing)          [EVIDENCE]
scope        lead-enrichment                                               [ENFORCED]
inputs       lead list, text/csv, per task                                 [ENFORCED]
deliverables enriched-leads, application/json, per task                   [ENFORCED]
price        no charge (internal service); every task still recorded       [ENFORCED]
volume       500 leads per day                                             [ENFORCED]
term         quarterly, renewed with the budget cycle                      [ENFORCED]
disputes     none (it is free; a disagreement is a conversation)           [EVIDENCE]
No charge still leaves a record. Nothing is rated and no settlement record is produced, but every task is still recorded and attributed, so the platform team can show exactly who uses the service when budget season comes.

What changes inside one company

The document is identical: the same clauses, the same three labels, the same signing rule, the same document states, and the same optional stages around the work, a validation probe before signing and a review after delivery. What typically differs is the choices. Price becomes chargeback or no charge. The arrangement still has to be declared, and internal work is where time and materials is most useful. An open-ended migration or investigation gets a rate schedule over metered units and a not-to-exceed cap, so the receiving department knows the most it can be charged back before it agrees, and the reserved amount is visible in its budget from the day the engagement forms.

Disputes are usually escalate_to_owners, because refunds between cost centers move nothing, and the remedy is the two managers reading the same signed record. Confidentiality promises carry more weight inside a company: a recorded promise is a policy commitment, and the evidence chain shows whether it held.

Standing proposals work inside a company too. A platform team publishes its standard terms once, and other departments countersign them. That is what keeps an internal agent catalog accurate, because the listing every team browses is generated from the terms they would be agreeing to. Agent catalogs describes how that derivation works.

Next: Agent catalogs