“If you can’t automate your own business — how are you going to automate someone else’s?”
Why does a developer need their own CRM?
There’s a category of tasks nobody ever asks you to do. Clients never say, “Build yourself a CRM.” The market doesn’t demand it. No deadlines are breathing down your neck. But deep down, a realization takes shape: either you bring order to how you work with clients, or you’ll drown in a chaos of emails, chats, files, and invoices scattered across a dozen services.
That’s exactly how clients.kaplia.pro was born — my client portal. Not out of an ambition to build “yet another SaaS,” but out of a simple operational need: one place where a client sees everything about their project, and where I stay in control of every process.
And yes, it’s WordPress. Custom development from scratch. No ready-made solutions. Because no off-the-shelf product covered even 60% of my needs.
The problem I was solving
Picture a typical day for a freelancer or a small studio. A client wants a backup of their website — you message them, send over a file or a link. Hosting needs to be paid — you draw up an invoice by hand, email the PDF, wait, double-check. They want access to the code — you send a GitHub invite. They need the admin panel — you dig through your notes for the password. A brief for a new project — a Google Form, or just “message me on Telegram.”
Each of these tasks is trivial on its own. But as the client list grows, the little things add up to operational chaos that eats your time and creates the risk of forgetting something, losing something, or sending something too late.
I needed a system where all of these processes live in one place. Not Notion, not Trello, not yet another “universal” CRM for $50 a month that does everything and nothing at once. My own system, tailored to my business processes.
What a client sees when they log in to the portal
First things first: logging in is dead simple. You sign in via email or Google One Tap — one click and you’re in. No passwords to remember. Cloudflare Turnstile handles security — invisible to the user, reliable for the system.
Once inside, the client lands in a personal space that gathers everything related to their projects:
Websites, domains, and email
The client sees a list of their websites, connected domains, and mailboxes. Each website comes with a quick-access button for the admin panel — the portal automatically detects the site type and, if it’s WordPress, pulls the current admin URL, even if it has been changed or hidden for security reasons.
Backups and code
Thanks to the Hosting Ukraine API integration, the client can download a fresh backup of their website and database at any time. No need to write to me, no need to wait — it’s all self-service.
There’s a separate GitHub API integration, too. The client can always grab the current version of the code I’m developing for them — a working archive of the repository, one click away.
Payments and invoices
This is where the portal starts closing a whole pile of legal and operational questions. LiqPay is built in, so clients can pay for hosting and domain renewals, as well as any additional invoices — right inside the portal, without a single external redirect.
For those who operate as a sole proprietor or an LLC and need an official invoice, the portal automatically generates a PDF invoice from the client’s details and emails it over. The client enters their information as an individual, a sole proprietor, or a legal entity — and the system produces a properly formatted document for payment by bank transfer.
The client sees their account expiration date, the cost of service, domain prices, and the full payment history. Everything is transparent, and everything is in one place.
Documents and access
Files can be attached to every client’s account: documentation, guides, logins, working materials. The client sees their own files — and only their own. Plus quick access to the Planka task manager, where the work on their project actually happens.
Brief builder
Right in the portal, a client can fill out a brief for a new website, or for a logo and brand guidelines. Under the hood is my own form builder and an API that serves those same forms to my main site kaplia.pro. One infrastructure, two interfaces — convenient for the client and for me.
Support chat
The portal runs a chat widget — my own build, based on a WebSocket connection through the Telegram API. The client types a message in the portal chat, and it instantly lands in my Telegram. I reply, and the client sees the answer in real time. Fast, convenient, no extra messengers. But the technical side of that chat deserves an article of its own.
An invite system: easy access for teams
Not every client is a single person. Often it’s a company where several people need access to one account. That’s what the invite system is for: a personal link — they click it, sign in, and access is granted automatically. No adding users by hand, no extra steps on my side.
Automatic reminders
The portal automatically reminds clients when a renewal is coming up — 14, 7, 2, and 1 day before expiration. No manual tracking, no Excel sheets full of dates. The system does its job — and I do development, not administration.
The legal side: everything official
The portal isn’t just a technical tool — it’s a full-fledged business infrastructure. The Terms of Use and Privacy Policy clearly govern every aspect, from personal data processing to refund terms.
Automatic invoicing with correct sole proprietor or LLC details, transparent pricing, official payment channels via LiqPay or bank transfer — all of it takes a major headache off my plate, and off my clients’. Their accountants get clean, understandable documents, and I don’t burn time issuing invoices by hand.
What’s under the hood
Technically, it’s a custom WordPress build. Not a ThemeForest theme, not a pile of plugins — an architecture that’s entirely my own, shaped around specific business processes. The API integrations that hold it all together:
- Hosting Ukraine API — backups, service information, statuses
- GitHub API — repository access and code downloads
- Telegram API + WebSocket — real-time support chat
- LiqPay API — online payments and automatic transaction tracking
- Cloudflare Turnstile — bot protection
- Google OAuth / One Tap — password-free sign-in
The portal is an abstraction layer between the client and the actual infrastructure. Deleting an account on the portal doesn’t touch websites, domains, email, or backups — they live on the hosting independently. The portal simply provides a convenient interface for managing it all.
Why WordPress and not something else?
A fair question. Why not Laravel, not Next.js, not some specialized framework?
The answer is simple: WordPress gives me a development speed and a depth of customization that are hard to find anywhere else. Its system of users, roles, hooks, and filters is a mature foundation you can build anything on. Plus, I know WordPress down to the last line of code. This is my home turf. When I need to ship a new feature or fix a bug fast, it takes me hours, not days.
The portal is living proof that WordPress in 2026 is far more than a “blogging toy.” It’s a platform you can build a full-fledged business system on — with a dozen API integrations, payment automation, real-time communication, and legally sound documentation.
What it changed in my work
Before the portal, my client communication looked like a patchwork quilt: Telegram here, email there, Google Drive somewhere else, invoices in Excel, backups on request. It worked — but always with friction.
Now a client logs in to the portal and has everything: their sites, backups, code, documents, payments, chat, brief forms. I don’t spend time on routine — the system runs itself. And I spend that time on what actually matters: the architecture and development of my clients’ projects.
And there’s one more effect I didn’t expect: trust. When a client sees that their contractor runs a system of this caliber, it works better than any portfolio. These aren’t screenshots of other people’s sites on Behance. It’s a real, working product they use every day.
More to come
The portal keeps evolving. Every new client request, every new integration is a reason to add something useful. There are plenty of ideas ahead — from advanced analytics to new ways of automating routine processes.
In the meantime — if you’re looking for a WordPress developer who doesn’t just “make websites” but builds infrastructure for your business, get in touch. Maybe soon you’ll be the one logging in to clients.kaplia.pro and seeing your account with all your services inside.
