Pricing
We do not publish a price list. Here is exactly why, and what yours depends on.
A four-store group on one point of sale and a twenty-store group carrying two POS systems and 300 unmapped employee records are not the same implementation. A single number on this page would be wrong for both of you — and you would find out which way at the worst possible moment.
Twenty minutes to scope · A written figure the same week · No card to see the product
The four things that move the number
Every one of these is something you already know about your own business. Bring the answers to the call and the quote takes minutes rather than a round of emails.
How many locations
The primary driver. Nexora scales from roughly three locations to three thousand, on the same data model — a growing regional group and a national or franchise-scale chain both run on it. Below three, a spreadsheet is genuinely cheaper and we will say so. The larger the estate, the more this call is worth having before you commit to a number.
How many point-of-sale systems
One POS across the estate is a clean implementation. Two — common after an acquisition, or where a franchisor changed systems mid-contract — is materially more work, because the definitions have to be reconciled before the comparison view means anything. This is the single largest variable, and it is the one most often left out of the first conversation.
The state of your employee records
In the live pilot group, 257 people existed on the point of sale and not on the roster, carrying 1,253 unattributed hours in ninety days. Mapping them is a one-time action that applies retrospectively to every hour they have ever worked — but it has to happen before any labour figure is worth reading, and how big that list is affects the first month.
Who needs to be reported to
A single owner-operator reading a dashboard is a different configuration from a franchise group where seven super admins, five area managers and twenty-three general managers each see a different slice, and where scheduled reports go out weekly to all of them scoped to what each one is entitled to see.
What you get, at every size
There is no feature ladder where the number you most need sits one tier above the one you bought. The live modules are the live modules.
| Module | What it does | Status |
|---|---|---|
| Dashboard | Net sales, prime cost, labour %, food cost %, sales per labour hour — one store or all, plus a live view of the floor right now | Live |
| Schedule | Cross-store rota, every shift priced before it is published, overtime radar naming individuals | Live |
| Team | One roster of record, CSV import, POS employee mapping applied retrospectively | Live |
| P&L | Store-level statement, gross sales to net income; store comparison; balance sheet. Excel or PDF | Live |
| Expenses | Separate ledgers so nothing double-counts; bank statements read line by line and held for human approval | Live |
| Planning | Weekly labour budget forecast from actual POS history, plan-versus-actual variance per employee | Live |
| Inventory | Purchasing across the estate by item, category and store, with in-hand shown as the estimate it is | Live |
| Reviews | Google and first-party reviews in one inbox per store, scored by theme | Live |
| Reports & Scheduled Reports | Labour, dashboard and P&L summaries emailed weekly or monthly, scoped per recipient | Live |
| NexAI | Ask a question of your own ledger in plain language and get the breakdown behind the answer | Live |
| Command Center & Settings | Access across every store from one screen, permission grid, integrations, audit log, API keys | Live |
| Attendance · Time Off · Onboarding | Clock-in reconciliation, requests and balances, new-starter paperwork | Coming soon |
| Insights · Benchmarking · Forecasting | Anomalies and ranked opportunities, store league tables, sales forecasting by daypart | Coming soon |
| Equipment & IoT · Food Safety | Asset register and connected-device monitoring, checklists and temperature logs | Coming soon |
A few capabilities are still in build, and the product marks them as such on the screen rather than hiding the tab. If one of them is the reason you are looking, say so on the call and we will tell you the honest timeline instead of the hopeful one — including when the answer is that you should buy something else this year.
What the twenty minutes actually is
- You describe the estate. Locations, point of sale, headcount, who needs to see what. Five minutes.
- We open the product on real data. The pilot estate, or yours if you have sent an export. You watch someone rank twelve stores on prime cost in about forty seconds.
- You ask the hard question. Usually one of: will this reconcile against my accountant, can my franchisees see each other's numbers, and what happens when my POS changes.
- We scope and quote. A figure in writing the same week, with the implementation cost in it rather than arriving later as a line you did not expect.
What it is not: a slide deck, a discovery call that books a second discovery call, or a form that puts you into a nurture sequence. If we cannot show you something you did not already know about your own numbers, we have wasted twenty minutes of your day and we will say so.
Fair questions about not publishing a price
Is this just so you can charge different customers different amounts?
It is so the number matches the work. The variable that moves an implementation most is how many point-of-sale systems your estate runs and how clean the employee records are — neither of which is visible from a pricing page. If you want a range before you spend twenty minutes, say so in the form and we will send one.
Do I need a card to see the product?
No. The demo is a demo. Beyond that, the platform has an evaluation tier — a real scope in the permission grid rather than a sandbox of fake data. What it is worth to you depends on setup: until your POS is connected and your employees are mapped, every labour figure reads low, so a fixed fourteen-day clock that expires while you are chasing POS credentials tells you nothing. We agree the scope and the length against your actual timeline.
Is there a contract?
Terms are agreed per group and confirmed in writing before you connect anything. Our position as a young product is that lock-in earns nothing: if the numbers are not useful you should be able to stop, and a long contract does not make the product better — it only delays our finding out that it was not working.
Is onboarding charged separately?
Implementation is quoted with the estate so you see it before you agree to anything, rather than as a line item afterwards. For multi-unit groups we run the first configuration with you, and we would do it even if it were free — clearing the unlinked POS employee list is the highest-value setup task in the product and the one most likely to be done badly by someone doing it alone for the first time.
Do you charge per POS connection?
Connections are scoped and priced with the estate rather than appearing later as a surprise. Tell us how many systems you run before you ask for a number — any quote given without that will move.
Is annual cheaper?
Annual terms are available and priced on the call. Ask for both figures and decide with them side by side. We would rather discount a commitment you actually want to make than advertise a percentage that assumes it.
What happens to our data if we leave?
It leaves with you, and you do not have to wait until the end to prove it. The P&L statement, the store comparison, labour reports, expense reports and the plan-versus-actual variance all export to Excel or PDF from inside the product today, and API keys are available under Settings → Developer for a full programmatic pull. Retention and deletion terms are in your agreement — ask for that clause and read it.
Bring your worst-performing store
Twenty minutes, your own POS data, no deck. If we cannot show you something you did not already know, we will say so and leave.
Book a 20-minute demo