Some clients I can name and some I cannot. Where a client is withheld, the sector and the stack are not — and where the architecture is mine to describe, it is described rather than gestured at.
Each one says what I actually was on it: my own product, an employee on someone else's programme, or QueueOne engaged directly. Two of these are employee work, and a portfolio that does not say so is quietly claiming something it should not.
My own product — in private beta
A multi-tenant operating system for real-estate teams, where the hard part is ingesting other people's events without corrupting your own data.
Idempotent webhook ingestion keyed on provider event IDs, anonymous-to-identified event backfill, CREA RESO OData sync, and pgvector semantic search over listings.
As an employee of a consultancy, on the client's programme
A 25+ API micro-service architecture carrying a 1,000 req/sec SLA, in front of reservation systems that do not forgive sloppy integration.
Booking, seat maps, flight search and automated baggage handling, integrated against airline reservation systems under a contractual throughput SLA.
As QueueOne — built from nothing, still maintained
The business did not exist before the platform went live. That is the whole brief: it had to work from the first day, because there was no manual process to fall back to.
A Laravel platform handling catalog, checkout and transactional email for an Edmonton client whose business was built on top of it.
As co-founder — I built the platform
Three years live on both app stores, with geofenced push in the hands of real people, RAG search behind it, and organic traffic that arrived on purpose.
A Flutter app on the App Store and Google Play using location, geofencing, maps and push, with RAG-based search and a vector recommender behind it.
As CTO and part owner
Getting regulator-ready reporting out of a white-labeled system I did not control, for a cash-to-crypto network that was live and taking real money.
FINTRAC reporting extracted from a vendor platform, KYC integrated into onboarding, and non-custodial fund movement between bank accounts and third-party APIs.
That is usually the useful signal. Describe what you have and what it is doing wrong, and I will tell you whether I am the right person for it.