Finance teams evaluate vendor engagements on metrics they can audit: hours billed, rates contracted, deliverables documented. Delivery Unit (DU) pricing — where the vendor is paid per shipped output rather than per hour worked or per seat reserved — looks unfamiliar from this lens. The accounting treatment, audit posture, and procurement controls all behave differently. Some finance teams reflexively resist DU pricing because the model violates assumptions they've operated on for years.
This piece is the practical primer. What DU pricing actually is, how it interacts with standard finance processes (accounting, audit, procurement, budgeting), and where the model genuinely produces better outcomes than the hourly-billing or per-FTE-subscription alternatives.
What DU pricing actually is
The vendor is paid per Delivery Unit (DU) — AiDOOS's universal delivery unit, a calibrated measure of shipped, accepted output. The DU's size reflects the complexity, technology, scarcity, and integration depth of the work itself, not the time taken to produce it. A senior architect, a junior engineer, and an AI agent all earn 1 DU when they deliver 1 DU of accepted output. The customer pays the same regardless of who or what produced the work.
The customer-facing model is a credit pack: pre-purchase 10 DUs ($2,000 Starter), 60 DUs ($10,000 Small), 300 DUs ($40,000 Scale), or a custom Enterprise pack. Validity windows run 90 days to 12 months. Bench time, ramp time, and pod-management overhead are all the vendor's risk. The customer pays per shipped DU, not per resource-hour.
For deeper breakdown, see DU pricing explained.
Accounting treatment
Expense recognition
DU-based costs are recognized when the work is accepted (when value is received), not when the credit pack is purchased. The pre-purchased pack itself sits as a prepaid-services asset on the balance sheet; consumption against shipped DUs converts the asset into recognized expense. This typically aligns with GAAP / IFRS standards for service expense and with the prepaid-services patterns most ERP systems already handle.
For procurement systems built around hourly billing, the data flow may need adjustment: a single line item per pack purchase plus consumption-based draw-downs, instead of weekly hour invoices. Most ERP systems handle this without modification; some require minor configuration to track DU balance and consumption events.
Cash flow profile
Pack-based pricing produces front-loaded cash flows (pay for the pack at purchase, draw down as work ships). For Starter and Small, this is typically a credit-card transaction that bypasses procurement entirely. Scale and Enterprise tiers can be invoiced and paid on net-30 terms like any traditional vendor.
Some finance teams prefer the predictability of smooth monthly billing; others appreciate that pre-purchased packs lock in the rate and remove month-to-month variance. Neither is structurally better; the preference depends on cash management practices.
Capitalization vs expense
Engineering work that produces capital assets (e.g., new product builds) may be capitalized rather than expensed. DU pricing supports either treatment because each DU consumed ties to a specific shipped, accepted unit of work — easier to justify capitalization than vague hourly billing tied to "work performed."
Audit posture
DU-priced engagements typically audit better than hourly engagements. Four reasons:
- Per-DU consumption documentation. Each DU draw-down ties to a specific, accepted deliverable with documented acceptance criteria. Auditors get a clear chain: scope → DU estimate → shipped work → acceptance → DU consumption.
- Single legal counterparty. One vendor with one contract handles all engagement work, vs multiple staff-aug vendors each requiring their own audit trail.
- Reduced timesheets-and-rates audit risk. Hourly billing audits often surface rate disputes, time-tracking inconsistencies, and change-order overhead. DU billing has fewer of these vectors — there are no hours to dispute.
- Refund trail is clean. Unused DUs in the wallet can be refunded at any time at the rate paid, with the refund event logged against the original payment. Auditors see the same dollar amount go out and (potentially) come back, with no rate arbitrage possible.
For external SOX or regulated-industry audits, the DU-based structure produces cleaner evidence. See how a regulated client ran a VDC under audit for a concrete case.
Procurement controls
The standard procurement controls translate to DU-priced engagements with adjustments:
Vendor selection
Compare vendors on $/DU rate × estimated DU count, rather than $/hour × estimated hours. Some procurement systems aren't optimized for this, but the underlying comparison is the same — just expressed in different units. AiDOOS publishes a single $/DU rate per tier, so the comparison is procurement-friendly: one rate, four tiers, transparent.
Approval workflows
Approval thresholds tied to total engagement cost rather than per-week or per-month spend. DU packs have predictable total costs from the moment of purchase; the approval workflow can be tighter than for open-ended hourly engagements. The Starter tier ($2,000) is engineered specifically to fit under most managers' discretionary spend limit, bypassing procurement entirely for first-purchase scenarios.
Change management
Scope changes consume different DU counts without contract amendments. The DU primitive absorbs scope evolution at the operational layer rather than the contracting layer. Procurement's change-control process applies less because the engagement framework already handles change.
Vendor performance management
DU-priced engagements have built-in performance measurement: DUs consumed must tie to accepted shipped work. The re-delivery guarantee on acceptance miss means the vendor cannot bill the customer twice for the same outcome. Procurement can score vendors objectively without designing custom KPIs.
Budgeting
For annual budgeting, DU-priced engagements behave more like project budgets than service contracts:
- Engagement cost = estimated DU count × $/DU at the relevant tier. Projectable from scope.
- Variance against plan: did the work consume the estimated DU count, or did scope evolution push consumption above estimate?
- Year-over-year planning: similar to project portfolio planning, not headcount-equivalent budgeting. Multi-year Enterprise commitments lock the rate and are predictable far in advance.
For finance teams accustomed to budgeting service work as headcount-equivalent (X engineers × Y hours × Z rate), the shift is real. Some find it more predictable; others find it less. Depends on which scenario produces less variance — and most finance teams find that DU-priced engagements have less variance once the team has calibrated DU estimates against actual consumption for a quarter or two.
The cost-control argument
The strongest case for DU pricing from a finance perspective is cost control:
- Bench tax doesn't pass through. The vendor absorbs unproductive time; the customer doesn't.
- Scope creep is bounded by DU consumption. Larger scope = more DUs consumed, visibly. Hourly contracts let scope drift quietly through "we needed more time."
- Vendor incentives align. The vendor's revenue grows when work ships faster — more DUs delivered against the same talent capacity. The "vendor lock-in via slow delivery" pattern that's expensive in hourly engagements doesn't exist here.
- Refundable unused DUs. If the engagement under-delivers or scope shrinks, unused DUs in the wallet can be refunded at the rate paid, no questions asked. This is a structural cost-control mechanism that hourly contracts and per-FTE subscriptions cannot match.
For total-cost-of-delivery analysis, see the TCD framework.
The cost-risk argument
The case against DU pricing from a finance perspective is risk transfer:
- DU estimation accuracy is the key variable. If estimates routinely under-call DU consumption, the engagement runs over budget. Mitigation: pre-flight DU estimation is shown transparently before work begins, with historical accuracy bands disclosed; the calibration board adjudicates disputes.
- Quality risk shifts. The vendor is incentivized to ship to acceptance criteria; if criteria are vague, "shipped" can mean less than the customer intended. Mitigation: tight acceptance criteria + the re-delivery guarantee on acceptance miss means the customer doesn't pay twice for the same outcome.
- Pre-paid vendor concentration risk. Pre-purchased packs sit as prepaid services with one vendor. Mitigation: refundable unused DUs let the customer recover the unconsumed portion within 24–48 hours if the engagement goes wrong, without negotiation.
Net: DU pricing trades hourly variability for DU-consumption variability, while adding refund-on-unused and re-delivery-on-miss as structural risk-transfer mechanisms back to the customer. Most finance teams find the combination easier to manage than hourly billing once they've run one engagement under it.
What to ask procurement
Five questions to surface model fit:
- Can our procurement system process pre-purchased credit packs and consumption-based draw-downs, or does it expect hourly invoicing?
- What's our standard payment-terms language for DU-pack purchases? (Credit-card up-front for Starter/Small/Scale; net-30 for Enterprise.)
- How do we audit DU consumption? (Same as milestone billing: documented acceptance + DU-draw-down events, all surfaced in the platform's real-time dashboard.)
- Can we capitalize DU-consumed engineering costs? (Yes if work produces capital assets — each DU ties to a specific deliverable.)
- How do we model engagement budget? (Estimated DU count × $/DU at the relevant tier rate, locked for the validity window.)
Frequently asked questions
How does DU pricing affect cost predictability?
Improves predictability for the engagement total once DU estimation has been calibrated for a quarter. May reduce predictability for monthly cash flow if pack purchases are lumpy. The Enterprise tier offers smoothed quarterly billing for finance teams that prefer it.
What if a DU estimate misses the actual consumption?
Three protections. First, pre-flight DU estimation is transparent — historical accuracy bands are shown with each estimate. Second, individual stories are capped at ~20 DUs, forcing decomposition that limits any single estimation error. Third, if the vendor systematically under-estimates, the customer can refund unused DUs and switch tiers without penalty.
Can finance teams negotiate volume discounts on DU-priced engagements?
Yes — the tier structure is the volume discount, baked in. Starter is $200/DU; Small is $167/DU; Scale is $133/DU; Enterprise drops to $120-$140/DU. Pre-purchased packs and Project flow share the same rate card at the same DU count, so customers don't pay an "on-demand premium" for piecemeal purchasing.
How do we model TCO across hourly vs DU-priced vendors?
The TCD framework normalizes both into per-shipped-feature cost. Comparison becomes apples-to-apples once both sides translate to "what did one shipped feature cost?" rather than comparing hourly rates against DU rates directly.
What happens to unused DUs at the end of the validity window?
Two options. Refund them at the rate paid (24–48 hours back to the original payment method), or top up before expiry — unused DUs roll forward into the new pack. There is no penalty for either choice.
Where to start
If your finance team is evaluating DU-priced vendors for the first time, walk through this primer with procurement and engineering leadership. The translation from hourly-thinking to DU-thinking is the main lift; once that's done, the operational mechanics follow.
For specific finance-side conversations about a candidate engagement, schedule a 30-minute call. For pricing-model context, see DU pricing explained. For contracting, see VDC contracting / SOW.