Custom projects

Automations and AI assistants for your practice’s specific processes.

We design tools to record enquiries, assign them to staff and prepare summaries, or connect CRM and practice management software where feasible. We start with one defined process, assess data and integrations, and build a pilot. Staff keep control of confirmations and exceptions.

ContentHierarchyContact
  1. The practice identifies a repetitive task or a manual handoff between tools.
  2. We design the interface, assess possible integrations and define the controls staff need.
  3. Staff test the project with sample data before any activation.

When it makes sense

A custom project for one specific front-desk task.

Some areas where custom development can make sense. Every project is assessed and activated after the analysis.

  • Integrations between the management software and the contact channels already in use.
  • Front-desk flows automated to fit the organisation of the practice.
  • Automations for repetitive, low-value tasks.
  • AI assistants configured on the real processes, with clear boundaries between logistics and clinical care.

How we work

The process first, then the technology.

The same careful method as the other solutions: no feature promised before understanding your context.

  1. Listening to the process

    We start from the concrete problem and the real workflow of the practice, not from a pre-packaged feature.

  2. Feasibility and boundaries

    We assess what makes sense and is compliant to automate, and where people stay in charge. If something does not make sense, we say so.

  3. Tailored project

    We design the solution on your tools and consent, in a modular way that can be activated in stages.

  4. Activation and measurement

    We start from a narrow scope, measure and decide together whether and how to widen.

Integration

Connect the practice’s tools and processes.

Many practices already use a CRM to record contacts, enquiries and conversations, and practice management software for diaries, records and documents. Integration means connecting permitted parts of these tools under clear rules, instead of copying information by hand.

Four common gaps, and how we would examine them.

  • Enquiries arrive by phone, messaging, email and website form, and are recorded in different places.

    Our approach. We check what the practice software actually offers: an API, permitted exports or no usable connection. We connect what can be brought into one queue; any step that cannot be connected remains manual and is documented.

  • Reception reconstructs the context before replying: who the person is, what they asked and what they were told.

    Our approach. Automation prepares and suggests. It may match an enquiry to an existing record if the software permits it, and show previous exchanges. A person retains confirmation, exceptions and any changes to practice management records.

  • Reminders leave one tool while replies arrive in another, without a reliable link between them.

    Our approach. If the channel and CRM permit it, and the conditions of use have been checked, reminders and replies may be linked. Reception reviews replies and handles changes. Anyone interacting with an automated system must be able to reach a person.

  • No one has a shared view of open requests, pending confirmations and gaps in follow-up.

    Our approach. A periodic summary could show open, confirmed and unanswered enquiries. Ongoing monitoring and maintenance when suppliers change their systems are separate from the initial project.

A closed practice management system, supplier contracts that prohibit connections, missing permissions for a proposed data use, or unreliable source information may limit the project. No automation can repair bad source data on its own. If an integration does not make sense, we say so.

Illustrative example

How an enquiry could move from arrival to report.

Enquiry

Someone writes or calls. The request is captured through a channel the practice has chosen to connect.

Recording

The CRM records the channel, date and stated reason. If the management software exposes the needed data, the contact may be matched to an existing record; otherwise reception does the matching.

Assignment

Agreed rules suggest the right person, perhaps by location or service. The practice decides those rules; the system does not.

Confirmation

Reception confirms and updates the diary. In an initial project, the system does not write to the management software; at most it reads availability, if that access is permitted and verified.

Reminder

If the channel is available and conditions are met, a service reminder may be sent. Replies reach the CRM only if that connection has been tested; otherwise reception handles them in the original channel.

Report

A periodic summary of open, confirmed and unanswered requests, using agreed operational measures. It informs decisions without replacing daily review.

Illustrative workflow, not a ready-made product. In the initial project the system does not write to practice management software. It may read availability only if permission and capability have been verified. Reception remains responsible for confirmations and exceptions; people know when they are dealing with automation and can ask for a person.

Proposed deliverables

What we would propose for an integration project.

These are items to agree during assessment, not a contractual commitment. The actual scope depends on the software and the decisions of the practice.

  1. Process map

    Where an enquiry moves between people and tools today, and where it loses its owner.

  2. Integration assessment

    A written check of what each tool exposes and what can really connect, with rules, channels and responsibilities agreed before activation.

  3. Agreed configuration

    Settings for the approved workflow and, only where feasible, authorised connections between tools, with human involvement at the agreed steps.

  4. Tests and documentation

    Workflow tests with synthetic cases, never real patient data, before daily use; a plain-language description of what the system does, does not do and who handles exceptions.

  5. Training and monitoring

    Sessions with reception and tool owners; agreed checks on what works and what needs correction.

Before starting

Is your practice ready to connect AI, CRM and management software?

Five yes-or-no questions to identify a sensible first step.

  • Have we chosen one priority process, such as appointment enquiries?
  • Do we know which tools serve that process, who administers them and whether connection access can be obtained?
  • Is the information in those tools accurate, or does it first need to be cleaned up?
  • Is there a named person in the practice who can make operational decisions about the process?
  • Do we know the purposes, lawful grounds, consent where relevant and roles for the data use, and who notices and handles a failure?

If all five answers are yes, describe that process in the form. If several are no, start with a process assessment. Request an assessment.

The same boundaries

Custom does not mean without rules.

No promise of results

We propose a project and measure it. We do not guarantee numbers and we do not sell ready-made software.

Clear clinical boundaries

Automations on logistics and organisation. Diagnosis, triage and advice stay with the people of the practice.

Privacy and consent

The practice and relevant professionals assess actual roles, data uses and applicable conditions before activation.

Frequently asked questions

Questions about custom projects.

Do you already have ready-made software to install?

No. Custom development starts from the process of the practice: analysis first, then design. We do not start from a one-size-fits-all package, but from what you actually need.

How much does a custom project cost?

It depends on the scope and complexity, which we define after the assessment. That is why we do not publish a fixed price list: we propose only what makes sense, with clear terms before starting.

Does a custom project also respect clinical boundaries and privacy?

The proposed work stays organisational and does not make clinical decisions. Before activation, the practice and relevant professionals assess the data, actual roles, applicable conditions and controls.

Do I need to replace my practice management software?

That is not a decision to make before checking the current software. If it allows no connection, we consider permitted exports, manual steps or a smaller project. Replacing it is a separate practice decision with its own costs and risks.

Where should we start?

With one small, frequent process in which enquiries or staff time are being lost. Appointment enquiries are one possible starting point. A narrow scope lets the practice measure and correct the process before considering expansion.

What if an integration is unavailable?

We document the limitation and adapt the scope. Some steps remain manual, or the project becomes smaller. We do not promise connections that the software or supplier does not allow.

Who checks replies and updates?

The people in the practice. Automation can prepare and suggest; reception handles confirmations, exceptions and changes to practice management records under agreed rules. Clinical matters stay with qualified professionals.

Custom development

Tell us the need of your practice: we start from the problem, not from a package. If a standard module is enough, we tell you.

What happens after you submit

  1. We read your request and classify it by the priority you indicate.
  2. We call you back to clarify context, priorities and next steps.
  3. We assess together whether and how to proceed. No commitment.

We use your data only to handle the request, under the Privacy Policy. No promise of results.

Tell us the need of your practice

Fill in the form: we call you back to understand the process, assess feasibility and propose the most sensible path. No commitment.

Describe organisational processes only. Do not include patient or client names, diagnoses, test results, case details or confidential documents.