A first step that is small, and safe because it is standard.
Start with the data you already have, against a scope you can describe in a sentence. A well-developed, structured process — a defined range, a fixed build method and published standard lead times — means the first installation stands up to a date rather than to an estimate — and expands only where the record says it is worth expanding.
acuitystore® ONE
One point, one applicationAn attended terminal, or one gated cabinetThe questionnaire still applies — every store needs a scope before it can be built. What changes is how much scope there is: one point, one application, a defined item list. Less to specify, and quicker to stand up.
acuitystore® SITE
Two to twelve pointsMixed formats · one or two applicationsThe design centre. Formats chosen per item, inspection regimes where items must be in date, and a real choice about whose balance sheet the equipment sits on.
acuitystore® CAMPAIGN
Up for the window, gone by handoverRented for the window · mobilised and demobilised to your datesA turnaround or shutdown store. Mobilised, controlled through the window, demobilised and reconciled against the scope. How a campaign runs →
A defined scope, built to a known method.
One controlled point: an attended terminal with scanner and label printer, or a single gated cabinet. It is a standard unit — the same one that sits on the counter of an attended Toolstore and the same one that goes out to a campaign store — so it is built to a known method and held in the finished-goods buffer rather than made to order.
| A record of one store | Every issue, return and restock against a person, an item and a point, from the first transaction. |
| Your people enrolled | People and credentials loaded during set-up, however they identify at the point. |
| An item master you own | Built with you from whatever you have now. Machine-readable, and yours. |
| Reporting from the start | Consumption by person, crew, job and cost centre, with the exceptions on the same report as the successes. |
| A record that keeps writing | Points and mobile peripherals hold a local copy and reconcile when the link returns. |
Nothing about the second point is different. Same platform, same contract, same reporting — you add a point, not a system.
A well-developed, structured process.
| What you can count on | What holds it up |
|---|---|
| A figure built the same way every time | Package, configuration template, standard lead time and approval tier are all determined by rule from what you tell us, so the answer is the same whoever you speak to and whenever you ask. |
| A date we can build to | A defined range with known configurations, a fixed build method for each, and a finished-goods buffer on the entry formats. |
| A clock that starts when you are ready | The standard lead time runs from your signed readiness confirmation, not from your purchase order — because a purchase order does not make a site ready. |
| A path for the unusual | Anything outside the catalogue is a logged Non-Standard Request, priced once. When the same request appears three times, it enters the catalogue. |
| A short document to sign | Terms once, then a Schedule per site carrying scope, dates and amounts. The structure → |
Six steps.
| Step | What happens | How long |
|---|---|---|
| 1 · Questionnaire | Seven short sections. The three drivers size the store. | short |
| 2 · Indicative figure | We size it and come back with a figure and a shape. | — |
| 3 · Scoping review | Short, no obligation. Confirms the figure and the readiness answers. | 45 min |
| 4 · Order | An Installation Schedule — scope, dates and amounts. | — |
| 5 · Readiness | You confirm the site is ready. The clock starts here. | — |
| 6 · Live | Built, configured, delivered, commissioned, Certificate of Completion issued. | — |
Start with the step in front of you.
Every one of these grows into the next without a new platform, a new contract or a migration.