We recently bought a piece of land in the Dalmatian hinterland.
That sentence still feels slightly strange to write. Most of my work happens in code, databases, product systems, and AI-assisted software workflows. Land is different. It does not care about a roadmap. It has access constraints, weather, neighbors, infrastructure, paperwork, seasons, and a very physical way of forcing you to think slowly.
But that is also why I like it.
The question I keep coming back to is simple: what would actually make sense here?
Not as a vanity project. Not as a generic villa. Not as something that looks good in a spreadsheet but turns into an operational headache. I am interested in a practical model that could become a real local business over time, with enough upside to matter and enough discipline to avoid overbuilding before the demand is proven.
The current direction
The main idea is an event estate.
Think small private celebrations, family gatherings, baptisms, first communions, birthdays, intimate weddings, company days, and similar events. A clean indoor space, a strong outdoor area, parking, shade, water, power, toilets, and enough flexibility to host different kinds of gatherings without pretending to be a full restaurant or hotel.
I like this direction because it matches how people here actually live. Families gather. Celebrations matter. Good outdoor space matters. Parking matters. Privacy matters. A place that is close enough to the coast and Split area, but not trapped inside coastal prices and congestion, can have a useful position.
The important part is phasing. The worst version of this project would be to build something expensive first and then hope the market agrees. The better version is to design the property so that it can support multiple small tests before the final shape is obvious.
The business models I am considering
The event estate is the anchor, but it may not be the first cash-flowing product. I am thinking in layers.
1. Secure storage and yard space
This is the least romantic idea and maybe the most practical one.
A fenced, camera-covered yard could serve people who need space for campers, trailers, small boats on trailers, jet skis, seasonal equipment, or contractor gear. Inland storage is not glamorous, but coastal space is expensive and crowded. A simple, secure, well-run yard could produce recurring monthly income while the larger estate is still being developed.
The risk is that storage can quickly make a property feel industrial. If this ever happens, it has to be contained, visually screened, and compatible with the longer-term direction of the place.
2. Outdoor family events
Before trying to host high-pressure weddings, a smaller outdoor product may be the right bridge.
Children's birthdays, family lunches, casual celebrations, and company afternoons are easier to test. They still require serious basics: toilets, shade, safe circulation, parking, cleanup, water, electricity, and clear rules. But they are a better way to learn how people use the space than jumping directly into the most demanding event category.
3. A private celebration venue
This is the higher-upside version: a polished venue for private events, with a strong indoor-outdoor flow and a clear operating model.
I would rather keep food as a partner/catering model than build a restaurant. A venue can be focused. A restaurant adds staffing, stock, daily operations, and a completely different type of risk.
The challenge here is that a venue needs to be excellent at the boring details. Sound, parking, cleaning, bathrooms, weather fallback, lighting, access, waste, guest flow, and neighbor impact matter as much as the photo-friendly parts.
4. Small rural stays or glamping
A small number of high-quality stay units could work in this part of Croatia, especially if they connect to nature, nearby towns, rivers, food, cycling, and a slower version of Dalmatia.
But hospitality is not passive. Guests, cleaning, reviews, booking platforms, maintenance, and seasonality are real work. I am open to it, but I do not want to confuse a nice-looking tourism concept with a business I actually want to operate.
5. Trades and small-business yard space
Another possible direction is controlled B2B yard space for small local businesses that need secure outdoor storage but not a full warehouse.
This could be a strong cash-flowing use if the legal and planning context supports it. It also has brand risk. A property cannot be both a premium family-event estate and a messy contractor yard unless the layout is very deliberate.
What I am trying to avoid
I do not want to build something that only works in a best-case spreadsheet.
I also do not want to create a business that depends on constant firefighting, unclear rules, or annoying the people around it. Any real use has to fit the local planning framework, permits, utility constraints, and neighbor reality. That is not a footnote. It is part of the product.
So my current filter is:
- Can it start small?
- Can demand be tested before major spending?
- Can it create recurring or repeatable revenue?
- Can it coexist with the long-term estate vision?
- Can it be operated without becoming a second full-time job in the worst possible way?
The model that makes the most sense right now
If I had to describe the current strategy in one sentence, it would be this:
Use simple recurring-income ideas to de-risk the land while slowly building toward a higher-value private event estate.
That could mean storage first, small family events second, and a more polished celebration venue later. Or it could mean discovering that one of those assumptions is wrong and adjusting before too much capital is committed.
That is the part I find interesting. This is not only a real-estate question. It is a product question. The land is the platform, but the product is the operating model.
What would you do?
I am especially interested in hearing from people who have built or operated:
- small event venues
- rural tourism projects
- secure storage yards
- family entertainment spaces
- hospitality businesses outside major city centers
What worked? What looked good on paper but failed in practice? Which details mattered earlier than expected?
If you have a useful perspective, send me a note at [email protected]. I am not looking for generic advice as much as real operating lessons.
For now, I am treating this as a slow build: learn the constraints, keep the options open, test demand early, and only then make the expensive decisions.