Software for places that can't stop

Software that keeps working when the network doesn't.

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.

Write to me
phone appfair servertills● TAKING ORDERS● SELLING
offline
0:00
sold at the tills meanwhile
0

Everything is on. Pull the plug.

Fig. 0Pull the plug and the tills keep selling. A drawing, not live data.
  1. 01Works when the network doesn'tA fair in a field, a quote in a customer's house. Neither needs a signal.
  2. 02Right to the centMoney is whole cents, never floats. A card is charged only after the order is accepted.
  3. 03Built for whoever uses itA cashier with a queue, a cook reading a screen from three metres.
  4. 04Written down firstEach decision gets a short doc, each bad night a runbook, each release one command.
01

Recent work

Two projects built for real businesses. Each comes with a drawing you can play with.

phonecloudfairkitchenpickupno. —

Follow one order, phone to plate.

Pizzaville

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.
orders in four nights
9k+
downtime
0
See how it works Pizzaville
1200960

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

Infissi Management

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.
automated tests
1.8k+
decision docs
82
See how it works Infissi Management

02 · 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
  1. Written first. A short doc for every decision, before any code.
  2. One-command deploys. Safe to re-run, checked before it touches anything.
  3. Handed over. Runbooks for the bad night, tests for the next developer.
03

Write to me

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

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

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.