Tenon is live in Hungary, and the beta is small on purpose

Tenon is a scheduling tool for tradespeople who travel to their customers. It is now live in Hungary, in a beta small enough that I activate every account by hand.

The problem it addresses is old and boring. A day with six jobs on it is six jobs and five drives, and nobody quotes for the drives. When bookings are taken in whatever order the phone rings, those drives quietly eat more of the day than the work does.

What it does

When a customer asks for an appointment, Tenon does not show them every free slot. It shows the ones that fit the days already taking shape: times when the tradesperson will be working nearby anyway. The customer enters an address, sees two or three arrival windows, and picks one. Nothing is confirmed until the tradesperson says yes.

Jobs agreed over the phone run through the same engine, so there is one calendar and one schedule no matter how the work arrived.

Why Hungary first

Tenon is built for a specific market rather than a general one. The interface, the writing and the support are Hungarian, and the trades it is designed around are Hungarian plumbers, gas fitters, electricians and boiler engineers. That constraint is deliberate. A scheduling product that has to stay vague about working hours, address formats and how people actually book a tradesperson tends to end up useful nowhere.

The English side of the site exists for a different reason: partners, future colleagues, and anyone reading about the product from outside that market.

Where it stands

Everything described above works. What is missing is scale, and the confidence that only comes from watching real working weeks go through it.

So the beta is deliberately small. Accounts are activated one at a time, and I walk through the first setup personally: services, working hours, service area, and the booking link that goes out to customers. If something breaks on a real working day, I would rather hear it from the tradesperson than from their customer.

What it costs during this period is on the home page, kept current there instead of written into a post that will age. The part that will not change is this: before anything about pricing moves, the people using it will hear it from me in a conversation and not in a billing email.