phuketdev

For villa and property operators

I build the software your team is doing by hand.

Guest messages at 11pm. Owner statements at month end. Maintenance requests lost in a group chat. I turn those into systems that run on their own, for one property operator here already, and I'm taking on one or two more.

It's already running down the road.

I'm the outsourced tech department for a property management firm here in Phuket. Their team was answering the same guest questions across WhatsApp, the OTA message centres, and email, nights and weekends included.

I built them a guest-support system that reads every channel, answers from live booking and property data, and replies through the channel the guest used. When it isn't confident, it hands over to a person with the whole conversation attached. It's in production now.

30 secTypical first reply
24/7Nights & weekends covered
3 channelsOne system answers all
One night, as the system sees itillustrative

What I take off your team.

Each of these is a thing someone on your staff does by hand today. I've built or scoped every one of them for an operator on this island.

Guest messaging that never sleeps

Anyone with guests who message after 6pm

Answers in seconds, day or night, in the guest's own language — from your live booking data, not canned replies. Hands over to your team when it should, with the conversation attached.

Owner statements on autopilot

Operators managing for owners

Monthly statements assembled from your PMS and bank feeds instead of someone's Excel evening. Same format, same date, every owner.

Maintenance that chases itself

Teams running requests through group chats

Requests captured from any channel, routed to the right contractor, chased until closed, logged against the unit. Nothing lost in a group chat.

OTA payouts that reconcile themselves

Anyone on two or more OTAs

Payouts matched against bookings and bank deposits automatically, with mismatches flagged now — not discovered at tax time.

Handovers written by the systems

Teams with a night and a morning shift

What happened overnight, summarised for the morning team from the records that already exist — instead of a chat thread nobody reads.

How it works.

No retainer to start. The first step costs you half a day and nothing else.

Half a day with your team

I sit with the people doing the work and follow it as it actually happens: the bookings, the messages, the spreadsheets, the chasing.

Written findings, yours to keep

What's costing you hours, what it's worth, and what I'd fix first. Free, whether or not we go further. If automation isn't worth it for you, I'll say exactly that.

I build the first one, fixed price

One system, quoted up front, live in days not weeks. You own it. If it earns its keep we do the next one.

Who you'd be working with.

I'm Saurabh. I've spent my career building software, most recently AI systems and automation for companies you've heard of and a few you haven't. I live in Phuket, which is the point: I can be at your office, and I'll still be here next year.

I work with one or two operators at a time. That's how the work stays specific to your operation instead of a template.

Hire a system, not a contractor.

Tell me what you'd need to hire someone for. I'll show you how a system replaces it. If it can't, I'll say so. I reply the same day.