Case studies.

The problem

Companies House publishes millions of filings, but they are raw, scattered across registers and hard for a non-specialist to read. Businesses need to know who they are dealing with — is a company real, active, solvent, who owns it — without wading through PDFs across a dozen sources.

What I built

• Search and profile pages across the full UK register — millions of companies — served from a local Companies House mirror for speed.
• A data layer that cross-references multiple official sources: Companies House, HM Land Registry, The Gazette, the FCA and ICO registers, charity and sanctions data.
• An AI assistant that answers natural-language questions about any company and writes due-diligence summaries, grounded in the underlying records so it does not invent answers.
• Downloadable PDF due-diligence reports, company-monitoring alerts, and subscription billing via Stripe with plan-gated features.
• The full stack underneath — accounts, entitlements, streaming responses, caching and the infrastructure to run it.

The problem

Running a hosting business means owning the whole stack. Not renting a reseller panel, but specifying hardware, getting it into a data centre, arranging transit, and building the automation to provision and bill customers.

What I built

• Physical server hardware colocated at Volta Data Centres in London.
• Network transit and peering arranged directly with Cogent, for low-latency routing to UK users.
• Virtualisation to carve capacity into VPS plans alongside shared hosting.
• WHMCS automation for provisioning, billing, domain registration and customer support workflows.
• Linux server administration, monitoring and backup across the estate.

The problem

Large Bitcoin transfers move markets, but by the time they surface on a public explorer or a news feed the opportunity has gone. Traders needed to see significant movements as they entered the network, not minutes later, and needed to know whose wallets were behind them.

What I built

• Continuous ingestion from the Bitcoin mempool, so transactions are seen as they broadcast rather than after block confirmation.
• Entity classification that resolves addresses to known exchanges and institutional holders, so a transfer can be labelled rather than shown as an anonymous hash.
• A WebSocket layer pushing updates straight to connected dashboards — no polling, no refresh, sub-second delivery.
• Automated Telegram distribution so subscribers get signals on the channel they already watch.
• Multi-category classification and filtering so users can narrow to the movement types they care about.

The problem

News aggregation is easy to prototype and hard to run. Feeds go down, change format, duplicate stories across sources and return inconsistent encodings. The site had to stay fast and current without a database server or a heavy CMS behind it.

What I built

• A scheduled fetch engine pulling roughly a hundred RSS feeds from international publishers — including major newspapers, broadcasters and specialist technology and blockchain sources.
• Normalisation and de-duplication into a single flat-file cache, so page loads never wait on an upstream feed.
• Seven category sections plus around forty topic routes, handled through URL rewriting rather than query strings.
• A self-healing refresh: if the cache goes stale between scheduled runs, the next page load triggers a background refresh.
• Direct attribution and outbound links to every original publisher.

The problem

Sending mobile credit across borders was slow and expensive. For the user it had to be simple: pay, and have prepaid airtime land on a phone on an international network, automatically. Accepting Bitcoin as one of the payment methods meant building the settlement and confirmation logic from scratch, since no processor offered it at the time.

What I built

• International prepaid airtime delivery through carrier and top-up APIs, triggered automatically on payment.
• Multiple payment methods, including Bitcoin, with on-chain confirmation tracking before fulfilment.
• Transaction processing that reconciles payment against delivery, so a confirmed payment always results in delivered credit or a traceable failure.
• A high-trust interface aimed at ordinary users, not crypto natives.

The problem

Most online readers bury the text under navigation, adverts and interface. The brief was the opposite: get the reader to any chapter in one action, and then get out of the way.

What I built

• A grid navigation system presenting all 114 chapters at once, so any chapter is reachable without a secondary menu.
• A single structured dataset driving the whole index — reorder or extend the content from one configuration file, with no markup changes.
• Client-side rendering for instant chapter switching after first load.
• A deliberately minimal interface with no advertising or tracking.