Exploration at volume
Generate many directions quickly so the choice is made against real options rather than one safe idea. The generating is fast; the choosing is still a designer's job.

Norml uses generative tools in real design work — exploration, asset production, variants, first drafts — and does not use them for the decisions that need judgement. This page is the honest version of where the line sits, because it is the question clients ask before they hire us.
A few clients we’ve worked with










Output went up and the work stopped looking like one company.
A generated identity looks competent and could belong to any business in the category.
Nobody can say whether the imagery is licensed, and it is already on the site.
A model produced a layout that looks finished and fails the moment real content goes in.
The team wants the speed and has no rule about when generating is and is not appropriate.
We agree up front which parts of the work are generated, which are drawn, and who signs off. The speed is real, and it comes from spending it on exploration and production rather than on decisions.
Generate many directions quickly so the choice is made against real options rather than one safe idea. The generating is fast; the choosing is still a designer's job.
Illustration, icon sets, textures and supporting imagery produced to a defined style, with provenance and licensing recorded per asset.
Once the design system is settled, produce the long tail of states, sizes and page variants against it instead of by hand.
Tokens, components and naming documented so both your team and a model produce output that is consistent rather than merely plausible.
A written checklist of the patterns that mark generated design — the same five palettes, the centred everything, the decorative numbering that encodes nothing — checked before anything ships.
What may be generated, what must be drawn, what must be licensed, and what must never be automated, written down so it survives without us.
The agreed scope identifies which of these deliverables your project needs.
Explored directions with the reasoning for the one chosen.
Produced assets with provenance and licensing recorded for each.
A design system documented so generated output stays consistent.
A review pass against the anti-slop checklist, with findings written down.
A written AI design standard your team can apply themselves.
Our process
Decide together what is generated and what is drawn, before any work starts. This conversation prevents most of the disappointment.
[ 01 ]Many directions, fast, so the decision has real options behind it.
[ 02 ]A designer chooses and justifies. This step is not automated.
[ 03 ]Assets and variants against the agreed system, with provenance logged.
[ 04 ]The anti-slop pass, then the files, the system and the written standard.
[ 05 ]