Contact

Bring the brief, the mess, or the half-formed idea

This page is for design inquiries that need concept, structure, and a point of view, even if the final scope is not clear yet.

Code:Emotion Design works best when the project needs more than polish. That might mean identity work, a digital product, an editorial system, or a stranger hybrid brief that does not sit neatly inside a normal agency menu.

When this conversation is worth having

Identity systems that need to hold

For brands, institutions, and initiatives that need a clearer visual language and stronger structural coherence.

Digital experiences with real use ahead of them

For websites, tools, and products where navigation, interface feel, and usability matter as much as aesthetics.

Unusual briefs

For hybrid projects that need a conceptual frame before execution, not just a cleaner finish.

What helps before the first conversation

1. Describe the actual task

Name what needs to change: an identity system, a website, a digital product, an editorial structure, or a project whose categories are still becoming clear.

2. Explain what is not working

That can be weak differentiation, a scattered interface, unclear structure, low trust, or a concept that still feels underdesigned.

3. Say what already exists

Bring the current site, a deck, a visual system, a prototype, or rough notes. An incomplete starting point is enough.

4. Name the outcome you want

For example: clearer positioning, stronger usability, a more distinctive identity, or a system that can scale without losing itself.

A useful first conversation does not require a perfect brief. It requires an honest picture of the situation.

Start with the entry point that fits best

If you are still figuring out the right entry point, use the pages below to narrow the conversation before reaching out.

Email is enough

The cleanest first step is a direct email to arthur@schmidtpabst.com.

If it helps, send the current site, a deck, a prototype, screenshots, notes, or the rough version of the problem right away. Precision is not required.

What to include

A rough picture is enough. Helpful things include:

  • What needs to change.
  • What already exists.
  • What kind of help you are looking for.
  • Any real timing or launch pressure.

If you already have links, decks, screenshots, prototypes, or notes, send them with the first reply or straight away.