ITLine develops custom back-office software for small practices and service businesses: who comes when, what came of it, what has been invoiced and what is outstanding, on one screen. Not an enterprise system, but software sized to how the business runs today, next to the invoicing tool it already uses.
A practice or service business of a few people. The calendar is in the phone, invoicing on a website, and what each person asked for is in a notebook. Nothing is wrong on its own. Together, though, nobody can see what happened last week.
A full business management system is too big a coat for this. The need is the same, only the size differs.
One interface holding this much: who is coming when, what came of it, what has been invoiced and what is left. No more. Extending it later stays possible, but you do not pay for that up front.
This branch exists separately because whoever is looking for it walks away at the sight of the word "ERP", and rightly so. It is not the same job.
Appointment, treatment history, invoicing: in three separate places. The designed interface brought them onto one screen, in the practice’s own vocabulary. The quotation was completed, with a working clickable sample.
Working-time records and the settlement that goes with them, alongside the existing invoicing tool, not in its place.
Less than a business management system, because there is less process: one screen, a few views. We state the timeline after the first one-hour conversation and the survey. For one healthcare practice a working, clickable prototype came with the quote, so they could see what they would get.
Today’s price only pays for what is needed today: extensions can come later. The quote is for a fixed scope; how it is put together is described here: What it costs.
Yes. Invoicing can stay where it is; the back-office screen is built next to it and feeds it data. It replaces the calendar and the notebook, not what already works.
An hour at the start about where you keep things today (calendar, invoicing tool, notebook), and a few real examples: a week of the calendar, an invoice or two, a typical client’s path. The specification is built from these, and a clickable prototype too if it helps you decide.
For a practice this is the first question, and a fair one. Where the system runs and who can access it is decided with you at the survey; the details (a GDPR data processing agreement) are settled by contract. With health data this also shapes how the system is built.
Only where it genuinely saves work, for instance when processing an incoming e-mail or note. What the machine reads uncertainly it does not guess; it asks for approval, and no invoice or appointment goes out without a person having seen it. How we measure this: How we work.
We do not build a CRM, marketing automation or a reporting module in here, because you did not ask for one. If you need it later, it can be added, but today’s price should not be paying for it.