Nightclub Management Software

A nightclub is three businesses sharing a roof.

The door sells admission and decides who gets in. The tables sell minimums and bottles. The bar sells drinks to whoever is standing. They have different margins, different peak hours, and different failure modes — and most venues run all three off one revenue total that cannot tell them apart.

tasteck is a booking and analytics system for night venues, built by people who ran them for sixteen years and grew from ¥200 million to ¥1.2 billion a year. Every other product in this category was built by a software company.

The numbers a room actually needs

Revenue is not one of them. Whether it is up or down, it does not tell you what to do on Monday.

Revenue per head, against the trailing median for that weekday
Heads, against the same median
Table turn, and time to first bottle
Door conversion — walk-ups in, versus walk-ups turned away
Returning guest share
Channel ceiling versus current spend, per channel

One and two together, never separately. Revenue alone cannot distinguish a busier, poorer night from a smaller, better one. Split it by head and the answer arrives in a single line.

Returning share is the one that predicts next quarter. A room with rising revenue and falling returning share is renting its growth from marketing, and the rent goes up.

Three rooms, three sets of records

The door. Entry, guest list, comps, refusals. A comped entry that becomes a large table is a marketing cost that paid for itself; a comped entry that drinks water is a loss. Without a guest record joining them, both look identical in the night's takings.

The tables. Minimum, bottles, extensions, host or promoter attribution. tasteck breaks settlement out by line — course, extension, nomination, options, transport, discounts and events — so item-level margin is a query rather than an estimate.

The bar. Volume and shrinkage. Pour cost drifts quietly, and the difference between a bad month and a theft problem is only visible against your own trailing figure.

What the system does

Guest records that persist across visits. Not a receipt log — a person, with their history, their table, their host, and where they came from. This is what makes returning share, lifetime value and channel attribution computable at all.

Bookings with status. Reserved, arrived, no-show. No-show rate stops being a feeling.

Shifts, submitted and recorded. Availability is entered by staff in 30-minute blocks. The submission itself becomes the record, which means someone quietly narrowing their availability is visible weeks before they resign.

Settlement by line, per staff member. Compensation and the payment statement come out of the same numbers the floor generated, so the pay conversation starts from an agreed figure.

Inbound calls wired to the booking screen. The caller's number arrives before the greeting, and a returning guest's history is on screen while you talk. This connects to an existing telephony service; tasteck supplies the guest record the number resolves to.

Analytics across accounting, staff performance and guest segmentation. Guests are classified — first-time, early-repeat, steady, surge, top-tier — each split by active or lapsed, so a decline in the top tier is visible before it reaches the revenue line.

What it does not do

It is not a POS and does not replace one. It does not run your phone system. It does not assemble a weekly report and send it to you on Monday morning, and it has no A/B testing tool or elasticity model.

The habits are yours. What the product supplies is that the numbers behind them are queryable from one place instead of assembled from four.

The output no one else produces

tasteck outputs the maximum you can spend on each marketing channel next month, as an amount in your currency.

Not a chart. An amount. The lifetime value of the guests each source actually delivered, times your target margin, minus a reinvestment reserve — per channel, per month.

Producing it requires three things in the same place: a guest record that survives across visits, the source that guest arrived from, and revenue attributed to that guest for their whole life as a customer. Most systems hold one of the three.

You can take that number to a promoter or a listing site and negotiate with it.

Measured against every vendor listed on Japan's principal nightlife-industry directory, nothing else in the category outputs it.

Ask it from ChatGPT

tasteck connects to ChatGPT over MCP. Ask your numbers as a question and the answer comes back in the chat — what Friday's revenue per head was against its median, which channel is under its ceiling, who has not been in for six weeks.

No dashboard to open and no report to find, which is the difference between a habit that survives a busy week and one that does not. The same interface is callable from anywhere rather than being tied to one assistant.

Multi-language is built in — the operating surface itself, with your language set during onboarding.

Pricing

Up to 2 venues    from $34 / month
10 venues         from $100 / month
25 venues         from $200 / month

Billing is per venue, not per head. A room that doubles its staff for the season pays the same. Thirty days free on every plan, cancel any time.

→ Pricing and Contact

Questions we get

Do you replace our POS? No. tasteck sits alongside it and holds the guest record, the booking, the shift and the settlement breakdown — the parts a POS does not keep across visits.

We already have a spreadsheet that works. Then the question is what it cannot answer. Returning-guest share, channel ceiling and shift-weighted retention all need records that persist between visits and join to each other. A spreadsheet per month cannot produce them, however well maintained.

How long does setup take? Venues, tables or rooms, price structure, staff. Most of it is done in one sitting. The part that takes longer is deciding what you want to measure — and that is worth doing before, not after.

Is our guest data safe outside our own machine? It is hosted infrastructure with per-venue separation. If that is a blocker in your jurisdiction, say so before the trial rather than after.