Minimal, type-led · Plum & gold · EB Garamond + Inter
Sales & marketing
A sales one-pager is the page a rep sends after the call: the problem, the offer, three proof points and a next step.
3 designs, each a separate take on the same document rather than a recolour of one layout: Minimal, type-led, Diagonal split and Full-bleed hero. 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.
Minimal, type-led · Plum & gold · EB Garamond + Inter
Diagonal split · Ochre & ink · Montserrat + Lato
Full-bleed hero · Charcoal & signal · Montserrat + Inter
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 |
|---|---|---|---|---|
| Gold Measure | Minimal, type-led | Plum & gold | EB Garamond + Inter | 1 · A4 portrait |
| Ochre Wedge | Diagonal split | Ochre & ink | Montserrat + Lato | 1 · A4 portrait |
| Signal Bold | Full-bleed hero | Charcoal & signal | Montserrat + Inter | 1 · A4 portrait |
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 |
|---|---|---|
| Gold Measure | the three service items; record figures; fee rows; objection columns | the display statement; the standfirst; per-item copy; objection answers; the client note |
| Ochre Wedge | reason columns; proof figures; price rows; objection columns | headline; standfirst; the three offer lines; per-reason copy; objection answers |
| Signal Bold | switch reasons; proof metrics; how-it-works steps; objection columns; plan rows | headline; per-reason copy; objection answers |
These document sets each include the sales one-pager designs above.
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.