LubLabs

BACKGROUND

Introduce your business and what you do there.

I’m the general manager of Sama Aan Travel and Tourism. We facilitate ticketing to over 50 travel agents in Jordan and arrange holiday trips for individuals within the Middle East, GCC, Asia, and Europe.

OPPORTUNITY / CHALLENGE

What challenge were you trying to address with LubLabs?

We needed to build a scalable and well-structured B2B selling platform for air tickets that integrated with the Sabre API and many other airline APIs.

SOLUTION

What was the scope of their involvement?

LubLabs has taken over the full-cycle development of our B2B travel distribution platform. The scope includes designing a scalable system architecture and implementing complex integrations with major airline GDS and NDC APIs, specifically Sabre, and FlyDubai. Key deliverables include a robust backend built for high-volume ticket processing, a custom middleware to unify different airline data formats, and an intuitive agent dashboard for booking and management.

What is the team composition?

We work with 2–5 teammates from LubLabs.

How did you come to work with LubLabs?

We found them through a referral. We chose them over other options because they had high ratings, were close to my geographic location, offered good value for the cost, and had company values aligned with ours.

How much have you invested with them?

The investment is confidential.

What is the status of this engagement?

We started working with them in May 2025, and the engagement is ongoing.

RESULTS & FEEDBACK

What evidence can you share that demonstrates the impact of the engagement?

The most measurable outcome has been the successful, stable integration of the Sabre API alongside multiple NDC carriers like Turkish Airlines and FlyDubai. We’ve achieved a significant reduction in search latency across these providers, and the system now handles complex booking flows without errors. The architecture is clean and well-documented, which has given us the confidence that the platform can scale as our agency network grows.We’ve measured success through two main KPIs: system latency and integration uptime. We’ve achieved a 40% reduction in data processing time for multi-source flight searches. Additionally, we’ve maintained 100% uptime during our intensive QA phase, with zero critical bugs reported in the core booking engine.Since we’re still in the staging and development phase, we haven’t seen market sales yet, but the internal impact is obvious. The way they’ve structured the backend has made our lives so much easier. Tasks that used to feel like a headache — like syncing different airline APIs — are now handled by a system that actually works. It’s saved us a ton of back-and-forth time, and for the first time, we feel like we have a platform that’s actually ready to scale the moment we hit 'live.'

How did LubLabs perform from a project management standpoint?

They’re very structured. We had a clear roadmap from day one for the Sabre and NDC integrations, and they’ve stuck to it. We haven’t had those typical 'developer delays' you usually hear about. Every time they promised a build for internal testing, it was ready. It’s been a very smooth process, which has allowed me to focus on the business side of things instead of worrying about whether the technical side is falling behind.We communicate through in-person meetings, virtual meetings, and emails or messaging apps.

What did you find most impressive about them?

The most impressive thing is the level of ownership they take. Even though we’re still in the staging phase, it feels like they’re part of my internal team rather than an outside agency. Their communication is transparent, and the code they deliver is clean and well-structured from the start. They’ve turned a really stressful, complex integration project into a very manageable and predictable process.

Are there any areas they could improve?

Early on, the updates were a bit more focused on the code side of things, but we quickly moved into more frequent, business-focused syncs. It’s hard to find a real flaw, but maybe more formal documentation during the initial onboarding would have saved us a little bit of back-and-forth time. Still, once we got into the rhythm of the project, everything was very smooth.