Case study · Rentals
Central Hill: public website, property CMS and blog in ~1 month
A public website with a property catalogue, a CMS to manage it without touching code, and a blog — for short and mid-term rentals, online in a month.
- Timeline
- ~1 month
- Investment
- €9,000 – €14,000
- Stack
“Adding a new property takes us minutes and the website is always up to date. We used to depend on third parties for any change.”
The problem
Central Hill manages short and mid-term rentals, and its digital storefront wasn't keeping up with the operation: without a website of their own to show the catalogue, every change depended on third parties and the property inventory lived offline.
What we built
Three pieces working as one:
- Public website with the property catalogue, designed to turn visits into enquiries.
- Property CMS: the team creates, edits and publishes properties — photos, prices, availability — without touching code or waiting on anyone.
- Integrated blog, for area and seasonal content that feeds SEO.
The stack: Next.js + Tailwind for the website, Neon (Postgres) for data, Cloudflare R2 for images and Netlify for hosting.
How we did it
The model came first: what a property is, which fields short-term needs that mid-term doesn't, and how publishing works. With that locked, website and CMS were built in parallel — Central Hill's team started loading real properties before the site went public, so launch day came with a full catalogue.
The result
The website is always current because it's updated by the people who know the properties, not an external vendor. Publishing a new property is a form, not a ticket. And the blog gives the brand its own channel to grow in search.