OH
Software to measure

The software you use every day stops being a rental.

Every year you pay thousands for software that isn't yours, that forces you to work like your competitors, and that takes three weeks to change one field. Software like that is now built to measure in hours, not months. You can learn to do it — or I can do it for you.

€6,000–20,000
A year in fees: the industry range
No fees
What you build stays yours
~170 hours
A year, from one automation alone
Where I work

Based in Bolzano, working anywhere — on site or remote, in Italian, German, French or English.

The bill

After ten years of fees you own nothing.

That isn't a figure of speech: it's how the software we've been buying for twenty years works. You pay to use it, not to have it, and the day you stop paying it switches off.
€6,000–20,000

A year, in subscriptions

PMS, channel manager, revenue tool, food cost and stock, guest app, staff attendance, guest CRM, dashboards. Each with its own fee, all up for renewal, none you can actually switch off.

€500–1,500

Per change request

Plus weeks of waiting. To change one field on a screen your staff opens forty times a day.

  • ×You pay the fee in the years you ask for nothing and nothing changes, too.
  • ×Every vendor keeps its data in its own silo, and doesn't speak to the others.
  • ×The day you want to switch, you pay for the migration twice: to the one leaving and the one arriving.

Here's the part that stings: most of those programs aren't doing anything difficult.

The difference

Rented or owned.

What you rent

You pay every month, forever. Stop paying and it switches off. If the vendor raises the price, changes strategy or shuts down, the problem becomes yours. After ten years you've spent, and you own nothing.

What is yours

You pay once. The accounts are in your name, the data sits where your data sits. If I disappear tomorrow, it keeps running anyway. After ten years you still have it, and it's still yours.

To measure

Standard software makes you work like your competitors.

Every property has its own way of doing things, and that way is why a guest comes back to you rather than to someone else. Software bought on a subscription doesn't know that: it gives you the fields somebody designed for a place that isn't yours, and it's you who has to adapt. Every time you change your process to keep a piece of software happy, you're paying to look more like everyone else.

  • The fields are yours, not the ones drawn for a city chain.
  • Your property's exceptions stop being exceptions handled by hand.
  • When you change how you work, the software changes with you — in hours, not in quotes.
  • No feature you pay for and will never use.
The hours

The time that comes back is the part you see straight away.

Two automations in production, running every day. Client names don't appear on this site — the numbers do.
~170 hours/year

Daily accounting

A 20–30 minute routine now runs on its own at a fixed time — zero transcription errors, ~170 hours a year handed back to the team.

~45 working days/year

The night run

Every morning at 07:00 the right messages reach the right people, without anyone writing them: ~65–75 minutes a day, which comes to around 45 working days a year.

Zero differences against the manual method, verified before going into production.
Acceptance test, daily accounting automation
  • +Tested on dozens of scenarios — missing data, typos, different ordering — on copies of the files, never on live data.
  • +The night run has been live since June 2026: it starts every morning, with nobody needing to be there.
  • +Every run leaves a log: you always know who received what.
The arithmetic

Sixty-six working days a year.

The hours above are measured, not estimated. Turning them into money takes two numbers that are yours: what an office hour costs you, and what would happen if those hours went back to selling.

Hours that come back
~530 h

A year, from the two automations above: ~170 on accounting, ~360 on the night run. That's 66 full working days.

Cost avoided
~€9,500

A year. An office employee costs the company around €2,700 a month: net of holidays and public holidays that's about €18 an hour, and 530 hours come to roughly €9,500. Put your own figure in: the number changes, the order of magnitude doesn't.

Fees switched off
On top

Only the ones you replace — the PMS stays where it is. How many those are, we count on your own list.

And then there's the part that isn't a saving

This is where the fair objection usually arrives: "I'm paying that person anyway." True. The hours don't vanish from the payroll — they move. Sixty-six days a year that stop copying data from one sheet to another and go back to where revenue is made.

Direct bookings

Every booking that comes through you instead of the portal is commission you don't pay: the market sits between 15% and 18% of the value of the stay. One more a week, multiplied by your average rate, is a sum you do in thirty seconds.

What sells by talking

Upgrades, half board, spa, late check-out: these are sold by whoever has time to talk to the guest, not by whoever is retyping numbers before the daily close.

The mistakes that don't happen

A mistyped entry costs twice: once to make it and once to find it. The automations in production run with zero differences against the manual method, verified before they start.

Over five years

One year is the wrong horizon.

Subscriptions make you think in years, because that's how they're sold. But you'll be running that process in your business for far longer, and what you build once doesn't renew. Here are the same hours, multiplied.

1 year
~530 h
~€9,500
3 years
~1,590 h
~€28,500
5 years
~2,650 h
~€47,500
  • 2,650 hours is 330 working days: a year and a half of one person's work.
  • The fees you switch off add on top — and by then they'd have been revised, as they are every year.
  • In year five, what you built still costs nothing and is still running.

The arithmetic is deliberately flat: no growth assumed, no fee increases built in, no opportunity revenue counted. The same hours, multiplied by the years.

The real sum is done with your numbers: your hours, your hourly cost, your average rate and the commission you actually pay. In thirty minutes we do it together — and if it doesn't add up, I'll say so.

Where I stop

The PMS stays untouched.

The PMS with its channel manager connectors, the revenue algorithm, invoicing: integrated, certified machinery that someone has to maintain on your behalf. Rebuilding that in-house is a mistake, and I'll say so before you ask me. The point is elsewhere: outside the PMS you're paying for ten or fifteen more, and those, yes.
Count yours
  • Staff attendance and shift register
  • Housekeeping checklists, room by room
  • Allergy and intolerance forms, wired to the kitchen
  • A small CRM for guests who come back
  • Today's dashboard, read from a phone
  • Stock checks and supplier delivery notes

If after counting them you're left with fewer than three, I have nothing to sell you — and I'll tell you so in thirty minutes, without dressing it up.

Guest data

The risk isn't that artificial intelligence gets it wrong. It's where the data ends up.

You'll find plenty of people teaching you to build something in an afternoon. Almost nobody tells you what you can't put into it. Your guests' data — identity documents, allergies, health, habits — comes with precise rules, and the European AI regulation has added more. Getting that wrong doesn't cost you a subscription: it costs you a fine, and the signature underneath is yours.

  • Risk classification under the European regulation on artificial intelligence.
  • Wherever there's AI there's a person who approves: human oversight isn't optional.
  • What may pass through a model, and what must never leave your property.
  • Every run leaves a log: you always know who did what, and when.

It's a competence I bring into the work, not a stamp to display: I don't sell certificates and I don't put any on show.

Where it actually runs

Not a demo on my laptop.

The right question to ask anyone talking to you about artificial intelligence isn't which model they use: it's where what it writes ends up, who keeps it running, and what happens when it breaks on a Sunday night.
Online, on
Vercel · Railway · Netlify
The data
Supabase on Postgres · SQLite · Redis
The email and messages
Resend · WhatsApp
The payments
Stripe
The jobs that start on their own
Inngest
The numbers are read in
Power BI
Packaged with
Docker
Shipped by themselves
GitHub Actions
Tested by themselves
Playwright
When it breaks, I know
Sentry
Also on
AWS · Firebase

Artificial intelligence writes the lines of code. Getting them into production, and keeping them there, is a different trade — and it's what separates a prototype from an app your staff opens on Monday morning, and it works.

Two roads

I teach you, or I do it myself.

Same result, two ways of getting there. What changes is who holds the keyboard — and how much of your own time you want to put in.
01

I teach you

Sixteen hours in a room, with your own work on the table: you leave with the first app of your own that genuinely runs. It makes sense when you want to learn it yourself — as the owner, or whoever runs the place — rather than hand it to someone on staff.

  • The result stays in-house: whoever did it once can do it again
  • A small room, with your laptop and your data on a copy
  • It costs you your own time, and that's its real price
See the course
02

I do it myself

You bring me a routine your office redoes every day, I hand it back running on its own, and I teach your team to keep it going without me. It makes sense when you want the result without having to train anyone.

  • It starts from one process, not from a six-month project
  • Acceptance on copies: live data stays untouched until the figures match
  • Day-to-day corrections are made by your staff, without calling me
See the services
Questions

The questions that always come up.

Do I have to change PMS?

No, and I'll never ask you to. We work around what you already have: the PMS stays where it is, and what goes are the programs running around it.

My PMS already does all of that.

It might. Try this: list what you pay every month and take the PMS off the list. What's left is what we're talking about. If little or nothing is left, I'll be the first to tell you that you don't need me.

And if it breaks and you're not around?

The accounts are in your name and the data sits where yours sits: if I disappear, everything keeps running. Day-to-day corrections are made by your staff in plain text files, with nothing to recompile.

How long does it take?

One process at a time, and for the first one I tell you when you'll see it running before we start. You aren't signing a six-month project: it starts with a single routine, and if that one doesn't pay off we stop there.

What does it cost?

It depends which of the two roads you take: the course has a published price, bespoke work depends on the process. In the thirty-minute call I'll tell you whether the time saved justifies the spend — and if it doesn't, I'll say so and that's that.

The next step

Count the feesyou pay every month.

Bring me that list and give me thirty minutes. I'll tell you which of those programs are worth rebuilding in-house, which I'd never touch, and whether it's better for you to do it or for me to. And if it isn't worth it at all, I'll be the first to say so.

Or book a call directly
30 minutes · Google Meet · no obligation