Defense Finance · Module 2

Why Your Contract Revenue Might Be Half What It Should Be

By  ·  June 2026  ·  5 min read

For example (hypothetical): two companies, same $10 million contract. One of them books $10 million in revenue. The other books $500,000.

Same contract. Completely different financial picture. And the company booking $500K didn't do anything wrong. They just don't know why it happened, or how to fix it on the next one.

It's one of the easiest concepts to miss in defense contracting finance. Plenty of PMs have never heard of it. And your Statement of Work has a lot to do with it.

There Are Two Kinds of Defense Contractors (Financially Speaking)

Here's the split. Under ASC 606 (the accounting standard that governs how U.S. companies recognize revenue), when another party is involved in delivering what the customer bought, a company has to decide, for each good or service it promises, which of two roles it plays (FASB's principal-versus-agent guidance):

You're either a Principal, or you're an Agent.

A Principal owns the delivery. In the standard's terms, it controls the good or service before the customer gets it. The usual signs: it's primarily responsible for making the work happen, it carries the inventory risk, and it has discretion over the price. A Principal books the full contract value as revenue.

An Agent is a pass-through. They coordinate, they facilitate, they manage the flow, but they're not really the ones doing the technical work. They only book their fee.

Example (illustrative): Quick Math $10M contract. $500K management fee.
Principal books: $10,000,000
Agent books: $500,000
Same contract. 20x difference on paper.

Why This Actually Matters to You

You might be thinking: okay, but the money is the same either way. The contract pays what it pays.

True. But revenue on paper isn't just about cash flow. It's about how your company looks.

Investors, lenders and bonding companies look at your top-line revenue. A company with $10M in revenue looks very different from one with $500K, even if the actual profit is the same. It can affect your bonding capacity, your ability to secure financing, and your attractiveness as an acquisition target.

For a small or mid-size GovCon firm, that distinction can be the difference between graduating to the next tier of contracts or staying stuck.

The SOW Is Where It Gets Decided

Here's where program managers have real influence, and most of them don't know it.

Your contract, and especially your Statement of Work (SOW), spells out what you've actually promised to deliver, and that promise is where the Principal-or-Agent call starts. Not the contract type. Not your company size. What you're really on the hook to do.

If your SOW reads like a "hardware dump" (you arrange for equipment to reach the government, the vendor sets the price and stands behind the product, and your role is procurement logistics), you may be an Agent. You're facilitating a purchase. Resellers who buy the equipment, hold it, carry the risk and set the price can still be Principals, so let your accountants make the call.

If your SOW reads like an engineering or integration contract (you're doing systems integration, hardening, testing, or technical development), you're probably a Principal. You own the outcome. You bear the risk. You add value. ASC 606 names a significant integration service, combining other parties' goods into what the customer bought, as a clear sign that you control the result.

So if your company really does integrate, test and stand behind the result, make sure the SOW says so. A SOW that undersells your role can push your accountants toward an Agent call on work where you're really the Principal. What you can't do is write your way into Principal status for work you don't control. Auditors look at substance, not adjectives. Accurate is the goal, not creative.

Most PMs Write SOWs Without Thinking About This

They focus on the technical requirements. The deliverables. The timeline. That's their job and they're good at it.

But often no one tells them that the framing of what they're doing (the language they use to describe their role) has real financial consequences for the company. How accurately the SOW captures your role can help decide whether millions of dollars show up as a "fee line" or as "top-line revenue."

Once you see it, you can't unsee it. And you start reading every SOW differently.

Drafted with AI from public sources. Spot a mistake? Email lucas@acqlerate.com and I'll fix it.

Ready to Go Deeper?

The full breakdown (including the exact ASC 606 criteria, Principal vs. Agent decision framework, and how to read a SOW through a financial lens) is in Finance Module, Lesson 9 on Acqlerate.

Take Lesson 9 → Revenue Recognition

Part of the Defense Finance module · Free to start