Features
Most feature lists are written to survive a comparison spreadsheet. This one is written so you can tell, before a trial, whether the thing you need is in here.
Every section says what the screen holds. The last one says what the product does not do.
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 operating screens
Bookings
Create, edit and move bookings on a board. Status on every card — requested, confirmed, dispatched, arrived, returning, done.
Drag and drop, because a dispatcher rearranging a busy night is doing spatial reasoning and a form-based interface breaks it. The board has to move at the speed the person is thinking.
Each booking carries the guest, the staff member, the course, the nomination type, options, and the source the guest came from.
Dispatch
Who is out, who is back, who is next. Drivers update arrival and return from their own screen, so the board is current without the dispatcher phoning anyone to find out.
Every call made to establish state is turnaround that was not spent moving.
Shifts
Staff submit availability in 30-minute blocks from their phone. Managers confirm.
The submission itself becomes the record, which is what makes availability trends visible — someone quietly narrowing their hours shows up weeks before they resign.
Separate boards for floor staff and for drivers.
Schedule
Confirmed shifts laid out against the day. Who is on, when, and where.
Settlement
Broken out by line, and every line is split three ways.
course time (extension) nomination option
cosplay area / transport hotel additional
discount channel fee other total
Each of those carries the amount, the house share and the staff share as separate figures — twelve lines, thirty-six columns, rather than one number per booking.
This is what makes item-level margin a query instead of an estimate, and it is why a price change can be measured at all. Per staff member it produces a payment statement, so the end-of-night conversation starts from a number both sides can see.
The channel fee sitting on the booking is the quiet one. It is what lets acquisition cost be attributed to the guest rather than to the month.
Nomination types
Nomination types are a master you define, one per venue. The product does not impose names on you.
Each type carries the total fee, the house share and the staff share — so a type is not just a label, it is a settlement rule. Rankings and payouts both come out of the same definitions.
Guest analytics
Guests are classified into five bands — first-time, early-repeat, steady, surge, top-tier — each split into active or lapsed. The lapse line is 90 days without a visit.
Because a guest record persists across visits, this answers the questions a per-booking system cannot: returning share, lifetime value, and which source actually delivered guests who came back.
Accounting analytics
Revenue by day, by weekday, by venue, by staff member. Guest counts and revenue per head alongside, because the two together separate a busier-and-poorer night from a smaller-and-better one.
CTI
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. A booking can be created from the call without retyping the number.
Call history is kept with timestamp and number.
Masters
Venues, rooms and tables, courses with time and price, options, staff, areas, media sources, guest categories. Organised by category with a sidebar rather than one long settings page.
The mobile apps
Staff mobile submit shifts, see the schedule, clock in and out, guest notes
Driver mobile assigned run, arrival, return. Deliberately almost nothing else
Guest mobile book, choose, see points and history
The driver screen is intentionally sparse. A screen used while working has to be operable in three seconds.
Ask it from ChatGPT
tasteck exposes an MCP interface, so your numbers can be asked as a question in a chat instead of found in a dashboard.
"What was revenue per head last Friday against its median." "Which regulars have not been in for six weeks." "Which channel is under its ceiling."
Measured against every vendor listed on Japan's principal nightlife-industry directory, this is the first implementation of it in the category, and the same interface is callable from anywhere rather than being tied to one assistant.
Multi-language
The operating surface itself is multi-language, with the language set during onboarding — not a translated marketing site with a Japanese product behind it.
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 needs three things in one 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.
What it does not do
Listed plainly, because finding out in week three is worse than finding out now.
Not a POS no cash drawer, no card processing, no payment terminal
Not a phone system CTI connects to an existing telephony service
Not a routing engine no map, no optimal-route computation
Not payroll settlement produces the figures; paying people is elsewhere
Not stock control no counting, no supplier ordering
Not an A/B tool no experiment framework, no elasticity model
Not a report sender it does not assemble a weekly summary and email it to you
And it does not decide policy. Nomination fees, rotation rules, dispatch priority, back rates — the product records what you decided and shows what it produced.
Where it fits, and where it does not
It fits venues with staffed service, guests worth knowing by name, and a booking or dispatch flow.
It fits less well a high-volume standing bar where nobody sits and every guest is anonymous. The value here is concentrated in the guest record; a venue that cannot attach a guest to a visit will not get it. A good POS will serve that room better and cost less.
Pricing
Up to 2 venues from $34 / month
10 venues from $100 / month
25 venues from $200 / month
Per venue, not per head. Thirty days free on every plan, cancel any time.