Mechanics walked to the counter for the next order
Done with a job? Back to the counter, see which note's on top. No visible priority, no idea what else was coming in.
← case · repair portal
Caravanreparatiespanje — from paper work order to iPad flow
A workshop where repairs came in by phone, email and loose notes. Mechanics walked back and forth to the counter for the next order, customers called for status, and admin in the evening meant retyping a stack of paper. Now: customer reports online, the order is on the iPads in the workshop, status gets updated while the work happens.
~80
repairs processed per month
0
paper work orders since launch
4
weeks fixed-price build
// the problem
The work order was a slip of paper that went missing.
Phone, email, a note on the counter — that's where every repair started. No overview of what had to happen that day, no status the customer could check themselves, and the admin after the fact was double work.
Customers called for status
"Is my caravan ready yet?" — a phone call someone from the shop floor had to answer, often without being sure.
Admin meant retyping paper in the evening
What was done, which parts, how many hours? It was on the note — if it wasn't lost — and then had to go into the invoicing tool and the accounting.
// what we built
One portal, three sides: customer, counter, shop floor.
Customers report their repair online. The order comes in at the counter and shows up on the iPads in the workshop. Mechanics see what needs doing, tick off steps, add parts and hours. The customer follows the status. On hand-over the invoice is ready.
- Public submission form for customers (NL + ES)
- Counter overview: incoming repairs, priority, planning
- iPad flow for the shop floor: order, steps, parts, hours
- Status tracking the customer can follow themselves
- Automatic work order + invoice on hand-over
- Hosting + monitoring + monthly maintenance
// how a panel start goes
Four weeks to live, then ongoing.
No quotes for additions, no extra-hours arguments. One monthly number that covers everything — build, hosting and continued development.
week 1
Intro + scope
One 60-min call, then a written scope with one number. Sign-off = we start.
week 2
Build
The stack is already in place. Your brand, content and integrations go on. First live preview at the end of the week.
week 3
Review + iterations
You click around, I tighten things up. Three review cycles baked in — no extra cost.
week 4
Launch
We point your domain over, monitoring on, first month of maintenance free. Done.
// the result
Paperless workshop, customer follows along.
Since launch: ~80 repairs processed per month, no more paper work orders, no more status phone calls to the shop floor. Admin isn't an evening job — by hand-over it's all there already. And the portal keeps growing: a second location or an extra service is added in steps, not as a new project.
“The repair orders now come straight to the iPads in the workshop. No more loose paper, mechanics see what needs doing and update the status while they work. Admin isn't an evening job anymore.”
Owner
Caravan repair Spain
what's under the hood
A workshop or service business with the same chaos?
First call is free — thirty minutes, no pitch deck. By the end you'll know if a custom portal fits you and what the shortest route looks like.
- Next.js 16
- Postgres (Neon)
- iPad-first work-order UI
- Status tracking
- Notifications
- Vercel hosting