Can you resend the logo? The one from the email in March.
The handoff that never ends
Months after delivery, the client still emails for “the logo”. Each reply costs billable time and slowly erodes the identity you designed.
For agencies and studios
Hand off a brand, not a folder.
The identity is approved and the invoice is paid. Then the emails start: the wrong logo on a slide, a font nobody can find, a color that drifted. GitBrand packages the deliverables in a repository that explains itself, so the client uses the brand the way you designed it.
- One repository per client
- Password-protect before launch
- Clients need no account
Password-protectedRepository created, password set
Create the client repository on day one and password-protect it. Add assets as they are approved instead of assembling a delivery folder at the end.
gitbrand.com/north
- Slug reserved: gitbrand.com/north
- Password shared with the client lead
- Empty sections: logos, colors, fonts
The endless handoff
Three emails every studio recognises
Delivery is not the end of the project. It is the start of the support period, unless the deliverables explain themselves.
I found a PNG in the delivery folder, is that the right one?
The zip nobody opens
A 300 MB delivery folder with nested subfolders is technically complete. In practice the client uses the first PNG they find.
Our new freelancer got the files from a forwarded email.
The freelancer with an old file
The client’s next contractor gets a logo forwarded from a forwarded email. It is the pre-approval version.
Your workspace
One repository per client, all in one account
Each client gets its own slug, its own assets and its own access settings. Your agency account keeps them together. The Free plan covers five repositories; Premium removes the limit and adds team seats for your designers.
North
gitbrand.com/north4 logos · 3 colors · 2 fontsPublicLaunched
North Outdoor
gitbrand.com/north-outdoorCloned from NorthMember-onlySub-brand draft
Client kickoff
gitbrand.com/kickoff-draft1 logo · 0 colors · 0 fontsPassword-protectedIn progress
Campaign kit
gitbrand.com/north-spring2 logos · 5 resourcesMember-onlyHanded over
The walkthrough test
Make the handoff a walkthrough, not a download
Send the link with a small task. If the client can find a presentation logo, the primary color and the body font without asking, the handoff is complete. If they hesitate, the fix is usually a clearer name or a one-line note, and it is cheaper to make now than in six months of support emails.
Name logo variants by their use (“Wordmark, dark background”), name colors by role (“Primary”, “Neutral”), and put font licensing beside the fonts. Tick the list on the right before you hand over the keys.
The full brand kit checklist covers everything else worth confirming before launch.
Handoff readiness0/5
After delivery
Write the repository into the contract
A maintained repository is a standing reminder of the work you did. Agree in the contract who updates it and how future work is scoped, and the agency that built the source of truth becomes the natural call for the next campaign or rebrand.
Scope the deliverables before you upload
The repository should contain exactly what the scope promised: logo variants, color specifications, typography references and supporting documents. Fonts and stock assets often carry licenses the client must buy themselves; say so in the usage notes rather than uploading files you cannot redistribute.
Name the owner
Invite one person on the client side as a member and write down that they own the repository. Decide whether you stay on as an editor or transfer maintenance entirely.
Set the access level for launch day
Password-protected during the project, then public for a press-facing brand or member-only for an internal one. The link never changes, so nothing you have already sent breaks.
Keep the archive where it lives
Source files stay in your design tool, campaign archives in your storage. GitBrand holds the approved, everyday assets. It has a publish step and a version history, but no approval workflow, so keep reviews in the tools you already use.
Sub-brands and campaigns
Clone the brand to start the next one
When a client asks for a sub-brand, a campaign identity or a second company, duplicate a repository you are a member of as a private draft. The clone keeps the logos, colors, fonts and notes; you change what differs and share a new link when it is ready.
Clones are private until you say otherwise, so the client never sees a half-finished variant at the original address.
Northgitbrand.com/northPublic · maintained by the client
North Outdoorgitbrand.com/north-outdoorPrivate draft · cloned, then edited
FAQ
Questions agencies ask
Can clients edit their repository after the handoff?
Yes, if you invite them as members. You decide whether you stay on as an editor or transfer maintenance entirely.
Can we white-label the page?
Premium lets you remove GitBrand branding and use a custom domain. On the Free plan the repository shows a small “Powered by GitBrand” footer. Premium is coming soon.
Does GitBrand replace our design files?
No. Keep source files in your design tool and archives in your storage. GitBrand holds the approved, everyday assets the client actually uses.
Do clients need an account to view the repository?
Not for public or password-protected repositories. Only member-only repositories require the viewer to sign in, which is what you want once the client owns it.
How many client repositories can we run on the Free plan?
Up to five. Premium removes the limit and adds team seats and roles so your designers can edit client repositories together.
Deliver the next brand as a link.
Create a password-protected repository at kickoff, walk the client through it at approval and hand over the keys at launch. Free for up to five repositories.