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.
Management Systems
Who may do what and when, which rule runs on its own, and who can see which record: all three are written when the system is built, so your team is not settling the same question again every week.
A management system is the internal tool that holds a business's operating rule, capacity limits and entitlement balances in the record. The rule is written when the system is built, not during the day: what a situation does to a balance, how many people an hour takes, who may see which record. At Pilatesco a cancellation, a no-show and a completed session each hit the package balance differently, and nobody decides on the spot.
At Pilatesco capacity is not one number. How many people an hour can take is worked out from the instructor, the equipment and the time together. A one-to-one session opens under a different rule from a group class, the same reasoning that keeps an appointment and a service request from sharing one form. A full hour reads as full on the calendar. What a cancellation does to the entitlement, and what a no-show does instead, is settled in advance rather than in the moment.
In the dental clinic CRM the manager reads where a patient has reached in the plan from one screen. The plan is not pulled from the calendar, the invoice from a ledger and the month-end picture from somewhere else again; the report is the day’s records read from another angle.
At AlgoCar the day’s work moves along a single chain. A job stays on the same record from the moment it opens to the moment it closes, so nobody has to ask where it got to.
All three follow the same order. The rule is written first, and the calendar, the invoice and the month-end report read it afterwards. Change the rule where it is written and every screen reads the new version, without the calendar and the invoice being corrected one by one.
The boundary is worth stating. A management system looks inward: the rule, the capacity, the permissions and what each role can see. The relationship with the customer itself belongs to the CRM page; the stock movement and invoice that come out of a work order to the ERP page; measuring recurring work that has a closing record to the process tracking page. All four can meet in one system, but their scopes are discussed separately.
We work on one technical footing, and it is the footing under our own products too. AlgoCar and AlgoKlima are our own products and both are live; we do this kind of maintenance every day in our own panels, and your system stays with the same team.
Six places where a rule written in advance earns its keep:
What each situation leads to is defined in advance. At Pilatesco a cancellation, a no-show and a completed session each hit the entitlement differently, and nobody decides on the spot.
How many people an hour holds is worked out from the instructor, the equipment and the time together. A one-to-one session and a group class open under their own rules.
At AlgoCar a job moves along one record from the moment it opens to the moment it closes. In the dental clinic the manager sees which step of the plan a patient has reached without leaving that screen.
Vipkurum keeps timetables, classes, exams and payment records in one place, and a teacher, a guardian and an administrator each reach that record at their own permission level.
The month-end picture does not require a second set of books; it is the sum of what was recorded during the day.
AlgoCar and AlgoKlima are our own products and both are live. We do the maintenance on software of this kind every day in our own panels, so it is not a promise we make for after handover.
Every project goes through the same four stages: planning, architecture, modelling, development.
See our process
Our own workshop software, built around the car on the ramp. A work order, the parts it consumes and the invoice it produces run as one chain, and the accounting side hangs off that same record. Maintenance history lives on the plate and chassis, so it travels with the car.
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.
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.
The request names a screen, but the list of questions is what is missing. Read the three lines that belong under an indicator, and the third one that never appears on screen.
OCR reads the letter shapes in an image and returns text. Which reading a job needs follows from the document: letters, a mark with a fixed place, or a region to separate.
The word automation covers a factory line as readily as a piece of business software. What a business owner is asking about is narrower: one step leaving somebody's hands.
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.
ERP stands for enterprise resource planning. Whether a business needs one, though, shows up somewhere else: in how many separate programs the record of a single job has to pass through today.
Hand a spreadsheet to a software team and only part of it can travel: some columns are typed data, some are formula results, and some have no counterpart in the old tool at all. Which is which?
The quote is in; the budget will not carry the list. Which line can you drop and lose nothing, and which one forces a rebuild later? The test is not price: is the line a record, or a reading of one?
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.
The difference is in what each one holds. A CRM holds the flow of your relationship with the customer: the step in the plan, the entitlement left, the history of the service. A management system holds the rule that governs that flow and decides who sees what. The dental clinic CRM keeps where a patient stands in the plan on the patient record, and the month-end figure a manager reads comes off that same record. The dental clinic case below shows both on one record.
You can, provided the rule was defined as a record from the start. What a cancellation does to the balance is then a setting you edit rather than a release you wait for. Pilatesco holds what a cancellation, a no-show and a completed session each do to the package balance, so nobody settles it again in a message thread. One limit is worth naming: a rule buried in code still needs a release. AlgoRandevu is the product we are building now to keep rules of this kind as product settings.
They can, each team reading the same record for its own job without opening a second program. What you get is one job entered once: the workshop and the accounts office stop keying the same work in twice and matching it at month end. AlgoCar ties the service side and the commercial side to the same vehicle record, so the work order, the parts used and the invoice move along one chain. The vehicle service case below shows how those two share one record.
We do, the same people who built it. That spares you a second supplier for maintenance and a search for someone willing to take over the code. AlgoCar is our own product, it is live, and it is still taking new features today; we do the maintenance on software of this kind every day in our own panels. After go-live you keep talking to the same team, and nothing is handed to a third party.