Built from experience, not theory.

I did not arrive at consulting from consulting. I arrived from operating.

My entrepreneurial work began in Southeast Asia, starting in Thailand and later moving into the Philippines, where I spent years working directly inside hospitality and tourism businesses. That meant the whole operation, not a function within it: staffing and rotas, cost control, supplier terms, guest experience, the booking infrastructure, the reporting that told us whether any of it was working, and the marketing responsible for filling capacity.

The systems side was not a career change. It was a consequence.

As the businesses grew, the tools stopped fitting. Availability lived in one place and revenue in another. Bookings arrived through channels that did not talk to each other. Staff spent hours moving information between systems that should have been connected, and the reporting that decisions depended on was assembled by hand.

So we built what was missing — booking infrastructure, internal reporting, operational controls, integrations between systems that were never designed to meet. That work was driven by a specific operational problem every time, which is a very different discipline from building software to a specification handed over by someone else.

Working across those markets meant learning several things at once that are usually separated into different jobs: how a service business is actually staffed and costed, how customers are acquired when the market is competitive and seasonal, how technology either supports an operation or quietly obstructs it, and how quickly a business can outgrow the systems that got it started.

It also meant learning where growth breaks. Almost always at the point where demand exceeds what the operation and its systems can absorb — not at the point where marketing stops working.

Perspektiva is the direct result of that experience. It combines the three things that were never separate in practice: the strategy that sets direction, the technology that makes it operable, and the customer acquisition that brings demand.

The approach is deliberately practical. The recommendation is not the deliverable — the working result is. Where a plan needs systems built to become real, they can be built. Where it needs demand, that can be built too.

Built from experience, not theory.