/Services
.services in detail

From the strategy to the prototype.

Consultancies decide what should happen and hand over a document. Studios execute a brief someone else got wrong. We do both halves, which is the only way the thinking survives contact with the thing that actually ships. Every engagement starts with how we will know it worked.

consulting

Deciding what to build, before anyone builds it.

Most design briefs arrive with the hard question already answered badly. This is the work that happens before a brief exists: what the business should compete on, what shape it needs to take, and how you will know whether it worked.

consulting / business strategy

Business Strategy

Where to compete, and what to stop doing.

Strategy is mostly subtraction. The useful output is not a deck of opportunities, it is a short list of the things you will do and an explicit list of the things you are now choosing not to, with the reasoning written down so it survives the next enthusiastic meeting.

We work from evidence you already have: what customers actually do, where margin actually comes from, and which of your assumptions have never been tested. Then we write down what would have to be true for the chosen direction to work, so it can be checked rather than believed.

WHEN YOU NEED IT

Growth has flattened, a market has shifted underneath you, or the leadership team would give four different answers to what the company is for.

WHAT YOU GET
  • Diagnosis of the current position, written plainly
  • Where to play and how to win, with the trade-offs named
  • The assumptions the strategy depends on, made testable
  • A stop-doing list, which is usually the hard part
  • Success measures agreed before the work starts
  • A one-page version the whole company can repeat
consulting / business design

Business Design

A strategy you can actually operate.

Business design is the bridge between a direction and a working proposition: what exactly is being sold, to whom, at what price, delivered how, and why the economics hold at scale rather than in the pitch.

This is where most strategies quietly die. The intent is sound but nobody has designed the offer, the pricing, the channel and the unit economics as one connected thing, so each gets decided separately by whoever is nearest.

WHEN YOU NEED IT

You have a direction but not an offer, or an offer that sells but does not make money at the volumes you are planning for.

WHAT YOU GET
  • The value proposition, stated as something a customer would recognise
  • Offer and packaging architecture
  • Pricing logic and unit economics
  • Channel and route to market
  • The operating model needed to deliver it
  • Commercial risks named, with the leading indicators to watch
consulting / organisational design

Organisational Design

The structure that lets the strategy happen.

An organisation is a design object. Reporting lines, decision rights, team boundaries and incentives all encode assumptions about what matters, and when those assumptions no longer match the strategy, people behave sensibly and the strategy still fails.

We design the structure around the work that actually has to flow, not around the current headcount, then make the decision rights explicit so the same argument does not get re-litigated every quarter.

WHEN YOU NEED IT

Work keeps stalling between teams, decisions escalate that should not, or you have grown past the structure that got you here.

WHAT YOU GET
  • Map of how work and decisions actually flow today
  • Target structure, designed around the work
  • Roles and decision rights, written down
  • Interfaces and handoffs between teams
  • Incentives checked against the behaviour you want
  • A sequenced transition plan, not a reorg announcement
consulting / systems design

Systems Design

The whole thing, not the parts.

Brand, product, service, operations and the physical environment are usually designed by different people at different times, which is why customers experience a company as inconsistent even when every individual piece is good.

Systems design treats them as one object with shared rules, so a decision made in one place holds in the others. It is also the discipline that lets a small studio deliver coherence a larger one cannot, because nothing has to be negotiated across departments.

WHEN YOU NEED IT

The parts are each fine but the whole does not add up, or every new initiative needs its own bespoke solution because nothing underneath is shared.

WHAT YOU GET
  • Map of the system as it currently behaves
  • The rules and principles that will govern it
  • Shared components, standards and vocabulary
  • Feedback loops, so the system can correct itself
  • Governance: who owns what, and who can change it
  • A roadmap sequenced by dependency, not by wish
design & build

Then building it, to the same standard.

A strategy nobody can execute is a document. We take the same thinking through brand, product, screen and physical object, which is the part most consultancies hand off and most studios start from.

design & build / brand identity

Brand Identity

A brand is a set of rules, not a logo.

The logo is the smallest part of the job. The work is deciding what the thing is called, what it sounds like, what it is allowed to look like, and how all of that survives contact with a business card, an eight foot board and a phone screen at the same time.

We build the system so it can be extended without us. If someone has to phone the designer to find out whether something is on-brand, the brand was not finished.

WHEN YOU NEED IT

You are launching, you have outgrown a logo someone made in a hurry, or the business has changed into something the brand no longer describes.

WHAT YOU GET
  • Naming, tagline and verbal identity
  • Logotype and mark system, drawn not traced
  • Palette, type scale and graphic language
  • Pattern and secondary assets
  • Usage guidelines a non-designer can follow
  • Applications: stationery, signage, print, collateral
  • Production-ready files in the formats your printer asks for
design & build / industrial design

Industrial Design & Advanced Prototyping

The same discipline, in three dimensions.

Physical products, from first concept through to the files a manufacturer can actually quote against. A render is not a deliverable. Tolerances, material, finish and how the thing comes apart for shipping are all part of the design, not problems for later.

Prototyping is treated as a way of finding out, not a way of presenting. We build to answer a specific question, and where it helps the geometry is parametric, so changing a dimension regenerates the part instead of restarting the drawing.

WHEN YOU NEED IT

Something has to be manufactured rather than rendered, a product needs to be made properly or made cheaper, or a decision needs a physical prototype before anyone commits tooling.

WHAT YOU GET
  • Concept development and CMF (colour, material, finish)
  • Parametric CAD, so changes propagate
  • Rapid and functional prototypes: 3D print, laser cut, bench testing
  • Design for manufacture, reviewed against a real process
  • Production drawings, DXF and STEP files
  • Packaging and on-product graphics
  • Vendor conversations, in the vendor's language
design & build / web design

Web Design

Structure first. Decoration last, if at all.

Before anything is drawn we work out what the site is for, who arrives on it, and what we want them to do. Layout is the answer to that question, not the starting point. A site that looks good and buries the one thing it exists to do has failed.

We also write the code. That matters more than it sounds: nothing gets lost in a handover, what ships is what was designed, and performance and accessibility are decisions we make rather than things we hope a developer preserves.

WHEN YOU NEED IT

The site is doing real commercial work, or the current one is a template that fights the content every time you add to it.

WHAT YOU GET
  • Information architecture and a content model
  • A responsive design system, phone treated as a first-class layout
  • Hand-written build, no page-builder lock-in
  • Performance budget and accessibility to WCAG AA
  • Content editing you can actually use, or static if that serves you better
  • Analytics, search basics and structured data
  • Deployment and a handover that does not need us
design & build / ui & ux design

UI / UX Design

Obvious the first time it is used.

Products rarely fail because they are ugly. They fail because a person cannot tell what to do next, or because the thing has grown feature by feature until no single screen makes sense any more. The first job is diagnosis: finding where people actually stall rather than where we assume they do.

Then the repair. Flows rebuilt around what the user is trying to achieve, and an interface system with enough structure that the next twenty screens do not each need a designer.

WHEN YOU NEED IT

People drop off somewhere you cannot explain, support keeps answering the same question, or the product has outgrown the screens it started with.

WHAT YOU GET
  • Audit of the current flows, with the stalls named
  • User journeys and task flows
  • Wireframes, then interactive prototypes
  • Interface system: components, states, spacing, motion
  • Accessibility built in, not retrofitted
  • Specs a developer can build from without guessing
  • A design file that stays usable after we leave
measurement

Design arguments end when someone produces a number.

Most design is defended with taste, which means the loudest person in the room wins and nobody can tell afterwards whether the work paid for itself. We agree what we are moving before we start, record where it stands today, and report against that. Where something genuinely cannot be measured, we say so rather than invent a proxy.

The measure is agreed first

Success criteria are written into the proposal, not reconstructed at the end. If we cannot agree what would count as working, that is a useful signal about the brief and worth having early.

A diagnostic, not an opinion

We built the Design Impact Quotient to score brand assets against repeatable criteria, so a mark can be assessed on evidence instead of preference. It is our own product, and it runs on the same logic we bring to client work.

Outcomes, where they exist

The White Flea doubled its sponsors and grew footfall by half against the preceding edition. Peakhavn has hosted over a thousand guests. Those are the numbers on record, and they are the only ones we quote.

Honest about the limits

Brand work is slow and attribution is hard. We will tell you which parts of an engagement are directly measurable, which are leading indicators, and which are judgement, rather than dressing all three up as the same thing.

what makes the difference

We build the tools, not just the output.

This is the part most studios outsource, and it is the reason the four disciplines above hold together rather than sitting next to each other. We write software. That changes what we can take on, and how fast a change costs you.

We write the code

Sites, interfaces and internal tools built in-house. No translation layer between the design and the thing that ships, and no waiting on a third party to fix a margin.

Parametric and generative

Geometry, layouts and artwork generated from parameters rather than drawn by hand. Useful when something needs one hundred variants, or one variant that keeps changing.

Measurement over opinion

Where a design decision can be tested rather than argued about, we test it. The Design Impact Quotient came out of exactly that: scoring brand assets instead of debating them.

AI where it earns its place

Used for the work it is genuinely good at, which is volume, variation and analysis. Not as a label on the proposal, and never as a substitute for the judgement you are paying for.

where we work

Remote-first, and it has never been the constraint.

The studio is based in India and the work does not care where you are. Knowchem is a laboratory in Pune. Peakhavn sits on a mountain road in Himachal Pradesh. The Raahat Sanctuary is in rural Madhya Pradesh. Moliora builds across borders. Every one of those ran remotely, including artwork sent press-ready to printers we never visited.

Anywhere in India

From metros to a village postal address. We are used to Indian print and fabrication vendors, the formats they actually want, and the paperwork that comes with it, so a brand does not fall apart between the file and the press.

Internationally

We work across time zones asynchronously, in English, and deliver in whatever the receiving side uses. Moliora, a property developer working across borders, was run this way start to finish.

How remote actually runs

One named person you deal with, not an account layer. Working files shared as they develop rather than revealed at a presentation, and reviews on a fixed rhythm so nothing waits on a calendar.

On the ground when it matters

Some work needs a person present: a press check, a site survey, a factory visit. We travel for those rather than pretend a video call covers it, and we say up front which parts of a project need it.

how to work with us

Two ways in, depending on what you need.

If the problem is a known shape, take a package and start next week. If it is not, which is most consulting work, it gets scoped to you. Same team either way, different front door.

DESEINHEIT

Packaged, for startups and SMEs

Published plans with fixed scope and a fixed fee, so you can see what you are buying before you speak to anyone. Built for founders who need senior design quickly and without a six-figure hire.

  • Fixed SprintOne outcome, one deadline, priced up front.
  • Monthly TeamSenior design capacity every month, priorities you set.
  • Founding PartnerEmbedded from zero to one, and one to ten.

Starts with a free Design Impact Quotient, which scores your current design in about ten minutes and points at the plan that fits.

See the plans at Deseinheit ↗
EINHEIT

Tailored, for everything else

Scoped to the problem rather than to a package. This is where the consulting sits: business, organisational and systems work, and programmes that run across brand, product and physical object at the same time.

  • Diagnosis before scopeWe work out what is actually wrong before quoting a fix for it.
  • Built around your constraintsYour timeline, your team, your regulator, your factory.
  • Measured against an agreed numberSet at the start, reported against at the end.

The usual route when the answer is not known at the outset, when several disciplines have to move together, or when the work has to survive a board.

Start a conversation →

Tell us what you are building, we'll tell you what it needs.