Hospitality & Shortlet

Stays in this market are branded hotels, independent shortlets, and the OTAs in between. Transcorp, Radisson, Marriott, Hilton sit next to Airbnb and Booking.com. In Lagos and Abuja the shortlet operator is as real as the hotel brand. Eko and Hotels.ng belong in that picture. Guests want a verified bed. Owners want occupancy and payout. Companies want one invoice.

Software in this sector is availability, access, money, and who is allowed through which door. A pretty landing page that cannot take a booking is marketing. Two calendars that both sell Friday is an argument at the gate. An owner who cannot see what they are owed will not stay on the platform.

We build that layer. We do not run a hotel. We do not list your flats. You keep the rooms, the owners, and the code. Kivo, built for short-stays in Abuja, is the case in this sector.

Inquire now

Who this is for

Shortlet operators who still close the calendar on WhatsApp and a spreadsheet.
Hotel or apartment products that need guest, owner, and company as separate doors.
Teams who have to pay owners and invoice corporates without reconstructing the month by hand.

In this sector

Hotels, shortlets, calendars, and who gets paid.

Branded hotels
Transcorp, Radisson, Marriott, Hilton: the names guests already trust. The product still has to hold a room and a night.
Independent shortlets
Owners, caretakers, and listings that are not a chain. Availability and access matter more than a brand film.
OTAs in between
Airbnb and Booking.com already own a habit. Direct booking still has to exist, and the two calendars cannot both sell the same night.
Corporate stays
One invoice, named guests, a company account. Not a personal Airbnb receipt the finance team will not accept.

Areas covered

We build the software a stay actually runs on. Typical work includes:

01
Guest, owner, and operations
Three doors. The guest books and arrives. The owner sees occupancy and money. Operations sees the calendar, the keys, and the problems. They do not share one login.
02
Calendars that do not double-book
A night is sold once. Blocks, turnovers, and OTA holds have to show up in one place. If two systems can sell Friday, you will meet both parties at the door.
03
Payouts and invoices
What the owner is owed, what the company is billed, what was refunded. Month-end cannot be a reconstruction from WhatsApp.
04
Handover
Repo, keys, hosting in your name. Same handover as Kivo. We do not keep the guest list after we leave.

What the software has to survive

A stay product is not finished when the listing looks like Airbnb. It has to survive a double booking, a payout argument, and a guest who cannot reach the caretaker.

The night is unique

Inventory is a date, not a SKU you can reprint. Overbooking is not a warehouse problem. The product has to lock the night.

Access without WhatsApp

Instructions, codes, a person on call. If the only way in is a chat that went unread, the review is already written.

Owner money

Occupancy without payout is a fight. Statements have to match stays. We are not the bank. We are the record.

OTAs and direct

If you sell on Booking.com and on your own site, both must see the same close. We wire what you actually use. We do not invent a channel you do not have.

Questions an owner — or a guest at the gate — will ask

If the product cannot answer these, you will settle it in person at 11 p.m. We design so you do not have to.

01
Can two calendars book the same night?
02
Does the owner get paid for the stay that actually happened?
03
Can a guest get in without WhatsApp-ing the caretaker?
04
If Booking.com and the site both take a night, who wins?
05
Can a company get one invoice for three stays?

How we build it

We build for the night, the door, and the statement — not for a travel brochure.

One calendar

Direct and channel holds in one model before we style the listing page.

Three roles

Guest, owner, operations. Drawn before the first marketing block.

Money as a record

Stays, fees, payouts, invoices. Exports an owner or a company can take.

Handover

Repo and runbooks: block a night, reverse a payout, rotate an access code.

Someone who has handed a guest a key sits in discovery if you have them.
We do not ship a listing site that cannot hold a night.
We do not keep guest or owner data after handover.

Where we stop

We build the system. We do not pretend to be the hotel, the OTA, or the landlord.

We do not operate Transcorp, Eko, Radisson, Marriott, Hilton, Airbnb, or Booking.com. Those names define the sector.
We do not hold rooms or take the guest’s money as the merchant of record unless that is a separate, named setup.
We do not hold an NTDC, NAFDAC, FCCPC, NDPC, or NITDA licence. Those agencies define the sector. They are not clients.
We do not keep the repository or production keys after handover.

The landscape

Agencies that write the rules, then hotel brands guests already know, and the OTAs that already own a habit. This is the market — not a list of Emicraft clients. Eko Hotels and Hotels.ng belong in that picture even when we do not host their marks.

Regulators & agencies