Integrations
Connecting a client's tools so they talk to each other: payments, booking, mail, calendars and third party APIs.
DEVELOPER FOR HIRE
Automation, integrations and custom builds, delivered as yours. I build the technical work your projects need, in your name. You keep the client and the relationship. I stay invisible, ship on time, and never contact your clients directly.
Jatzo is mine, a SaaS cyber security company focused on email security and business email compromise (BEC). It scores an email for fraud out of a hundred and shows the evidence behind the number. Underneath that is a sophisticated detection engine with custom built rules, each one declared in a registry and tested, and every message is taken apart inside an isolated container with no network access. Around it is everything a real product needs and a demo never has: subscription billing that raises its own VAT invoices and credit notes on a sequence that cannot have gaps, signing in against a company's own staff directory, two step sign in with recovery codes, an add-in that works inside a mail client on a desktop and on a phone, team accounts with seats and roles, and a data export that has to account for every column in the database.
Invoice Guard is mine too. It reads the bank details off a supplier's invoice and checks them against what that supplier used last time, which is how a redirected payment gets stopped before it leaves. The details are sealed with AES-256-GCM under a key held in the machine's keychain and never in the database, and matching is done on keyed fingerprints, so finding a supplier never means decrypting the register.
Around six thousand tests run on every push, and a deploy is refused if one of them fails. That is the standard I will work to in your codebase.
WHAT I BUILD
Connecting a client's tools so they talk to each other: payments, booking, mail, calendars and third party APIs.
Replacing manual processes, including the ones where off the shelf automation tools have hit their limits.
Admin panels, reporting and the small applications a business runs on.
Python, APIs, databases, authentication and payments.
A new feature for something already live, or a working first version of a product.
Assistants and language model tools wired into a client's real systems rather than bolted on.
Multi factor and secure sign in, and email and website security done properly. I build security software for a living.
An extra pair of hands when you are stretched, or when a build has stalled and needs finishing.
HOW I WORK WITH AGENCIES
Delivered as yours. No branding, no credit, no claim on the work.
You keep the relationship end to end. I never approach your client.
A written estimate before anything starts, so there are no surprises.
You know where a build is without having to ask.
Whenever you want one.
Competitive day and hourly rates, or a fixed price per project. Happy to discuss what suits the job.
WHAT A TYPICAL JOB LOOKS LIKE
You send the brief, or the codebase and the problem. I come back with a written estimate: what I will build, what it will cost as a fixed price or a rate, and how long it will take. If there is anything in the brief that will not work as described, you hear that then rather than halfway through.
During the build you know where it is without having to chase me. At the end you get the work, the code and whatever notes your own team needs to keep running it. There is no lock in and nothing of mine is left in it.
QUESTIONS
Yes. Every engagement is white label by default. The work is delivered as yours, with no branding and no claim on it, and I am not named to your client unless you choose to name me.
No. You keep the relationship end to end. I work through you, and I do not approach your client directly at any point, during the build or afterwards.
A day rate, an hourly rate, or a fixed price for the whole project, whichever suits the job. Fixed price suits well defined work; a rate suits open ended or exploratory work. Either way you get a written estimate before anything starts.
Yes, whenever you want one, and before any detail of the project is discussed if you prefer.
That is a normal way to start. I pick up existing codebases and work to the stack and conventions already there rather than rewriting to suit myself.
Mostly Python and JavaScript, with SQL databases, REST APIs and the usual cloud tooling. I am comfortable picking up a codebase in something adjacent and working to it.
The United Kingdom, working remotely with agencies anywhere in the country.
A sentence about the job is enough to start. I will tell you whether it is something I can take and what it would cost.
United Kingdom, working remotely with agencies anywhere in the country.