Backend Systems · Integrations · Workflow Engineering · Azure
Got a technical problem that needs fixing? Let’s solve it.
Senior C#/.NET freelance developer, founder-led and 100% remote. Fixed-price quotes, agreed up front. I work with SMEs, startups, and direct buyers on backend systems, integrations, and workflow automation — without the overhead of a formal engagement.
Integration broken? Backend system needs urgent changes? Azure setup nobody understands? A manual process failing every month? I diagnose it, quote it clearly, and fix it — with a 30-day warranty on everything I deliver.
Free call — you leave with a clear assessment and a written quote. No commitment to proceed.
The work
Things I get asked to fix
- An integration that worked until the other side changed something.
- A backend change nobody on the team has time to make safely.
- An Azure setup configured by somebody who has since left.
- A manual process that fails once a month and is now somebody's job to babysit.
- A report that takes a day to produce and is wrong often enough to be argued about.
- A legacy Access or VBA tool that quietly became business-critical.
- An API that needs building, or one that needs consuming and does not behave.
If yours is not on the list, it is worth asking. The list is what recurs, not what is possible.
Related areas I am often asked about: production reliability, maintainability, operational systems, document processing and knowledge transfer.
The process
How this works
Typical first response within 1–2 working days.
Every time
What you get, every time
- A written scope before work starts. Not a proposal document. A list of what will be true when it is finished.
- The source code, yours to keep. Committed to your repository or delivered at handover, yours to keep, modify or share. There is no licence fee for continued use of code I wrote for you.
- A thirty-day defect warranty. If it does not do what the scope said, I fix it.
- Enough documentation to run it without me. Not an architecture handbook. The things somebody would need at two in the morning.
Pricing
How pricing works
For clearly bounded work, I normally quote a fixed price against a written scope, so you know the cost before the work starts. That suits most of the list above: a rate tells you what an hour costs, not what the job costs, and for a bounded fix those two numbers are not related in a useful way.
There is no rate card, because the price depends on scope. If your work is better suited to a different arrangement, say so on the call and we will work out what fits.
The quote comes after the call, so it is a number about your problem rather than a number about my availability. If the scope changes, we agree a new number before anything is done, not afterwards.
Evidence
Three jobs, delivered and still running
Chosen for delivery rather than for architecture: bounded work, finished and handed over.
Working with your team
Joining work that already exists
Most of what I am asked to do is not a clean start. It is a codebase with history, a team with conventions, and a deployment process that somebody built in a hurry and that everybody now depends on.
That is fine, and it is most of the skill. I read before I write. I follow the conventions already in the repository rather than importing my own. I keep changes small and single-purpose so they can be reviewed by someone who was not in the conversation. If I disagree with how something is done, I will say so once, in the pull request, and then I will do it your way unless it is actually unsafe.
Handover
What happens when I finish
I leave, and things keep working. That is the whole test.
Concretely: the code is merged and deployed, the documentation is in the repository rather than in an email, anything I automated has a way to be turned off, and there is a thirty-day window where defects are my problem. If you want a handover call with whoever picks it up, that is included.
Current availability is published on the availability page and comes from my actual calendar rather than from a form I remember to update.
Common questions
What people ask before getting started
Straight answers to the questions that come up on almost every first call.
Is there a minimum engagement size?
No. There is no minimum engagement. Small, well-defined problems are quoted and fixed just like larger ones. Written scope and fee are agreed before work starts — you will never receive an unexpectedly large invoice.
What does it cost?
Most work is quoted as a fixed price against a written scope, agreed after a short discovery call. There is no rate card — the exact price depends on the nature and expected duration of the engagement. A written estimate is provided before work begins.
VAT is charged at the standard rate — VAT no. 514295790.
How quickly can you start?
A discovery call can usually be booked within 1–2 working days. Current availability is shown on the availability page. I will confirm the earliest start date on the call.
Is my job too small?
No. Small, well-defined problems are often the easiest to scope and fix. If something is genuinely trivial, I will tell you that on the call and give you a clear picture of the work involved. I do not artificially inflate scope.
If I think the problem is outside my area or better handled differently, I will tell you that too — the call is free regardless of the outcome.
Do I need a formal contract?
A written scope confirmation is required before work starts — this protects both parties. For most short engagements this is a simple email exchange confirming deliverables, fee, and timeline. For larger projects a formal statement of work is more appropriate and I can produce one.
I work under my own standard terms, which are available on request before you commit to anything.
What if I don’t know exactly what the problem is?
That is fine — describe the symptom, not the diagnosis. “The API stops working every Tuesday morning” is enough to start with. I will ask the right questions on the call and give you a clear picture of what is likely causing it.
If investigation is needed before a fix can be scoped, that investigation is scoped and quoted separately — so you have a decision point before committing to the full fix.
Can you work inside our existing tools?
Yes. I can work directly inside your Azure subscription, GitHub or Azure DevOps repositories, and join your Microsoft Teams tenant as a federated guest. I integrate into your existing tools and workflow — no new platforms required.
What if the problem turns out to be bigger than expected?
If scope changes once work has started, I raise a written change request before any additional work begins. This covers what changed, the extra effort needed, and the revised cost and timeline. Nothing proceeds without your written agreement — no surprises.
More questions? Get in touch directly or see the full FAQ.
Got a problem? Let’s look at it.
A free 20-minute call to understand what’s happening. You leave with a clear assessment, a written quote, and the option to proceed or walk away — no commitment either way.
No minimum engagement. No sales pitch. Just a clear picture of the problem and what fixing it involves.
- Clear assessment of the problem
- Written quote with no surprises
- Option to proceed or walk away
- No minimum commitment
- Fixed-price quote
- Written scope before work starts
- 30-day defect warranty
- Full source code and documentation
- 100% remote delivery, UK business hours
- VAT registered — no. 514295790
Prefer to start in writing? Send a brief description of your situation and I’ll come back within 1–2 working days.