Typography system
Choose typefaces and define a hierarchy for headings, body text, labels, and supporting information.
Design files and agreed exports. Implementation is a separate scope.
Once the individual request becomes active. Content readiness and feedback can affect timing.
What you can request
Choose typefaces and define a hierarchy for headings, body text, labels, and supporting information.
Typical handoff
An approved typography system direction, refined for the agreed use and supplied in the formats we confirm in the brief. Editable source files, alternate sizes, or additional versions can be included when agreed at the start.
What to bring
Supply approved copy, brand files, examples, the intended audience, required sizes, and any deadline. We confirm the deliverable and production requirements before starting.
How it fits the partnership
Request this on its own or as a stage within a larger module. We confirm scope and timing, then work through one active request at a time. Related formats and variations are prioritized in the queue rather than assumed to be a single small task.
Typical specifications
Files & handoff. Figma source where appropriate, plus SVG, transparent PNG, JPG, and PDF exports for approved artwork.
Setup. Vector masters for scalable marks; raster exports at agreed pixel sizes. Print color versions are prepared to the agreed production requirements.
Limits. Font and stock licenses are separate. JPG has no transparency; PNG is not a vector. No trademark search or registration.
Ready to start
0 of 4 reviewedUse this to prepare your request. We confirm scope and readiness together.
Before this becomes active
Can follow at the agreed stage
- Refinements after the first direction is reviewed.
- Inputs for later stages, only when we agree they are not needed yet.
Personal checklist only. Ticks are not saved or sent, and do not start the delivery estimate.
Copying a template does not submit a request.