What I build
12 service lines. Every one backed by delivered projects.
A website, a store, a blog, business software, a SaaS platform, a mobile app. And, because that is where I cut my teeth, real-money games. Under each line, the work that proves it.
For any organisation
What I build for a company, a practice, an association or a freelancer going digital.
Work that backs it
Showcase and professional websites
The site people open when they type your name into Google, and that makes them want to call you.
- Company, practice and association websites
- Rebuilding an existing site without losing its ranking
- Copy and page structure, not just the layout
- Fast loading, including on a slow connection
Work that backs it
Blogs, media and content platforms
Publishing regularly is the one kind of ranking you cannot buy. It still needs a tool that does not put you off.
- Company blog, editorial media, newsletter
- Publishing without touching code, by you or your team
- Structured data and careful social sharing
- Bilingual version with correctly paired hreflang
Work that backs it
Business software and back offices
When the spreadsheet no longer holds and off-the-shelf software does not fit, it has to be built.
- Decision dashboards and business indicators
- Roles, branches and team management
- Data import, reconciliation and exports
- Invoicing, collection and payment tracking
Work that backs it
SaaS platforms and APIs
A product your customers use online, with accounts, subscriptions and billing that runs by itself.
- Accounts, roles, isolated customer workspaces
- Subscriptions, trials and recurring billing
- Documented, versioned and authenticated API
- Access log and full operation traceability
Work that backs it
Mobile applications
One codebase, two stores, and offline handled from day one.
- React Native and Expo, iOS and Android
- Flutter client when the back end calls for it
- EAS builds and distribution, demo before release
- Haptics, gestures and transitions at native quality
Work that backs it
Cloud, continuous integration and DevOps
Going live is not an event, it is a command.
- Docker containers, reproducible environments
- Continuous integration pipelines with blocking tests
- Automatic deployment, rollback in one commit
- Performance monitoring and a loading budget
For gaming operators
My specialty, and the most demanding thing I build: real money, in real time, that has to add up every single time.
Work that backs it
Sports betting and casino
Bet placement interfaces, from singles to accumulators, and online casino games.
- Odds board, bet slip, accumulators and system bets
- BetBuilder, 2Up and cash-out simulators
- Casino and multiplier games (Aviator style)
- Match debriefs and editorial content that brings traffic
Work that backs it
Virtual games
High-frequency events rendered in 3D, with no dependency on a sports calendar.
- Virtual horse races, from the gate to the photo finish
- Ball roulette and proprietary variants
- Real-time rendering in the browser, no plugin
- Blender modelling, then React Three Fiber integration
Work that backs it
Operator integration and wallet
Your wallet stays with you. The game comes to it, through a signed API.
- Seamless wallet: debit, credit, getBalance
- Operator authentication by HMAC-SHA256 signature
- IP allowlist and versioned API
- Back office, reporting and transaction ledger
Work that backs it
USSD channel, down to 2G
The channel that reaches the players the web does not.
- USSD menu trees tested on feature phones
- Playable with no app and no mobile data
- SMS campaign attribution and short links
- Carrier detection from the number prefix
Your need fits none of these boxes?
Describe it and I will tell you in one reply whether it is for me.


















