A request arrives from your site, becomes a proposal, becomes a project with a brief and a chat, and ends with a payment — without ever leaving one window. We built it because we needed it ourselves, and we run our own studio on it every day.
Not on rates and not on taxes. On the seams between the tools — the places where information has to be carried from one to another by a human being who is also doing the actual work.
A form on the site sends a letter, the letter lands among forty others, and by the time someone answers, the person has already written to a competitor. The lifetime of a warm lead is measured in hours, and an inbox does not know that.
What exactly was promised, for how much and by when is scattered across Telegram, WhatsApp and two mailboxes. Six weeks later the client remembers one version and you remember another — and neither of you is lying.
The advance came to a card, the second payment to an account, the third was a discount agreed in a call. The balance lives in a spreadsheet that one person maintains — and asking a client for money you cannot prove is how relationships end.
Four steps, and none of them requires copying anything from one place to another. Each one leaves the trace the next one needs.
Not just a name and a phone number: what pages the person read before writing, where they came from, what they answered in the brief. The manager opens the card already knowing what the conversation is about.
Scope, price and deadline are assembled in the panel and open in the client's browser. You can see that it was read, and correcting a figure does not mean sending «version 4 final» after it.
The brief, the files, the stages and the correspondence with the client are one object with one history. A new person on the team reads it instead of asking everyone where things stand.
The client pays by card in their cabinet, and the operation lands in the project's history without anyone typing it in. The balance is the sum of the operations, so it cannot disagree with them.
Everything listed here works today — the studio runs on it. The list is deliberately short: a CRM nobody fills in is worse than a notebook.
Every request from the site with its source, its correspondence and its status, from first contact to signature. You can see where they stop — which is the only number that tells you what to fix.
On your own site, in your own colours: their projects, their documents, the chat with the manager, their balance and payment. A client who can look things up himself asks fewer questions and trusts more.
Invoices, card payments through AmeriaBank vPOS, crypto to your own wallets, and a ledger where the balance is the sum of the operations. The bank confirms a payment, not the redirect the browser came back with.
Traffic, geography, devices and the path of a single visitor — and when that visitor later registers, the earlier visits attach to their profile. You stop guessing which channel brought the client who paid.
Task boards you can switch between, studio mail, documents attached to the project rather than to somebody's disk, and lead search built on 2GIS for the weeks when the funnel is thin.
The AI assistant, the site chatbot, mail and payments connect as modules, each with its own keys and its own switch. Keys are stored, never shown back — not even to you, not even in the browser.
A CRM holds the two things a studio cannot afford to lose: the correspondence and the money. Both decisions below were made against convenience, on purpose.
Staff and clients are two separate circuits with different tokens. No endpoint takes an account identifier from the request — it is always resolved from the session, so no address bar can be edited into somebody else's project.
After the payment page returns, the status is read with a merchant request to the bank, not from the redirect parameters — those are not signed by anyone. Without bank keys the system says payments are not configured instead of crediting money that never arrived.
Docker, PostgreSQL, one command. Your clients' correspondence and your revenue figures do not live in someone else's account under someone else's terms, and taking a backup does not require asking permission.
A designer does not need the finance screen and a contractor does not need the client base. Access is granted per section, and the same rule is enforced on the server — not only hidden in the menu.
Three ways in, depending on whether you want us to run it or you want it standing on your own hardware.
For a team that wants to start on Monday and not think about servers.
For those whose client data is not allowed to leave the building — by policy or by conviction.
When the studio has its own way of working and bending it to fit a box would cost more than changing the box.
The system has been running the studio for months. What is ahead is turning it from our tool into someone else's product — which is a different job entirely.
In daily use: requests, proposals, projects, client cabinet, payments, analytics, boards, mail.
Closed alpha: the first outside studios, with setup and data migration done by us and a weekly call with each of them.
Self-service: sign-up without us, your own fields in the project card, a monthly report for the client.
Beta: recurring subscriptions and acts, deeper analytics on where deals die, mobile view for the team.
Only if the client cabinet and the money matter to you. Most CRMs manage a sales funnel and stop there — the project, the correspondence with the client and the payment live elsewhere. This one is built around the seam between them, and that is the whole reason it exists.
Through a proxy on your own domain: the browser only ever talks to your site, the session token lives in a cookie that page scripts cannot read, and the CRM address is never exposed to the visitor. If your site is on Next.js it is a copy of one file; for other stacks we do it during onboarding.
Yes — AmeriaBank vPOS is connected and working, on your own merchant contract with your own keys. Crypto goes to your own wallets, without an intermediary: the client sends the hash, and a manager credits the amount they actually see in the network. We do not invent exchange rates.
You take them with you. It is a PostgreSQL database — a dump on request in the Studio plan, and simply yours from the start in the self-hosted one. Data held hostage is not a retention strategy, it is a reason to be spoken badly of.
The panel and the client cabinet are in Armenian, Russian and English, and each person picks their own. For us this is not a localisation project but a habit: the whole platform has been built in three languages from the first day.
Tell us how a client reaches you today and what happens between the first message and the payment. We will show the same path inside the panel — on your own example, before any decision.