A brand board that outlives the client who commissioned it

Graphic design work produces a specific kind of reference clutter: type specimens saved from years of type-hunting, colour palettes screenshotted from wherever they were spotted, competitor branding kept for a pitch, and a past client's board that would be genuinely useful again if it were not buried three projects deep in a hosted tool's account. Most of that material gets thrown away and rebuilt from scratch every time it would actually help.

Why hosted boards stop paying off after the third client

A hosted moodboard tool is easy to start a board in and hard to keep a library in. Every new brand pitch starts its own board, references get re-uploaded because nobody remembers which old board already had that type specimen, and the boards that made the pitch usually sit forgotten in an account rather than feeding the next one. None of that is a flaw in any one tool — it is what happens when reference lives inside boards rather than in a searchable library the boards are built from.

A type specimen, found by what it is rather than which pitch it was for

Tag a specimen or a palette the moment it is saved — serif, condensed, warm-palette, whatever the property that made it worth keeping actually is — and the query line reaches it later regardless of which pitch it was originally saved for: tag:any:a,b matches either tag, rating:>=4 keeps results to specimens that actually shipped in past work, -is:favourite excludes whatever is pinned to a board in progress right now. AND across keys, OR inside a comma list.

tag:any:competitor-review rating:>=3       past competitive audits
has:notes no:tags                          annotated but never filed
added:>2025-01 tag:any:warm-palette        this year's palette references

A brand board, saved as a file the client's project folder can keep

Dragging a shortlist onto a canvas produces Something.coii-canvas, pretty-printed JSON saved wherever the client's project already lives. It sits inside the project folder alongside the actual deliverables rather than in a separate app's account, and it names the images it uses without copying them — so a type specimen used on three different client boards stays a single file on disk, not three uploaded copies.

Reusing a specimen library across every pitch that follows

The habit that pays off across a design career is registering one general specimen and palette folder — separate from any client's project folder — and building every pitch board by pulling from it rather than re-collecting material each time. Because a canvas places files without copying them, the same warm-palette reference can sit on a food brand's board this month and a hospitality brand's board next month without ever existing twice on disk, and tagging it once means both boards found it from the same search.

What a past client's board is still worth

A hosted tool's per-project boards tend to become unreachable the moment a project account is archived or the subscription lapses, which means the type and colour decisions made for a past client stop being reference at all. Rebuilding a killed or completed pitch as a .coii-canvas file inside that client's own project folder — kept, not deleted, once the job ships — means the direction is still there to reopen the next time a similar brief comes in, with no account required to see it again.

Competitive audits, kept without pretending they are a mood board

Reviewing a competitor's branding before a pitch produces its own kind of reference — packaging shots, screenshots of a rival's site, photographs of their signage — that is useful for a defined stretch of one project and worth keeping afterward purely as a record of what the category looked like at the time. Tag it plainly as an audit rather than folding it into general inspiration, and it stays out of the way of a search for actual creative direction while still being reachable the next time a similar category comes up for a different client.

tag:any:competitor-review added:>2025-01     recent audits only
tag:any:packaging,signage rating:>=3         audit material worth revisiting

None of this needs a separate tool from the rest of the specimen library — the same workspace and the same query line cover both, and the tag is what keeps an audit from being mistaken for a genuine style reference months later.

Handling a rebrand across several rounds of revision

A single rebrand pitch rarely produces one board — it produces several, as directions get narrowed across rounds of client feedback. Because a canvas is a plain file rather than a row in a shared account, each round can be its own file — Northline rebrand — round one, — round two — sitting in the same project folder, so the history of how a direction narrowed stays on disk rather than being overwritten inside one evolving board. A client asking "what did round one actually look like" three weeks later is answered by opening a file, not by hunting through an account's version history.

Sharing a specimen library across a small studio

A studio of two or three designers pulling from the same type and colour library does not need a shared account or a hosted database to do it. Pointing each person's Coii Ref install at the same specimen folder — over a network share the studio already runs — gives every machine its own local index of the same files, so a tag one designer applies while filing a new specimen is visible in a search run from another desk, without a server process or a login to manage across the team.

Comparing this to keeping everything in one working file

Some designers keep all their reference pasted directly into a working Figma or Illustrator file as a reference layer, and that approach works fine for the one project it lives in. Its limit shows up later: reference buried inside a finished working file is invisible to any search and not reusable without opening that specific file. Registering the same source images with Coii Ref does not replace pasting references into a working file — it means the specimen or palette outside that file stays searchable on its own, independent of which project eventually used it.

Building a specimen library that survives more than one brand

A structure that holds up across a design career organises by visual property rather than by client — Serif, Condensed, Warm palette, Competitor audits — with a client tag layered on for anything gathered specifically for one pitch. That answers both "what condensed faces have I liked" and "what did I show Northline specifically," from the same folder, because the search does the sorting a folder structure alone cannot. Neither structure is required; an existing per-client layout searches exactly as well, since the query reaches subfolders regardless of depth.

What it costs and what it runs on

$19 once, three Macs, updates included, nothing that renews. The trial runs 30 days with every feature enabled, no card and no account required. It needs macOS 11 Big Sur or later, on Apple Silicon or Intel, as two native builds rather than one shared binary.

The app's entire outbound network activity is a licence check on Activate and a launch-time read of a server's Date header, so a wound-back clock cannot extend a trial. There is no in-app updater and therefore no update check, and no analytics or crash reporting.

Past day thirty of an unpaid trial, growing the library — registering a new folder, running the importer, starting an index by hand — needs a licence. Search, tags, ratings, notes and every canvas already saved keep working permanently.

What a killed direction is still worth

A rebrand direction that dies in round two does not need to be deleted, and tagging it by its visual qualities rather than only by the client it was built for means it stays available for the next pitch it happens to suit. A warm, condensed-type direction rejected by a food client is exactly as useful for a different food client eighteen months later, found through tag:any:warm-palette,condensed rather than buried inside a project folder for a job that never shipped.

Working across a studio desktop and a laptop for client meetings

A designer presenting on a laptop away from the studio desktop where a specimen library actually lives can register the same folder, over a shared drive or however the studio already keeps files in sync, from both machines — each one builds its own local index without an account tying them together. Licensing covers three Macs on one purchase, enough for a studio desktop, a laptop and a backup machine without paying twice.

A specimen library that survives a change of software

Design tools change across a career more often than a specimen and palette library should have to — a new subscription model, a studio switching from one design app to another, a personal move off a tool that raised its price. None of that should threaten a reference library built from ordinary image files: nothing about Coii Ref ties the collection to a specific design application. The working files change; the specimens, palettes and past client boards underneath them stay exactly as tagged and rated, regardless of what draws the actual work afterward.

Who this actually suits

A designer or small studio with years of accumulated type, colour and past client reference who wants a pitch board built from a searchable library rather than rebuilt from scratch each time. If a board only ever needs to be shared as a live, commentable link with a remote client, a hosted tool covers that job more directly than a file-based canvas does.

For the broader argument without the graphic-design framing, the general moodboard page makes the same case without assuming a client-facing pitch is the reason a board exists, and the reference-manager version covers the search side in more depth. Against the hosted tools this page is most often weighed next to, Coii Ref vs Miro, Coii Ref vs FigJam and Coii Ref vs Milanote each concede what the hosted board does better — live collaboration chief among them — specifically rather than in general.

A specimen library built this way also survives a change of Mac entirely — copy the folder to new hardware, register it once, and the index and thumbnails rebuild from whatever is already tagged and rated, with nothing to re-download and no account to sign back into first. The same is true of a change of design software: the specimens and palettes stay exactly as tagged regardless of which application eventually opens them for a layout.

Thirty days, every feature, no card and no account: download it and point it at the specimen and palette folder that has been rebuilt from scratch for one too many pitches already. Index the oldest client folder next — the direction that got killed two years ago is usually still exactly right for a different brief.