One source of truth
Every surface reads from the same kit version. There is no second copy of a hex value anywhere in the product.
Test: can a token be defined in two places? If yes, redesign.
About Jigsaw
Brand guidelines have always been written as PDFs and enforced by email. Jigsaw moves the rules into the tool where posts are actually built: tokens that lock, templates that hold their grid, and a review step that knows which version is current. This page covers why we built it, what we won’t compromise on, and how it’s run.
01The problem
A logo gets exported once, then forwarded, renamed “final_v2”, and re-saved from a slide deck. Six months later a regional team is posting with a green that is #1F8A4C on one channel and #23904F on another, and nobody can say which is right.
The guideline was correct. The tool that built the post simply never read it.
Existing options each solve half of this. Asset libraries store files but can’t stop anyone from editing them. Design editors are flexible enough to break any rule you give them. Review lives in inbox threads where the feedback is detached from the layer it describes.
Jigsaw was built to close that gap with one object, the brand kit, that the editor, the template library and the approval step all read from. When a token changes, it changes everywhere, and the change is logged.
02Principles
Each one has a test. If a proposed feature fails it, it doesn’t ship, however good the demo looks.
Every surface reads from the same kit version. There is no second copy of a hex value anywhere in the product.
Test: can a token be defined in two places? If yes, redesign.
A guideline that’s checked after export is a suggestion. Locked tokens leave the picker; the brand check re-runs on every edit.
Test: does the violation surface before the post is saved?
Constraints should remove busywork, not talent. Templates leave copy, imagery and an accent slot open so teams still make things.
Test: can a field team ship without asking a designer?
Kits, templates and posts snapshot as versions with an author and a timestamp. Rolling back is one action, never a support ticket.
Test: can we restore v-1 in under a minute?
03Build and support
Specifics, so you can judge the product before you commit a team to it.
Logos import as SVG, PNG or EPS; fonts as OTF, TTF or WOFF2. Kit tokens export as JSON on every version, so developers can consume the same values designers lock.
Editors build, Reviewers comment and approve, Brand leads change locked rules. Seats are scoped per kit, so a freelancer only ever sees the brand they’re hired for.
Write to support@jigsawbrand.com and the message reaches the people who maintain the product, with your workspace and kit version in view. Release notes land in the changelog.
04Direction
The roadmap follows one idea: push more of the guideline into software that can check it. These are directions we’re working on, not dated promises; shipped work is recorded in the changelog.
Read the changelogChecks for tone-of-voice terms, banned phrases and required legal lines in post copy, held in the kit next to the swatches.
Additional publishing destinations that inherit the same approval rules and safe zones as the existing four.
Broader token export and approval hooks for the tools teams already use, such as Teams, GitHub and Asana.
Plans start at $0
Import your assets, lock the rules that matter, and give every designer, freelancer and regional team one kit to build from.
Get started