A CRM for teams that would rather sell than administer.

Why it exists

Klienta began as work for one company. They already had a CRM, and it held their customers well enough. What it did not hold was the thing they were actually selling: the products, their prices, and the offer that goes in the email. That lived somewhere else, and was rebuilt by hand every time.

So we put their catalogue in the CRM. An offer is built from it, sent from your own email, and kept with every version you sent — beside the person it went to, and the deal it belongs to.

Then it turned out the problem was not theirs alone: every small team we showed it to was keeping what they sell in one place and who they sell it to in another. So we made it a product.

The rest follows from doing fewer things the whole way. Most CRMs are built for the sales operations department of a large company, and it shows: a hundred fields, a pipeline for everything, a report nobody reads. A five-person team needs to know who called, what was promised, and what to send next.

Where the name comes from

Klienta is the Romanian word for the customer.

The name is hers. She asked for it first, and the product still answers to the person on the other end of the line.

Who answers

A small team in Romania: product and design on one side, engineering on the other, and the same people answering support. Write to contact@klienta.org and one of them replies, usually the same working day.