Engagements scope from single tools to multi-month builds. Everything is delivered with documentation, a clear support model, and a written scope you can hand to a finance team.
Senior-level Apex, LWC, Flow, and integration work for mid-market orgs that need engineering depth without the cost of a full hire. This is the day-job specialism carried into the practice: estate-scale habits applied to your org, whatever its size.
Recent work includes Lightning Out 2.0 embeds into external TypeScript applications via OAuth Authorization Code and Frontdoor URLs: the kind of integration where the documentation runs out and engineering judgement takes over.
Bespoke pipelines wiring Claude, Claude Code, n8n, and custom C# services into systems that actually do work for you. Multi-agent orchestration, state machines, sliding-window review loops, versioned outputs. Built to run unattended, not to demo.
The house test for agentic systems is simple: would you let it commit to git while you sleep? Ours do.
Engineering for retail algorithmic systems, scoped carefully and built FCA-aware. Multi-layer risk stacks, broker-side stop-losses, weekend gap handling, AI-assisted signal validation. Sold as engineering rigour; not financial advice, not signals.
Privacy-first desktop applications for Windows, built the WorkRecap way: data stays on the machine, transcription and AI run locally where the problem allows, and encryption is bound to the user's own login.
This is the newest pillar, proven by shipping WorkRecap. The same architecture (local pipelines, offline AI options, licensing and update infrastructure) is available for bespoke builds where the data is too sensitive for someone else's cloud.
Home Assistant integrations, voice assistants, IoT segmentation, Raspberry Pi satellites, Telegram bots, Docker-hosted brains. For people who want more than off-the-shelf smart home, and who care that it stays local-first.
The same shape every time, scaled to the size of the job. No stage is skipped for small work; small work deserves scope too.
You email what you're trying to do. If it's not a fit, you'll be told quickly and pointed somewhere better. If it is, we arrange a call to understand the problem properly.
A proposal in plain English: what's being built, what's explicitly out of scope, what it costs, and what "done" means. You can hand it to a finance team or a sceptical spouse.
Progress notes as work lands, honest flags when something turns out harder than scoped, and no surprise invoices. Threat models and design notes are written before the interesting code.
Documentation, credentials handed back, a support model in writing, and a rollback path. If it can't be supported, it doesn't ship, so what ships, you can live with.
Describe it in an email. You'll get an honest answer about whether this is the right shop, and a pointer elsewhere if it isn't.