Services: payments, AI integration, performance audits
Freelance full-stack services: Stripe and payment integrations, AI feature development (LLM agents, tooling), and web performance and architecture audits.
Services
I'm a senior freelance full-stack developer working 100% remote (UTC+1). My focus is on the parts of a product that need to work correctly the first time: payment integrations and billing flows, AI features that hold up under real usage, and the web performance and architecture decisions that either compound or drag over time.
Every article on this blog comes from something I've shipped or debugged in production. If one of the topics below sounds like your current problem, that's the point.
Payment integrations (Stripe and friends)
I build and migrate payment flows for SaaS: Stripe manual capture, multi-provider checkout (Stripe, GoCardless, PayPal), webhooks, refunds, reconciliation, VAT/MOSS, and third-party loyalty or insurance integrations. I've shipped this kind of work for a multi-site booking platform under live traffic with no downtime.
If you have a checkout that's leaking conversions, a Stripe migration you've been putting off, or a billing edge case that keeps coming back, I can own it end to end. Read: How Stripe manual capture works (and when to use it).
AI features that ship (LLM integration, agents, tooling)
I build AI features that actually make it to production: LLM integrations, agentic coding pipelines, RAG over codebases (CocoIndex + pgvector + Tree-sitter for incremental semantic indexing), and Mastra-based agent orchestration. I pay attention to the boring-but-critical production concerns too: cost, latency, evaluation, and human-in-the-loop.
If you're shipping an AI feature and you need someone who's already thought through the failure modes, I've been there. Read: Claude Code with multiple accounts: how I manage it in practice.
Web performance and architecture audits
Performance and architecture decisions made early tend to compound quietly. I do focused audits of rendering strategy, bundle composition, data fetching, and the structural choices that make a codebase harder to change over time. The output is a concrete set of changes, not a slide deck.
If you're hitting a wall on Core Web Vitals, or your team is spending more time working around the architecture than building on it, that's worth a look. Read: Why architecture matters more than the code itself.
Get in touch
If any of the above fits what you're working on, drop me an email. I'll reply within a day or two and we can set up a short call to see if it makes sense.