Software for places that can't stop

The service never stops.

I build ordering systems, configurators and the tools people use at work. Every cent adds up, and every decision is written down before the code is.

Fig. 0Pull the plug and the tills keep selling. Network on
tunnelphone appcloud● TAKING ORDERSfair serverall the truthtills● SELLINGkitchens● LIVEpickup boards● LIVEthe cloud is never askedphone appfair servertills● TAKING ORDERS● SELLING
offline
0:00
sold at the tills meanwhile
0

Everything is on. Pull the plug.

Recent work

Three projects, shown live: Pizzaville, Infissi Management and DA Solver.

Project 01

Pizzaville

orders in four nights
9k+
downtime
0
phonecloudfairkitchenpickup"ready" back to the phoneno. 412phonecloudfairkitchenpickupno. —

Follow one order, phone to plate.

The problem
Four nights to sell, in a field where the internet drops.
The outcome
Tills, kitchens and pickup boards run from a server at the fair, so a dropped connection never stops a sale.
See how it works Pizzaville

Project 02

Infissi Management

automated tests
1.8k+
decision docs
82
1200960

rails 1164 · mesh 1140 × 884 mm (invented deltas)

The problem
A made-to-measure product starts as numbers taken on site, often with no signal.
The outcome
Measure, quote and draw on one tablet. The workshop gets a cut list it can trust.
See how it works Infissi Management

Project 03

DA Solver

years in production, no downtime
2+
versions to get there
5
Shifts for the week, Monday 16 to Sunday 22
personMon 16Tue 17Wed 18Thu 19Fri 20Sat 21Sun 22
Anna36 hfreefreefreefreefreefreefree
Bruno30 hfreefreefreefreefreefreefree
Carla24 hfreefreeon holidayon holidayfreefreefree
Dario30 hoff sickfreefreefreefreefreefree
Elena30 hfreefreefreefreefreefreeon leave

Five people, seven days, contracts and holidays. Press and watch the week write itself.

The problem
With many branches, doing the schedules had become one person's full-time job.
The outcome
The solver writes the month from contracts, absences and preferences. Changes arrive as requests to approve, not as messages.
See how it works DA Solver

Working together

Got a process that can't afford to fail, or a system that has outgrown its first version?

I'm Lorenzo. I build software for businesses that run in the real world: fairs, workshops, people on site. You deal with one person, from the first question to opening night.

Write to me

Write to me

Tell me what you need to build. I answer within two working days.

What you write is kept for 12 months so I can answer you, then deleted. A scrambled version of your IP address is kept for one hour to stop repeat submissions. Ask, and I delete everything sooner.

Email or phone: one is enough.
What budget do you have in mind?
What it is, who uses it, and by when.