The pieces and their boundaries are settled before code.
Several institutions, one system, records kept apart.
One codebase, both stores: iOS and Android.
We take a running system over and improve it.
AI only where the problem actually calls for it.
CRM
Keep track of customers, appointments, package balances and the history of the service you provide in one system, with the rules an off-the-shelf CRM cannot hold built in.
Our CRM development service brings your customers, appointments and service history into one system built around your business. Where an off-the-shelf CRM does not fit, such as a treatment plan spread over many sessions or classes sold in packages, we set the rules up to match how you actually work. The dental clinic CRM and the Pilatesco booking system were both built this way.
A custom CRM keeps what you know about your customers in the shape your business actually runs in. If a contact list and a calendar are all you need, an off-the-shelf CRM is usually the right choice. In clinics, studios and service companies, though, the information that matters most tends to live elsewhere: which session a treatment has reached, how many classes are left in a package, what maintenance a device has already had.
In the dental clinic CRM the treatment plan is built tooth by tooth and every appointment is attached to a session in that plan, so the calendar changes when the plan does. At Pilatesco the package balance sits on the customer’s card and goes down with each booking. At AlgoKlima the service history belongs to the device rather than the person. We explain why we keep appointments and service requests apart in a separate article.
A CRM project starts with where this information lives today: a spreadsheet, a notebook, a messaging app or a packaged program. From there we agree who sees what and which rules should run on their own, and at the end of each stage we try the working screens with your team. AlgoKlima is our own product, so we also know from our own work how a customer system grows over the years and what keeping it maintained takes.
These are the areas we scope a CRM project around; we choose together which of them your business needs.
A treatment or maintenance programme that runs over several sessions is kept as its own plan, separate from the bookings. In the dental clinic CRM the plan is built tooth by tooth and split into sessions spread over weeks.
Each appointment is attached to a step in the plan. When the plan changes or a session is added in between, the calendar updates with it.
When you sell classes or services in packages, what a customer has left shows on their card. At Pilatesco a booking takes one class off the package, and cancellations and no-shows follow different rules.
Warranty, maintenance and fault history for the equipment you service is kept against the device, not the person. At AlgoKlima three air conditioners at the same address keep three separate files.
When a device passes to someone else, its history stays with the device instead of being retyped onto the new customer's card.
The procedure sits on the customer's record, so what was billed and what was carried out are read from the same place and nothing is entered twice.
Every project goes through the same four stages: planning, architecture, modelling, development.
See our process
Treatment is planned tooth by tooth and split into sessions spread over weeks. An appointment is a scheduled step of that plan rather than an empty slot, so changing the plan moves the calendar. Invoices and reports come off the same patient record.
Our own product for HVAC, boiler and appliance service companies. The customer and device records the office works from are the same ones the technician carries into the field. A job can be opened and closed in a basement with no signal, and service history stays tied to the device.
Instructor, equipment and time slot together decide how many people a class can take. Members buy packages, so each reservation draws a credit off a balance, while cancellations and no-shows post to it differently. An invoice arises at the sale; usage is read from the calendar.
CRM is short for customer relationship management. What it has to hold in your business is not set by your industry but by where the weight of the relationship sits: before the sale, or after it.
The same question comes in daily; whoever reads the messages that day answers it. Whether a bot can take it depends on where the answer lives, not on its topic. No rule, and the bot improvises.
An appointment attaches to a place; a service request attaches to an installed unit or a plan. Three builds show which record carries that difference, and what breaks when none of them does.
An off-the-shelf product may well do, and if a contact list and a calendar cover your work we will tell you so. A custom CRM makes sense when rules specific to your business have to live in the system: which step of a treatment plan a patient is on, what is left in a package, or a device's service history. Put the steps of your service into the quote form and we can draw that line together.
Booking software keeps the time slot. A CRM also keeps which step of the customer's plan that appointment belongs to and what happened before it, so when the plan changes you do not have to fix the calendar by hand. If all you need is online booking, a narrower appointment system may suit you better.
The balance is kept on the customer's record, so nobody keeps a second count on paper. Your package goes into the system together with its cancellation and no-show rules, and you see who has how many sessions left on screen rather than in a message thread. Pilatesco takes one class off the package when a booking is made, while cancellations and no-shows are handled the way the rule defines.
No. Each device or file keeps its own history, and warranty, maintenance and fault details are attached to the device rather than the person, so a customer of yours with three devices has three separate files. AlgoKlima keeps air conditioners at the same address in separate files, and a unit that changes hands keeps its history.