Ask the awkward questions.

Lite is the trading essentials: customers, quotes and sales orders, purchasing, stock and batches, goods-in, despatch, invoicing and core reports. Professional switches on the rest of the operation: production and works orders, the shop-floor app, cut-piece pricing, the AI assistant and AI capture, the customer portal, accounting export, multi-currency and the full report suite. Corporate adds API access, EDI/integrations and white-label options.

Yes — it's built around them. Every batch carries a theoretical and an actual weight; prices work per kg, per metre, per each or lump sum; and invoices can use either weight basis, with variance over 2% flagged for review.

Every physical lot is a batch with its heat and cast number. Mill certificates are records — with the PDF plus extracted chemistry and mechanicals — matched to batches by heat number and ranked EN 10204 2.1 to 3.2. Customers can require a minimum certificate type, and allocation and despatch gate on it. Splits, cuts, remnants and subcontract returns all keep the genealogy.

Yes. The customer portal gives each customer their orders, invoices, statements and credit position, and builds one-click document bundles — delivery notes, cert packs, invoices — served on short-lived secure links.

Works orders consume a parent batch and produce outputs, remnants and scrap with inherited heat and certificate. 1D cutting lists handle kerf, end trim and minimum offcut; there's a scheduling board and a shop-floor app for operators. Cut-piece pricing charges cut length plus kerf plus facing allowance, by saw type.

Goods-in supports two-stage receipt: book material in from the delivery note, and it sits as awaiting-weight — unsellable — until the actual weight is confirmed. At despatch, weighbridge readings record gross, tare and net against the load.

Yes — a single-use ePOD link opens on the driver's or customer's phone, captures an on-glass signature and any exceptions, and a clean POD can trigger the invoice automatically.

That's the point of the migration offer. Customers, suppliers, stock codes, live batches with heats, certificate PDFs, order history and ledger balances are mapped and moved. The first stage is an analysis of your current system — we tell you honestly what moves cleanly and what needs work.

No. The staged approach exists precisely so nothing is lost: analysis, field-by-field mapping you sign off, a trial migration into a test company, parallel running, then a planned cutover with the old data preserved.

It depends on the state of your data, and anyone who quotes a number before looking at it is guessing. The analysis stage produces a real timeline; the stages are sized so the office keeps working throughout.

Yes — parallel running is a formal stage, not a favour. You switch when the evidence says it's safe, not when a project plan says it's Friday.

It's normal. The mapping stage surfaces the mess, we agree cleaning rules with you, and the trial migration shows the result before anything is committed.

Anything that lives in your data: stock positions, aged debt, margins, works-order status, supplier performance. It runs read-only queries against your company's schema and returns answers, tables and charts. It also explains how to use the system and can take you to the right screen.

No. Documents and queries are processed to produce your results and are not used to train models.

Nothing, until a person says so. Every capture is a draft for review — the heat number, grade and chemistry are shown against the source PDF before anyone confirms. The AI proposes; your team decides.

Only through Act mode, which drafts a typed, listed action — create a stock code, raise a PO, book a GRN — and executes it solely after explicit confirmation. Report mode is read-only by construction.

The primary database is managed Postgres in London (eu-west-2). Files — certificates, document bundles — live in private storage buckets accessed only by short-lived signed links.

Backups are platform-managed on Supabase. We deliberately don't publish recovery-time promises we haven't tested — the current backup detail is available on request. [CONFIRM-WITH-MARK: final wording once backup/PITR posture is verified]

Your company's users, under seven operational roles that gate what each person can do. Each company lives in its own database schema and every request is checked for membership and role. Platform administration for support is superadmin-only and audited.

Your data is yours. Structured exports are provided on exit, and GDPR data-subject export and erasure are built into the product. [CONFIRM-WITH-MARK: committed export formats]

Yes — TOTP two-factor per user, and a company can require it for everyone.

A monthly licence per tier — Lite, Professional or Corporate — with a number of users included. Pricing is on request while the tiers are finalised: ask in the demo and you'll get a straight number. Every tenancy is set up with us directly rather than self-serve checkout.

We provision your company, import your starting data, and invite your master admin — who invites everyone else. Guided help and the in-app assistant carry most of the training load; new starters ask the assistant, not the veteran at the next desk.

In-app help articles that match the current release, a ticket system with AI triage grounded in that same help content, and the developer behind the product rather than a call centre. Support hours: [CONFIRM-WITH-MARK].

[CONFIRM-WITH-MARK: term length, notice period and payment terms to be stated here before launch — not invented.]