Ferrystone grew out of our build for a patient transport operator with around 200 staff and 90 vehicles that had five Access databases, 102 online forms and 26 automated workflows. We rebuilt all of it as one web application: staff records, the PTS rota grid, the journey log, vehicles, invoicing descriptions, reports, induction courses with video and assessment, assessor sign-off with a real gate, and a crew portal on the phone. The first rollout migrated more than 330,000 records without a failure.
We do not knock the system you have. If it is doing the job, keep it. The reasons operators move are usually that changes cost too much, that forms and certificates live outside the system, and that nobody can see who is out of date until an inspector asks. Those are the three things Ferrystone is built around.
It is bought the way Milkware is bought: one price for the software, a setup that includes the server, the migration and on-site training on the install day, and an optional monthly plan. Stop the plan and the system keeps running.
What operators tell us they have now
- A package or database that works but cannot be changed without a quote
- Online forms that live outside the system and have to be filed by hand
- Workflows that break when a folder moves
- Certificates and assessments tracked in a spreadsheet
- Crew paperwork on paper or a phone form that goes nowhere
Ferrystone
- One system for staff, rota, journeys, vehicles, forms and compliance
- Every form a screen, filed to the record on send
- Certificates, assessments and expiries tracked automatically
- A crew portal on the crew's own phones, nothing to install
- Your existing database read directly and migrated. Changes included on the plan