AstraCaB GmbH, Munich#
- Industry
- On-demand transport (moving, man-with-a-van, courier, waste collection)
- Project type
- Driver app (mobile), booking website (web), backend work
- Year
- 2025
- Duration
- multi-week episodes across several months
The starting point#
AstraCaB operates a transport platform in Munich: private customers and businesses book moving services, van transport, courier runs and waste collection — in German and several other languages, with a particular focus on expats arriving in Munich who need a transport organised quickly. On the driver side, job handling did not run through an app, but through routes that cost a lot of coordination in daily work.
The problem#
Without a driver app, every status change lived in phone calls and follow-ups: has the job been accepted? Where is the vehicle? Is the delivery complete? For a company coordinating moving drivers and waiting customers, that uncertainty is directly visible — in lost minutes per job and in calls nobody enjoys making.
Scope#
My contribution in this project:
- The driver app in Flutter — job acceptance, job details, status handling and navigation for the driver's day, from one codebase for the devices drivers actually use.
- The booking website (web frontend, React) — the customer-facing side of the platform, where orders originate.
- Work on the backend (.NET/C#) — the interfaces connecting app and website to the platform logic.
- A further module — its name and scope stay unnamed here.
Not part of my contribution: the platform's marketing, its operations team and AstraCaB's internal organisation.
Result#
The driver app is in production use: drivers accept jobs in the app, work through them and close them without a phone chain. What that saves in time and calls per day I cannot prove here in numbers — the client would have to have measured what happened before the app, and that is not a figure I will invent. The app itself is the evidence: it runs, it is in operation, and it was not replaced.
What the project did not solve: the platform is not my product, and I do not operate it. My contribution ended with handing the developed parts over into the client's running operation.
Cost#
A project of this shape — a production module inside an existing system — sits today in the low five-figure range with me, as a fixed price per written scope. The path there runs through the intro call and the scope sheet (process), not through an estimate over the phone.
Screenshots#
No screenshots exist for AstraCaB; the page deliberately ships without images rather than showing substitutes. An image slot is marked and will be filled once material is cleared for publication.
Naming#
AstraCaB GmbH is named with its permission: no NDA prevents it, the project is finished, and no public attribution existed before. The technical listing (Flutter, React, .NET/C#) is honest context, not a selling point — and no evidence of Serverpod experience; that comes from my own artefacts.
Also of interest#
- BZBGear — control software for professional video technology, developed over years.
- App development — how a Flutter production build runs with me.
- Web development and backend development — the other parts of this stack.
- Partner service — this project is the proof that I can work productively inside a foreign stack.