Ongoing web management for a resort in Koh Samui, Thailand. Daily upkeep, content updates, and a $200 bandwidth saving the client never asked me to find.

A resort website is never finished. Room rates change, seasonal offers rotate, photos get replaced, pages break in small ways nobody notices until a guest does.

Most properties handle this in one of two bad ways. Staff with no web experience push updates and slowly degrade the site. Or nobody touches it, and the site drifts out of date while guests read last season's offers.

I manage their Webflow site as an ongoing retainer.

Daily tasks: content updates, new offers going live on time, layout fixes, keeping every page accurate to what the property is actually selling this month. When the marketing team needs something changed, it is changed the same day, done properly, without breaking anything around it.

See, maintenance work is invisible when it is done right. The site just stays fast, current, and correct. That is the whole job.

While managing the site I audited how it was using Webflow bandwidth. Found waste: assets loading heavier than they needed to, media served larger than it displayed.

Cleaned it up and cut $200 off their bandwidth costs. Nobody asked for that audit. I did it because I was in the account every day and the waste was sitting right there.

That is the difference between someone who executes tickets and someone who manages your site. One waits for instructions. The other watches your costs like they are his own.

Ongoing relationship. The site stays current daily, and I keep watching the numbers.

If an agency or freelancer manages your site and has never once told you where you are overspending, they are executing tickets.

Stack: Webflow, Figma Role: Ongoing site management, content operations, cost optimization