A software glossary for people who run companies

The terms that come up in any conversation about software, explained for the person who has to decide rather than the person who writes code: what they are, an example and when they matter.

  1. 01What an ERP is and when a small business needs oneERP stands for enterprise resource planning. Put simply: business management software in which sales, purchasing, stock and accounting share the same data.
  2. 02CRM: what it is and when a customer spreadsheet stops being enoughCRM stands for customer relationship management. It is where everything that happens with each customer and each prospect is written down, before, during and after a sale.
  3. 03SaaS: what it means to use software on a subscriptionSaaS stands for software as a service. You do not buy or install the program: you pay a fee to use it from a browser or phone, and the vendor looks after the rest.
  4. 04What an API is and why your ERP vendor keeps mentioning itAn API is the door through which one program lets another request or deliver data, under fixed rules. It is what lets two programs talk without anyone copying anything by hand.
  5. 05Systems integration: getting your software to share dataIntegrating systems means getting your company’s programs to pass data to each other automatically and without contradicting each other. The technical side matters less than deciding who owns each piece of data.
  6. 06Webhook: the automatic notice between two programsA webhook is a notice one program sends another the moment something happens, without anyone having to ask. It is what makes a payment, an order or a signature appear in your system on its own.
  7. 07Role-based permissions and RLS: each person sees only what is theirsWhen several people use the same program, not all of them should see or change the same things. Role-based permissions say what each type of user can do; row level security says which specific records they can see.
  8. 08OCR: how a program reads a scanned documentOCR (optical character recognition) turns the image of a document into text a program can use. It is the first step towards no longer typing in invoices, delivery notes or paper job sheets by hand.
  9. 09Reconciliation: checking that two records tell the same storyReconciling means putting two sources that should say the same thing side by side and explaining every difference. Bank reconciliation gets the attention, but a small business reconciles much more than that.
  10. 10Traceability: being able to rebuild where it came from and what happenedHaving traceability means being able to answer two questions with data, without relying on anyone’s memory: where did this come from, and what was done with it? It applies to products and also to the data in your system.
  11. 11Verifactu invoicing records: the terms worth knowingWhen your adviser or software provider talks about Verifactu, the same words keep coming up. Here they are one by one, with an example and the question worth asking. For the what, the why and the timetable, our Verifactu guide is the main reference.
  12. 12Business-to-business e-invoicing in Spain: what it means and why a PDF will not doMany people think they already issue e-invoices because they email PDFs. For the obligation coming between businesses, that is not the case. Here are the terms and how they differ from what you already know.
  13. 13Electronic signatures: simple, advanced and qualified, with small-business examplesSigning on a tablet, accepting a quote with a click and signing with a digital certificate are different things, even though all are called electronic signatures. Here are the three levels and what is worth keeping in each case.
  14. 14GDPR in custom software: what each term means for the business commissioning itWhen you commission software that stores data about customers, staff or patients, GDPR vocabulary appears in the contract and in meetings. Here is what each term means in practice and which decision is yours.
  15. 15Backups: what 3-2-1, RPO and RTO mean for your businessAlmost every company thinks it has backups until the day it needs one. These are the terms worth understanding to know whether yours would work, and the questions that settle the doubt.
  16. 16Data hosted in the EU: what it actually means and what to ask“Your data stays in Europe” appears in a lot of proposals. It only tells part of the story: where the database lives. Backups, support and supporting services may be somewhere else.
  17. 17Who owns the source code of your application?Source code is the written set of instructions a program is built from. Who holds the rights to it decides whether tomorrow you can change provider, bring in another team or sell the company with its software inside.
  18. 18Corrective, evolutive, adaptive and preventive maintenance: how they differSoftware is not finished on the day it is delivered. Bugs appear, regulations change and new screens are needed. Each has a name, and it is worth knowing which ones are included in what you pay for.
  19. 19No-code and low-code, explained for a small businessThey are ways of building applications and automations without writing code, or writing very little. Used well they solve a lot; it pays to know their limits before resting an important part of the business on them.

ServicesSectorsIntegrationsGuidesProcessesSee all projects

Tell us the problem

A person on the team reads it and replies with a proposed next step.

Tell us your problem