Frequently asked questions

Loaditude is a warehouse and transport management system built for mid-market UK logistics operators -- third-party logistics providers, road hauliers, retail implementation firms, and freight forwarders who run goods-in, kitting, transport, and installations as connected steps in a single programme. It replaces spreadsheets, WhatsApp, and disconnected tools with one system that holds the full workflow from goods arriving to proof of delivery.

Loaditude is built for UK operators running 5--50 vehicles or an equivalent scale in kitting and storage operations. The ideal user runs multiple service lines (warehousing + kitting + transport, or kitting + installation + transport) and needs their team, drivers, and clients all looking at the same job data. Solo operators or pure-transport businesses may find a simpler tool is a better fit.

Yes. The WILD Axis Group -- a UK retail implementation business -- runs its daily freight, transport and logistics operations on Loaditude in production. Loaditude is not a demo or a roadmap promise.

Loaditude connects the full operational workflow: goods-in receipting (scan or manual, condition at intake), kitting and VAS (multi-step assembly with per-unit QC), transport job management (create, assign, track), mobile proof of delivery (driver app with photo and signature, synced in real time), client portal (real-time job visibility for your clients without granting internal system access), and reporting (job completion, turnaround times, programme summaries).

The current offer is a founding design-partner seat at £199/month -- flat, not per user. This price is locked for life for founding members. When Loaditude opens to the wider market, pricing will increase to reflect broader scope and support. Founding members stay at £199/month permanently.

The founding cohort is three design-partner seats. Founding members get full access to every Loaditude module from day one, a direct line to David (the product founder), and a monthly changelog showing what shipped based on their feedback. In return, they do a monthly 30-minute review call with David, give honest feedback when something does not work, and write an honest review at 90 days. It is a real design-partner relationship, not a standard SaaS subscription.

No. The founding cohort requires an application. If your operation is a good fit, David will book a 20-minute demo before you commit to anything. There is no self-serve free trial and no credit card required to apply.

No. The founding-cohort price (£199/month) covers your operation, not a per-seat count. Multi-user access is included. If you have 15 people who need access, that is still £199/month.

No minimum contract for founding members. Pay monthly. Cancel if it is not working. No exit fees.

When 3 seats are filled. There will not be a second founding cohort -- the next wave of customers will be on standard pricing.

Currently live: goods-in receipting, inventory management, kitting and VAS workflows, transport job management, the driver mobile app (iOS) with digital proof of delivery, client portal, and reporting. All of these are in production use.

iOS only at launch. Android is on the roadmap. If Android support is a hard requirement for your fleet, flag it in your application.

Xero integration is on the roadmap -- not in the first release. If this is a hard requirement, flag it in your application and it will move up the priority list.

The driver app is designed to handle intermittent connectivity. Critical job data and proof-of-delivery capture queue locally and sync when connection is restored.

Your clients get read-only access to their jobs with a secure link. You control what they can see. No complex onboarding required for your clients.

For founding-cohort members, onboarding is hands-on with David. The goal is to have your operation running in Loaditude within the first two weeks. Most of the setup time is configuring your job types, location structure, and client accounts -- not deploying infrastructure.

Direct line to David. Not a ticket queue. Founding-cohort members have David's contact details and a guaranteed response. If a critical issue affects live operations, it gets fixed before anything else.

Yes -- that is the point of the founding cohort. The monthly review call is the mechanism. Features that are core to the founding-cohort use case go into the roadmap. Requests from operators who are actively using the product in production are how the development priority is set.