"Custom" is one of those words that gets said a lot and understood very little. To some it sounds like an expensive two-year project. To others, like a spreadsheet full of macros that only its author understands. Almost everything interesting sits between those two extremes.
A custom solution, properly understood, isn't about reinventing your software. It's about building a small piece that fits the exact gap where your operations get stuck: between the inbox and the management software, between WhatsApp and the ERP, between the data you already have and the decision nobody makes based on it.
The six examples below are possible scenarios, not client cases. They include no savings figures, because any number that doesn't come from measuring your operations would be made up. What they do include is detail: exactly where the friction happens, which rules shape it and what the solution would look like step by step. The scenarios are set in Spain, so the regulations cited are Spanish and European. The references, checked on 29 September 2026, are linked at the end.
1. Accounting and tax firm: closing the third quarter
The friction. In Spain, third-quarter tax returns (forms 303, 130, 111 and 115, covering VAT, income tax prepayments and withholdings) are filed between 1 and 20 October 2026, and if the client wants the payment direct-debited, the deadline is the 15th. But the real work starts earlier: gathering every client's invoices for July, August and September. They arrive by email, by WhatsApp, as crooked photos or as a single PDF with twelve documents inside.
Having them isn't enough, either. To deduct input VAT you need a full invoice containing the details required by Article 6 of the Spanish Invoicing Regulation: the issuer's tax ID (NIF), date, taxable base, rate applied and VAT amount shown separately, among others. A till receipt (a simplified invoice) only counts for deduction if it includes the recipient's tax ID and address and shows the VAT separately. Checking all of that document by document in the final week is where the time goes, and where the "I'm missing the diesel invoice" calls come in.
The solution, step by step.
- A single entry point. One email address and one WhatsApp number for all documents. The system identifies the client by sender and, if it can't, asks them.
- Reading. It splits PDFs containing several documents and extracts from each one the issuer, tax ID, date, base, rate and VAT amount. It classifies each document as an issued or received invoice and assigns it to a quarter.
- Automatic checks. It validates the tax ID format, confirms the date falls within the quarter, detects duplicates (same issuer, same number, same amount) and flags documents that probably can't be deducted, such as a till receipt without the recipient's details.
- A dashboard per client. Complete, incomplete or with issues, and in each case the specific list of what's missing.
- Deadline-aware reminders. From 1 October, specific messages to each client ("we're missing your supplier invoices for August"). If something is still missing a few days before the 15th, the adviser in charge is alerted to call.
- A reviewed export. The validated data is exported in whatever import format the firm's accounting software accepts.
What it doesn't do. It doesn't file returns or decide on borderline cases (mixed-use expenses, whether a cost relates to the business). That judgement belongs to the adviser. And an honest caveat: once structured e-invoicing between businesses becomes mandatory, part of this reading will get easier. Until then, and for everything that still arrives as a photo, the problem exists today.
2. Law firm: the first consultation and conflicts of interest
The friction. The General Statute of the Spanish Legal Profession (Article 51) prohibits lawyers from defending interests that conflict with those of other clients or with their own. Checking this means cross-referencing the names of every party, including the opposing one, against the firm's database of clients and matters before taking on the case.
In practice, information arrives in fragments. The name of the opposing company appears on page three of an attached contract, not in the email. Dates that trigger deadlines are buried in the story: in a dismissal, for instance, the right to challenge it expires after 20 working days. And for certain transactions (property, corporate, fund management), the firm is also an obliged entity under Law 10/2010 on the prevention of money laundering, which requires formal client identification.
The solution, step by step.
- An intake form by practice area (employment, family, commercial), with the questions the lawyer always ends up asking: parties, key dates, amount at stake, available documents.
- Extraction of people and entities mentioned in the form and the attachments: opposing party, companies, directors.
- A cross-check against the firm's database, including closed matters, with fuzzy matching (variants of a name, the same tax ID under a different company name).
- Date detection for anything that may trigger a deadline, flagged as "to be verified", never as a calculated deadline.
- A one-page pre-meeting brief: summary of the facts, possible matches, documents provided and documents missing. Missing items are requested from the client before the meeting.
What it doesn't do. It doesn't assess the case or decide whether there's a conflict. It flags matches for the lawyer to review. And because of professional confidentiality, the choice of providers and where the data is processed are part of the design from day one.
3. Estate agency: leads coming in from property portals
The friction. Leads come in from several portals, each with its own format, into a shared inbox. Often they bring nothing more than a phone number and a standard message. What that person is looking for (area, price, bedrooms) stays in the agent's head or on a loose note. And when, three months later, a property comes in that would have suited them, nobody looks at that lead again.
On top of that there's an obligation that isn't always front of mind: agencies acting as intermediaries in property sales (and in rentals of 10,000 euros a month or 120,000 a year or more) are obliged entities under Law 10/2010 on the prevention of money laundering, with identification and due diligence duties as the deal progresses.
The solution, step by step.
- A portal email reader. It extracts the name, contact details, property enquired about and message, whichever portal it came from.
- An editable search profile. It infers criteria from the property enquired about and the message, and the estate agent corrects them in one click.
- A drafted first reply for the estate agent to review and send. If you decide an assistant should reply on its own (at night, say), since 2 August 2026 the EU AI Act has required that the person be aware they are talking to an AI.
- Reverse matching. When a new property is listed, the system shows the compatible past leads and when they were last contacted.
- A document checklist for identification and beneficial ownership once a deal reaches the offer stage.
What it doesn't do. It doesn't negotiate or value properties. The relationship with the buyer stays with the estate agent; the system simply stops leads getting lost in the inbox.
4. Clinic: the day's call list
The friction. Clinic management software stores a lot of useful information. A typical list of treatment estimates lets you filter by status (proposed, accepted, rejected), rejection reason, person responsible, financing status and follow-up actions. Add to that the pending periodic check-ups. The data is there. What's missing is turning it, every morning, into a short list of who to call and why.
Regulation matters here, and it pays to design with it in mind. Health data is a special category under the GDPR (Article 9), so the system should access only what is strictly necessary. And not all calls are the same: reminding a patient about a check-up or booking a treatment they have already accepted is care follow-up. Offering financing or a promotion is commercial communication, and since June 2023 Spain's General Telecommunications Law (Article 66.1.b) has required prior consent or another valid legal basis for such calls, according to the criteria in Circular 1/2023 of the Spanish Data Protection Agency (AEPD).
The solution, step by step.
- Minimal reading. Each day, only the necessary fields are read (estimate status, dates, rejection reason, last visit, pending check-up, marketing consent) from the reports the software already produces. Clinical records are not touched.
- Sorting into three groups. Accepted estimates with no appointment; overdue check-ups; estimates rejected for financial reasons. This third group only goes on the list if marketing consent is on record.
- A prioritised list with a short script for each type of call.
- Logging the outcome. What was discussed goes back into the software as a follow-up action, so the history stays where it has always been.
What it doesn't do. It doesn't replace the clinical software, decide on treatments or make calls on its own. If a voice agent is ever added, it will have to identify itself as an AI. And the provider handling the data signs a data processing agreement as a processor (Article 28 GDPR).
5. Distributor: orders that arrive in the customer's own words
The friction. Customers don't order "item 40213, twelve boxes". They order "the usual, but double the small ones" by WhatsApp at seven in the morning, leave a voice note or forward last week's order with changes. Someone translates all that into codes and quantities in the ERP, and that translation is where errors creep in: wrong sizes, mixed-up formats, forgotten lines.
What's more, mandatory e-invoicing between businesses in Spain now has its implementing regulation (Royal Decree 238/2026). It will apply 12 months after the implementing ministerial order enters into force for businesses with a turnover above 8 million euros, and 24 months after for everyone else. The draft order set its entry into force for 1 October 2026, but the final timetable depends on when it is published. The cleaner the customer's order comes in, the cleaner the rest of the chain will be: delivery note, invoice and status reporting.
The solution, step by step.
- The usual channels. WhatsApp, email and voice notes, which are transcribed automatically.
- Interpretation in context. The system uses the catalogue and that customer's history: "the usual" is their regular order and "the small ones" is the format that customer normally buys.
- A draft order in the ERP (or on an intermediate screen), with each line marked as certain or doubtful, and the reason for the doubt.
- Validation and confirmation. A person validates the order and the customer receives a summary through the same channel they ordered on.
What it doesn't do. It doesn't change prices or terms, and it doesn't confirm stock if the ERP doesn't provide that data. Customers keep ordering the way they always have: nobody makes them use a new portal, which is exactly where many B2B digitalisation projects get stuck.
6. Installers and service companies: from job sheet to draft invoice
The friction. The technician finishes the job, fills in a job sheet by hand (or doesn't) and days later someone in the office tries to decipher it. Materials get forgotten, hours don't add up. And there are deadlines: under the Spanish Invoicing Regulation, an invoice to a consumer is issued at the time of the transaction, and to a business before the 16th of the following month.
From 2027, the software used for invoicing will also have to meet the requirements of the VeriFactu regulation (Royal Decree 1007/2023): from 1 January for companies subject to corporate tax and from 1 July for the self-employed, under Royal Decree-Law 15/2025. That shapes the design: the custom piece prepares the invoice, but it is the invoicing software that issues it.
The solution, step by step.
- A voice note at the end of the job, from a mobile phone, plus a photo of the materials if needed: what was done, how long it took, what was used.
- Transcription and extraction of the client, address, tasks, hours and materials with their quantities.
- A cross-check against the catalogue of materials and rates, flagging anything it doesn't recognise.
- A structured job sheet linked to the client, with the option for the client to sign it via a link.
- A draft delivery note or invoice loaded into the invoicing software, where the office reviews and issues it.
What it doesn't do. It doesn't issue invoices outside the invoicing system or replace the mandatory working-time record. Technicians aren't asked to learn an app; they're asked to talk for two minutes.
What the six have in common
- None of them replaces software that already works. They all sit on top of it or next to it, in the gap between tools.
- They all start with a specific process. "Sorting the quarter's documents" is a project. "Digitalising the firm" isn't.
- They all use data that already existed. The data is rarely what's missing. What's missing is someone, or something, to work on it in time.
- They're all designed with the regulations, not against them. Tax deadlines, professional ethics, data protection, AI rules. Knowing them changes what gets built.
- In every case, a person validates at the critical point. The AI prepares, sorts, proposes and alerts. The decisions that matter still have an owner.
- None of them forces the end customer to change their habits. Plenty of tools work well on paper and fail because they ask clients, patients or technicians to change the way they do things.
When you don't need anything custom
It wouldn't be honest to talk about custom solutions without saying when they make no sense:
- When a standard tool already covers the essentials. For managing appointments there's dedicated software with WhatsApp reminders and free plans for small volumes. Building your own rarely pays off.
- When the public administration provides the tool. E-invoicing between businesses will come with a free public solution from the Spanish Tax Agency. Developing your own issuer would make no sense; what can make sense is connecting what you already have to it properly.
- When the process rarely comes up. If something happens three times a month, automating it may cost more than carrying on doing it by hand.
- When the process isn't defined. If everyone on the team does it their own way, automating it just makes the mess move faster. First you put it in order, then you automate.
- When nobody is going to look after it. Formats, providers and rules change (in the last twelve months alone, VeriFactu and part of the AI Act have been postponed, and business e-invoicing is still waiting for its ministerial order). A solution nobody understands from the inside ends up being more of a dependency than an improvement.
Five questions to tell whether your case is one of them
- Is there a task that repeats every week and consists mainly of copying, sorting or chasing information?
- Does that information arrive through messy channels (email, WhatsApp, calls, paper)?
- Does your current software have the data but not tell you what to do with it?
- Are there errors or last-minute scrambles that always happen at the same point, often close to a deadline?
- Could you explain that process in five steps to someone who has just joined?
If you answer yes to several of the first four and also to the fifth, there's probably a small solution waiting for you. If the fifth is a no, the first step isn't technological: it's putting the process in order.
Frequently asked questions
What is a custom AI solution for an SME?
A small tool, designed for a specific process in your business, that connects to the software you already use and automates the repetitive part (reading, sorting, preparing, alerting), leaving the important decisions to your team.
Do I have to change my management software or ERP?
Usually not. In most cases the work is done on top of the existing system. Replacing your core software is a different kind of project, longer and riskier, and it only makes sense when the system itself is the problem.
What does the EU AI Act say about all this?
Since 2 August 2026, the transparency obligations in Article 50 have applied: if a person is conversing with an AI system, they must be made aware of it, unless it is obvious. The obligations for the high-risk systems in Annex III have been postponed to 2 December 2027 by Regulation (EU) 2026/1744, known as the Digital Omnibus on AI. None of the six examples, as described here, falls within the Annex III high-risk cases, but those that talk directly to customers do have to meet the transparency requirement.
Is it safe to use AI with client or patient data?
It can be done safely, but it takes deliberate design: access only to the data that is strictly necessary, providers with a data processing agreement and GDPR-compliant safeguards, and a log of what the system does. With health data the bar is higher, and it's worth reviewing it with your data protection officer or adviser.
How long does it take and how much does it cost?
It depends on the process, but a well-scoped project is usually measured in weeks, not months. At Isenzo-IA, automating one or two processes starts at €950, with an implementation period of 4 to 6 weeks. Before building anything, the first step is a diagnosis to check whether it's worth it in your case.
If, reading any of these examples, you thought “that happens to me”, you already have the best starting point. You don’t need to know what to build. You just need to know where the work gets stuck.
Let's talk about your caseThis article is for general information only and does not constitute tax or legal advice. Regulations checked on 29 September 2026.
Sources
Linked documents are in Spanish, except for EU texts.
- Spanish Tax Agency (AEAT). Filing deadline for form 303 and 2026 taxpayer calendar
- Royal Decree 1619/2012, Invoicing Regulation (Arts. 4, 6, 7 and 11)
- Royal Decree 1007/2023, VeriFactu Regulation and Royal Decree-Law 15/2025 (postponement of VeriFactu)
- Royal Decree 238/2026 (mandatory e-invoicing between businesses) and AEAT note
- Spanish Ministry of Finance. Draft ministerial order on the public e-invoicing solution
- Royal Decree 135/2021, General Statute of the Spanish Legal Profession (Art. 51)
- Royal Legislative Decree 2/2015, Workers' Statute (Art. 59.3)
- Law 10/2010 on the prevention of money laundering (Art. 2.1) and Spanish Treasury, Catalogue of risk indicators for the real estate sector
- Law 11/2022, General Telecommunications Law (Art. 66.1.b) and AEPD Circular 1/2023 on commercial calls
- Regulation (EU) 2016/679, GDPR (Arts. 9 and 28)
- Regulation (EU) 2024/1689, AI Act (Art. 50), amended by Regulation (EU) 2026/1744 (Digital Omnibus on AI)
