A studio that builds systems, not slides

What does Leisson Creative do?

Leisson Creative is a design system studio in Tallinn, owned by LEISSON OÜ (Estonian business registry code 16952932; source: the Estonian business register, entry checked on 12 September 2026). The studio builds two things and they belong together: tokenised design systems — one source of truth generating CSS, Tailwind, TypeScript and Figma — and the products that run on those systems in production. Working languages are Estonian and English.

The boundary is clear: we do not deliver a slide deck or a Figma file for someone else to translate into code later. The delivery is a repository that builds, gates that fail at the right moment, and an address you can open.

Who is it for?

The client is usually a founder or product lead with a real product and two problems at once: the interface has sprawled and the pace of development has slowed. The other client is a small business that needs a clear service page, a working enquiry form or a new website. The studio is small and works with few projects at a time — which is why the scope of every job is written down before it starts.

Domains with evidence to show: agricultural compliance and data (AgroNutikas), UX audit and SaaS (ProUXAudit), real-time and audio/DJ systems (AxonDeck), assistants and messaging products (Maris), workshop and service logic (GarageOS).

What are the engagement models?

There are two kinds of engagement and they are priced differently.

Ordering a website package does not require a separate paid discovery phase: the package scope is written on the price page and we agree the start date in writing. System and product work starts by mapping the scope, because its extent depends on the existing code and surfaces. Current prices, deposits and terms are on the Prices page.

What does AI-augmented building actually mean?

“AI-augmented” here does not mean someone asks a chat window for code and pastes it into the repository.

1. A human decides the architecture. Token spec, component boundaries, data model and gates are written before the first generated line.
2. Agents write code in parallel. Claude Code and Codex CLI run as an orchestrated swarm on separate branches; the same methodology is a portfolio entry of its own called Swarm24.
3. A code change starts with a test. The test is written first and it has to fail before the fix. Documentation and dependency updates have no failing test.
4. Gates are the judge, not an opinion. Token checks, content gates, Playwright, axe-core and Lighthouse run in CI; a red gate stops the release.
5. A human reviews and ships. The production release runs from a separate branch and requires confirmation.

The evidence for the pace is this site: Orbit v1.0.0, a component library, the gates and a bilingual site went from source file to production in two days (source: the commit history of this repository, 11–12 September 2026). The current released artifact token count appears on the Systems page, where it is read from the generated file.

Frequently asked questions

How long does a design system take?

The effort depends on how many surfaces the system has to cover, but the scale is weeks, not quarters. Orbit went from token spec to production release in two days; a client system with existing product code and a migration is a larger job, but the same pipeline.

Do you only do design, or code as well?

Both, and the delivery is code. Figma is the mirror, not the source — the tokens live in the repository and the Figma variables are generated from the same file.

Who writes the code — a human or an AI?

A human writes the architecture and the decisions, an agent swarm generates much of the code, and a human reviews and ships. A code change starts with a test that fails before the fix.

Does the client own the work?

The solution built for you becomes yours once the final invoice is paid. Leisson's general tools, methods and design system components remain the intellectual property of LEISSON OÜ; the right to use them in your project is written into the proposal. The delivery lives in your repository and on your accounts – the studio does not hold it on its own platform. The binding wording is in the terms.

Can the next developer continue the work?

You decide how the solution that became yours is developed further. Use of Leisson's general components, including by the next developer, follows the usage right written into the proposal.

Where can I see the evidence?

On the Work page: all entries with status, dated screenshots and metrics with a source. On the Lab page: what is not finished yet, with an honest label.

How do we start?

Write through the contact form or to gert@leisson.eu. We reply within one business day. It helps to describe the product, the deadline and what is not working today.