Capability statement
Summarize the business, expertise, relevant proof, and contact route in a concise document.
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
Summarize the business, expertise, relevant proof, and contact route in a concise document.
Typical handoff
An approved capability statement 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 or PDF. PowerPoint, Google Slides, or another native editable format must be agreed in advance.
Setup. Page or slide size, approved content, slide/page count, and editing requirements are confirmed before work starts.
Limits. Short-form layouts and presentation systems only. No extensive document production, fillable forms, InDesign files, research, or financial verification.
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.