CRM and Business Systems
Custom CRMs and business systems built around your company’s processes: client portals, e-document workflows, billing, booking, and routine automation
Custom CRMs and business systems built around your company’s processes: client portals, e-document workflows, billing, booking, and routine automation
A CRM is not a contact list in a spreadsheet. It’s your business processes, translated into code
For over 18 years I have been building digital products — websites, eCommerce platforms, web apps, CRMs, bots, and AI agents. And for years I have seen the same pattern: a company buys a “universal” CRM, then breaks its own processes to squeeze them into someone else’s box. I do the opposite. First I dig into how your business actually works — who interacts with whom, where documents are born, how money moves. Only then do I design a system that mirrors those processes: client accounts, team roles, document workflows, billing, and routine automation. The foundation can be WordPress or a custom engine — I pick the platform for the task, not the other way around.
My client portal Clients is a client dashboard plus an admin back office. Ninety-one modules. Invoices and acts are generated automatically, signed with a qualified electronic signature under the DSTU-4145 standard, and delivered to the counterparty via Vchasno.EDO. LiqPay and MonoPay payments arrive as webhooks with signature verification — no “send me a payment screenshot”. I use this system every day, so I know exactly where it hurts and what to automate first.
Depending on the task, a business system is assembled from different subsystems:
client accounts and team roles with granular permissions
document workflow: automatic invoices, acts, digital signing
billing: online payments, plans, wallets, PDF invoices
booking, calendars, and online scheduling
notifications and integrations: email, SMS, Telegram, payment APIs
All of this is not a pile of plugins — it is one system with one logic and one source of truth.
An off-the-shelf CRM offers “best practices” — in reality, someone else’s processes. I build the system around yours:
fields, statuses, and pipelines that are yours, not “like everyone’s”
roles and permissions that match your real team structure
automation of exactly the routine that eats up hours
reports and dashboards with the numbers you actually track
When the system mirrors the process, the team does not “learn the CRM” — it just works.
Most of the routine lives in documents and payments. In the Clients portal I automated it end to end:
invoices and acts are generated automatically as PDFs — including the amount in words
documents are signed with a DSTU-4145 qualified signature and sent via Vchasno.EDO
LiqPay and MonoPay payments are recorded via webhooks with signature verification
every email and payment leaves a trace in the logs
Accounting routine that used to take hours comes down to a few clicks.
A business system is not only about sales. A few examples from my projects:
Clients Express — a multi-tenant CRM with online booking: a drag-and-drop calendar, a wallet, automatic proration on plan changes, PDF invoices
Skyta — tour booking with online payments and a loyalty program
Mytar — a Telegram bot that controls access to a paid group with payment moderation
Different businesses — different systems. What they share: the routine is done by code, not by a person.
businesses that have outgrown spreadsheets and chats
companies whose processes do not fit into boxed CRMs
services that need online booking, billing, or a client portal
Examples of implemented solutions can be viewed in the portfolio section or learn more about other services.
A custom CRM is not “yet another app” — it is an asset that grows with your business. You work with me directly: consulting, architecture, and development — no middlemen. If your processes no longer fit into spreadsheets and boxed solutions — drop me a line and we will map out your system together.