Values

Customer Love

We love our customers and love to solve their problems. We don’t build products just because it’s fun (it is fun), but we do it to help our customers. We feel true happiness and joy when our products and services simplify the life of our customers and we see that our work is used and appreciated.

Product Ownership

All individual team members working on a product own the product and have full responsibility for things to get done. What this means is that if a team member notices that something is not done correctly or at all, they are responsible for it to be done. This doesn’t necessarily mean that they should do it by themselves, but notify another team member or the team as a whole about the problem. We support each other in fixing problems. It’s under no circumstances allowed to think that a specific problem is someone else’s problem.

Focus on Key Features

We spend the majority of our time on features that truly matter. Features that solve real problems, move the product forward, and create lasting value for our customers. We would rather deliver one well-thought-out feature, built with care and high quality, than many shallow additions that don’t hold up over time.

KISS

Keep It Simple, Stupid. Things can at first look simple, but when new ideas are added they will get more and more complex. At that time we take one step back and find the real problem we are solving and simplify it. Everything can be simplified, and it might be hard now, but if we don’t simplify, it will become even harder in the future.

Think Big Act Small

All our companies have international growth ambitions. Therefore all products and services should be able to scale to multimillion users. We do however start small and it’s more than okay to build things that can’t be scaled in the beginning. First we solve a problem fast and use shortcuts when possible, because we need to validate that our product really solves the problem our customers have. When our product is validated, it’s time to refactor, rebuild and create a scalable product.

Fail Fast

We want our solutions to be validated by customers fast. If possible with just a PowerPoint, Google Sheet, a new process or a quickly developed MVP we do that. During validation it’s better to build something rough for a couple of days than build perfection for a couple of years, if the result is that we didn’t solve the customer’s problem. But when we have validated that the customer’s problem is solved, we double down on our solution and start to build for quality.

Transparency

We strive to share all kinds of information and thoughts within our teams, between teams, to customers and everybody else. If everybody has access to all possible information they can make decisions that are for the greater good themselves. Unfortunately not all information can be shared, for example when NDAs are signed with customers or when we have a competitive advantage, we prefer not to share with our competitors.