Work
Most of what I build has no front page. It is a payment that updates an access list, a PDF that ends up in a database, a validation stage that throws work away. Those get drawn here rather than described, because a browser frame around a database would be a lie about what the job was.
Beauty & wellness · client
A booking website that moved enquiries out of Instagram DMs and into a five-step flow that collects everything before the appointment.
Automation · membership
A successful payment adds someone. A failed one removes them. Nobody opens a spreadsheet, and nobody is left paying for access they lost or holding access they stopped paying for.
Data · reporting
Invoices arrive as PDFs, get read, get checked against what the numbers should add up to, and land in a database that feeds a dashboard. The refresh nobody remembered to do stopped being a job.
Research · systematic trading
A data pipeline, a backtesting engine and a live execution layer. The interesting part is the validation stage in the middle, whose entire job is to throw out strategies that only worked because they were lucky.
Travinyx is new. One of the sites above is a paying client and is live today; the other is a concept I built end to end so that the automotive version of this job existed before somebody asked me for it. Both are labelled as what they are, on the card, because the alternative is being found out later.
The three systems are real work with no public page attached. They are described here at the level of detail I can give without saying whose they were.
Tell me what is going wrong rather than what you think you need building, and I’ll tell you what it would take to fix and what it would cost.
