Trust20

If you run a restaurant group, every person on staff needs a valid food handler and allergen certificate, and an inspector can ask to see them at any location on any day. With dozens of sites and people coming and going every week, keeping that straight by hand is a full-time job nobody has. Trust20 exists so the group can buy the training in one place and always know where every employee stands.

A customer buys a bundle of courses, invites their staff, either one at a time or by uploading a list, and the staff take the courses on Docebo, the learning platform behind it. Trust20 pulls completions back, produces the certificates as PDFs, and sends location managers a weekly report of who passed and who didn’t. As certificates get close to expiring, the people who need to know get told at 90 days, 7 days and 2 days. Once a month the billing runs on its own: it works out what each customer owes, charges the card on file through Stripe, and sends the account managers a report, with an invoicing path for the enterprise accounts that don’t pay by card.

I’m the lead engineer on the backend and the platform. I rebuilt the billing from the ground up, including adjustments, how a payment method gets picked, and the command that does the charging. I made the Docebo sync something you can trust, with queued imports and a reconciliation step so enrollments don’t drift. A good share of my time goes to the unglamorous data-integrity work the product rests on: what happens when a user is deleted, who’s allowed to change what, and validation on the records that matter. On the front end I work in Filament and Livewire on the admin and team panels and the signup flow. It’s live and I’m still shipping on it every week.