How We Version Every Deliverable

Graffold is our own content engine. It holds every deliverable this studio makes: logos, spec sheets, manuals, 3D renders, icon sets. Nothing is a loose file on someone's desktop. Graffold keeps every version of every file. For any asset we can see what changed, when and why. We can also go back to an earlier version. Every export traces back to the version it came from.

The panel beside this shows our own work in Graffold: the brand mark, the Graffold app itself, and the icon system that draws this site. One cropped asset per square. Click a square to trace how that asset was made.

Open an asset and Graffold draws its iteration tree: every version, the version it branched from, and the file that is live right now. The colours show each version's status:

• Green — the working file.
• Orange — the committed asset the rest of the system points at.
• Faint — a dead end we kept on purpose: a version we did not take, held for the record.

When a client asks "why does the manual say X?", we open the asset and read its history. We walk back through the exact iterations that got there, instead of searching through old exports. Every document that used an earlier version stays linked to that version. When an asset changes, we can see every document affected and update it, so nothing goes stale.

A package is a defined set of deliverables across a set number of product lines. Because the work is structured this way, we can scope and estimate it up front. You are not buying an open-ended retainer.

Drag the tier from Quick Start to Full Program. The scope and the estimate update together. Quick Start is a single SKU with the essentials to ship. Full Program is a multi-SKU line with renders, a long-form manual, web content and animation. These are indicative figures, not a quote. They show the rough scale of a package before we scope your work.