April 2026
Omniboost wasn't supposed to be a hospitality company. The industry had other plans. The best origin stories rarely start with a plan — ours started on a golf course.
We were building tools for other industries. Struggling to find product-market fit, like most early-stage companies do. When someone asked how things were going, I could have given the standard answer. Instead, I told the truth. I wasn't crushing it and I wasn't doing great.
That honesty turned into a conversation. Someone in my network had a local hotel group that needed to connect their Dutch accounting platform to a new cloud PMS based in Prague. The project had a two-month deadline. He wanted to know if I was up for the challenge.
I was.
We had no background in hospitality. No roadmap. No existing relationships in the space. The integration took us a couple of days. The Prague team didn't believe it. They checked. Concluded it actually could be done. Then they invited me over. That trip is where our first real partnership started. Everything else from there is history.
We Decided to Go All In — Deliberately
That first win could have been a one-off. Instead, we made a conscious choice: hospitality was where we were going to build.
Not because we had a thesis. But because we saw a real problem, and we knew we weren't close to understanding it yet.
That led to a second decision, one that might sound counterproductive: we chose not to go API-first.
Most software companies at that stage would have built an API and let partners come to them. We went the other way. We built toward partners — integrating on their terms, in their environments, at their pace. It felt slower. It was slower. But it was the right call.
We didn't have the authority to define how hospitality accounting should work. We hadn't earned it yet. The only way to earn it was to be in the room — connecting systems, watching what happened, learning what the documentation never told you.
The Same Systems. Completely Different Outcomes.
On paper, the stack looks clean. PMS. POS. ERP. A standard like USALI. It feels like it should fit together.
It rarely does.
Two hotels can run the exact same PMS and the same ERP and produce completely different financial outputs. Revenue categorized differently. Tax logic applied differently. Packages split differently. Deposits recognized differently. Timing handled differently.
None of that shows up in a spec. You only see it when systems actually run — and you're the one responsible for making sense of what comes out.
Hospitality Isn't Complicated. It's Inconsistent.
People say hospitality is complex. I don't think that's the right word.
The real challenge isn't complexity. It's inconsistency. Revenue doesn't come from one source — rooms, restaurants, bars, events, spa, parking, each with different logic. Accounting frameworks exist, but interpretation varies by property, operator, and market. The same transaction can be perfectly correct in one environment and completely wrong in another.
That's not something a better connector solves. That's something you earn the right to understand.
What 7 Years Actually Gives You
After thousands of integrations, patterns emerge.
You start to understand what "correct" actually looks like across contexts. Where errors are most likely to occur. How systems behave when they interact — not in isolation. What scales across properties and what breaks under growth.
More importantly, you learn what not to trust. Documentation is often incomplete. Configurations drift. Systems don't enforce consistency. And "good enough" is usually where the real problems begin.
That accumulated experience — not the technology, not the connectors — is the asset.
Why This Matters More Now Than Ever
For most of our history, these inconsistencies lived in the finance department. They showed up as manual reconciliation, late nights at month-end, small fixes that became routine.
Now, with AI entering the picture, the stakes are different.
Systems are more connected. Automation is accelerating. AI is starting to act on financial data — not just report on it. And when that happens, inconsistency doesn't stay contained. If the foundation is wrong, every output built on top of it is wrong. At scale. At speed.
Now We're Ready to Make the Switch
After seven years of building toward partners, we've reached a different point.
We've seen enough. We've earned the perspective. And we're confident enough now to shift — to become the layer that others build on top of, while still maintaining the flexibility to integrate toward partners where it makes sense.
That's not a pivot. It's a maturation. One we couldn't have made honestly at year two or year three.
Because you can't build a reliable foundation on assumptions. You build it on what you've actually seen — transaction by transaction, property by property, system by system.
What It All Comes Down To
The problem isn't moving data.
It's making sure that data means the same thing everywhere it goes.
That's the difference between data and financial truth. And in a world where systems are more automated and decisions happen faster, that difference becomes everything.
We didn't start as experts in hospitality. We became experts by paying attention — and by being honest about how much we still had to learn, for longer than was comfortable.
That's what makes the foundation worth trusting now.
