Invoice templates
Build and maintenance-retainer line items, with usage/API costs itemized separately from the management fee.
See the template as a client-facing document, then open the same starting point inside Hanko.
Invoice
AI Agency Invoice
Automata Works
billing@brightlinestudio.com
Invoice #: INV-2026-014
Issue date: September 30, 2026 | Due date: September 30, 2026
Total due
$13,000
Card, ACH, wire or stablecoin
Automata Works / OpsPilot
Automata Works / OpsPilot
| Description | Qty | Amount |
|---|---|---|
| AI discovery and use-case mapping | 1 | $2,500 |
| Agent workflow build | 1 | $6,000 |
| CRM/API integration | 1 | $3,000 |
| Monthly monitoring retainer | 1 | $1,500 |
Card, ACH, wire transfer or USDC.
An AI agency invoice bills the initial discovery-and-build phase separately from an ongoing maintenance retainer, and keeps usage or API costs itemized apart from the management fee so the retainer price stays stable.
Build vs. maintenance
Kept as separate line items or separate invoices, since they're different scopes of work with different billing logic.
Usage cost pass-through
Itemized separately, whether billed at cost or with a markup.
Maintenance scope reference
A brief note on what the maintenance retainer covers, to avoid "one more automation" disputes.
Copy this into your own document, or open it directly as a branded starting point in Hanko. Bracketed text like [Client Name] is a placeholder to fill in.
Invoice
Invoice #: [INV-001]
Issue date: [Date] | Due date: [Date]
From / Bill to
[Your Agency Name] / [Client Company Name]
Line items (build)
Description Amount
AI Discovery & Use-Case Mapping $2,500
Agent/Workflow Build $6,000
CRM/API Integration $3,000
Recurring (maintenance)
Description Amount
Monthly Monitoring & Maintenance Retainer $1,500/month
Model/API usage (passed through at cost) $[amount]
Totals
Subtotal: $[amount]
Total due: $[amount]
Payment terms & methods
Due within [15] days of issue date.
Card, ACH, wire transfer [and stablecoin — USDC, if applicable].
Yes — the build is typically a fixed-price or milestone project; ongoing monitoring and maintenance should be a separate recurring retainer, stated explicitly.
As a separate line item, passed through at cost or with a stated markup, so the retainer price stays stable even as usage varies month to month.
See how Hanko fits the complete client workflow for this industry, not just the invoice.
Milestone invoices for the build, then a recurring invoice for ongoing maintenance — in Hanko.
One account for proposals, agreements, invoices, client payments and contractor payouts.
Get StartedProduct updates and the occasional tip, about once a month.