THE QUICK READ

The story in brief

Build a small, maintained media kit around a dated company fact sheet, concise founder biographies, properly identified images, evidence for public claims and a monitored press contact. Make the files easy to open and understand without requiring a second explanation from the founder.

Source starting point: GitLab: logos and brand assets — checked 3 November 2026 ↗. Full sources and context appear below.

Make the handover useful

Imagine an editor has read your pitch and wants to check three things: what the company does, whether a claim is supported and which photograph shows the right person. A folder full of unnamed attachments makes each question harder.

A media kit should reduce that work. Start with a short index that points to the current files, explains what each contains and names the person responsible for updates. The goal is not to make the company look larger. It is to make a small set of accurate material easy to use.

Borrow the organisation, not the scale

GitLab’s public press kit separates logo downloads, additional images and other visual resources, and points users to brand guidance. Micron’s corporate media kit groups company information, executive biographies, a timeline and image galleries, with a media contact for further requests. These are useful examples of making different kinds of material findable.

A startup does not need the same volume of assets. Our suggestion is to copy the separation of tasks: facts in one place, images in another and a clear route for questions. A journalist should not have to extract a company description from a design file or search a long presentation for a usable portrait.

Keep the fact sheet short and dated

Write a plain description of the customer, the product and the problem it addresses. Add the founding year, location and names relevant to the story. Separate when the business began from later milestones such as incorporation or a product launch if those dates differ.

Put an “information checked” date on the sheet. For every public metric, state what it counts and the period it covers. Registered accounts, active users and paying customers are different measures. If a figure cannot be explained or supported, leave it out of the public kit until the team can answer those questions.

Give every image a usable identity

For each photograph, include a descriptive filename and a nearby caption naming the subject, setting and date where known. Record the photographer or supplied credit and any applicable usage instructions. Keep an original high-resolution file alongside any smaller preview.

Label mockups and conceptual illustrations clearly. A picture of a planned product should not be presented as a photograph of an available one. For a founder portrait, confirm the person’s current name and role before sending it. This is a practical asset-management check, not a reason to retouch the person into a different likeness.

Build a kit someone else can navigate

Use the following as a starting checklist, then remove anything that does not help explain your actual story. Keep sensitive customer records, private contact details and internal dashboards out of the public folder.

A compact startup media kit — Founderline editorial checklist
ItemWhat to includeQuick check
Start-here indexLinks, owner and last review dateCan a new reader find the current version?
Company factsPlain description and dated milestonesCan each claim be explained?
Founder biographiesNames, current roles and relevant backgroundDo the bios match the supplied portraits?
Visual assetsLogos, portraits and genuine product imagesDo captions and credits travel with files?
Evidence notesPublic source links and metric definitionsAre actual results separated from plans?
Press contactA monitored inbox and named responderCan a query reach someone who can answer?

Test access before sending the link

Open the public kit while signed out. Follow the index, download a photograph and check that the caption still makes sense away from the folder. Confirm that public links do not accidentally require membership of the company’s workspace.

As a fictional example, a founder sends a folder containing “final-final.png” and a slide saying “10,000 users.” A more useful handover identifies the product screen and version, then explains whether the number means accounts created or people active during a specified period. The improvement is clarity, not decoration.

Give maintenance a named owner

Review the kit when a role, product, metric or contact changes. Keep a clearly marked archive for superseded material and make the current version obvious. If a file already sent to an editor contains a material error, explain the correction directly rather than silently replacing it and assuming it will be noticed.

A useful kit supports independent reporting; it does not determine the eventual headline or guarantee publication. Finish with a simple test: could a colleague unfamiliar with the pitch use these materials to answer the first factual questions without calling the founder?

YOUR WORKING NOTES

Run a ten-minute media-kit handover

Use these questions to investigate the idea in your own context.

  1. Ask a colleague to open the kit while signed out.
  2. Have them find the company description, one portrait and its credit.
  3. Ask them to explain one metric, including its definition and period.
  4. Check the press contact and remove stale or ambiguous files.
  5. Record the review date and assign the next update to a named person.

A closer look

Does a startup need a designed PDF media kit?

Not necessarily. A clear web page or organised folder can work. The useful test is whether the facts, images and contact details are accessible and maintained, not how elaborate the packaging looks.

Should the kit include every company document?

No. Include material relevant to public reporting and clearly separate current assets from historical ones. Do not expose private customer information or internal documents merely to make the kit feel complete.

Is a press kit the same as a pitch?

A pitch explains why a particular story deserves attention. The kit supplies organised background and assets for checking and presenting it. Each should make sense without forcing the reader to reconstruct the other.

Sources & editorial note

Original Founderline editorial guidance, researched on 3 November 2026. GitLab and Micron are examples of public resource organisation, not endorsements or evidence that a particular kit guarantees coverage. The suggested checklist and fictional example are our own. This is not a company announcement, original interview or sponsored feature.

See our editorial standards or request a correction. For a useful comparison, read How to write a founder story pitch: evidence and examples. Explore the founder topic guides for connected reading paths.