Anonymised by default. Client names stay out of this by default — industry, region, and engagement type are enough to show the shape of the work. References from past engagements are available on request, under NDA where appropriate.
The recurring engagement: choose the technology, direct the people who run it, and be accountable for what happens after.
Engaged to make the foundational technical decisions for a new product rather than to write it. Selected the stack — Vue and Node on TypeScript, across Azure, AWS and Google Cloud — defined the developer roles the build would need, and hired into them. Led development through to a fully operational product, then handed over and exited. Nearly three years, ending by design rather than by attrition.
Engaged to establish technology for a multi-site gaming operator and to decide what it should consist of. Structured the network, specified and selected the video surveillance systems and gaming equipment, wrote the surveillance procedures and operating guidelines around them, and hired the operators and maintenance staff. Then ran it for two years: regulatory compliance under local gaming law, tax reporting, a 24-hour maintenance rota, and a standing team of around 25 trained on both the equipment and the rules.
Engaged to set digital direction for the business as a whole rather than to build one part of it. Selected the technology stack, chose the direction for each online revenue stream, and coordinated the external resources delivering against them — spanning a luxury property magazine, the associated real estate business, and native apps across three mobile platforms.
Specialty mortgage products for self-employment income carry eligibility logic most applicants can't parse. Built the origination process as a single automated flow: quote request, collection of supporting documentation, soft and hard credit checks, and qualified offers returned to the applicant — with merchant support so approved funds could finance services directly. The strategy question underneath was how much of the complexity to expose, and where the system should make the judgement instead of the applicant.
Guest wireless and business connectivity across ten live properties. The design problem was sequencing rollout against occupancy so no property lost rooms. Owned architecture and vendor selection across access, routing, security, fiber and guest billing.
Six towns operating berths and moorings independently, needing one payment system. Designed and implemented across every site.
Teleconferencing connectivity linking isolated island health centres to mainland specialists, and ten emergency-care offices to their headquarters over MetroEthernet.
Want a read on an engagement like this? Start a conversation →