First Invoice Template: Milestone Billing for Federal Products

Milestone-tied invoice structure for a Level 2 productized service, with CLIN mapping, payment terms, and federal billing discipline. Rate card values populate once pricing is finalized.

2.1 · First-SKU Launch · artifact id: first-invoice-template-v0.html · 2026-05-28 · v0

Format stub. The billing structure and milestone logic are complete. Dollar amounts, user counts, and CLIN line prices populate once the rate card is finalized and the first contract is signed. This template supports both the sub-of-prime route (prime invoices the government; NorthAI invoices the prime) and the CHN-direct / GSA MAS route (NorthAI invoices the government directly).

Why milestone billing beats time-and-materials

Ch 13 of Shrink-Wrap It draws the contrast precisely: "Per-endpoint pricing is different. We're selling protection. Outcomes. Something they can point to and say: that's what we bought." Milestone billing ties payment to product outcomes, not hours consumed. It also disciplines the internal team: a milestone has a definition of done. Hours do not.

For the first federal customer, milestone billing matters for a second reason: it gives the agency a clear invoice narrative. Contracting officers process invoices against deliverable descriptions in the contract. A milestone invoice maps cleanly to the CLIN deliverable description. An hours invoice requires the CO to verify rates, loaded cost, and direct hours, all of which slow payment.

Milestone billing schedule

Three milestones cover the standard onboarding period (Weeks 1-12). After go-live, billing shifts to subscription invoices against CLIN 0001 on the anniversary cycle.

Milestone	Trigger event	CLIN billed	Amount	Evidence required
M1 · Kickoff complete	Contract award + kickoff meeting held; deployment environment confirmed in writing	CLIN 0002 (50%)	$[TBD] (50% of onboarding fee)	Signed kickoff notes; agency ISSO email confirming environment details
M2 · Go-live	UAT signed off by agency PM; ISSO confirms deployment matches authorized boundary	CLIN 0002 (50%)	$[TBD] (50% of onboarding fee)	Signed UAT acceptance document; ISSO written confirmation
M3 · Subscription Year 1 start	Go-live date + 1 day; subscription period begins	CLIN 0001	$[TBD] ([user count] users x $[TBD]/user x 12 months)	Go-live confirmation email; user roster as of billing date

Federal invoice format requirements

Federal invoices must conform to FAR 32.905. The elements below are required on every invoice submitted to a federal contracting office (or to the prime for flow-through).

Required element	Value (placeholder)	Note
Name and address of contractor	[NorthAI legal entity name and address]	Must match SAM.gov registration exactly
Invoice date	[Date invoice is issued]	Starts the Prompt Payment Act clock (30 days for non-construction)
Contract number	[Contract number from award document]	Include order number for task orders under a GWAC or IDIQ
CLIN number and description	CLIN 0002: Standard deployment and onboarding	Description must match the contract CLIN description exactly
Quantity and unit price	[Quantity] x $[Unit price] = $[Extended price]	For subscription CLIN 0001: quantity = users, unit = per user per year
Milestone or period of performance	[Milestone: Go-live acceptance, signed [date]]	Reference the specific trigger event and evidence document
Total amount due	$[TBD]	Sum of all CLIN line items on this invoice
Payment instructions	ACH: [Bank name, routing, account] or as directed by agency finance office	Most agencies pay via ACH. Confirm payment method at kickoff.
DUNS / UEI	[NorthAI UEI from SAM.gov]	Required for all federal invoices. Confirm SAM.gov registration is active and not expired.

Sub-of-prime billing flow (Route A)

When flowing through a prime, NorthAI invoices the prime, not the government. The prime's subcontract should specify:

Payment terms: net 30 from prime's receipt of government payment, or net 45 from NorthAI invoice date, whichever comes first. Do not accept net 60+ in the subcontract.
Invoice format: confirm whether the prime requires its own internal invoice format or accepts FAR 32.905 format.
Milestone alignment: NorthAI's milestone trigger (kickoff, go-live) should align with the prime's obligation to the government. Misaligned milestones create payment delays.
Pass-through fee: the prime's fee is taken from NorthAI's rate before invoicing the government. The subcontract must state the fee explicitly.

Annual subscription renewal invoice

Option year renewal invoices follow the same format but reference the SLIN (Sub-CLIN) for the option year (e.g., CLIN 1001 for Option Year 1). Key discipline points:

Issue the renewal invoice at least 60 days before the option period start date. Give the agency time to exercise the option before the gap in coverage.
Confirm user count at renewal. If users have grown beyond the original contract quantity, a contract modification is required before billing the incremental users.
If pricing has changed since Year 1, the new rate applies only if the contract has been modified to reflect the new Schedule price or negotiated rate. Do not unilaterally change the invoiced rate.

ConMon cost allocation per invoice

Ch 13 is explicit: "Build your ConMon costs into pricing." The table below shows how FedRAMP Moderate ConMon costs ($200-500K annually) allocate across the customer base at different volumes. Use this table to validate that CLIN 0001 pricing is sustainable before the first invoice is issued.

Customer count	Annual ConMon cost (midpoint)	ConMon per customer	CLIN 0001 revenue needed to cover ConMon (at 250 avg users)
1 (first customer)	$350K	$350K	$1,400/user/year (ConMon portion alone)
5 customers	$350K	$70K	$280/user/year (ConMon portion)
10 customers	$400K	$40K	$160/user/year (ConMon portion)
25 customers	$450K	$18K	$72/user/year (ConMon portion)

This table makes the pricing discipline visible. The first customer cannot carry the full ConMon burden at a price the market will pay. The pricing model must assume a minimum viable customer count (typically 5-10) before subscription revenue covers ConMon fully. Bridge funding or Phase 1 sub-of-prime revenue covers the gap.