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

Information about the world’s hot springs is scattered — a paragraph on a travel blog here, a data point in an open dataset there, a photo somewhere else. There was no single, structured place to find where thermal springs are, what they are like, and see them on a map.

What I built

• An automated pipeline that sources hot-spring locations and facts from open data (Wikidata) and pulls correctly-licensed photography from Wikimedia Commons.
• Enrichment and normalisation into a clean dataset — location, country, description and imagery per spring — across 1,477 sites in 69 countries.
• Programmatic pages for every spring and country, each with maps, photos and structured data for search engines.
• A content-quality rule that keeps thin pages out of the search index, so only substantial pages are exposed to Google.
• The full stack and hosting underneath, served through Cloudflare.

The problem

Architecture students are shown finished buildings and told to reproduce a look, but rarely taught the underlying process — the frameworks, the tooling and the real-world standards and dimensions that turn an idea into a workable design. The good material is scattered, paywalled or aimed at practising professionals.

What I built

• A free content platform organised around design frameworks, software tutorials and standards & dimension guides — the “how to think” rather than the “what to copy.”
• A clean, distraction-free reading experience built for long-form learning, fast on any connection.
• A structured, SEO-focused content architecture so each guide is discoverable and stands on its own as a landing page.
• Served from a lightweight PHP stack behind Cloudflare — fast to load, cheap to run and simple to maintain.

The problem

When a site goes down or slows, you need a straight answer — is it really down, or is it DNS, TLS or routing? Most tools that answer this are cluttered, ad-heavy, or hide the basics behind a sign-up.

What I built

• Fourteen free diagnostic tools, no sign-up, run live from London: website status, redirect and response-time checks; ping, open-port, IP and WHOIS lookups; DNS lookup and a worldwide DNS propagation checker; SSL certificate and HTTP header/security checks; email deliverability, header and blacklist checks; and a website health score.
• Uptime monitoring with email alerts on every state change, public status pages, embeddable status badges and certificate-expiry warnings.
• A freemium model billed through Stripe: free forever (3 monitors, checks every 5 minutes, 90 days of history, usable commercially) and a £6/month Pro plan (25 monitors, one-minute checks, a full year of history).
• A documented read API, and a deliberately lean front end — strict Content-Security-Policy, no framework, fast pages.

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.