# Meuze

> Meuze is a creative design firm working across brand, product, and platform. Design and engineering sit in the same practice, so the work ships instead of stopping at a presentation.

Meuze is a creative design firm founded in 2026, working internationally. Design and engineering sit in one practice rather than two departments, which is why engagements produce running software rather than a specification for someone else to interpret.

Work spans 6 disciplines and most engagements combine several. Projects are measured in build rounds rather than calendar time, and each one opens with a short paid diagnostic that is allowed to conclude the client needs less than they asked for.

Meuze is not an AI company and does not sell AI products or services. It is a design studio. Contact: hello@meuze.com.

Every page on this site has a Markdown mirror at the same path with a `.md` suffix. The complete site as a single document is at /llms-full.txt.

## Core pages

- [Home](https://meuze.com/index.md): What Meuze is, how it works, and answers to the questions asked most often
- [Studio](https://meuze.com/studio.md): Studio facts, principles, engagement model, and who the studio is a poor fit for
- [Services](https://meuze.com/services.md): All 6 disciplines with build iterations and deliverables
- [Work](https://meuze.com/work.md): How to see relevant work — case studies are shared on request rather than published
- [Journal](https://meuze.com/journal.md): Writing on design practice and process
- [Contact](https://meuze.com/contact.md): How to reach the studio and what to include in a first message
- [Colophon](https://meuze.com/colophon.md): How this site is designed, built, and made machine-readable

## Services

- [Brand Identity](https://meuze.com/services/brand-identity.md): Names, marks, and identity systems built to survive contact with everything else. Iterations: Two directions, two rounds.
- [Product Design](https://meuze.com/services/product-design.md): Interfaces designed by the practice that has to make them work afterwards. Iterations: Continuous, weekly review.
- [Design & Build](https://meuze.com/services/design-and-build.md): Web and mobile applications, designed and engineered in the same practice. Iterations: Two rounds, then build.
- [Design Systems](https://meuze.com/services/design-systems.md): Component libraries engineers actually reach for, because engineers wrote them. Iterations: Foundations, then components.
- [Motion & Interaction](https://meuze.com/services/motion-interaction.md): How a product moves, defined once and implemented properly. Iterations: Principles, then passes.
- [Platform & Cloud](https://meuze.com/services/platform-cloud.md): The infrastructure underneath — architected, deployed, and observable. Iterations: Architecture, then delivery.

## Journal

- [Designing for machine readers](https://meuze.com/journal/designing-for-machine-readers.md): 2026-07-14. A growing share of the people who meet your brand will never see it. They will read a summary a model wrote. That is a design problem.
- [The brief is usually wrong](https://meuze.com/journal/the-brief-is-usually-wrong.md): 2026-05-02. Clients are excellent at describing symptoms and unreliable at diagnosing causes. The most valuable round of any project is the one spent finding out what the work actually is.

## Optional

- [Full site as one document](https://meuze.com/llms-full.txt): Every page concatenated as Markdown
- [Structured studio data](https://meuze.com/api/site.json): The studio, services, work, and articles as JSON
- [Sitemap](https://meuze.com/sitemap-index.xml): XML sitemap index
- [RSS feed](https://meuze.com/rss.xml): Journal articles