01 · CLIENTS
One record per client
Contact details, history, documents, balances and notes in one place. Individuals and companies. Anyone on the team can pick up where a colleague left off.
02 · CRM
Generic CRMs are built for someone else's sales team: fields that don't fit, pipelines nobody updates, a bill per seat. We build the client system around your work: your services, your calendar, your staff rules and your clients' languages.
Why custom
A client calls, writes on Instagram, then on WhatsApp. The quote is in someone's email and the payment is in the accounting software. A CRM built for your business connects all of it, and shares one database with your stock and orders if you need an ERP later.
What we build
01 · CLIENTS
Contact details, history, documents, balances and notes in one place. Individuals and companies. Anyone on the team can pick up where a colleague left off.
02 · LEADS
Where the lead came from (phone, website, Instagram, Telegram, WhatsApp, referral), who owns it and when to follow up. A lead turns into a quote and an order without retyping.
03 · CALENDAR
Day and week calendar per staff member, drag to move, warnings on overlaps. Booking requests from your website land in the same calendar.
04 · FOLLOW-UPS
Nudges for quotes nobody answered, recall lists for repeat visits, and a review request after the job: happy clients go to Google Maps, unhappy ones reach you privately.
05 · PORTALS
Clients sign in with a link, no password, to see their orders, documents, bookings and invoices. Fewer calls asking where things stand.
06 · STAFF
Each person sees their own clients and nothing more. Commission and earnings rules per person, with monthly statements.
07 · MESSAGING
New bookings, payments and overdue work as Telegram alerts, and a morning summary for the owner. Client messages through WhatsApp.
08 · REPORTS
Revenue by staff, service and lead source. Debts, lost quotes, requests by channel. CSV export for the accountant.
Proof
Clinic · Go-live pending
Patients, calendar, treatment plans, lab orders, five staff roles, doctor earnings, review requests and Telegram alerts for the owner.
Dental clinic case study →Manufacturing · Pilot, retired
Leads by source with follow-up dates, site measurement visits, quotes with revisions, contracts and payments in one pipeline.
Window and door ERP case study →Retail · Live
Customer accounts with magic-link sign-in, carried over from Shopify, and one admin for orders, customers and staff roles.
Vape retailer case study →FAQ
Yes. Importing clients, history and balances from Excel or your old system's export is part of the build, checked with you before the switch.
Telegram works well for staff alerts and bots. For clients we use WhatsApp through the official Business API, which needs approved message templates, or a link that opens the chat with the text ready.
It runs next to it. Payments and invoices stay in sync with ArmSoft, HC or 1C, so the accountant keeps their tools and nobody types the same invoice twice.
You do. Your server or a cloud account in your name, full source code, and no per-seat licence for the software we build.
The staff interface in Armenian, Russian and English. Anything a client sees, such as quotes, consents and reminders, can be in their language, French included.
Pricing
Every build is scoped in a written spec with a price before we start. There is no licence per user: hiring more people does not change the bill.