PRDs
Product requirement docs — the outcome we’re after, the problem it solves, why now, and the milestone-by-milestone scope. One page per PRD so a spec can be read, commented on, and approved in place.
-
Global Agents — lifting agents out of a single matter
2026-07-29. Lawrence stays the in-matter default; global agents (finance, compliance, intake) operate across the whole caseload, and firms get a default set out of the box. Outcome, problem, why now, and nine milestones from the backend platform through a global agent, agent inbox and manager to user-built agents, with user stories, acceptance criteria, open questions, and the default sub-agent matrix.
House structure for a PRD
- Outcome — what a user can do once this ships, in plain terms.
- Problem statement — what breaks today and at what scale.
- Why now — what’s changed / what’s newly possible / why it’s the highest-leverage unlock.
- Scope — the milestones, in order, with what’s in and out.
- Requirements — per milestone: user stories, acceptance criteria, and open questions.