SpecPRD2025
Order Book v2 PRD
4,000-line PRD for a revenue ops platform. Got specific: sub-projects as the billing unit, invoice source-lineage fields, field inheritance logic, 8 build phases. The kind of spec that actually gets built from.
Overview
Order Book v2 is a 4,000-line product requirements doc for a revenue operations platform. It restructures the data model so sub-projects ( not contracts) carry billing model and frequency, since contracts in practice are parent shells and the actual commercial unit is the sub-project.
Key decisions
- Sub-projects own billing_model, billing_frequency, and revenue schedule. Contracts demoted to grouping shells.
- Canonical invoice source-lineage fields added to invoice line tables (13 fields), so any invoice can be traced back to the originating sub-project state at the time of generation.
- Field-level inheritance tables for context-aware prefill: when a user creates a sub-project, fields default from parent contract / client / billing entity in defined order.
- Auto-computation for 12 derived values (e.g. recognizable revenue this month, deferred revenue rollforward).
Implementation
Build phases broken into 8 sprints, with a separate ~676-line implementation prompt for Claude Code execution.
The full PRD is internal — the architecture diagrams and decision logs are available on request.