Building better restaurant operations through connected technology.

Restaurants and hospitality businesses, and deliberately a fairly wide range of them rather than one narrow slice. The same connected approach is meant to suit an independent single site and a group running several outlets under one roof, which are genuinely different operations — a group cares about consistency and roll-up reporting across venues in a way a single site does not, and a single site cares about not paying for machinery it will never switch on. What actually fits your business depends on things this page cannot see: how many sites you run, how you take orders, how your kitchen is laid out, whether you need multi-venue reporting, and what you already have in place that would need to be replaced or connected to. That is a conversation rather than a checkbox, and it is the right conversation to have before anyone quotes you anything. So rather than assert here that Vertex is or is not right for a business of your size, the honest answer is to route the sizing question to the people who can look at your specifics: our sales team can tell you plainly whether what you need is something the platform does well today, and if there is a gap they can tell you that too. Ask them directly about your number of sites and your setup — that is the fastest way to a real answer.

This is the part of an about page where it is tempting to reel off a head-office city, a list of countries served and a count of markets, and this answer is deliberately not going to do that, because those specifics are not stated here and putting an invented one in front of you would be worse than leaving the question open. Regional availability, supported languages and currencies, local payment arrangements, and whatever tax and compliance handling a given country needs are exactly the details that vary from place to place and change over time, so they are not the sort of thing to pin down in a static paragraph. What can be said honestly is that if where you operate matters to your decision — and for anything touching payments, tax or local regulation it always does — the reliable way to get a correct answer is to ask the team directly rather than infer it from marketing copy. Tell them the countries or regions you run in, and they can tell you what is available there, what is not yet, and what any of it would involve for you. You can reach them through the contact page, and if you would rather see the product against your own market before going further, a demo is the natural next step. Better a precise answer from a person than a confident-sounding one on a page that has not met your business.

Two straightforward routes, depending on what you want out of the conversation. If you have questions — about whether the platform fits your setup, about a particular part of the product, about regional availability, or anything else this page has sent your way — the contact page at /contact is the front door, and it reaches the people who can actually answer rather than a general inbox that forwards things around. If what you would really like is to see the thing working rather than read about it, ask for a demo at /get-a-quote; that is where you can arrange to be shown the product against something close to your own operation and, in the same conversation, get pricing scoped to what you would actually use rather than a list price for a bundle you do not need. The two overlap in practice — most real conversations start with a question and end with a walkthrough — so do not overthink which link to pick. Either one gets you to a person. The only thing worth doing before you reach out is having a rough sense of your own setup to hand: how many sites, how you take orders now, and what you are hoping to fix or replace. That turns a generic demo into a useful one, and it turns a pricing conversation into a real number instead of a range.

Roles come and go, so rather than state a headcount or a growth plan this page does not have, the honest answer is to point you at the one place that is always current: the careers page at /careers lists whatever is genuinely open right now, and that list is the source of truth rather than anything a paragraph here could claim. If you look and nothing fits, that is worth reading as this-moment rather than never — open roles change, and it is entirely reasonable to check back. If you are keen on the kind of work we do but do not see your exact role listed, the careers page is still the right first stop, because it will tell you how the team prefers to hear from people and whether speculative applications are welcome; that beats guessing at an email address from here. What this answer is deliberately not going to do is describe the size of the team, the pace of hiring, or where the roles are based, because those specifics are not given on this page and an about section that makes them up is doing the reader no favours. Go straight to /careers for the live picture, and treat that page — not this one — as the accurate account of what is open.