HomePlatform

GLEEM · the platform

There is one engine under all three systems.

It is why a judicial vehicle pound and a heating installer each get a program that looks purpose-built for them, while both sit on the same base, already proven with the other customers. If you have someone technical assessing this for you, this is the page they need.

[ Why the name ]

GLEEM is not a name. It is a statement of intent.

GGentleLLogicEEnhancedEEnterpriseMManagement

The word that carries the weight is the first one. Gentle is not there for politeness: it is a design constraint, and in this shop it counts as a technical requirement.

What that means in practice

  • No wall of fields to fill in before you can get anything done.
  • No error messages written for the programmer instead of the person doing the job.
  • Nothing gets wiped without asking first.
  • Every screen has one job, not seven.
  • The person using it should feel guided, not interrogated.
  • The phone is not an afterthought: it is where half your people actually work.

We did not read this somewhere. Before writing software we used seven management systems as the business owner, not as the supplier. None of them got the sums wrong: every one of them got the same thing wrong about people. Ten tabs to set up one customer. Errors written in a language nobody speaks. Screens designed for the database, not for the person sitting in front of it.

That flaw, met seven times over, became our first requirement. And it went into the name, so that nobody forgets it: we say it out loud every time we name the product.

[ What is underneath ]

The things every company has, written once.

Who the customers are, which documents exist, who can see what, what came in and what went out: these are the same in a vehicle pound and in a heating firm. We write them once and put them through their paces across every customer at the same time. When a fault turns up at one of them, it is closed for all of them.

Shared

One customer, one record

The customer on your quote is the same one in the accounts and on the stock paperwork. Not three records with three different addresses that somebody has to reconcile at the year end.

Shared

Each document grows out of the last

The quote becomes the order, the order becomes the delivery note, the delivery note becomes the invoice. Lines and amounts travel with them: nobody retypes them, so nobody mistypes them.

Shared

Everyone sees what they need

The storeman does not see margins, the bookkeeper does not see the staff rota. Not as a prohibition: a screen full of things that are not your business is a screen where mistakes get made.

Shared

Who changed that figure, and when

When an amount does not add up and nobody remembers touching it, the answer is there. It is the feature that looks pointless until the day it is needed — and on that day it is worth all the rest put together.

Shared

Italian accounting, the real thing

Double entry, chart of accounts, VAT, electronic invoices in the format the Italian state demands. Written once and used by all three systems, because Italian accounting does not change from one trade to the next.

Shared

Your data never mixes with anyone else's

The wall between one company and the next is enforced by the database, not by a check inside the program. Which means that not even a mistake by whoever writes the software can let a record out of your fence.

ON TOP Business management ON TOP Judicial vehicle pounds ON TOP Maintenance and installation

On top of that base we fit the trade: the words you use, the documents you produce, the steps you cannot skip. That part really is made to measure — and it is the small part of the work, not the large one. Which is why it costs less than having a system written from scratch, and holds up like one that has already been proven.

[ If you want to leave ]

What happens the day you want to leave.

It is the most awkward section on this site and we write it on purpose, because it is the question nobody asks the salesman and everybody asks themselves later. You stay with a system because it pays to stay, not because getting out is difficult.

The database is yours

Your documents, your customers and your accounts are in it. Ask us for a copy and you get one, without explaining why you want it and without waiting for anyone to approve it.

It comes out in formats another program can read

Customers, items and documents come out as files a competing system can import. The electronic invoices are already in the format the state imposes on everyone, so anybody can read them.

Leaving costs nothing

No penalty, no minimum term to see out, no month's notice to pay for. If it ends, it ends.

The server can be yours

The program runs on our cloud or on a machine in your own building. In the second case it stays on even on the day we disappear.

[ Reliability ]

The things you cannot see, and that count for more.

A management system holds your money and your customers' data. You can look at the screens in half an hour; what sits underneath you find out the day something goes wrong.

[ Where it runs ]

Where the data sits, and who can look at it.

On our servers

Machines in Europe, under European rules. Updates, backups, monitoring and security are ours to handle: you do not have to think about them.

Or on yours

If your own rules require it, the program runs on a machine in your building. What changes is who holds the keys, not what the software can do.

Who gets into your data

Our engineers go in for support only, at your request, and every access is logged. We profile nobody, we resell nothing and we do not use your documents to train models.

The dull parts

Encrypted traffic, protected passwords, sessions that expire. Nobody mentions them while selling, and they are the only ones that count when somebody has a go at you.

Let us talk architecture
[ Book a diagnostic ]

If you have someone technical you trust, send them to us.

Hard questions suit us: they are the ones we have already had to answer with a customer on the phone.