Inside XeniaKit: How I Pivoted From Guidebooks to an Operating System

I built something that worked. People signed up. Made a beautiful digital guidebook for your short-term let(Airbnb) in minutes.

Then they didn’t come back.

Not failure. Indifference. That’s worse.

When I started XeniaKit, the idea was straightforward: hosts need a faster way to create guidebooks. Digital, AI-generated, shareable, with analytics built in.

It made sense on paper. One clear problem. One clear product. The lean startup playbook.

I spent weeks on the spec. Built it. Shipped it.

Sign-ups came in. Early momentum looked real. Week one, a few hosts were using it. Week three, activity dropped. Week six, most users had gone quiet.

I’d built something useful. But useful isn’t the same as necessary.

Here’s what I didn’t realize: creating a guidebook is a one-time job. You do it once. Maybe update it once a year. It’s not something hosts open daily. It’s not recurring.

If it’s not recurring, I don’t have a business. I have a feature.

I own two holiday lets. I started managing them last year to understand the space better.

Around week five, when retention was flatlined, I stopped theorizing about what users needed and started looking at my own workflow.

Guidebook built. Finances in a spreadsheet. Compliance reminders on post-its. Calendar scattered. I’m running my entire business across five different tools and constantly worried I’ll forget something critical.

That’s when it hit me: I wasn’t solving a problem for some hypothetical user. I was living this exact problem.

Fragmentation kills hosts. And I was getting killed by it.

The guidebook I built? It was just one slice of the mess.

I had to ask myself: Is XeniaKit actually solving what hosts need, or am I optimizing the wrong thing?

The answer was obvious once I stopped guessing and started paying attention.

Hosts weren’t struggling because guidebooks were hard to create. They were struggling because they were juggling four completely separate worlds:

Guest Experience - How do I welcome guests and reduce support requests?

Compliance - How do I stay on top of certificates, renewals, and regulations?

Finance - How do I actually know if my properties are profitable?

Operations - How do I see what’s working and what isn’t?

Each required a different tool. A different login. Different data. Different workflows. And when you’re managing multiple properties, that fragmentation becomes chaos.

I wasn’t building for a gap. I was building for one small part of a much bigger problem.

I faced two paths:

Option 1: Stay narrow Keep XeniaKit as a guidebook tool. Own that niche. Build a small, profitable business focused on one problem.

Option 2: Expand and solve the real problem. Reframe this as an operating system for hosting businesses. Add compliance tracking. Add finance management. Connect it all. Solve the actual workflow, not just one slice.

The safe choice made sense on paper. Focused product. Clear positioning. Lower complexity.

But I kept coming back to the same reality: I wasn’t asking “how do I improve guidebooks?” I was asking, “How do I stop managing my business across five different tools?”

Every conversation pointed in the same direction. The problem wasn’t about improving one feature. It was about building a platform that actually connected everything hosts needed.

So I pivoted.

The Four Pillars

I mapped out what hosts actually need to run a successful hosting business:

Pillar 1: Guest Experience Beyond just guidebooks. AI-powered guides that answer questions before guests ask. 24/7 AI concierge for common questions. Lead capture for direct bookings. Multi-language support. The goal isn’t the prettiest guidebook. It’s reducing host workload and improving reviews.

Pillar 2: Compliance Hub. This surprised me. I didn’t expect compliance to be such a pain point until I started hosting in the UK myself.

Gas safety certificates expire. EPC ratings need renewal. Insurance requires proof of compliance. Hosts track this with spreadsheets and calendar reminders. It’s stressful. It’s error-prone. It’s constant background anxiety.

What hosts need: A single place to track all compliance requirements. Automated reminders before expiry. Risk assessments. Document storage.

Pillar 3: Finance Hub: The biggest gap I found.

Hosts have no idea if their properties are actually profitable. They export CSVs from Airbnb, Vrbo, and Booking.com. Paste them into spreadsheets. Manually add expenses. Still don’t have a clear picture of Net Operating Income per property.

They can’t compare properties. Can’t see trends. Can’t make data-driven decisions about which properties to keep, which to optimize, and where to invest next.

What hosts need: Automatic data import. Real profitability metrics. Actual numbers instead of spreadsheets and guesswork.

Pillar 4: Analytics & Operations The feedback loop that ties everything together.

Hosts don’t know what’s working. Which sections of the guidebook do guests actually read? Which properties get the most engagement? Without this data, they’re flying blind.

What hosts need: Visibility into how guests interact with their properties. Engagement metrics. Data that informs decisions about what to improve.

Here’s what I realized: these four pillars aren’t separate features. They’re interconnected.

A great guidebook reduces support requests and improves reviews. Better reviews lead to more bookings and higher revenue. Compliance tracking prevents costly fines and keeps properties listed. Analytics tells you what’s working so you can optimize everything.

When you bring these four pillars together in one platform, something shifts. Hosts stop juggling tools. They stop losing data between systems. They start seeing their business clearly.

Managing my own two properties made this crystal clear. I was living the pain. And I was building the solution for the exact problem I faced every day.

1. Hosts want simplicity, not features: They don’t care about having 50 features. They care about solving their four core problems without switching between five different apps. I certainly don’t want to juggle five tools to manage my two properties.

2. Compliance anxiety is real: I didn’t expect this to be such a pain point until I hosted in the UK myself. Hosts lose sleep over missed renewals. A simple compliance hub removes that anxiety.

3. Finance data is power: Once hosts see their real NOI per property, they make better decisions. They optimize. They scale. They know which properties to keep and which to sell.

4. One platform changes behavior: When everything is in one place, hosts use it more. They check analytics. They update compliance records. They make data-driven decisions. Fragmentation kills engagement.

I’m still building. Still learning from hosts. Still refining what “operating system for property hosts” means.

But the four pillars are solid. They reflect real problems. And they’re guiding everything I build next.

The goal: By the end of Q1, 20+ paying customers using XeniaKit to manage their properties, not just create a guidebook.

I almost spent six months perfecting a product nobody needed to use every day.

What saved me wasn’t a better plan. It was stepping back and looking at what I was actually living.

I own two properties. I manage them myself. I was using five different tools. I was the exact problem I was supposedly solving.

Sometimes the best customer research is just paying attention to your own pain.

Here’s what I’m curious about:

What product are you building right now? More importantly, are you solving something that happens once, or something that happens every day?

Hit reply and tell me. I read every response, and your answer shapes what I write about next.

(Also: If you’ve made this mistake before, built something people liked but didn’t love, I want to hear about it. Helps me know I’m not alone in this.)