What we sell, we use ourselves

This website is our first customer

The content on gawenda-studio.com comes from Mesa, our CMS: this article, the product pages, the case studies and their images. The website is published in German, English and Polish, and we manage that in Mesa too.

Every enquiry you send through our forms lands in Kepler, our CRM. There we see who enquired, what it is about and who takes care of it.

So every day we use the tools we sell to you. In software, this is called “eating your own dog food”: you eat what you serve to others.

We see many bugs first

If something jams in Mesa, we notice it while writing our own pages. If a form in Kepler does not file an enquiry properly, we lose a customer. We do not have to wait for you to report a bug.

That changes how fast we fix things. A bug that would bother you usually bothers us first.

Features come from real work

Many features exist because we needed them ourselves. One example: Kepler has unlimited user accounts. When we built a coffee brand in 2023, we saw a subscription tool stall our collaboration because of account limits. Every assigned task had to be followed up on WhatsApp because the tool did not notify anyone. That should not happen in Kepler.

What you get out of it

With Mesa and Kepler, you do not get a concept that only works in a demo. You get systems we work with ourselves, every day, with real enquiries.

And if you want to know how Mesa feels in daily use: you are reading one of its results right now.