How we work

A system, not improvisation.

This flow comes out of ten years of its founder's craft. Every step is there because of one specific error we watched happen.

01

Concept or base pack analysis

If the pack doesn't exist yet, we design it from the concept up, with scale built in from the first stroke. If it does, before touching anything we audit the original artwork against a 40+ point checklist. Do the fonts support diacritics? Do the text boxes absorb +30% length? Does the halftone survive short runs? This is where we catch the problems that would otherwise appear at language seven.

Deliverables
Scalability reportDetected risksPrep plan
02

Built to grow from the start

When a product works in one market, it rarely stays in one. So we prepare the files with the next versions, languages and markets already in mind. When the next adaptation lands, nobody starts from scratch.

Deliverables
Versioned master fileComponent systemInternal usage guide
03

Multilingual adaptation

We deploy the system to each export market. The right typography, controlled lengths, special characters, and the language each destination country requires by law. All version-controlled, so you know exactly what changed, when and why.

Deliverables
Versions by languageChangelogTypographic validation
04

Quality control

Double review: visual and regulatory. A sector-specific checklist, because pharma is not cosmetics: braille and pharmacode in one, INCI and PAO in the other. Nothing ships without structured, documented approval.

Deliverables
QA report per versionSector validationFormal sign-off
05

Structured delivery

Full prepress: print-ready files with consistent naming, the die line on its own layer, correct ICC profiles, metadata and a colour proof to check against. It is what your printer is glad to get right first time. And it stays live: when something changes in six months, we know exactly which packaging file to open.

Deliverables
Print-ready filesDie line and ICC profilesPackaging kept current
The process in numbers

What the system is made of.

40+
checkpoints in every audit
5
steps, from audit to delivery
2
checks of ours per version: visual and regulatory
1
master file per product family
Differentiators

Four things a generalist studio will not give you.

01

Audit before designing

We do not open a file without knowing first what will break it. The scalability report is the first deliverable, and it lands before there is any design to show.

02

Versioned master file

We don't work on copies. We work on a master with full history.

03

Sector-specific QA

In pharma we check EN 15823 braille, pharmacode and the QRD template. In cosmetics, INCI, PAO and 655/2013 claims. It is not the same filter.

04

Documented traceability

Every delivery ships with its changelog: what changed, in which version, against which validated document and who approved it.

Initial audit

Ten of the forty-odd checkpoints.

The full list comes in the report we hand over at step 01. These ten are the ones that most often turn out wrong in artwork that arrived signed off.

  1. 01The artwork fonts carry Eastern European and Turkish diacritics.
  2. 02There is a declared fallback for Greek, Cyrillic and CJK.
  3. 03Text frames absorb 30% more length without moving the die line.
  4. 04The legal minimum type size holds in the longest language, not only in Spanish.
  5. 05The safety margin takes the full legal block of the strictest market.
  6. 06Braille clears text and varnish, and dot height matches EN 15823.
  7. 07Barcode and pharmacode have enough quiet zone and contrast.
  8. 08Text is live, not outlined. Outlined text cannot be versioned.
  9. 09Colours separate cleanly: no RGB, no orphan spot inks.
  10. 10The die line sits on its own layer and does not print.
About the process

What to expect if you start today.

No. We need a 90-min kickoff and validation per milestone. We handle the rest. If your team has zero bandwidth, we can operate async.

The system is built to absorb it. A claim, regulatory or formula change propagates with traceability. Everything documented. There is a versioned changelog the client signs before we continue.

Your regulatory adviser validates the content. We answer for the artwork we deliver matching exactly what was validated. In practice: we send the version with changes marked field by field, your adviser signs off on that, and what is approved gets frozen into the master file with its changelog. We don't sign the dossier and we don't tell you what the label has to say. We do know how to read it and apply it without anything getting lost on the way.

That works too. We hold capacity each month for urgent work. A reply within 24 working hours with scope and timeline in writing, and delivery in 72 hours if the scope is reasonable and the master file is already prepared.

If there are changes, we make them. The point is that you get the version ready, not that you keep count of how many passes it took. The two reviews we do count are ours, one visual and one regulatory, and they happen before the version reaches you.

Fonts with Eastern European and Turkish diacritics, a declared fallback for Greek, Cyrillic, Arabic and CJK, legal minimum type size in the longest language, safety area and die-cutting tolerance, EN 15823 braille, barcode and pharmacode contrast and quiet zone, live rather than outlined text, and clean colour separation. The first ten are published on this page. The full list comes in the step 01 report.

When it shows

The process shows from market three onward.

If you are on your third and each one costs what the first did, something needs fixing before the fourth.