It was half past six in the afternoon and Pilar was still at the office, alone, with a wad of job sheets on her desk. Thirty-odd. She picked them up one at a time, held them to the light to make out the technician's handwriting, and typed them into the computer, field by field: client, address, boiler, fault, parts, hours. What the technician had written by hand in the morning, she wrote again in the afternoon. The same. Once more.
That morning's sheet was for a repair at a house on the outskirts. The technician, Dani, had changed a valve and an expansion vessel. He jotted it down in a hurry, standing up, with the pen that only half writes, on the three-page carbonless pad they keep in the van. He left the pink copy with the client. The white one went into the glovebox, with the other seven from the day.
Rubén runs a heating and air-conditioning maintenance company in Zaragoza. Six technicians, six vans, around forty call-outs a day between them. And at the end of every shift, all that work came back to the office on paper, crumpled, sometimes wet, sometimes with a number you couldn't read, for someone to write up clean before it could be invoiced.
What the paper really cost
The problem wasn't the moment Dani spent filling in the sheet. That's two minutes, and it's right that it's done: the client signs, takes their copy, all in order. The problem was the second time. Pilar's. Typing in the afternoon what had already been written in the morning. Thirty sheets a day, at three or four minutes each with the doubts, came to a good two hours of one person spent copying from paper to screen. Work that added nothing. The data already existed; it was only changing place.
But the expensive part wasn't even those two hours. The expensive part was what got lost along the way. The sheet that stayed in the glovebox and turned up the following week, and the invoice went out ten days late. The part number Pilar couldn't read and left blank "to ask about", and didn't ask, and that valve never got invoiced. The material the technician changed and forgot to note down in the rush, that the company paid the supplier for but never charged anyone.
When we set about adding up those small forgettings, they came as a fright. Rubén was failing to invoice several thousand euros a year in parts fitted and not noted. Not through anyone's dishonesty, nor laziness: through the journey of the data, which passed through too many hands and too many papers before reaching an invoice. Each jump was a chance to get lost, and something always did.
What he asked for and what he needed
Rubén called me with the solution already worked out, like nearly everyone. He wanted, he said, two things. One, to buy a small printer for each van, "to print the sheet right there". Two, for the technicians, instead of paper, to fill in a spreadsheet on their phones.
The printer solved the client's copy, which wasn't the problem, and left the real one untouched: someone at the office still had to put that data into the system to invoice. More paper, not less.
And the spreadsheet on the phone he'd already tried, on his own, three months earlier. It had been a disaster. A spreadsheet isn't made for the thumb of a technician standing in a boiler room with gloves on. Cells went out of line, rows got deleted by accident, each technician saved the file under a different name, and in the end Pilar had to tidy up twenty spreadsheets instead of typing thirty sheets. He'd swapped one mess for another.
—So what do I do?
—Have the sheet written once. Where the work is done, by the person who does it, and from there it doesn't get copied anywhere.
How it works, no smoke
The idea, in one sentence, is that: write the data once and let it travel on its own. The rest is making it easy for whoever writes it.
We built the technicians a simple app on their phones, made for their hand and their situation, not for an office desk. Big buttons. The client already shows up in a list, no need to write the address. The most common faults and parts, the ones they put in every day, are picked by tapping, not typing, and the prices are already in. A photo of the boiler or the old part, if needed. And at the end, the client signs with a finger on the screen itself. They tap save, and that's it.
That "that's it" is the whole difference. The moment Dani saves the sheet at the house, the sheet is at the office. No glovebox, no wad, no afternoon of typing. The material he's fitted is already counted, with its price, ready to invoice. If he wants, the invoice can go out that very afternoon, automatically, without Pilar touching a key.
And the honest thing is to say what it doesn't do and what it cost. It doesn't think for the technician: if Dani picks the wrong part, the sheet comes out wrong, just as it used to come out wrong by hand. What it does is make sure it doesn't have to be written twice, which is where things got lost. And it cost its share of patience: the first two weeks there was grumbling, because to a lifelong technician the notebook feels faster. Until they saw they were clocking off on Friday with no sheets pending.
What changed
Pilar's was the most visible. The good two hours of typing in the afternoon vanished from one day to the next. We didn't swap them for another task: they vanished, because they were work that was surplus. Pilar stopped staying till seven deciphering handwriting and started doing things that were actually needed and that she never had time for: calling clients about the year's servicing, chasing two overdue invoices, organising the routes.
The invoicing, which used to go out an average of eight or nine days late, started going out in two. Getting paid sooner, without selling more, is money that comes into the company earlier and a client who gets the invoice while they still remember the repair.
And the forgotten material stopped being forgotten, because noting it down was now easier than not noting it down: two taps on the spot, instead of remembering in the afternoon. Those several thousand euros a year of parts fitted and not charged were recovered almost in full. Not by charging the client more, but by charging for what had already been done and was being given away by accident.
The work you only do once
There's something Pilar told me a month in, and that to me is worth more than any number.
—The best thing isn't that it takes me less time. It's that I no longer take the work home in my head.
In a lot of small companies the same data gets written two, three, four times. On a delivery note, on a job sheet, on a spreadsheet, in the invoicing program. And every time a piece of data gets written again, it isn't just time that's lost: a gap opens through which an error slips, a forgetting, an invoice that never goes out. Repeated work seems harmless because it's quiet, but it keeps dripping away money and afternoons.
Real automation, very often, isn't putting in a clever machine that decides things. It's something humbler and more profitable: getting each piece of data written once, where it's born, and from there reaching on its own everywhere it's needed. So nobody writes up clean again what was already written.
Write the data once, where it's born
When the same data is noted on paper and then typed in at the office, it isn't just an hour that's lost: it's the invoice that goes out late, the number nobody can read, the material that was fitted and nobody charged for. Repeated work is quiet, but it drips money every single day.
Automating well isn't always a machine that decides. Often it's the simplest thing: the technician writes the sheet once, on the phone, where the work is done, and from there it travels on its own to the invoice with nobody copying it. One piece of data, one place, zero times written up clean.
How many times does the same data get written in your company?
If your job sheets, delivery notes or orders are filled in on paper and then someone writes them up clean on the computer, it can be set up so they're written once and reach invoicing on their own. We can look at your process together.
Let's talk