Home / A One Page Brand Guide for a Small Company
A One Page Brand Guide for a Small Company
A remodeling company with six people and four trucks does not need a bound brand manual. It needs one sheet of paper that a new project manager, a sign printer, a freelance photographer and the person who updates the website can all read in five minutes. The sheet exists to answer small questions before anyone has to ask the owner: which blue, which typeface, how much empty space should surround the logo, what does a headline sound like. When those answers live in one place, the business starts to look like a single company instead of a pile of separate decisions.
Why one page is the right size
Long guides get filed and forgotten. A single page gets pinned above the office printer, pasted into the first message to every new vendor and checked when a quote for printed shirts arrives. The constraint also forces choices. If a rule cannot fit on the page, it is probably a preference, not a rule, and preferences are the first thing a busy crew drops. Treat the page as the minimum that protects recognition, nothing more.
Keep the layout plain: a header with the company name and the date of the last revision, then five or six short blocks. Print it, but also save it as a shareable file so vendors never work from an old copy.
Block one: the name and how it is written
Start with the plain facts that people get wrong most often. Spell out the full legal name, the short name used in conversation, and the exact way each appears in print: capital letters or not, ampersand or the word and, a service word after the name or not. A remodeler who is called one thing on the truck, another on the estimate and a third in a directory listing teaches homeowners that the company is not quite organized. Also note the license line that must appear on vehicles and written proposals, spelled and placed the same way every time, since California contractor rules expect the license number to be visible in advertising.
Block two: color with a purpose for each
List two or three main colors and one accent, with the exact codes your printers and web designer need. Then say what each color is for. A deep neutral for text and large surfaces, a warm tone for buttons and highlights, a light tone for backgrounds. Without the purpose, vendors guess, and the guesses drift. Add a line about what never happens, such as stretching the mark, placing the accent behind small text or using a gradient the printer cannot reproduce on a cotton shirt.
Check each color against its background for legibility. A pale accent that looks lovely on a screen may vanish on a white proposal cover when an office printer renders it.
Block three: type that survives every program
Choose one typeface for headings and one for body text, and name a fallback for each that every computer already has. The fallback matters more than people expect. A proposal opened on a client's older laptop will quietly swap an uninstalled font for something else, and the carefully built layout shifts. State sizes loosely: headings noticeably larger than body text, body text never so small that a homeowner reading a printed scope sheet in a kitchen under pendant lights has to squint.
Block four: the voice, in a few examples
Voice is the part owners skip and customers notice most. Write three adjectives, then show them in action. If the company sounds calm and exact, say that an email subject line reads like "Cabinet delivery moved to Thursday" and not like "Great news!!". Give one example of how the company writes a first reply to an inquiry and one example of how it writes about a delay. Crew leads who text clients will lean on those samples whether or not anyone tells them to.
- Say what happens next and when, in the first two sentences.
- Use the room names homeowners use, not trade shorthand.
- Admit delays plainly and offer the new date in the same message.
Block five: the do and do not list for the mark
Keep this to a handful of pictures or short lines. Minimum clear space around the logo. Smallest size at which it still reads. Which version goes on dark backgrounds. A reminder not to recolor it to match a client's cabinetry for a photo caption. If your logo files are organized properly, this block can simply point to them by name, so nobody improvises a screenshot from the website.
Block six: who to ask and who decides
End with a name and a contact method. One person approves exceptions, and that person answers quickly. Brand guides fail less from bad rules than from slow approvals, because a sign shop with a deadline will not wait three days for permission. Also record when the guide was last reviewed. A yearly read through is enough, and it is a natural moment to update the license line, add a new service or retire a color that never printed well.
Handing it out and keeping it alive
Send the page to everyone who touches the public face of the business: the person who orders uniforms, the designer who builds proposal templates, the photographer, the supplier who co-prints a flyer and the freelancer who answers reviews. A short note with it helps: this is how the company looks and sounds, please follow it, and call with questions. Put the file in the onboarding folder for new hires so the crew sees the same rules on day one.
Watch for the quiet failures. A new truck decal arrives in a slightly different green. A subcontractor's yard sign leaves off the license line. A team member posts a project photo with a heavy filter. None of these are disasters, but each one erodes sameness, and sameness is how a name gets remembered across a sprawling metro area. When you spot a drift, fix the cause rather than the single item: update the guide, resend it, and ask the vendor to confirm.
One practical test closes the loop. Lay a business card, a proposal cover, a printed truck photo and a screenshot of the website homepage on a table. Squint. If they read as the same company, the page is working. If one looks like it belongs to a different business, find which block of the guide was missing or ignored and tighten that block. A sheet that small will always have gaps, and that is acceptable, provided you keep closing them whenever a real project exposes one.