TMR reporting and the shift log
The paperwork of a BEA never stops. Make it a by-product of the day, not a job for the weekend.
Getting licensed Stories
Build stories
Short write-ups of the problems I hit building DyComDrive, what I did about them, and what I’d tell someone starting now. Each one is dated, and sticks to what we can show.
Written quotes, and receipts that are tax invoices
Build the legal rule into the button, and generate every compliance document from the record, never by retyping it.
The systemThe quote that was too long to send
Test your text provider with your longest real message, not a "hello".
The systemHosted in Queensland, and why it matters
Decide where the data lives first. Then write the privacy page from the facts.
The systemThe licences, and our own BEA
Each licence answers a different question: the car, the driver, and who takes the booking. Get them in that order, and diary every expiry.
Getting licensedCharging an EV9 off the roof
Test the stop, not just the start. Then add a hard stop anyway.
The carShared rides, inside the rules
Write your legal reasoning down, then make the system enforce it.
Product designStarting on Uber
Driving for an app tells you whether there's work. The moment you take a booking yourself, you need your own BEA.
Getting licensedBuilt with AI, checked hard
AI writes code fast. Review and tests are what make it trustworthy.
The systemThe record nobody can edit
Make the database refuse the bad thing, instead of trusting people not to do it.
The systemWait & Return: the ride home, guaranteed
Price the thing people are actually afraid of, and put it in writing.
Product designPets in the boot
If you say yes to something riders love, write down the rule that protects the riders it could hurt.
Product designRide days for mountain-bike crews
Build the safeguards before the demand: consent, permits and a clear line around what you are selling.
Product design
No stories in this section yet.
Something you’d like written up? Ask on the contact page.