Plusight

Connected software for restaurants, hotels and inns

Start with one. Add the next without an integration project.

Reservations, websites, inventory, rooms, point of sale and staffing. Each product works on its own, and they share one account, one permission model and one description of your venue — so the second one has nothing to connect.

Right now, you are the integration.

Every venue runs on five or six systems that were never introduced to each other. Someone carries information between them, and it is almost always the person who can least afford the hour.

A venue should not have to be the integration layer between its own tools.

  • The booking sheet fills up and the kitchen finds out at four o'clock.
  • A price changes in three places, or in one, and the other two go stale.
  • The register knows what left the building. The stock count doesn't.
  • A manager is promoted and gets access to four systems over two weeks.
  • A room is taken offline and the website keeps selling it.
  • Food cost becomes real at month-end, four weeks after you could have acted.

The products

Six products, and where each one honestly stands.

Nothing here is generally available yet. Two run every day in our own venues, one is in private beta, one is working through fiscal certification, and two are still experiments.

Bring guests in

Fill the room, and be findable before anyone calls.

Reservations

Live in our venues

Fewer empty tables, and no missed calls at seven o'clock.

Bookings, deposits and the waitlist, with a voice agent that answers when nobody on the floor can. No-show risk is scored before a table is held. Tiering and entitlements are still being finished.

For the host stand and the phone

Discuss a productReservations

Frontsign

Private beta

A working website in a day, not in six weeks.

Built from the menu, photographs and reviews the venue already has, and set up over WhatsApp. Bring-your-own domain works today; buying a domain through us does not yet.

For a venue with no site, or a bad one

Discuss a productFrontsign

Lodging

Experimental

One availability that every channel agrees with.

Rooms, rates, availability and the whole stay, with a concierge that answers guests in their language. The newest thing we have built, and not yet in front of a venue.

For independent hotels and inns

Discuss a productLodging

Run the service

Everything between the door and the dish.

TableTalk

Certification in progress

Service that doesn't stop when the connection does.

The register, the kitchen display, the counter and the shift board. Keeps taking orders and payments offline, then reconciles when the line returns. Fiscal receipt signing is built and the certification itself is still under way. The largest product we make.

For the floor, the kitchen and the shift

Discuss a productTableTalk

Inventory Pro

Live in our venues

Food cost you can act on Tuesday, not at month-end.

Counts taken by text message from any phone, recipe costing, and purchase orders built from what the venue actually used. Running daily in our own rooms while we work through a pilot checklist.

For whoever counts the stock

Discuss a productInventory Pro

Support the people

A separate network, with its own front door for workers.

Vero

Experimental

Cover a gap without starting a group chat.

A worker-owned shift network: open shifts shared between venues, and a reputation that belongs to the worker rather than the last employer. Early, and deliberately built to answer to workers rather than to us.

For the people working the shifts

Discuss a productVero

Pricing is agreed with each design partner rather than published, because the shape of early access is still changing.

How they fit together

Every kitchen already solved this. It's called the pass.

The counter where the dining room and the kitchen hand things across — the one place information crosses. We built the software version: guest-facing products on one side, operations on the other, and what each of them knows meeting in the middle.

Guest-facing

ReservationsBookings, deposits, waitlist, the phone line
FrontsignThe venue's website
LodgingRooms, rates, stays, the concierge
TableTalkThe register, the kitchen, the counter, the shift
Inventory ProCounts, true food cost, purchase orders
VeroWorker-owned shifts and reputation

Operations

  • Reservations → Inventory Pro

    Eighty covers on the book Saturday. At your usual mix you are six kilos short on salmon, and the supplier cut-off is at two.

  • TableTalk → Frontsign

    You changed the price of the striploin on the register. The website and the online menu now show it too.

  • Lodging → Vero

    Eighteen rooms check out Saturday morning and two housekeepers are on. That is about four hours short. Three cleaners who have worked here before are free.

The shared foundation

Why the second product isn't a project.

Every product is built to stand alone. None of them was designed alone.

One job each
Reservations owns the booking. Inventory Pro owns what's in the building. TableTalk owns the sale. Each product owns exactly one thing and nothing else claims to own it — so there is only ever one answer, never two that disagree.
Where they touch
A menu item is something you sell and something you count. A person is an employee and a shift. We decided who owns each of those before we built, and taught the others to ask rather than keep a copy.
One account
One sign-in, one set of permissions and one description of the venue, honoured by every product and at every location. No keys, no connector, no mapping screen.

Security & compliance

Guest data, payroll and fiscal receipts. The parts nobody markets.

Regulation changes at the border, so we handle it per market rather than inside the product.

Hosting
The platform runs as regional cells. A venue's guest, staff and payment data stays in the region it operates in.
When the line drops
The register keeps serving, printing and taking payment offline, then reconciles when the connection returns.
Languages
English, French and Spanish across every product, notification and assistant — each written as a source language, not a translation.
Separation
Each venue's data is separated by the database itself, which refuses any request that doesn't name the venue it belongs to.
Fiscal certification
Receipts are cryptographically signed and verifiable. Certification is held per zone — today that is one in progress and none yet granted.
Assistants
Every assistant starts by watching. It suggests, then acts with your approval, and automates only what it has been trusted with.

The company

The first venue that had to live with this was ours.

Plusight is a software company. Restaurants and hotels aren't a market we picked off a list — it's the work we already do. Every product here has to survive a Saturday night in our own rooms before anyone else is asked to trust it.

We're small, we ship in public, and we'd rather show you it working than send a deck. Nothing above is described as finished when it isn't.

The point isn't a venue that runs itself. It's one that stops wasting the people in it.

Design partners

Arrange a walkthrough.

We are taking on a small number of venues as design partners. You get the products early and a direct line to the person building them; we get an operator willing to say when something is wrong.

  • Thirty minutes, and no deck.
  • Your venue, your numbers, your actual week.
  • We show you the one product that fits, at the stage it is really at.
  • No obligation, and no pressure to take the rest.