Brand Kit Sprawl: Auditing Your Assets Against Your Actual Launch Pages
Founders who need a brand quickly often collect assets faster than they can use them. A logo file here, a color palette there, a font pairing someone recommended in a chat thread, and suddenly the brand kit is a folder of options with no clear rule for which ones belong on the live site. This article takes a different angle from a general asset inventory. Instead of sorting assets by type, it starts from the pages you plan to publish and works backward to the assets each page really needs. The method is simple: list the pages, list the jobs each page must do, and only then decide which brand elements earn a place. This keeps the kit small enough to maintain and keeps the public site consistent from its first day.
Start With the Pages, Not the Palette
Before opening a single design file, write down every page a visitor could reach on your site at launch. For most founders this is a short list: a home page, a plan or pricing page, a page describing what you offer, and perhaps a contact or sign-up page. Each page should get one line describing its main job. The home page introduces you. The plan page helps a visitor choose a tier. The contact page gets a message or a sign-up from someone ready to act.
Once the pages and jobs are written down, you can ask a useful question of every brand asset: which page does this serve? A color palette that appears nowhere on the list is a candidate for removal. A logo variant meant for print business cards is not needed on a web page built to collect visitor emails. This question prevents the common pattern of building a kit around aesthetic preferences and then discovering that half of it never reaches a visitor.
Separating Reusable Pieces From One-Off Choices
A brand kit has two kinds of material. Reusable pieces appear on every page and every channel: the primary logo, the main text color, the body font, and the button style. One-off choices appear once and can be changed without affecting anything else: a decorative background image on a single page, a seasonal accent color, or an illustration used in one section.
Keep reusable pieces few and stable. A useful rule is to limit the kit to one primary logo, one secondary mark if you truly need it, two or three colors with clear roles, and no more than two typefaces. When a one-off choice proves valuable, promote it to reusable only after you have seen it work on more than one page. Founders who skip this step end up with a kit where every asset feels equally important, which makes later decisions slow and inconsistent.
A Practical Checklist for Asset Review
Work through this checklist before you finalize the kit. First, confirm every page on your list has a named job. Second, for each brand asset, write the page or pages it appears on; if the list is empty, mark the asset as unused. Third, check that each color has a single role, such as primary action, background, or text, and that no two colors compete for the same role. Fourth, make sure your logo remains readable at the smallest size it will appear, such as a browser tab or a navigation bar. Fifth, confirm that your typefaces are available in the formats your site will use, and note any licensing terms written in the source material you received.
Last, ask whether a stranger could identify the brand from the home page alone. If the answer depends on details that only appear deeper in the site, the kit may need a clearer primary mark or a more consistent header. This checklist is not a guarantee of any outcome. It is a way to reduce avoidable confusion before visitors arrive.
Questions to Ask Before You Commit to a Kit
Whether you build your kit yourself or use a service, several questions will clarify whether it fits your launch. Which pages are you launching with, and does the kit cover all of them? Who decides when an asset changes after launch, and how will that decision be recorded? If you hand the site to a designer or developer later, can they find every file and understand its role without asking you? What format does each asset come in, and will you need different versions for different screens? If you plan to use a subdomain first and a custom domain later, does your kit work in both places without edits?
Ask these questions of any platform or template you consider. Look for clear answers in the product's own documentation rather than assumptions. Where the answer is not stated, treat it as unknown and plan a manual check instead of trusting it. A small, well-documented kit that matches your pages will serve a fast launch better than a large collection no one has reviewed against the site it is meant to support.