The correspondence leaves with the person
A manager leaves and takes two years of agreements with them — inside a personal mailbox that was never yours. What remains is a client who remembers a promise nobody in the studio can find.
Mail on your own domain, built into the CRM: every letter lands in the client's card and in the project it belongs to. Nothing lives in a personal inbox, so nothing leaves with the person who wrote it.
The first stage is closed. You can pay by card right in your cabinet — the link below opens the exact screen.
Open the invoiceNone of them looks like a problem until the week it does — and by then the letter has already not arrived.
A manager leaves and takes two years of agreements with them — inside a personal mailbox that was never yours. What remains is a client who remembers a promise nobody in the studio can find.
A bare grey block with a link is what a phishing attempt looks like, and people have learned that. An invoice the client did not open is an invoice the client did not pay — and they are not to blame for it.
The system said «sent», the provider refused it, and the manager finds out a week later from the client. A letter that failed without a trace is worse than one that was never written: everybody is still waiting.
Half an hour of DNS records once, and after that mail is simply a part of the client's card.
SPF, DKIM and DMARC are set up together with you, once. This is the boring part that decides whether your letters land in the inbox or in the spam folder for the next three years.
hello@, invoices@, personal ones for the managers — and all of it in one shared inbox where the studio sees the whole correspondence, not just its own half of it.
Registration, invoice, project status, password recovery — all of them in one layout with your mark, one heading and one button. A letter should be recognisable at a glance, before it is read.
The client answers from their own mail, and the letter appears in the same thread inside the project card. No copying, no forwarding, no «I am attaching our correspondence below».
This is not another mail client. It is the mail your CRM already needs in order to speak to a client at all.
Everyone with the right to see the client sees the whole thread. A holiday, an illness or a resignation stops being an event that loses letters.
A letter is not a separate world: it lies in the client's card next to the brief, the invoice and the chat. Six months later the answer to «what did we agree» takes ten seconds.
One layout, your mark, your colours, three languages — and the language chosen by the client, not by the sender. Every system letter arrives looking like it came from a company, not from a script.
Registration, an invoice, a payment received, a project stage closed. The client learns about it from you at the moment it happens — which is most of what people mean by «they keep me informed».
What was sent, to whom, and what the receiving side answered. A refusal is visible immediately and by name — so the manager finds out about it before the client does.
A common signature for the studio and a personal one for each manager, with rights by section: an accountant does not need the design correspondence, and a contractor does not need the client base.
A mail reputation is built for years and lost in one week of careless sending. Everything below exists to make that week impossible.
Letters go to people who are in a relationship with you: a client, an invoice, a project. There is no «send to the whole base» button here, and its absence is the feature.
The mail provider's credentials live in your own installation and are never shown back — not in the browser, not in the panel, not to us. Changing them means writing new ones, not reading the old ones.
A letter that could not be sent is written into the log with the reason and shown in the panel. Silence about a failure is how a studio finds out from an angry client that it went quiet for a week.
Mail is a part of the CRM: letters have to attach to a client and a project, and there is no client card outside it.
For those who already keep their clients with us and are tired of two windows.
When nobody in the team wants to touch DNS — and rightly so.
When correspondence with clients is not allowed to pass through anyone else's servers.
The letters the studio sends already look the way this page describes. Turning that into mail a client runs themselves is what is left.
Outgoing letters in one layout, three languages, with a log: registration, invoices, project events, password recovery.
Incoming mail: the client's reply returns into the project thread, with attachments.
A shared inbox with rights, personal signatures, a template editor without a developer.
Deliverability reports, domain reputation monitoring, scheduled sending.
No. Whatever you already pay for stays — the CRM sends through it, on your own domain and your own keys. What changes is where the letters end up: in the client's card instead of somebody's personal inbox.
That is decided by the DNS records and by what you send, so we set the records up during onboarding and check deliverability before launch. Anyone who promises more than that is selling you something they cannot control.
No, and that is on purpose. This is transactional mail: it exists to keep a relationship going, not to reach an audience. Mixing the two burns the domain that your invoices depend on.
It stays on your domain and comes with you: it is your database and your mailbox. We hold neither the letters nor the keys hostage — that is not retention, it is a reason to be spoken badly of.
Honestly — little. Everything valuable here comes from the letter knowing which client and which project it belongs to. Without a client card it is just another inbox, and you already have one of those.
We will show you the same letter in your own template, in three languages, with the delivery log — so you can see the difference on your own text rather than on a demo we prepared.