Draft. Replace the text in [brackets] with real details the client has approved before publishing.
Where they were stuck
[In a few plain sentences: e.g. jobs were handed out by phone call and whiteboard, nobody knew which truck was being worked on, and paperwork was re-typed at the end of each day.]
What made it tricky
- No signal. Repair bays and yards often have no mobile coverage, so the app had to keep working offline.
- Busy, greasy hands. Mechanics won't use anything that takes more than a few taps.
- [Any other limits, e.g. connecting to the existing parts and inventory system.]
What we built
A simple phone app for mechanics that keeps working without signal and catches up automatically when it reconnects, plus a live dashboard for the office showing every job and vehicle. [Add two or three things you learned from spending time on the shop floor.]
For your tech team
React Native app with offline-first sync and conflict handling, Go back end, WebSockets for live dispatcher updates, containerised with Docker and deployed via CI/CD.
What the client got to keep
- Notes from our shop-floor visits and the screen designs
- All the code for the app and dashboard, in their own accounts
- Running guides plus alerts that warn them if anything goes down
The result
[A result the client will confirm, e.g. "48% faster from breakdown to repair" or "no more end-of-day paperwork".]