Software built, shipped, handed over.
Web apps, internal tools, MVPs, automations. Any stack the job needs, shipped to a fixed scope and a fixed price. A modern AI-assisted workflow under the hood means quicker MVPs, faster debugging, and the code stays clean.
Four shapes the work usually takes.
MVPs and prototypes
An idea, scoped and built to a working version in a couple of weeks. Honest enough to test on real users, simple enough to throw away if the answer is no.
Internal tools
The dashboard, the admin panel, the bulk-edit screen, the thing that replaces a sprawling spreadsheet. Built around how your team actually works.
Web apps and sites
Customer-facing apps and sites, from a single landing page to a multi-tenant product. Modern stack, sensible hosting, yours to take anywhere.
Automations and joins
Connect the tools you already pay for. AI assistants on your own documents. Inbox triage. The handoffs between systems so the manual work runs itself.
A call, a scope, a delivery.
We talk
Fifteen minutes on a call. You tell me what you need and what a good outcome looks like. Every call ends with a clear answer: a fixed price and timeline in writing, or a pointer to the right specialist for the job. You leave the call knowing what to do next.
I scope
Fixed price, fixed timeline, in writing within a few days. Everything spelled out: what you get, when you get it, what it runs on.
I deliver
Two to six weeks for builds. Same-day or same-week turnaround for support. You get a working answer and the docs to run with it.
What you get that you don't get elsewhere.
One person, start to finish
You email me, you call me, you get the work from me. No account manager, no rotating team, no handovers between sales and delivery. The person who quotes you is the person who does the work.
Fixed price, agreed before any work starts
The quote is the price. If the scope changes, you decide whether to extend it. No surprise invoices, no scope creep, no 'discovery phase' billing.
You own what I build
Code lives in your repo. Systems run on your hardware where you want them to. No subscription that holds your data hostage, no vendor lock-in.
A real answer in weeks, not quarters
Builds run two to six weeks. Support gets handled the same day or week. You see progress every few days, not at the end.
Quoted properly, in writing, before you commit.
Every project gets a fixed price for a fixed scope, in writing before you commit to anything. Smaller jobs scope quickly. Bigger ones get quoted properly after a short call.
Hardware, on-site labour, and any opted-in subscriptions sit alongside the fee in your quote, at cost. One total, every line visible, no surprises during the project.
If a scoping call shows the work would cost more than the value you'd get from it, I'll tell you. The point is to leave the call knowing what to do next.
Hi, I'm Kylam.
A developer based in Essex. I build computer vision systems for businesses that already have cameras, take on the dev work most studios are too big to bother with, and keep the kit running for the firms next door. Whatever you bring in, it goes from first email to handover with me, not a team.
I take a handful of projects at a time, so each gets real attention. I say yes when I know I can ship it well, and point you elsewhere when someone else is a better fit.
The things people ask before we start.
What stacks do you work in?
Whatever the job needs. TypeScript and Next.js for most web apps. Python for data, ML and automation. Node, Postgres, the usual cloud platforms. If your existing system is in something else, I work with that rather than forcing a rewrite.
What's the AI-assisted workflow you mention?
Modern AI tooling is part of how the code gets written, tested, and debugged. In practice that means MVPs land sooner, bugs are caught earlier, and less of your budget is spent on plumbing. The output is still real code I'm responsible for, reviewed and shipped properly.
How quickly can you ship an MVP?
Most prototypes land in two to four weeks from a signed scope. Bigger products scope longer; you get the timeline in writing before any work starts.
Do I own the code?
Yes. Code goes into your repo. You can run it, change it, hand it to another developer. No licensing strings, no vendor lock-in.
Do you maintain what you've built?
If you want me to. Ongoing changes and small fixes can sit on a retainer, or be paid by the hour. Or you can take the codebase and run it yourself; the docs are there to make that possible.
What if the project needs a designer or a specialist I don't have?
I'll bring one in or point you to someone I trust. You stay dealing with me; the specialists are stitched in behind the scenes.
Tell me what you need built.
A sentence is fine. Web app, internal tool, MVP, automation: send what you've got, I reply the same day, and you get a fixed price and timeline in writing.