Skip to content

Proposals

Generate statement of work PDFs from your data

An SOW is where a proposal becomes contractual — deliverables, acceptance criteria, milestones, rates and assumptions, set out in numbered particulars that survive legal review.

3 designs, each a separate take on the same document rather than a recolour of one layout: Swiss grid, Minimal, type-led and Boxed form planner. Every preview below is the actual compiled output, not a mock-up.

Open one in the editor and render it from your own JSON over the API — 1 page of A4 portrait, the same engine either way.

Designs
3
Page size
A4 portrait
Length
1 page
Document family
Formal record

Statement of work designs

How the statement of work designs differ

Same document, same data model, 3 different arguments about how it should look on paper. Pick on layout and typography — the content behaves identically.

Design Layout Palette Typefaces Pages
Hairline Grid Swiss grid Plum & gold Montserrat + Merriweather 1 · A4 portrait
Legal Rules Minimal, type-led Ink & cream Libre Baskerville + Inter 1 · A4 portrait
Ruled Particulars Boxed form planner Ochre & ink JetBrains Mono + Inter 1 · A4 portrait

What your data drives in a statement of work

Each design is authored against an explicit reflow contract, so it is defined up front which blocks are emitted once per record and which fields absorb longer content. That is what stops the layout falling apart at a hundred rows.

Design Repeats per record Grows with your data
Hairline Grid metadata cells; articles; clauses with run-in numbers; lettered sub-items; shoulder notes, one per clause at most; schedule rows with the head repeating on a page break; execution cells, one per party the recital; every clause body; shoulder notes (they wrap in their own column and never push the text measure)
Legal Rules numbered clauses, sub-clauses and lettered items; defined-term rows; schedule rows; execution columns (one per party) clause bodies and defined-term definitions (any length)
Ruled Particulars particulars cells; clause rows (number cell + body cell); lettered sub-items; schedule rows with the head repeating on a page break; execution cells, one per party the recital; every clause body and sub-item; the deliverable descriptions in the schedule

Start from one of these statement of work designs

Open a design in the editor and the agent reshapes it around your schema — then render it from your own data over the API, or let your users edit it in the embedded editor.