About
A small studio with a long memory.
Kerd is a software studio in Lithuania. Right now it is building its own app, UnPeel. Programming and IT consulting for business clients are planned for later.
The last decade has been spent inside enterprise resource planning — Microsoft Dynamics NAV, then Business Central, then Odoo — which is a polite way of saying we have seen what happens when software is bolted on to a business that has already moved on without it.
Alongside that came the web and mobile work: React and TypeScript front ends, Node services, iOS and Android apps. The two halves feed each other. Knowing how an ERP thinks makes for better integrations, and knowing how a product team ships makes for better ERP work.
UnPeel is the studio’s own product. It exists because nobody reads the back of the pack, and because a company that only ever builds to someone else’s brief slowly forgets how to make decisions.
- Based in
- Lithuania
- Experience
- 10+ years
- Disciplines
- Consulting, ERP, web, mobile
- Own product
- UnPeel
- Languages
- Lithuanian, English
širdis
Lithuanian
cor
Latin
kardía
Greek
heart
English
The Proto-Indo-European root behind the word for heart across half of Europe. In Lithuanian it also left šerdis: heart, and core.
Named after the heart. Which mostly means telling you the hard part first.
In most company copy, heart means being nice. We mean being honest, which is not always the same thing. The most useful thing a technical partner can do is say the sentence you were hoping nobody would say — while it still costs you a conversation instead of a year and a budget.
To make sure the expensive decision is the right one.
Things we have had to say out loud
The rewrite will not fix it. The process that broke the old system is still in the building.
You do not need an app. You need two people to stop keying the same order twice.
The integration is fine. Your data is not, and no amount of code will make it agree with itself.
Yes, it can be built. It should not be, and here is what it would cost you every year afterwards.
What that is worth to you
We ship.
Every stage ends with something you can run, not a deck to interpret. You are never paying to find out where the project actually is.
We stay.
Business systems live for years, so we write for the person who inherits them — and we are still reachable when they need us.
We say no.
The cheapest feature is the one we talked you out of. You get an opinion with reasons attached, not an order form.
How we work
Small on purpose
You talk to the person writing the code. There is no account manager between the question and the answer.
Written down
Decisions, trade-offs and reasons live in documents, not in one person’s head.
Boring where it counts
Interesting architecture is a liability in a system that has to run payroll. We save the novelty for the product.
0+
years building systems that had to stay up
Ten years of shipping, not just planning.
Long enough to have inherited other people’s systems, watched a few rewrites fail, and learned which shortcuts cost money later.
Working with
Have a question?
Write to us about UnPeel, about the studio, or about work we might take on once services open.
or email info@kerd.lt