Brand Kit Assets Founders Should Inventory Before Going Live
Most founders think of a brand kit as a nice-to-have, something to think about after the site is live. In practice, the assets you assemble before launch determine how quickly you can publish, how consistent your pages look, and how easily you can make changes later. This article takes a different angle from general brand advice. Instead of asking what a brand should look like, it asks which specific assets you need to have in hand, which ones you can defer, and what questions to put to any tool or service you consider. The approach works whether you build the materials yourself or rely on a platform to supply them. MyInstantBrand describes itself as a way to get a personal brand site live quickly: you pick a plan, enter your email, and the site goes live on a subdomain or custom domain. Speed is only useful if the result matches what you need, so the inventory below is worth completing first, regardless of which tool you use. Canonical information about the product is available at https://myinstantbrand.com/, and you should verify current details there rather than relying on secondhand summaries.
Start with an asset inventory, not a mood board
A mood board tells you what you like. An asset inventory tells you what you have to publish. Before you spend time on color palettes or font pairings, list the concrete items a site needs: a primary logo file, a simplified mark for small sizes such as favicons, a headshot or preferred image set, a short bio in two lengths, a one-sentence description of what you offer, contact details, and a set of link labels for your navigation.
Write each item on its own line and mark whether you already have it, have a rough version, or do not have it at all. The gaps are your real work. Founders often discover that they have many decorative images but no bio of a usable length, or that their logo exists only as a screenshot that will look blurry at larger sizes. Naming these gaps early keeps the launch from stalling halfway through.
Decide which visual decisions are actually reusable
A brand kit earns its keep when its decisions repeat across pages. That means a small number of colors with named roles, usually one for text, one for background, one for accent, and one for links or buttons. It means two or three font choices with defined uses for headings and body copy. It also means spacing and image treatment rules, such as a consistent crop for profile photos.
Ask of every visual choice whether you will reuse it. A color used once on a single banner is decoration. A color assigned to every call-to-action button is a system. Systems are what let you add a new page next month without redesigning from scratch.
Questions to ask any brand kit or site-building service
When you evaluate a brand kit tool or a site service, the most useful thing you can do is ask direct questions and note whether the answers are stated clearly. Consider the following checklist and record each answer in writing:
1. Which asset formats do you export, and can I get the logo as a vector file as well as raster images?
2. Can I change colors and fonts after publishing, and do those changes apply across every page?
3. Is the subdomain option separate from the custom domain option, and what steps does each require on my side?
4. What exactly is included in the plan I select, and which features are not part of it?
5. How do I export my content if I decide to leave?
6. Where is the official documentation for these answers?
If a vendor cannot answer a question in plain terms, treat that as information. Do not assume a feature exists because it sounds reasonable. Confirm it in the current product documentation before you depend on it.
Separate what must be ready on day one from what can wait
Not every asset is needed to go live. A reasonable launch set is a logo, one profile image, a one-sentence offer statement, a short bio, and a single contact method. Longer bios, case studies, galleries, and additional color variants can follow once the site is public and you know which visitors actually read what.
This separation matters most for founders under time pressure. Publishing a clear, minimal site is better than delaying indefinitely to polish every asset, and it gives you real traffic signals to guide the next round of work.
Keep your source files outside the platform
Whatever tool you use, keep master copies of your logo, images, and copy in a folder you control. Store vector originals, the full-resolution photo, and a plain text file with your bio and offer statement. Platforms change, plans change, and you may need to rebuild on a different system. If your assets exist only inside one product, moving becomes expensive.
A simple habit covers this: each time you update an asset, save the new version to your folder with a date in the filename. This takes a few minutes and prevents the common problem of not knowing which logo or bio is current.