Pricing
This is the price of FACE by Runink: Fulfilment Autonomous Claims Engine. You pay for the number of people who use it, and you choose where the work runs: on Runink's shared machines, in your own cloud account, or on your own premises.
That is the whole shape of it. The three licences below differ on that one question of where the work runs, and the price follows from it. What the work is comes first, though, because that is the part a price is worth arguing about.
The work
Operations Actionable Twins
These are the operational jobs FACE by Runink is built for. In each one the evidence is already in your systems and nobody has the hours to join it up. Each one ends with a person approving a drafted action rather than reading another dashboard.
They are grouped by when in the operation the problem turns up. Each opens onto the page that explains it: what it reads, what it drafts, and the measures to write your own figures against.
Enterprise Exclusive
Digital Paralegals
Your claims and recovery desk. They read freight bills, proofs of delivery and your SLA terms, assemble the evidence for each shortage, damage or late-delivery claim, and draft it inside the carrier's filing window. A person on your team approves every claim before it is filed.
Statistical Buyers
Your demand planning desk. They test forecasting methods against your own sales history, keep the one that would have predicted it best, and flag where stock cover falls short of lead time. Transfers and reorders are proposed for your planners to approve.
Revenue Operators
Your freight audit desk. They check every invoice line against your negotiated carrier contracts and rate confirmations, flag fees and accessorials the contract does not support, and draft each short-pay with its evidence. Your finance team decides what is withheld.
Planning what you will need
Before you commit. What next quarter will ask for, what cover you are holding, and what a change would cost if you made it.
-
Demand forecasting
A line starts moving weeks before the reorder point does.
-
Stock cover and supplier planning
Most stockout warnings arrive after the safety stock is already gone, which leaves you paying for air freight.
-
Testing a change before you commit
A port shuts and you have a day to pick a new route.
Moving it
While the work is moving. The route, the picture across the whole chain, and the driver whose hands are on the wheel.
-
Route planning
The plan that was optimal at six in the morning is not optimal by ten.
-
Supply chain visibility
The facts are in four systems in four formats, and joining them takes a morning nobody has.
-
Hands-free dispatch for drivers
The person who knows a load is late is the one who cannot type.
When something goes wrong
After the event. A container that drifted warm, a return sitting on the dock, a claim with a deadline running.
-
Cold chain and yard safety
A container drifts warm overnight and nobody opens the door until morning.
-
Returns and reverse logistics
A returned item is worth the most on the day it comes back.
-
Freight claims and port charges
Claims expire because assembling one takes a morning.
Paper, policy and proof
When someone asks you to prove it. The claim file, the clause that governs, the report.
-
Underwriting and claim files
The policy wording, the loss report, the reserve history and the authority limit for a claim that size sit in four places.
-
Contract and obligation review
A routine question settled by a paragraph takes a day and a half to answer, so it gets answered from memory instead.
-
Privacy and audit records
Operating a system quietly writes personal data into its own logs.
The three licences below differ on one question: how many people need it, and whose machine it runs on.
A separate kind of charge. Everything above is the seat price: flat, set by headcount, unaffected by how much you use it. These two are the opposite of that on purpose — nothing is billed until FACE has already created or protected money for you.
Business Outcome Fees
Auto-Provisioning
1% to 3% of the transaction value FACE places on your behalf, capped at $50 per order. A large bulk order is never penalised for its size.
Claims & Short-Pay Recovery
20% of what is recovered. Success-fee only — nothing is billed when nothing is recovered.
LITE LICENCE
FOR TEAMS OF 1 TO 9 PEOPLE
PER PERSON, PER MONTH
PER PERSON, PER MONTH
- RUNS ON RUNINK'S SHARED MACHINES, TAKING ITS TURN ALONGSIDE OTHER CUSTOMERS' WORK
- 18,000 UNITS PER PERSON PER MONTH, POOLED ACROSS THE TEAM
- MORE UNITS AS YOU GO, OR BOUGHT AHEAD: 10% LESS FOR A MONTH, 20% LESS FOR A YEAR
- UP TO 900 UNITS PER PERSON PER HOUR; WORK PAST THAT PACE WAITS ITS TURN
DEDICATED LICENCE
FOR 10 PEOPLE AND UP
PER PERSON, PER MONTH, ON A YEARLY CONTRACT
ON YOUR OWN CLOUD
- RUNNERS IN YOUR OWN GOOGLE CLOUD PROJECT, DATABRICKS OR SNOWFLAKE ACCOUNT
- UNLIMITED COMPUTE UNITS
- YOUR CLOUD BILLS YOU FOR THE COMPUTE DIRECTLY
- YOUR OWN WEB ADDRESS
ENTERPRISE LICENCE
FOR RUNNING IT WHERE YOU CHOOSE
PRICED WITH YOU
WHERE YOU RUN IT
- RUNNERS ON YOUR OWN SERVERS, INCLUDING SITES KEPT OFF THE NETWORK
- OR IN YOUR OWN CLOUD ACCOUNT
- UNLIMITED COMPUTE UNITS
- A FULL RECORD OF WHO DID WHAT, AND WHEN
Questions Before You Sign
What the work needs from you and who decides it, then what you are charged for.
We carry losses in returns, in claims, in cold chain. Will this touch them?
Each of those has a page of its own above, and so does every other job listed there. Reading them and agreeing is not the way to find out, though. Bring one of them and a month of the records behind it.
Every one of those pages ends with the measures to take out of your own systems first — days from a box landing to the call being made, claims filed against claims available, forecast error by line. Write yours down before anything changes, because the baseline is gone for good once it does.
If the losses you carry are not the shape of the ones described there, we will say so.
What does it need from our systems before it can do any of this?
Records you already hold. Each scenario names what it wants in order to start: one month of returns and your credit notes; one lane or one carrier and a quarter of invoices; a year of weekly history for one product family; one closed claim file and your delegated authority schedule; one contract and a question your team answered from memory.
Extracts in whatever format your systems produce them are enough to begin with. The joining is the work.
Who signs off a claim or a letter that it drafts?
A named person. The paperwork is gathered — the entry, the port, the reason it is held, the documents that are missing, the days it has been held and the per-day charge — and the letter is drafted. Then it stops.
Somebody reads the case and approves it, edits it or throws it out, and that sign-off is kept on the record. Nothing goes to the carrier before it. The same shape holds elsewhere: what arrives is a proposed action, and an action nobody approves is an action that has not been sent.
What does it do when it cannot tell?
It says so, rather than answering anyway.
A return grade it does not recognise is refused instead of filed under a best guess. A demand series it cannot fit comes back saying it could not be fitted, instead of as a confident-looking line with nothing underneath it. Where part of a drafted action cannot be carried out, the reply names the step that did not happen instead of reporting the work as done.
That matters more than it sounds. The failure this replaces is a plausible answer that nobody downstream could tell apart from a real one.
What happens when the forecast is wrong?
You can see why it was wrong. Competing methods are tried against periods your own history already contains, and the one that predicted those periods best is the one used. The answer carries the name of the method that won.
So a miss is something to look into — which method, against which history, and what changed — rather than something to take on trust. Your own forecast error by line is the figure to write down before any of it is running.
In a year, somebody asks why a claim was filed. What do we show them?
The record. Each proposed action waits in a queue as a record of its own, and approving it is the step that carries it out.
That approval is written down with the name of the person who gave it and what they decided, kept together. So the answer to why a claim was filed or an entry was held comes out of the record rather than out of whoever still remembers.
Where does our data go?
Onto the machines your licence names, and no further: Runink’s own shared machines on Lite, runners in your own cloud account on Dedicated, your own servers on Enterprise. The order files, the customs papers, the sensor readings and the reasoning about them stay there. Nothing goes to an outside model provider.
That is the answer a security review asks for before it will let a supplier hold its order data. It is also why the three licences above are told apart by where the work runs: that question is the first one a buyer in a regulated business has to settle.
What am I actually paying for?
Seats. A seat is one person who uses FACE by Runink. You count the people who need it, multiply by the price above, and that is the licence.
The licence you pick decides where the work runs. Lite runs on Runink’s shared machines and includes Compute Units with every seat. Dedicated runs on runners in your own cloud account with no limit on units: your cloud bills you for that compute directly, and Runink adds 1% of what those runners cost. Enterprise runs on your own premises or in your own cloud, priced with you.
These seats are for FACE. PULSE and Runink TIDE are separate products, each sold with its own subscription. Beyond the licence, the only fees on a FACE seat are the usage fees on FACE’s automated actions, set out above.
What is a Compute Unit?
It is how Runink counts work on its shared machines. Each analysis Runink runs draws Compute Units from your allowance, so that what you were given and what you have used are stated in the same terms, and both are on screen in the console rather than arriving at the end of the month.
Every Lite seat carries 18,000 units a month, pooled across the team, so a heavy week for one person draws on the same allowance as a quiet week for another.
On Dedicated and Enterprise the work runs in your own cloud or on your own servers, and units are unlimited.
What happens if we go over the allowance?
On the Lite Licence, you choose how to pay for more. Units beyond the allowance are charged as you go at $0.10 per 100 units, or you can buy units in advance: 10% less for a month’s worth, 20% less for a year’s. Dedicated and Enterprise have no allowance to go over.
You can see the running total in the console and set a budget against it, so the first you hear of a heavy month is not the invoice.
Which licence fits us?
Decide where the work should run.
Under ten people, the Lite Licence is the fit. It runs on Runink’s shared machines at the lowest price, and it is the only one you can take a month at a time — so an evaluation does not need a year’s commitment. Work there takes its turn alongside other customers’ work.
Ten or more, the Dedicated Licence runs on runners in your own Google Cloud project, or your Databricks or Snowflake account. It costs more per person than Lite and brings unlimited Compute Units; your cloud bills you for the compute. It is taken a year at a time.
If the work has to run on your own servers, including sites kept off the network, that is Enterprise, and the conversation starts with where it has to run.
Do we have to sign for a year?
Only for Dedicated and Enterprise. The Lite Licence can be taken month by month at $89 per person, or a year at a time at $75 — the same difference, about 16%, shown by the toggle above.
Dedicated and Enterprise are a year at a time because both set runners up for your company specifically, in your own cloud or on your own servers.
What does Enterprise onboarding cost, beyond the licence?
We already have committed spend on GCP, Snowflake or Databricks. Can we buy FACE against that?
Yes: that is the Dedicated Licence. Its runners run in your own Google Cloud project, or your Snowflake or Databricks account, on compute you already pay that platform for.
The compute is billed to you directly by the platform rather than provisioned and billed by us, so there is no infrastructure margin of ours stacked on top of theirs: you pay their compute rate, our seat price, and 1% of what those runners cost. We do not quote a discount here; the rate against your committed spend is between you and that platform.
What does heavier use cost?
On Lite, a team can use up to 900 units per person per hour. Work past that pace waits its turn in line; it is never refused, and the pace itself costs nothing extra. Units beyond the monthly allowance are paid as you go or bought ahead, as above.
On Dedicated, units are unlimited: heavier use shows up on your own cloud bill as the compute it used, plus 1% of that from Runink. On Enterprise it runs where you already run things.
Either way your spend follows decisions you made — how many seats, and where the work runs — rather than a price per question.