Services

Need something built? I take on a small number of fixed-scope side projects alongside my day job — typically weekend-sized engagements where you know the price and the deliverable in advance.

I’m a Technical Lead with 8+ years of production experience — currently leading LLM & AI product engineering at Rentr, a PropTech platform used across the UK property sector. I work in Python, TypeScript/JavaScript, Flutter and Java, and I’ve been a FOSS contributor for a decade (Fedora, Mozilla, Debian-adjacent projects).

What I can build for you Link to heading

LLM & AI integration Link to heading

Give your product or internal workflow an AI edge: retrieval-augmented search over your documents, AI agents that process invoices/compliance docs/support tickets, chat interfaces over your own data. I’ve shipped LLM features that cut manual review time by 75% in production. Typical shape: 2–4 weekends. You get a working integration, not a slide deck.

Automation & data pipelines Link to heading

Still copying data between systems by hand? I build pipelines that move, clean and enrich data automatically — PDF/document extraction, spreadsheet-to-database flows, scheduled reporting, third-party API integrations. My automation work has saved past employers 7–10 hours a week. Typical shape: 1–3 weekends depending on the number of systems involved.

Cross-platform apps with Flutter Link to heading

One codebase, iOS and Android. If you need an internal tool, a customer-facing app or an MVP to validate an idea, Flutter gets you there without paying for two native builds. Typical shape: scoped per milestone; an MVP is usually 4–6 weekends.

Web backends & APIs Link to heading

Fast, well-documented APIs and backends in Python (FastAPI/Django) or Node.js — plus the boring-but-critical parts: deployment, Docker, monitoring, backups. I’ve architected systems handling 200,000+ transactions a week. Typical shape: from single-endpoint APIs (1 weekend) to full backends (several).

How working with me looks Link to heading

  1. You describe the problem — a 30-minute call or a written brief, whichever suits you.
  2. I reply with a fixed quote — scope, price and timeline, in writing. If it doesn’t fit a fixed scope, I’ll tell you honestly rather than pad an estimate.
  3. We build in weekly increments — you see working software early and often, on a schedule that respects that this is my weekend time (I keep a day job I enjoy).
  4. You own everything — code, documentation and deployment knowledge transfer at handover. No lock-in, no mystery.

The small print Link to heading

  • I only take on work I can do well in the time available — small and excellent beats big and late.
  • Rates are per project, agreed in advance. No surprise invoices.
  • FOSS-friendly: I’m happy to work with open-source stacks and self-hosted infrastructure (it’s rather my thing), or with your existing cloud setup.

Get in touch Link to heading

The fastest routes: email me or connect on LinkedIn. Tell me what you’re trying to achieve — even if it’s half-formed — and I’ll tell you honestly whether I can help, and what it would take.