I build the boring operating layer that makes automation useful.
Hotel teams do not need another vague AI promise. They need source reports to arrive, checks to run, exceptions to surface, and the morning brief to be trustworthy before the meeting starts.
The work starts where dashboards usually fail.
Most hotel reporting problems are not caused by a lack of charts. They are caused by the manual path between source systems and the view people need every morning.
Exports before APIs
The first pilot can usually start from scheduled reports, emails, Drive folders, and spreadsheets.
Reliability before interpretation
AI summaries only help when the source data has been assembled, checked, and caveated.
Scope before scale
One recurring workflow, one operating output, one handoff. Then expand from proof.
What I believe about this work.
The edge cases are the product.
Late files, duplicates, renamed columns, stale numbers, and approval gates decide whether automation survives contact with operations.
Human judgment stays in the loop.
The goal is not to remove people from decisions. It is to stop wasting them on assembly.
The first win should be narrow.
A clean pilot beats a sprawling transformation plan. Buyers trust what they can see working.
“I look for the place where smart hotel people have become human middleware.”
That is usually where the first automation pilot belongs.Why the founder story matters.
The same method behind this business is the method used for client work: map the workflow, build the smallest reliable system, test the failure modes, document the handoff, and keep public claims grounded in what actually shipped.
Bring me the messy reporting workflow.
If it repeats, affects decisions, and still depends on manual assembly, it is worth reviewing.