Appointments + payments + client file: the practice (medical, technical, legal) that still looks like 1998

Three tools that don’t talk to each other

Walk into a lot of professional practices — medical, technical, legal — and under the varnish you find the same scene: a practice that in 2026 works like a company from 1998. Not because the tools are missing: on the contrary, there are too many of them. There’s an app for the appointment calendar. There’s another tool (or a POS, or a bank) for payments. And there’s a third place — a folder, an archive, a physical drawer — for client documents. Three tools, three islands, and the whole problem sits right there: they don’t talk to each other.

The result is a practice that, from the inside, is a continuous manual pour between the three islands. The receptionist takes the appointment in the calendar, then when the client pays they record it somewhere else, then they look for the documents in a third place, then they copy the data from one system to another. Every client crosses three systems that don’t communicate, and the glue holding them together is people’s time and memory. While the practice is small, it holds. As it grows, every day becomes a race of manual pours, with the inevitable errors: the appointment without the document ready, the payment that doesn’t show up, the datum copied wrong.

The conceptual error at the root is this: thinking a practice is three separate things — a calendar, a till, an archive — when in reality it is one thing. The client who books an appointment, who pays, who has a file with their history, is the same client: appointment, payment and documents are three faces of the same relationship, not three worlds. Treating them as three disconnected SaaS tools is what creates the manual pour, the errors, and that feeling of a “old” practice even when the tools are new. Real software for a practice is not “the calendar + the payments + the archive”: it is one product where the three things are tied because the client they refer to is tied.

This article is for whoever runs a practice and feels that race: we talk about how the three islands become one product, what the client file actually is, how calendar and till have to add up, the portal that makes the phone stop ringing, what’s sensitive when the data is health or legal, and — honestly — when a ready-made vertical is enough and when you need to build. And above all: how to do it without stopping the practice, because a practice cannot close to “migrate to the new system”.

The client file: documents, consents, history in one place

The heart of a professional practice is not the calendar: it is the client file. That’s where the real value lives — the history of that client, that patient, that case: what was done, when, with which documents, with which consents, with which outcomes. A calendar tells you when you see the client; the file tells you who they are and what’s between you. And in too many practices the file is still scattered: some on paper, some in a computer folder, some in emails, some in the professional’s head.

What it has to contain, in one place and tied to the client:

• The documents. Everything that concerns that client: reports, opinions, contracts, deeds, appraisals, correspondence. Not in ten different folders with improbable names, but collected in that client’s file, findable in an instant. I wrote about this talking about finding company documents without searching for hours: the value isn’t archiving, it’s having the right document at the right moment.
• The consents. In a practice, consents (to data processing, to the services, to the terms) are not bureaucracy to keep in a binder: they are part of the file, they have to be collected, kept, and findable when you need them. A consent you can’t find when you need it is a serious problem, not a nuisance.
• The history. The sequence of what happened with that client over time: past appointments, services delivered, payments, communications. The history is what lets you arrive at the appointment knowing who you’re dealing with, instead of reconstructing from scratch every time.

When the file is one and complete, the way of working changes: you arrive at the client with everything in front of you — who they are, what you’ve done, which documents, which consents, what they’ve paid — without searching for anything. When instead it’s scattered, every client is a small treasure hunt before you can serve them, and every treasure hunt is lost time and risk of error (the document not found, the missing consent, the forgotten history). The single file isn’t an organisational luxury: it’s the base on which the quality and the safety of a practice’s work rest.

Calendar and cash: if they don’t add up, it’s chaos

The other two islands — the calendar and payments — have a specific problem when they’re separate: they don’t add up. And when a practice’s calendar and till don’t add up, it isn’t an accounting nuisance: it’s operational chaos that costs you money and peace of mind.

Think about what happens when appointments and payments live apart:

• Services delivered and not collected. The client comes, receives the service, and then — in the pour between calendar and till — the payment slips through. Nobody ties “this appointment” to “this payment”, and at month-end you discover certain services don’t show as paid. In a practice where services are many and payments fragmented, that hole is real money lost in the void between the two islands.
• You don’t know who owes what. Who paid in advance, who has an open balance, who has a package of sessions with how many still to go: if calendar and till don’t talk, this information doesn’t exist in one place, and you reconstruct it by hand every time you need it.
• The deposit that protects the appointment. Tying payment to the appointment allows precious things: asking for a deposit at booking (which, as with any agenda, cuts no-shows — whoever has put money down shows up), managing session packages, knowing at a glance every client’s financial situation.

When calendar and till are the same thing — the appointment that carries its payment status with it — the practice knows, without reconstructing anything: what was done, what was paid, what’s missing. This is the same principle I described talking about the multi-operator professional calendar: for whoever sells time and services, the agenda isn’t an accessory, it’s where revenue is born — and if the till isn’t hooked to the calendar, revenue gets lost in the holes between the two. Making calendar and till add up isn’t order for the sake of fussiness: it’s stopping giving away uncollected services and navigating by eye on clients’ financial situation.

The portal: the client who doesn’t call for a PDF

There’s a piece that transforms the practice in the client’s eyes and at the same time frees the practice from a mountain of repetitive work: the client portal (or patient portal). It’s the area where the client, on their own, does the things that today require a phone call and the intervention of someone in the practice.

Think how often, in a practice, the phone rings for things the client could do themselves:

• “Can you send me that document / that report / that invoice again?” Every request for a document is a person in the practice who stops working, looks for the file, sends it again. With a portal, the client accesses their area and downloads their documents when they want, even on Sunday evening, without making anything ring. The client who doesn’t call for a PDF is time given back to the practice.
• “I’d like an appointment.” Booking, moving, cancelling from the portal instead of on the phone in opening hours. The client books when they think of it (and whoever books in the moment they think of it is captured revenue, instead of the “I’ll call tomorrow” that gets lost), and reception no longer acts as a switchboard.
• “I need to pay / sign a consent.” Paying online, signing consents digitally, filling in the forms before coming: things that take friction off the client and work off the practice.

The portal does two things at once, and that’s why it’s worth so much: it improves the client’s experience (they have access to their things when they want, without depending on the practice’s hours and availability) and it frees the practice from the repetitive work of acting as a go-between for every document, every appointment, every payment. It’s exactly what distinguishes a practice that “looks like 1998” (where for everything you have to call and wait for someone to deal with it) from a modern practice (where the client is autonomous on what concerns them). And to work, the portal has to be tied to everything else — to the file (for documents), to the calendar (for appointments), to the till (for payments): which is again the point of the whole article, one product and not three islands. A portal disconnected from the rest is just one more island.

What’s sensitive: health and legal data, in owner language

A professional practice handles data that is, often, among the most sensitive that exists: health data in a medical practice, highly confidential information in a law firm, sensitive personal and technical data in a technical practice. I’m not a lawyer and this isn’t legal advice — it’s the common sense of someone who builds these systems and knows where you get hurt. But precisely because the data is sensitive, some things have to be kept in mind as an owner, without needing to be an expert.

• Who accesses what. Not everyone in the practice needs to see everything. A patient’s health file, the confidential details of a legal case: the people who need to, for what they need to do, access it. A serious system has the right permissions from the start, and keeps a trace of who saw what. This isn’t bureaucracy: it’s protection for you and for the client, and it’s what lets you sleep at night keeping important data in a system.
• Where the data sits and who custodians it. Data this sensitive cannot sit in just any place, managed by who-knows-who. You have to know where it is, that it’s safe, that there are copies, and that nobody outside those who must can put their hands on it. With ready-made vertical software, this depends on who supplies it to you; with a system of your own, you have control — and it’s one of the reasons certain practices prefer the second road.
• Consents as part of the system. As said for the file: consents to data processing are not a form to sign and forget, they are a living part of the system — collected, kept, findable, and tied to the client.

The owner’s point is: the sensitivity of the data is not a reason to stay in 1998 (paper, scattered folders, everything in the clear on anyone’s computer) — on the contrary, it’s the reason the old way is more risky, not less. A paper file in a drawer, or health files in a folder shared with the whole practice, are less safe than a system with serious permissions and traced access. The rest — the formal details, the notices, the specific obligations of your sector — you see with your advisor. The software only has to make it easy to do the right thing and hard to do the wrong one: sensible access, traces of who sees what, data custodied as it should be.

What AI can do, and what it can’t

The practice too will get people selling “the AI that does everything”. It’s worth being precise, because here — with health and legal data — the error is particularly dangerous, and the boundary has to be held firm.

Where AI really helps, on the repetitive work:

• Drafts of communications. The letter to the client, the appointment reminder, the standard communication: AI throws down a draft in a few seconds, which the professional rereads and sends. Time saved on mechanical work.
• Classification and order of documents. AI can help put things in order: understand what type a document is, suggest its place in the right file, make findable what you need. It’s the boring work of keeping order, where AI gives a real hand.
• Finding the information in the file. As with search on documents, AI can answer “where’s that document, what does that report say” citing the source — finding it in the real material, not inventing.

Where AI must not arrive, ever, in a practice: the professional decisions and the judgements that are your craft. AI does not make the diagnosis in the doctor’s place, does not give the legal opinion in the lawyer’s place, does not sign the appraisal in the technician’s place. Those are professional responsibilities that stay with the person, period — both for obvious reasons of competence and liability, and because a language model is not reliable where an error has serious consequences. The rule is the same I hold everywhere, but here it weighs double: AI prepares, orders, finds; the professional decides. AI takes off the mechanical work that smothers the professional’s time, so that time concentrates where their judgement is needed. Whoever sells you “the AI that does the diagnosis / the opinion / the assessment” in a practice hasn’t understood that there the value is the professional responsibility, and it’s exactly the part you don’t delegate.

Vertical SaaS or custom?

A practical and honest question, the one that decides the spend: do I take a ready-made vertical for my type of practice, or do I have it built to measure? I tell you this as someone who lives on custom, so listen because it goes against my immediate interest: very often the ready-made vertical is the right choice.

Ready-made is enough when:

• A good software made specifically for your type of practice exists (practice management for medical practices, for law firms, for technical practices — there are excellent ones), and your needs are the standard ones of your category.
• You want something that works immediately, maintained by others, without having to think about it.
• You don’t have particular needs that fall outside the standard of your sector.

If you’re in this case — and many practices are — buy the vertical software, and you’re sorted. Don’t have built from scratch what already exists done well for your profession: that would be throwing money away. Ready-made covers 80% of practices with standard needs, and that’s right.

You need custom when:

• You have a particular way of working that vertical software doesn’t follow, and they force you to bend the practice to their logic instead of the other way around.
• You have to integrate things that vertical software keeps separate, or connect to systems of your own.
• You want full control over sensitive data and over the system, which with a vertical supplier you don’t have.
• Your practice is large enough or particular enough that the vertical is too tight, or that the cost per seat/feature exceeds that of having the tool of your own.

The rule is the usual one: ready-made covers the standard 80%, custom is for the 20% of your own needs that are worth the money they’re worth. If you’re in the 80%, take the vertical and be happy. If you have the 20% of particularity that distinguishes you — or if ready-made forces you to work in a way that isn’t yours — then it’s worth building. This honest reasoning on when ready-made is enough runs through the whole bookings and scheduling cluster: the goal isn’t to sell you software, it’s that you spend where it matters.

What the practice owner sees (and how much they recover)

Let’s put the pieces together from the point of view of whoever runs the practice, because that’s where you see the concrete return. When file, calendar and till are one product, the owner opens a screen and knows — they don’t “have a feeling” — how the practice is doing:

• The real till. What was invoiced, what collected, what’s still open, and — the detail that’s worth gold — the services delivered but not collected, the ones that today get lost in the hole between calendar and till. Let’s do a rough count: if in a practice with decent volume even a handful of services a month slip past collection because nobody ties the appointment to the payment, at year-end that’s easily several thousand euros of work already done and never paid. It isn’t money to conquer by selling more: it’s your money, already earned, that you’re giving away for an organisational hole. A system that ties calendar and till recovers it almost on its own.
• How full the practice is. The calendar seen as capacity: how much time is sold, which slots stay empty, where you could grow. For a practice that sells time and services, it’s the number that decides revenue.
• No-shows and holes. Who doesn’t show, what it costs, and whether the deposit at booking is cutting them.
• The clients’ situation. Who has a package running out to renew, who has an open balance, who hasn’t come back in a while and would be worth calling.

This is the same value as the dashboard that answers the real questions of whoever runs the place, applied to the practice: not a mountain of charts, but the few numbers that say whether the practice is running full and where it’s losing ground (and money). And these numbers don’t exist as long as the three islands are separate, because to calculate them you need calendar, till and file to talk. It’s the payoff that makes the investment not a cost but a recovery: you stop giving away uncollected services and you start running the practice on facts instead of by nose.

The piece-by-piece plan: digitise without stopping the practice

We arrive at the most concrete fear, the one that blocks many practices even when they’ve understood the old way no longer holds: “but I can’t stop. The practice has to keep working. How do I change everything without blocking everything?”. The answer is: you don’t change everything together. You go piece by piece.

The “big bang” — switching off the old and switching on the new all in one day — is the surest way to make a disaster in a practice: if something goes wrong, the practice stops, and a stopped practice is lost clients and chaos. The healthy way is one piece at a time, each of which carries a value in itself and doesn’t blow up the rest:

• You start from the piece that hurts most. What’s the manual pour that costs you most today? For a practice it’s often the file (scattered documents) or the calendar-till hook (uncollected services). You start there, you fix that, and you already feel the relief — without having touched the rest.
• You add the next piece when the first is solid. File sorted, you tie the calendar. Calendar tied, you hook the till. Then you open the portal to clients. Each piece grafts onto the previous one, when the previous one works and people have got the hang of it.
• Old and new coexist in the transition. You don’t switch anything off before the new piece actually works. The practice never has a void in which “you no longer know where the thing sits”: there’s always a system that answers, while you migrate calmly.

This phased approach is what makes digitising a practice bearable and safe instead of a leap into the void. People learn one piece at a time instead of being overwhelmed by everything together; the risk is split; and if a piece needs adjustments, you make them without the rest suffering. It’s the same principle of starting from a core and growing in phases that holds for every healthy software project: value arrives early (from the first piece) and risk stays small (because you haven’t bet everything in one blow).

If you have a practice that “looks like 1998” and you feel the race of manual pours, the first step isn’t buying the first software that passes nor remaking everything: it’s understanding which piece hurts most and starting from there. Look at the projects I’ve built or drop me a line and we reason it on your practice — including just to tell you “the vertical is enough for you”, if that’s so.

It’s for you if / it isn’t for you if

It’s for you if:

• you have a practice (medical, technical, legal, or similar) where calendar, payments and documents live in three separate places that don’t talk;
• the clients’ file is scattered between paper, folders and email, and every client is a small treasure hunt;
• you lose uncollected services in the hole between calendar and till;
• the phone rings constantly for documents, appointments, payments the client could handle on their own;
• you handle sensitive data and you want to keep it seriously, not in folders within anyone’s reach.

It isn’t for you if:

• you’re a tiny practice with few clients you manage well in your head: here a complete system is more weight than help;
• a ready-made vertical exists that covers your standard needs well: take it, don’t have built what already exists;
• your real problem is finding clients, not managing them: that comes first.

8 questions from someone who runs a practice

1. Why isn’t it enough to keep calendar, payments and documents separate as I do now? Because they’re three faces of the same client, and keeping them separate forces you into a continuous manual pour, with errors and things that get lost (uncollected services, documents not found). A practice is one product, not three disconnected SaaS tools: when the three things are tied, the practice knows without reconstructing anything.

2. What is the client file and why does it matter so much? It’s the heart of the practice: the complete history of every client in one place — documents, consents, history. It lets you arrive at the appointment knowing who you have in front of you and what’s between you, instead of searching every time. A scattered file is a treasure hunt before every client, with the risk of the missing document or consent.

3. What do I get from tying the calendar to payments? You stop losing uncollected services in the hole between the two, you know at a glance who has paid and who owes, you manage deposits and session packages, and the deposit at booking cuts no-shows. For whoever sells services, the agenda is where revenue is born: if the till isn’t hooked, revenue gets lost.

4. What is the client portal and what is it for? It’s the area where the client, on their own, downloads their documents, books or moves appointments, pays and signs consents — without making the phone ring. It improves the client’s experience (autonomous when they want) and frees the practice from the work of acting as a go-between for everything. But it has to be tied to file, calendar and till, not another island.

5. My data is sensitive (health/legal): isn’t it riskier to put it in software? On the contrary: paper in a drawer or files in a folder shared with the whole practice are more risky than a system with serious permissions and traced access. The sensitivity of the data is the reason the old way is dangerous, not a reason to stay there. The formal details you see with your advisor; the software has to make it easy to do the right thing.

6. Can AI run my practice? It can do the repetitive work: drafts of communications, classifying and ordering documents, finding the information in the file citing the source. It cannot and must not make the professional decisions — the diagnosis, the opinion, the appraisal — that are your responsibility and your value. AI prepares and orders; the professional decides.

7. Better a vertical or custom? If a good software for your type of practice exists and your needs are standard, take ready-made: it costs less and you don’t maintain it. Custom is needed if you have a particular way of working, you have to integrate systems of your own, you want full control over the data, or ready-made is too tight. 80% of practices are fine with ready-made; custom is for the 20% with their own needs.

8. How do I change without stopping the practice? Piece by piece, never with the big bang. You start from the pour that hurts most (often the file or the calendar-till hook), you fix that, then you add the next piece when the first is solid, with old and new coexisting in the transition. That way value arrives early and risk stays small, without ever a void in which the practice stops.