What I learned building a local tour company across Lombok, Sumbawa, and Labuan Bajo

We started Sungkar Group in Mataram as a small local tour company focused on Lombok, and over time the work pulled us into Sumbawa and Labuan Bajo too. On paper that just sounds like "we added destinations." In practice it meant learning how land tours, open trips, car rental, and phinisi charters actually behave when you try to run them as one connected product.

Most operators specialize in one line. A car rental company stays in transport, a boat operator stays at sea, a land tour team stays on the road. The moment you start connecting those pieces, the real work begins. And what I've learned is that the destination is rarely the hardest part. The handoff is.

Think about what a single trip actually looks like. A traveler lands in Lombok, needs an airport pickup, a hotel check in, a private route the next day, then a boat transfer or a flight toward Labuan Bajo. Each step looks simple on its own. Strung together, they become a chain, and if one link is weak the whole trip feels unreliable even when every individual part was fine. That is the problem we kept running into, and eventually the problem we decided to build the business around.

The shift for us came when we stopped thinking in single products. It's easy to sell a private tour, an open trip, a car rental, and a boat charter as separate items. But travelers don't experience a trip that way. They experience continuity. They care whether the driver shows up on time, whether the guide explains the route clearly, whether the hotel transfer lines up with the boat schedule, whether someone actually answers when plans change at night. Once we started looking at it that way, the whole product structure had to change. We still sell different trip styles because private tours and open trips genuinely solve different needs, but the operating layer underneath them has to stay consistent no matter which one you book.

A few things I'd pass on to anyone running something similar.

Clarity beats hype. People are far more confident when the structure is clear, meaning what happens on day one, what transport is used, whether it's private or shared, and what's flexible versus fixed. Clean explanations do more work than big claims. Related to that, private and open trips are not the same product at different prices. A private tour is about control, so pace, route, group, and timing. An open trip is about access, so a lower barrier, a fixed schedule, and a shared experience. If you don't explain that difference well, people compare the wrong things and walk away confused.

The weakest point is almost always the transfer, not the attraction. Guests remember the Gili snorkeling or the Komodo route, but the trip's real quality usually gets decided earlier, at the airport pickup, the hotel timing, the boat or flight connection, and the coordination between teams. If the handoff fails, the destination never gets a fair shot. And local knowledge only matters if it's operational. Knowing a place isn't enough. The useful knowledge is practical, like which routes cause backtracking, which timings create rushed transfers, and which combinations look great online but fall apart on the ground. That only becomes valuable once you turn it into process.

The website turned out to be part of operations, not just marketing. We rebuilt ours so packages, destinations, and guides are easier to understand before anyone contacts us, because a lot of travelers want to understand the difference between trip types and regions before they send a WhatsApp message. We're still refining a lot of it, like how package pages explain inclusions without overloading people, how to present private and open trip options side by side, and how support stays responsive when there are a lot of moving parts. Running across three islands means accepting that no system ever really feels finished.

If you're building a travel business with many products in one region, the temptation is always to keep adding packages. But the more useful work is usually the less visible stuff, like tightening the handoffs, cutting unclear trip descriptions, separating products that actually solve different jobs, and treating support as part of the product instead of an afterthought. For us, that has been the real work of growing from a Lombok base into a three island operation.

Here's a link to what we developed: sungkargroup.com

Curious if others here have hit the same thing. Where's the point in your operation that breaks most often, the destination or the handoff between all the pieces?