About

Background

Mattias Hising has been building software professionally since 1999 — before the dot-com boom, when the web was still figuring itself out. That early period taught valuable lessons about building things with limited tools, moving fast, and not knowing exactly what is being built until it ships.

Over the past 25+ years, Mattias has worked across media, gaming (DICE, King, Embark Studios, Star Stable), finance, manufacturing, and e-commerce. Along the way he has served as a front-end engineer, principal engineer, solution architect, and technical director. The role has changed, but the work has always been about the same thing: helping teams build software that actually works for the business.

Work across a wide range of industries and company sizes is deliberate. That breadth is deliberate. Patterns that seem unique to one team often aren't — and recognizing them early is one of the most useful things an outside perspective can offer.

Why Yetric

After years inside engineering teams, Yetric was started to focus on the kinds of problems that matter most: teams that are capable but stuck, systems that need to evolve without stopping, and decisions that will still matter two years from now. Independence makes it possible to focus on those problems without the overhead of a large organisation getting in the way.

Independence also supports honest advice. When hiring a consultant from a large firm, that consultant often has the firm's interests to manage alongside yours. Yetric's only interest is solving the actual problem well enough that you would want to work together again.

How Yetric works

Great software rarely comes from brilliance alone. It comes from iteration, honest feedback, and teams that trust each other. Most systems don't fail because of the wrong framework or a missing design pattern — they fail because people stop talking, stop adjusting, or optimize for the wrong thing.

The work is hands-on. The focus is not on producing a document and leaving. Whether it's architecture, development, or team process, Yetric stays close to the work, keeps feedback loops short, and works to keep mistakes small and recoverable.

The goal is to leave a team better than it was found — not dependent on external help.